Key takeaways
- An RFP earns its cost when you are comparing several firms for a project big enough to justify the process, not as a default for every purchase.
- Nine sections, background, workflow, systems, constraints, what you want back, evaluation criteria, timeline, commercial format and submission instructions, cover what a partner needs to quote responsibly.
- Group vendor questions so every firm answers in a structure you can score, then rate the answers as a team rather than after the most persuasive call.
- Weight the criteria that matter for your project, score each vendor answer from no evidence to strong, and let the total drive the shortlist rather than which proposal reads best.
- Run the process fairly: the same information to every bidder, a public question window, and a working session on real data before you decide.
A request for proposal earns its cost when you need to compare several AI implementation partners on the same basis, for a project large enough that a bad match is expensive. It earns nothing when it becomes a formality: twenty pages of boilerplate questions that every vendor answers the same way, while the one thing that predicts whether the engagement works, whether the firm understands your workflow before naming a technology, never gets asked directly. This piece sets out what to put in an AI RFP, the questions worth asking every bidder, and how to score what comes back.
When does an RFP help, and when is something lighter better?
An RFP is the right tool when you are comparing three or more firms for a project above your normal procurement threshold, when more than one internal stakeholder has to sign off, or when your organization needs a documented, defensible process. It is the wrong tool when you already trust one or two firms and want to move quickly, when the workflow is narrow enough that a scoped conversation covers it, or when you do not yet know enough about your own process to write firm requirements.
That last case is common, and worth naming plainly. If you cannot describe the workflow's steps, the systems it touches and where it breaks down today, an RFP will not close that gap, it will distribute it to every bidder, who will each guess differently and hand back proposals that cannot be compared. Write a requirements brief first, or hold a paid discovery conversation with one or two candidates, then write the RFP once you know what you are actually asking for.
The same discipline shows up in federal guidance. The U.S. General Services Administration's resource guide for generative AI acquisition includes recommendations on using testbeds and sandboxes before committing to large scale buys, and introduces questions contracting officers should ask to make informed procurement decisions (GSA). The same logic applies at a smaller scale: a short paid pilot with your top two bidders often tells you more than either written proposal does.
| Situation | Better approach |
|---|---|
| Comparing three or more firms for a project above your procurement threshold | A formal RFP |
| You already trust one or two firms and want a fast start | A direct conversation and a paid discovery or audit |
| The workflow, systems or data involved are still unclear | A requirements brief and a discovery call before any RFP |
| The engagement is small enough that a formal process adds more delay than value | A scoped proposal request from two or three firms, not a full RFP |
AI RFP template: nine sections you can copy
An AI implementation RFP needs nine sections to give a partner enough to quote responsibly. Copy the headings and prompts below into your own document, replace the bracketed text and drop any section that does not apply to your project.
- Background and business problem. "[Company] is a [size] [industry] business. [Workflow] currently costs us [hours, errors or delays] each [week or month], affecting [teams or customers]. We want [outcome]."
- Workflow in scope. "The process starts when [trigger] and ends when [result]. List every step, who does it, the volume per week, and the exceptions that need judgment. Out of scope: [list]."
- Systems and data. "The solution must read from ERP, [CRM, document store, email] and write to [system]. Data is [structured, scanned, free text] and must be current within [time]. Access is administered by [role]."
- Constraints. "Security and compliance obligations: [list]. Systems that cannot change: [list]. Fixed date and the real event behind it: [date and reason]. A named person must approve [decisions]."
- Response format. "Respond in this order: your understanding of our workflow, proposed approach, how you will test against our real cases, where a person reviews output, team and references, timeline, and costs."
- Evaluation criteria and weights. "Responses are scored on the criteria in the table below. Weights are fixed before any proposal is opened."
- Timeline. "Questions due [date]. Answers published to all bidders by [date]. Responses due [date]. Working sessions with finalists in [week]. Decision by [date]."
- Commercial format. "Quote three figures separately: build, monthly running and usage costs, and support after launch. State what is included in each and what would change the figures."
- Submission instructions. "Send responses to [contact] by [date and time]. Send questions only to [contact]. Questions and answers will be shared with every bidder."
Sections 1 through 4 cover close to the same ground as a software requirements brief, organized for a competitive process rather than a single partner conversation. If a brief already exists for this project, most of the RFP is assembling decisions you have already made rather than writing new ones.
What questions should you ask vendors?
Group your questions so every vendor answers in a structure you can score, rather than repeating the same idea under five different headings.
| Group | Ask | Why it matters |
|---|---|---|
| Scoping | How will you understand our workflow before proposing a solution | Shows whether the proposal fits your process or a template |
| Evidence | Can you describe a comparable engagement in detail and give us a reference | Separates a track record from a sales narrative |
| Data and security | Where is our data processed and stored, and is it used to train any model | Determines what your security team must review |
| Integration | How will you confirm our systems and data can support this before committing to a date | Surfaces licensing and access problems before a contract |
| Human control | Where exactly does a named person approve or review output before it takes effect | Shows whether consequential decisions stay with people |
| Testing | How will you test this against our real cases before it goes live | The most reliable predictor of what actually ships |
| Commercial | What is included in the build price, and what will this cost to run each month | Prevents a headline number that hides the real cost |
| Ownership and support | Who owns the code and accounts, and what happens after launch | Determines your position if the relationship ends |
Ask two or three specific questions inside each row rather than one broad one, so a vendor cannot answer in a sentence. For the data and security row, the NIST AI Risk Management Framework, a voluntary framework for building trustworthiness into AI systems, is a useful public reference for what to ask about risk. These eight groups cover the same ground as the ten questions and the red flags in how to choose an AI implementation partner, which also shows what a good answer to each one sounds like.
How do you score AI vendor responses with weighted criteria?
Scoring AI vendor responses works best when every vendor gets the same questions in writing, with the same deadline, and the team scores the answers as a group rather than deciding alone after the most persuasive call. Give each criterion a weight from 1 to 3 based on how much it matters for this project, rate each answer from 0, no evidence, to 3, strong and specific evidence, multiply weight by rating, and add up. The weights below are starting points to adjust.
| Criterion | Weight (1 to 3) | What strong evidence looks like |
|---|---|---|
| Understanding of our workflow | 3 | Asks to see real documents and exceptions before naming a tool |
| Testing on our real cases | 3 | A written test plan built from our own cases, with pass criteria |
| Data and security handling | 3 | Names the provider, where data is processed and whether it trains any model |
| Comparable work and references | 2 | A detailed comparable engagement and a reference we can call |
| Integration feasibility | 2 | Checks system access and licensing before committing to a date |
| Human approval design | 2 | States exactly where a named person reviews output before it takes effect |
| Commercial clarity | 2 | Build, running and support costs quoted as separate figures |
| Ownership and support | 2 | Says who owns code and accounts, and what happens after launch |
The highest weighted total is not automatically the right choice, but the exercise forces the comparison onto evidence instead of memory of who presented best.
The AI implementation partner scorecard runs this method for up to three vendors against ten criteria drawn from the questions above. Set your own weights, rate each vendor as answers come in, and it ranks them, flags any high weight criterion where a vendor offered no evidence, and lists the follow up questions worth asking before you decide. Our AI vendor due diligence checklist covers similar ground as a set of statements to tick off against a specific proposal, useful for whoever on your team is not sitting in every vendor call.
What are the red flags in vendor responses?
- Every vendor answer arrives at the same platform, no matter what you actually asked.
- A fixed price offered before anyone has seen your data, your systems or a sample document.
- A case study with no year, no company size and no reference you can call.
- Data handling described in marketing language, such as bank level security, rather than the terms of a named provider.
- Silence on what happens after launch, or an assumption that hosting includes support and monitoring.
- A refusal to separate the build price from what the system will cost to run each month.
- Urgency created by the vendor rather than by anything in your business.
How do you run the process fairly?
Four habits keep an RFP honest. Send the same information to every bidder, in writing, at the same time. Open a defined question window, and publish every question and its answer to all bidders at once, so nobody works from a private advantage. Take the responses down to a short list of two or three, then hold a working session with each, using one real batch of documents or requests rather than a rehearsed demo. Only then take reference calls, prepared with specific questions about what went wrong on a past project and how it was handled.
Illustrative example: Consider a 120 person distributor sending an RFP to four firms for a document processing project. The procurement lead sends all four the same nine section RFP and a two week deadline, publishes every question and answer from the window to all four at once, and asks each of the two finalists to spend half a day working through a real batch of invoices with the operations team. One firm treats the session as a demo of its platform. The other asks to see the invoices with handwriting on them and asks what the current error rate is before touching a keyboard. That difference, more than anything in either written proposal, decides the shortlist.
Read the contract before you sign for the details that are awkward to raise later: ownership of code and data, what happens to accounts at the end, notice periods, and whether any part of the arrangement requires exclusive use of one provider.
How Kastling approaches an RFP for AI work
Kastling is an AI solutions and implementation partner, and a well structured RFP is a reasonable way to reach us. Sent a fixed brief, we would rather spend an hour on a call first understanding the workflow behind the document than return a proposal built only from what is written down, and we would say so in our response. Engagements otherwise start with a free discovery call, and for AI and operations work a separately scoped, paid audit is common next. The background, workflow, systems and constraints sections in this guide are close to what that audit would establish anyway, so a well written RFP tends to shorten the scoping conversation rather than replace it.
We expect to answer the same kind of questions as any other firm on your list: where a human stays in control, how the work would be tested against your own cases, and who owns the code and accounts once the engagement ends. Read more about AI Integration & Automation.
AI implementation partner scorecard
Score up to three partners against the criteria that matter for your project and see a ranked comparison with the gaps to probe before you sign.
AI vendor due diligence checklist
AI vendor due diligence checklist for evaluating an AI implementation partner before you sign: scope, evidence, data handling, security, integration and terms.
Questions
How long should an AI implementation RFP be?
Long enough to give every bidder the same specific picture of the workflow, systems, constraints and response format, and no longer. Use the nine sections in this guide as a starting outline, then remove anything that does not help bidders understand or price your project. Page count is less useful than whether every bidder can answer on the same basis.
Should we ask for a fixed price in the RFP?
Ask for a pricing structure and a range, not a fixed number, unless the scope is genuinely narrow and well understood. A credible partner prices AI work after seeing your data and systems, and a firm number returned before that review is either padded to cover the unknowns or a guess that will move once real scoping begins.
How many vendors should we send an RFP to?
Invite only as many qualified vendors as your team can evaluate fairly through written responses, working sessions and reference checks. A shortlist of three to five can be a practical starting point, but it is a planning suggestion, not an industry benchmark. Adjust it to your procurement rules, project complexity and the time available to review each response.
What if only one vendor responds well?
Treat that as useful information rather than a problem to fix. A single strong response, checked with references and a working session on real data, is a legitimate way to proceed, and is more honest than padding a shortlist with firms you would not actually hire.
Do we need a lawyer to write the RFP itself?
Not usually. The RFP is a business document that states the problem and what you want back, and legal review matters once you move to a contract, where ownership, data handling and liability terms need to be checked properly. Involve legal earlier only if internal procurement policy requires it above a certain value.