Fixed Price AI Consulting Quote: How to Scope It and Protect Your Margin

BOTrento Team18 October 20266 min read

Why fixed price AI work goes wrong

Most margin loss does not come from the work itself. It comes from three gaps in the quote:

• A vague outcome. “Build an AI assistant for sales” can mean a prototype, a tested workflow or a trained team.
• Unknown inputs. Data turns out to be messy, incomplete or locked in someone's inbox.
• Open-ended review. Feedback rounds continue until the client is happy, with no limit.

A fixed price is only safe when each of these is bounded in writing. If you cannot bound one, either split the work into a paid discovery step or quote it as time and materials.

Step by step: scope the quote before you price it

1. Write the outcome in one sentence. Describe what exists at the end, for example: “A documented workflow that drafts first replies to inbound enquiries, tested on your last batch of enquiries.”
2. List deliverables. Documents, configured tools, training sessions, a handover call. Each should be something you can hand over and the client can check.
3. List client inputs and deadlines. Data exports, access, a named decision-maker, feedback within an agreed number of working days.
4. Set acceptance criteria. How does the client confirm it is done? A test on a sample, a walkthrough, a checklist.
5. Limit the review rounds. One or two rounds is common. State what happens after that.
6. List exclusions. Be explicit about what is not included.
7. Price the scope, then add a buffer for the unknowns you could not remove.

If you need a general skeleton for the document itself, the service quote template covers summary, scope, itemised price, validity and next step.

Exclusions and assumptions that matter in AI projects

Assumptions say what must be true for the price to hold. Exclusions say what you will not do. Both should be short and specific.

Assumptions to consider

• The client provides data in a usable format by an agreed date.
• Access to systems and mailboxes is granted before work starts.
• One person can approve decisions on the client side.
• Any third-party AI usage costs are paid by the client directly.

Exclusions to consider

• Cleaning or restructuring the client's data beyond a stated sample.
• Integration with systems not named in the quote.
• Ongoing support after handover, unless priced separately.
• Legal review of data protection or AI obligations. Recommend the client takes advice from a lawyer for their specific case.

For before-and-after phrasings that remove ambiguity, see quote wording for scope, exclusions and assumptions.

Copy-ready wording for scope and change requests

Adapt this to your own project:

Outcome: A documented enquiry-reply workflow, configured and tested on a sample of your recent enquiries.
Included: One kickoff call, one workshop, one configured workflow, one handover session, two review rounds.
Not included: Data cleaning beyond the agreed sample, integrations not listed above, support after handover.
Assumptions: You provide the sample data and system access by the date agreed at kickoff, and feedback is returned within five working days.
Changes: Anything outside this scope is quoted separately as a written change request. Work on it starts only after you approve it. If a delay on your side moves the timeline, the delivery date moves with it.

When the client does change the brief, send a clear updated offer. The revised quote email templates show how to name the new version and say what it replaces.

Pricing choices that protect margin

Split into phases

A short paid discovery phase turns unknowns into facts. Then you can fix the price of the build with far less risk.

Offer options, not open scope

Present a core package and optional extras. The client chooses; you do not absorb extras by default.

Tie payment to milestones

Link invoices to deliverables, not to calendar dates alone. That keeps cash flow steady if the client is slow with inputs.

Keep a record of what you quoted

Version every quote and keep the latest one visible, so nobody works from an old scope. A quote structure and pre-send checklist helps you catch missing assumptions before the document leaves.

How BOTrento helps you keep quotes under control

Writing the quote is half of it. The other half is not losing it: the enquiry that arrives on Friday, the promise to “send a proposal by Wednesday”, the follow-up nobody remembers.

BOTrento Chief of Staff is a managed process for enquiries and quotes. It watches enquiries in your mailbox and uploaded data, shows a daily overview each working day morning, catches promises such as “I'll get back to you by Friday” and reminds you. It prepares draft replies, quotes and follow-ups in four languages. Nothing is sent without a person approving it, and BOTrento does not send anything by itself. It does not replace your CRM or accounting, and it does not read attachments, only the text of the email.

AI use is included in the plan within a monthly usage limit. You can see how it works in the process demo. For consultancies, B2B services is the most relevant starting point.

The trial is 14 days free, with no card and no API key of your own. The 14 days start with your first successful data upload, and you have 7 days to prepare. After it ends you keep read-only access and export for 30 days. Try it on your own data. We make no promise about revenue or number of deals; that is why you test it first.