People delay contacting a consultant because they feel unready: no spec, no requirements document, no diagram. Good news: consultants who require a spec from you are outsourcing the hardest part of their own job. The discovery is the work.

That said, preparation multiplies the value of every conversation. The useful preparation is not technical. It is six things you already know, written down plainly.

1. The pain, described as a story

Not "we need an inventory system." Instead: "Every Monday, Dana exports three reports, merges them in a spreadsheet, and flags reorders by eye. It takes half a day and mistakes reach the shelf." A story like that contains the workflow, the people, the frequency, and the failure mode. It is worth ten pages of requirements.

2. The tools you already use

A plain list: POS, accounting, e-commerce, loyalty, marketing, chat, and the spreadsheets that glue them together. Note which ones you like. A good consultant designs around what already works, and the list determines what can be integrated versus replaced.

3. Who touches the process

Names and roles for everyone in the workflow, plus one thing each of them complains about. The people doing the work know where the bodies are buried, and a system designed without them gets quietly rejected in month two.

4. What "better" means, in numbers you care about

Hours saved, errors eliminated, faster response to customers, questions you wish you could answer instantly. It does not need to be precise. "Dana gets Monday back" is a measurable outcome. This is also your defense against scope creep later: features either serve the stated better or they wait.

5. Your constraints, stated early

  • Budget shape: even a range changes the recommendation honestly. Small budgets produce different good answers, not just smaller ones.
  • Timing: seasonality, launches, staff changes that a rollout must respect.
  • Data boundaries: anything that must not leave your control, especially in regulated industries.

6. The graveyard

What has been tried before, and how it died. The abandoned SaaS subscription, the cousin who built a database in 2021, the automation nobody trusted. Every graveyard entry is a requirement in disguise: it tells the consultant what your operation rejects.

What to expect back

Given those six things, a competent consultant should give you, within a call or two: a plain-language read on what is worth building, a recommended smallest first step, an honest range for it, and at least one thing you can improve without paying anyone. If what you get instead is a big proposal and a bigger invoice before understanding, keep looking.

Have your six answers ready?

Bring them to a thirty-minute call and we will turn them into an honest recommendation.

Discuss Your Project