Comparison
How do you tell a real AI consultant from a grifter?
Ignore fluency and ask for artefacts. A real AI consultant shows the mechanism, names the limits, prices first and hands over what your team can run.
By the Foxnut team · Updated
How do you tell a real AI consultant from a grifter?
You tell a real AI consultant from a grifter by ignoring fluency and asking for artefacts. A real practice can show you the mechanism behind a claim, name what a system cannot do, price before building, and hand over something your team can run without them. A grift produces vocabulary, urgency and certainty, all cheaper to manufacture than evidence.
Disclosure: we are Foxnut AI, a senior-only AI consultancy in Bengaluru and Paris, so we are one of the people you are vetting. That is precisely the problem with this genre, because buyers asking this question get their answers almost exclusively from the people being vetted. There’s a link to talk to us at the end of this article. Let’s first give you checks concrete enough to turn on any author, including us.
What questions should you ask an AI consultant?
Ask how the system works, what evidence they have, where the approach fails, what a defined piece costs, what they have refused, and what you keep after they leave. These are the axes buyers themselves used after being burned, in the practitioner accounts we read. The table shows what each answer looks like from a real practice and from theatre.
| Signal | From a real practice | From theatre |
|---|---|---|
| The “how” | Names the mechanism in plain terms: what the model reads, what it produces, where the checks sit | ”Intelligent algorithms” and category buzzwords, with no answer beneath the second question |
| Evidence | Specific and modest: a named workflow, a measured result, what went wrong on the way | Round numbers, transformation stories, and results that are always someone else’s |
| Scope | Tells you where the approach fails and which problems it should not be pointed at | Everything is a fit; every failure mode has a workaround, priced later |
| Price | Can say what a defined piece costs before building it | Discovery first, and the discovery recommends more discovery |
| Refusal | Has turned work away, and can say what it refuses on principle | Has never met a brief it could not serve |
| After exit | Hands over prompts, tests and a runbook your team runs alone | A system only the vendor can safely touch, and a renewal conversation |
The last row is the one Foxnut AI’s AI consulting territory exists for. What a consultant leaves behind is the cheapest check to state and the most expensive to fake, because what a complete AI handover includes is a concrete artefact list you can put in the contract before anyone starts.
What kind of help should you choose?
Choose by where the hard part sits, because filtering out grifters still leaves a real choice between kinds of legitimate help. Each has situations it genuinely wins, and a failure mode the others do not.
When does a specialist consultant win?
A specialist consultant wins when the question comes before the system. If the problem is not yet defined, meaning which workflow, whether AI belongs in it at all, and what the measurable outcome would be, a small senior practice earns its fee by judgment and by handing the result over.
Its failure mode is scale. It cannot staff a large build, and a real one says so at the first call and does not subcontract quietly.
When does a delivery agency win?
A delivery agency wins when the build is the hard part. If the workflow is defined and the work is engineering volume, meaning integrations, infrastructure and many hands over many months, an agency or systems integrator with a bench is the correct buy, and good ones do this well and repeatably.
The category’s failure mode is inherited scoping. An agency is structurally paid to build what the brief says, and a weak brief gets built as written. The checks in the table apply unchanged, and the good agencies pass them.
What if your brief is just “we need AI”?
Nobody wins when the brief is a slogan. If the brief is “we need AI” with no named workflow and no number attached, hiring anyone converts a vague anxiety into a confident invoice. Practitioner accounts are blunt that this is where most wasted AI spend starts.
The failure mode of hiring nobody is drift, so the question deserves an owner inside your company. A self-run readiness check is our version of that test, and it is free.
What qualifications should an AI consultant have?
No qualification proves much, because credentials are the weakest signal on the list, even though vetting guides fixate on them. There is no licence for this work. Certificates measure course completion, not judgment, and the loudest vocabulary in the field changes faster than any curriculum.
The practitioner accounts offer the GDPR consulting wave as an analogue. When a rule or technology is new, the confident-sounding interpretation sells best precisely because nobody can check it yet. The durable check is the one that worked then too: make the seller show their reasoning on your case, in your terms, and watch whether they name limits without being pushed.
If you apply the table above and get artefacts, mechanisms and refusals, you can safely ignore the plaques. How we answer these same checks is written down plainly in how the studio itself works - who does the work, what it refuses, how fast it responds, which is this page’s own test applied to its author.
Do we pass these checks ourselves?
You should judge that yourself, and here is the evidence against our own interest, from our intake. A small industrial machinery manufacturer in Texas asked us to deploy AI for tracking their working capital. Our advice was not to use AI at all, because it would have been unnecessary overkill, and to buy a one-time-licence software that met every requirement at a fraction of the cost. That advice was the whole engagement.
At Foxnut AI there is one tier, so the person who gives you that kind of advice is the person who would do the build. We designed, made and launched our own products before we advised anyone, and we hand what we build over to your team.
When a buyer asks us to prove we are real, the answer is a working session, not a credential. We get on a call and demonstrate our proof of work live: the systems we have built, shown running. Ask to see it. Book the call.
The part most pages leave out
When not to choose Foxnut AI
Situations where another option is the better call, and where we say so in the first conversation rather than the fourth.
- The work is execution volume: a large system built and integrated by many hands, on infrastructure a two-person studio cannot staff. An engineering agency or systems integrator with a delivery bench. That category is full of real firms doing real work, and this page's checks apply to them exactly as written.
- You need an audit, certification or compliance opinion on an AI system, for a regulator, an insurer or your own counsel. Accredited auditors and licensed professionals. A commercial consultancy's view is not a compliance artefact, and a real consultancy will say so unprompted.
- You already know the workflow and just want a tool recommendation. Your own team, running two trials for a week. Paying consulting rates for a product pick is exactly the purchase this page is trying to talk you out of.
- Procurement requires named client case studies in your category before anyone signs. A firm with a public client list. We have no publishable named client case study yet, and it is better said here than discovered in procurement.
Foxnut AI takes on work like this from Bengaluru and Paris. If you want to see how we do it before you talk to anyone, here is what an AI engagement covers and what you keep.