A friend who runs a twelve-person brand studio forwarded me a 64-page RFP last month with one line attached: "This will eat my whole week." She was right. Not because the questions were hard, but because every answer already existed somewhere in her business and none of it was findable in under six hours.
That is the real shape of the problem, and it is why I built this on my own side.
An RFP is a retrieval problem wearing a writing costume
Count the questions in your last RFP that you had already answered before. For most founder-led agencies it lands somewhere between 70 and 80 percent. The security questionnaire, the team bios, the process section, the insurance certificate, the case study that happens to match their industry.
The writing was never the bottleneck. The bottleneck is that the answers live in eleven places: a Drive folder from 2021, an old proposal buried in a sent mail thread, a PDF your designer made, three case studies that need updating, and your own memory of how you handled a similar project in 2019.
Bid managers exist to hold that library. You are not going to hire one for a $40,000 project, and honestly you should not want to, because a bid manager who does not know your clients will write something accurate and forgettable. What you need is retrieval, and retrieval is a solved problem now.
Build the answer library before you build anything else
Do not start with prompts or tools. Start with the pile.
Take your last five RFPs and every proposal you sent in the past two years. Pull out every question you have ever been asked and put them in one table. I use Notion, Airtable works just as well, and the columns are simple: the question, your best existing answer, the proof (client name, number, outcome), and a category tag like process, team, pricing, security, or results.
Copy the good answer you already wrote. Do not rewrite it from scratch. If an answer has no number and no named client in it, mark it weak and fix it later.
Sixty to ninety questions will cover most of what you get, because agencies get asked the same forty things in different fonts. The first build takes a solid afternoon, maybe two if your files are as messy as mine were.
Then load that table into a Claude Project or a custom GPT with a system prompt that says three things: answer only from these documents, flag any question where the library has nothing, and never invent a number or a client name. That last instruction matters more than the other two combined.
I have trained more than 90,000 people on software like this, and the pattern never changes: the tool is never the hard part. The library is the hard part.
The afternoon workflow
Here is the sequence.
Step one, decompose. Paste the full RFP into Claude or ChatGPT and ask for a numbered table: section, question, word limit, mandatory or optional. Twenty minutes instead of ninety, and you catch the three questions buried on page 51 that would have cost you points.
Step two, batch by section. Feed the table back in with the library attached and ask for drafts section by section, never all at once. All at once and the answers blur into each other. Add a column called Source that reads either "library" or "missing" so you can see exactly where the gaps sit.
Step three, you only touch two things. The missing rows, and the rows that require an actual point of view: pricing philosophy, why us, team composition, and the paragraph where you push back on something in the brief. Dictate those into Otter or a voice memo and paste the transcript in. Your spoken voice is better than your typed voice, and it takes me a minute to talk through a question I have answered out loud fifty times.
Step four, assemble once. Build the document skeleton in Google Docs to match the RFP structure before you paste anything, so you are not reformatting at 11pm. If the submission is design-heavy, Gamma gets you a clean layout fast.
Total founder attention: about two hours. The rest is the system moving text around.
How to not sound like every other agency
Left alone, AI writes the average of your industry. It will produce "we take a collaborative, insight-led approach to brand transformation" because that is the statistical center of a thousand proposals. That sentence loses.
Four rules fix it.
Ban any sentence that could appear in a competitor's submission. Ask for a rewrite with that as an explicit constraint and watch how much gets cut.
Every claim gets a name and a number. Not "we have worked with leading retailers." Instead: "We rebuilt the loyalty program for a 41-store regional retailer and repeat purchase went up 19 percent over two quarters." One of those gets read. The other gets skimmed.
Include one short section called "Where we would push back." Two paragraphs, honest, specific to their brief. In my experience that section is often the reason a founder gets called into the room, because everyone else submitted the same compliant document.
Read the whole thing out loud before you send it. Anything you would not say to the client's face comes out. Then write the executive summary yourself, last, after you have read every answer. Some evaluators never get past page one.
This is the same problem you have everywhere else
The RFP library is one instance of a pattern that shows up in every part of a founder-led business. The knowledge is not missing. It is trapped in your head and in folders named finalv3REAL.
The fix always has the same shape: pull the knowledge out once, structure it, let the system retrieve it, and keep the twenty percent that requires judgment for yourself. That is what founder operations systems actually are, and it is why the same build that speeds up an AI RFP response also cleans up your proposal follow-up, your onboarding, and the CRM you keep meaning to fix.
I wrote more about the difference between building this alone and building it with people who run the same kind of business here: https://www.mastermindshq.business/mastermindvsl. There is also a free walkthrough of the build itself at https://workshop.mastermindshq.business.
If this resonates and you want to build this kind of infrastructure in your own business, the Mastermind is where we do the work live. You can learn more at mastermindshq.business.