What a Consultant's Answers Reveal: Read the Answer, Not the Question

When you ask an AI consultant a question, the real information isn’t in the answer itself — it’s in how the answer is built. A clear answer proceeds step by step, states its margin of uncertainty openly, and stays specific about timeline and price. An evasive answer, by contrast, is padded with generic phrases, spreads responsibility around, and never ties itself to a number or a sequence. This page puts two different answers to the same question side by side and walks through, line by line, what each one actually means through its tone and structure.

The Structural Difference Between a Clear Answer and an Evasive One

I put together the questions you should ask on this page; here I’m covering how to read the answers you get back. Put the two answer types side by side and the difference shows up immediately. An evasive answer works like this: sentences like “we’ll probably handle it,” “we usually get good results,” “we’re experienced in this” don’t tie to anything concrete — no step, no sequence, no metric. A clear answer does the opposite: it follows a concrete sequence, like “First I’ll map out your current campaign structure, then I’ll check the conversion data, and in the third step I’ll rebuild the budget allocation.” The difference here isn’t optimism, it’s traceability. A clear answer can still turn out wrong, but you can see at which step it went wrong; an evasive answer, when it turns out wrong, feels like nothing was ever said — because nothing was.

The Consultant Who Says ‘I’ vs. the One Who Says ‘We Usually Do It This Way’

“I” isn’t inherently more sincere than “we” — but the two carry different information. A sentence like “I ran into exactly this problem on an e-commerce account last month, and here’s what I did” points to a personal experience and is grounded in a verifiable event. “We usually do it this way” is often part of a rehearsed sales pitch — especially when no concrete example follows it. Using “we” on its own isn’t a bad sign; some consultants genuinely work as a team. The real test is whether a date, a number, or a verifiable detail follows the sentence. If detail follows, there’s real experience behind it; if it doesn’t, the sentence might just be a repeated template.

The Risk of an Answer That Comes Too Fast

An answer to a complex, situation-specific question that arrives in seconds, without any hesitation, feels reassuring — but it should actually be read carefully. Such an answer is often a pre-built template repeated identically to every client — given before the question was really listened to. By contrast, a consultant who says “hold on, to answer this properly I need to know: how many months has your campaign been live, how clean is your conversion data” shows that they’ll build the answer around your specific situation. That’s not a weakness — it’s actually a trust signal. For simple, repeated questions (like a pricing model), a fast answer is normal; the real warning sign is giving the same rehearsed lines to a complex question, with no distinction made at all.

How Specific the Answer to Price and Timeline Questions Is

Price and timeline questions are the best litmus test for a consultant’s overall reliability. “It depends, we’ll see” can sometimes be a fair answer in a first conversation, because the scope isn’t clear yet — but left on its own, it says nothing. “I can’t give you an exact figure without narrowing the scope, but similar projects usually land in this range, and if you give me this information I can narrow it down further” still doesn’t give you an exact number, but it offers a clear method. That’s the difference: uncertainty is acceptable, lack of method isn’t. A consultant who, under no circumstances, ever offers a framework, a range, or a next step on timeline and price has probably not correctly assessed the scope of the work from the start.

An Observation From the Field

One of the questions I get asked most often is “how soon will we see results.” I know the evasive answer: saying “you’ll see it in a few weeks” brushes the question off, and the client is still waiting six months later. Instead I say: “The first 2 weeks are data collection and structure-building; you’ll see the real impact in weeks 4–6, once the campaign has finished its learning phase — if I gave you an earlier number, I’d be lying.” This answer sometimes disappoints the client because I’m not saying “it’ll be sorted tomorrow.” But that’s exactly why it works: something real actually happens on the date I named, and I’m not coming back three months later saying “actually, it takes longer than that.” What you’re looking for when reading a consultant’s answer isn’t optimism — it’s this kind of consistency.

You Can Ask Me for This Work

If you’ve received a proposal and you’re not sure which category the answers fall into, a second pair of eyes helps. We can go through the proposal text or the meeting notes you send me together and work out what’s specific and what’s evasive. This is typically a 2-hour to 2-week job, remote, billed hourly. For details and booking, see the AI consulting page.

Frequently Asked Questions

Is a very short answer from a consultant a bad sign?

No, brevity alone isn’t bad. “Yes, we typically set that up in 3 weeks using method X” is short but specific, and it’s a good answer. The problem isn’t shortness — it’s emptiness: sentences like “We’ll handle it, don’t worry” are just as short but carry no information at all. When evaluating an answer, don’t look at its length — look at how many verifiable details it contains.

If a consultant always says ‘we,’ does that mean they have a team?

Not always. Some solo consultants say “we” to sound more corporate, while some real teams say “I” and put the speaker front and center. “We” on its own isn’t a signal; the real signal is whether a concrete date, number, or event follows the sentence. If it does, there’s real experience behind it; if not, the sentence is probably a rehearsed template.

Is a fast answer always a bad sign?

No. For frequently asked questions like a pricing model or working process, a fast, clear answer is normal, because the consultant has already answered that question dozens of times before. What you should actually watch for is a complex, situation-specific question getting the same speed and the same rehearsed lines — that can be a sign the question wasn’t really listened to.

Should I avoid a consultant who won’t give an exact price or timeline?

Not on its own, no. Not giving an exact figure in a first conversation is normal, because the scope isn’t clear yet. The real distinction is this: a consultant who says “I don’t know, we’ll see” is not the same as one who says “if you give me this information I can give you a range, and I’ll finalize it once the scope is clear.” The second still doesn’t give you an exact number, but it offers a clear method — and that’s what you should actually be looking for.