What should be in an AI project proposal?
A good AI project proposal names one specific job, the hours it takes today, what done looks like, who approves the output, what stays under your control, and how the price is set. If it describes tools and technology before the job, be wary.
What should an AI project proposal contain?
Seven things, in this order. If any is missing, ask for it before you agree.
- The job. One real task, described the way the person who does it would describe it. "Weekly customer updates" is a job. "Improve efficiency with AI" is not.
- The hours today. How long the job takes now, per person, per week. This is what the benefit gets measured against.
- What "done" means. A test you could check yourself, such as "a draft proposal in our format appears within ten minutes of the call notes being saved".
- Who approves the output. The person who owns the job should approve it before anything goes live or goes out.
- What you own and control. Whose accounts it runs on, what happens if the supplier disappears, and whether anything routes through their systems.
- What happens after handover. Documentation in plain English, a fixed period to fix snags, and what ongoing support costs.
- The price terms. A fixed price agreed before work starts, or a clear cap. Open-ended day rates on a vague brief are how projects overrun.
What should make me suspicious?
- Technology before the job. A proposal that opens with models, platforms and architecture and never names a task someone does today.
- A report instead of a result. An audit gives you a document about what could be automated. A build gives you the thing itself, running on real work. Both have a place, but know which one you are buying.
- No stated way to say no. A good proposal should include the outcome where the sums do not work and the project should not go ahead.
- Vague ownership. If you cannot say who owns the finished system, ask.
How do I write one myself?
If you are the buyer writing a brief, use the same seven headings and fill in what you know. Time the job for a normal week first; Is AI worth it for a business with fewer than 20 staff? shows how. Then ask suppliers to respond under the same headings, so you can compare like with like.
How do I work, as an example?
My own process follows this shape, so you can see it in practice. It starts with a free 30-minute call. I sit with whoever does the work, we find the hours and do the maths together, and if it will not clearly pay for itself I will say so. A fixed price and what "done" means are agreed before any work starts. It is built and tried on real work, and nothing goes live until the person who owns that job approves it. It is handed over working, with a plain-English handover and a 30-day snag window. You own the system outright.
I also build the proposal step itself: your call notes become a branded proposal, ready to check and send, typically giving back about 5 hours a week per person doing that job.
Questions people also ask
Should I get an AI audit or just build something?
An audit gives you a report on what could be automated. A build gives you one job done and running. If you already know the painful job, build it. If you have no idea where to start, a short conversation about where the hours go is usually enough.
Should I train my team or hire someone to build it?
Train the team when the work varies and people need to use AI themselves every day. Hire a builder when one repeated job is worth automating end to end. The two also combine: train people first, then build the one job worth automating.
How long should an AI project take?
It depends on the job, so be wary of a firm answer before anyone has looked at the work. Ask for the timeline in the proposal, tied to the "done" test, and for what happens if it slips.
Who should own the finished system?
You should. Ask that it runs on your own accounts and stays under your control, with nothing routing through the supplier's systems after handover.
See it working
Things I've built that do this, and the time they give back.
Proposals from your notes
Your call notes become a branded proposal, ready for you to check and send.
Typically 5 hrs a week per person
See how it works →