The same consultant produces wildly different results for different clients, and the difference is mostly preparation on the client's side. Five things to do before the engagement starts — none of them take more than an afternoon.
1. Write the one-sentence problem statement
"We lose roughly 15 enquiries a month because nobody follows up within a day" briefs a consultant infinitely better than "our sales process needs work." The number can be an estimate; the specificity is the point. If you genuinely can't produce this sentence, say exactly that — "we can't tell where the problem is" is itself a well-defined diagnostic brief.
2. Gather the real numbers, ugly as they are
Revenue by month, leads by source, hours spent on the suspect process, tool subscriptions actually in use. An engagement that starts with two weeks of the consultant chasing basic data is an engagement where you paid consulting rates for data entry. A folder of exports beats a polished deck — polish hides things.
3. Name one internal owner with real authority
Not a committee, not "whoever's free." One person who attends every session, can make decisions between sessions, and will own the system after handoff. This is the strongest predictor of whether recommendations become reality: advice delivered into a vacuum stays advice. If nobody can spare the time to own the engagement, the business isn't ready for it yet — see AI Consulting Myths vs Facts for how "an owner, a process, and a follow-up date" separates value from theatre.
4. Give honest access, not a tour
Let the consultant talk to the person who actually runs the process — not just the manager who describes it — and resist tidying anything first. The workarounds, the spreadsheet nobody admits to, the step everyone skips: that's the diagnostic material. Businesses that stage-manage the engagement get recommendations for the business they pretended to be.
5. Define "done" before signing
A specific capability or number: "the team logs every deal in the CRM without reminders," "response time under one hour," "reporting takes ten minutes, not a day." Insist it appears in the proposal. A defined finish protects both sides — you from an engagement that drifts, the consultant from goalposts that move. This is exactly why our own process runs on fixed scopes and milestone boundaries — see How We Work.
The honest recommendation
Do steps 1 and 3 at minimum — the problem sentence and the owner. Those two alone put you ahead of most engagements we've seen, and they cost nothing but honesty. If you've picked your consultant already, How Much Does AI Consulting Cost? is the sanity-check for the quote; if you haven't, start with the questions worth asking before any contract is signed.
Frequently asked questions
What's the single highest-impact preparation step?
Naming one internal owner with real authority who attends every session. Engagements without an internal owner produce recommendations that nobody implements — the most common way consulting fees get wasted has nothing to do with the consultant.
Should we clean up our data/process before the consultant arrives?
No — resist the urge to tidy. The consultant needs to see how things actually work, including the workarounds and the mess. Cleaning up first is like tidying symptoms before a doctor's visit; it hides exactly what they need to diagnose.
How do we know if the engagement worked?
You wrote down what 'done' means before it started — a specific number or capability, not a feeling. If you didn't define it up front, you'll be arguing about it at the end. Insist the definition of done appears in the proposal.
Yash
Founder & Principal Consultant, Ynexgen
Yash leads Ynexgen, helping small and mid-sized businesses turn technology into a stronger foundation for growth — 7+ years across Salesforce CRM, websites, and AI adoption.
