Questions to ask a client before accepting an AI engagement
5 minute read. Updated 2026-08-08.
Before accepting an AI engagement, ask who owns the decision if it fails, what happened to the last person who tried this, whether the budget is signed off or still being argued for internally, and whether you can see a sample of the data before quoting. These questions feel rude. They are the ones that surface a doomed project before you have spent two weeks confirming it yourself.
Qualification is not optional
Most doomed AI engagements were doomed before the contract was signed. The client had no real budget owner, the data did not exist in the form described, or the sponsor had already decided the answer and wanted a consultant to confirm it. None of this shows up in a scope document. It shows up if you ask.
A freelancer who skips qualification because it feels awkward to interrogate a prospective client ends up doing the interrogation anyway, three weeks in, unpaid, while trying to explain to a sceptical stakeholder why the timeline has slipped.
Questions about the decision
Who signs off the go or no-go, and what happens if the recommendation is not to build anything. If nobody can answer the second half, the client has already decided the outcome and is buying validation, not judgement.
What happened to the last attempt at something like this. Most organisations that want AI now have tried something adjacent already and quietly parked it. Asking what happened and why reveals the real constraints far better than any written brief will.
Who loses if this fails. If the honest answer is nobody, in particular, the project has no real sponsor, and it will be the first thing cut when priorities shift six months in.
Questions that feel rude and are not
Can I see a sample of the data before I quote. Clients sometimes treat this as presumptuous. It is the opposite: quoting without seeing the data is guessing, and a guess dressed as a fee is worse for both sides than an honest ask up front.
Is the budget already approved, or are you still building the internal case. This gets treated as none of your business. It is entirely your business, because the second answer means the real decision-maker is a finance committee you have not met, not the person sitting across the table.
Has anyone told the people whose jobs touch this that it is happening. If the answer is no, you are about to become the person who breaks that news, which is a materially different job to the one described in the brief.
Questions about access and constraints
Who has to say yes before I can see production data or systems, and how long has that approval taken on other projects here. An answer measured in months tells you the engagement's real timeline before the contract does.
Is there an existing AI or data initiative I would be replacing, extending, or quietly competing with internally. Overlap with a parallel effort, often run by an internal team defending its own budget, is a common and rarely volunteered cause of stalled work.
Questions about status and terms
Has an IR35 determination been made for this engagement, and can I see it. Since April 2021, medium and large private-sector clients make this determination, not the contractor, and a vague answer here becomes a tax problem later, not a contract problem now.
Ask plainly what day rate range the client has in mind before spending time on a full proposal. Clients researching the market will likely have seen the median Artificial Intelligence contract rate of £551 a day advertised over the six months to August 2026; if their figure sits well under that with no explanation offered, find out why before investing more time.
What to do with the answers
None of these questions is a trap designed to catch the client out. They are the same questions a good client wants answered before committing budget, because an engagement that fails wastes their time as much as yours.
If two or more answers are evasive rather than simply unclear, treat that as data rather than bad luck. Decline politely, or price the risk into the fee, but do not proceed on the assumption that clarity will arrive once the contract is signed. It rarely does.
What to do about it
- Ask who signs off the decision and what happens if the answer is not to build it.
- Ask what happened to the last attempt at this before scoping the new one.
- Ask to see a sample of the data before quoting, not after.
- Ask whether the budget is approved or still being argued for internally.
- Ask whether an IR35 determination exists and read it before signing anything.
- Treat evasive answers as information, not as an unlucky first meeting.
Questions people also ask
Isn't it risky to ask about budget approval before I've even proposed anything?
It is riskier not to. A prospective client still building an internal business case is not yet able to commission you, whatever they say in the first meeting. Asking directly saves both sides weeks. Most clients respect the question, because it shows you have run engagements before and know where they typically stall.
How do I ask to see the data without sounding like I don't trust the client?
Frame it as normal practice, not suspicion: I price data work by what I actually find, not by what the brief describes, so I would like a sample before I quote. That is true, and it places the reason on your method rather than on any doubt about their systems.
What if the client won't discuss why a previous attempt failed?
The refusal is itself the answer. It usually means the failure is politically sensitive, which means your engagement will be read against it whether anyone says so or not. Proceed if you choose, but price in the extra care that navigating that history is going to require.
Should I ask these questions on the call or in writing?
Ask the direct ones, decision ownership, sponsor, prior attempts, on the call, where tone softens a pointed question. Save written qualification, like requesting a data sample or the IR35 determination document, for a follow-up email, where the same question reads as process rather than interrogation.
Where the figures come from
Every rate and salary quoted in this article is a median or percentile of figures advertised in UK job postings over the six months to 8 August 2026. They are not rates paid, and the gap widens at the top of a range.
- IT Jobs Watch, UK contract rates, 6 months to 8 August 2026, read 2026-08-08.
- IT Jobs Watch, UK permanent salaries, 6 months to 8 August 2026, read 2026-08-08.