How I turned ChatGPT into my proposal co-pilot and started consistently landing in the top 3.
I used to hate writing proposals.
Not the technical parts. Those I could do in my sleep. The parts that killed me were the executive summaries, the methodology write-ups, the compliance matrices, and the 30-page documents that needed to sound professional, comprehensive, and convincing all at the same time.
I would spend entire weekends on a single tender. Sometimes we would win. Most times we would not. And every loss felt like I had wasted days of my life formatting tables and rewriting the same project methodology for the fifteenth time.
Then I started using AI. Not to replace the thinking. To replace the suffering.
Our win rate went up. Our turnaround time went down. And I stopped dreading the words “new RFP just dropped.”
Here is exactly how I did it.
First, Let Me Be Honest About What AI Cannot Do
Before I share the playbook, I need to say this clearly: AI did not win us any tenders. We won them. AI just removed the bottlenecks that were slowing us down.
AI cannot understand your client’s unspoken concerns. It cannot read the political dynamics behind a government tender. It cannot decide whether to price aggressively or play it safe. It cannot tell you that the evaluation committee cares more about local experience than technical innovation because you overheard that at a networking event last month.
Strategy is human. Judgment is human. Relationships are human.
But turning a rough technical outline into a polished 20-page proposal at midnight before the deadline? That is where AI earns its place.
If you go into this thinking AI will do the hard work for you, you will produce generic proposals that evaluators can smell from a mile away. If you use it as a force multiplier for work you already know how to do, you will move faster than anyone competing against you.
The Playbook
Step 1: Dissect the RFP With AI Before You Write Anything
The first thing I do when a new RFP lands on my desk is feed it into ChatGPT. Not to get answers. To get clarity.
I paste the entire document and ask it to extract the key evaluation criteria, rank them by likely weight, identify mandatory requirements versus nice-to-haves, and flag any ambiguous language that could be interpreted multiple ways.
This takes me five minutes. It used to take an hour of highlighting and note-taking.
The output is not perfect. Sometimes it misreads the weighting. Sometimes it misses context that only someone who has worked with that particular agency would understand. But it gives me an 80% accurate breakdown that I can refine with my own experience in another ten minutes.
That first hour I saved? I reinvest it into strategy and figuring out what angle to take, what to emphasize, and what our competitors are likely to propose.
Step 2: Build Your Proposal Skeleton, Not Your Proposal
This is where most people go wrong. They ask AI to “write a proposal for a web application project” and get back something that reads like it was generated by a machine. Because it was.
I never ask AI to write the proposal. I ask it to structure one.
I give it the RFP requirements, our company profile, the project scope as I understand it, and any specific points I want to hit. Then I ask it to generate a detailed outline, section by section, with bullet points for what each section should address based on the evaluation criteria.
The skeleton is the most valuable output AI gives me. Because now I am not staring at a blank page. I am filling in sections with real content with our actual experience, our specific team members, our honest approach to the problem.
The difference between a winning proposal and a losing one is almost never the writing quality. It is the structure. Evaluators score proposals section by section, criterion by criterion. A well-structured proposal that directly mirrors the RFP’s evaluation framework will outscore a beautifully written one that buries key information in the wrong sections.
AI is exceptional at structural alignment. Use it for that.
Step 3: Write the Technical Approach Yourself, Polish It With AI
The technical approach is the soul of your proposal. This is where you prove you actually understand the problem and have a credible plan to solve it.
I write this section myself. Always. Every time.
I write it rough, fast, and ugly. I dump everything I know about how I would build this system from the architecture, the technology choices, the phases, the risks, the mitigation strategies, etc. No formatting. No polish. Just substance.
Then I hand it to AI and say: “Rewrite this for a non-technical evaluation committee. Keep all the technical substance but make it accessible. Use clear headers. Add a brief summary at the top of each section.”
This is the magic step. Most technical founders and leads write proposals that are too technical for the people evaluating them. We assume the reader understands our stack, our acronyms, our architectural decisions. They usually do not.
AI is remarkably good at translating technical depth into business-friendly language without losing the substance. It bridges the gap between what you know and what the evaluator needs to understand.
I review every line of the output. I correct technical inaccuracies. I add specifics that AI generalized away. But the readability improvement alone is worth the effort.
Step 4: Let AI Handle the Compliance Grind
Every tender has compliance sections. Company registration documents. Past project references formatted in a specific table. Team CVs in a prescribed format. Methodology statements that need to hit certain keywords.
This is tedious, repetitive, and absolutely critical. Miss one compliance item and your entire proposal gets disqualified, no matter how brilliant your technical approach is.
I maintain a master document with all of our company information, team profiles, past projects, certifications, and standard methodology statements. When a new tender comes in, I feed the compliance requirements and our master document to AI and ask it to generate compliant responses matched to the specific format requested.
Does it get everything right the first time? No. But it gets 85% of the compliance matrix done in thirty minutes instead of three hours. I spend the remaining time on manual verification making sure dates match, references are current, and nothing has been fabricated.
That last point is critical. AI will sometimes hallucinate details in compliance sections. It might invent a certification you do not have or attribute a project to the wrong year. Always verify. Compliance is binary, you either meet the requirement or you do not. There is no partial credit for creative fiction.
Step 5: Executive Summary Last, Not First
Most people write the executive summary first. I write it last.
After the entire proposal is complete, the technical approach, methodology, team composition, compliance, pricing, I feed the full document to AI and ask it to generate a one-page executive summary that highlights our three strongest differentiators relative to the evaluation criteria.
Why last? Because by this point, I know exactly what our strongest selling points are. The process of writing the proposal reveals them. Maybe our team composition is unusually strong for this project. Maybe our timeline is more aggressive than what the RFP expects. Maybe we have a directly relevant past project that no competitor can match.
The executive summary is not a summary. It is a sales pitch. And you cannot write a good sales pitch until you know exactly what you are selling.
AI helps me distill 25 pages into the most compelling single page. I rewrite it heavily. The voice needs to feel human and confident, not robotic and generic. But the structure and key points it identifies are usually spot on.
Step 6: The Final Review — AI as Devil’s Advocate
Before I submit, I do something that has saved me multiple times.
I paste the entire proposal back into AI and ask: “You are an evaluator reviewing this proposal. What are the three weakest points? Where would you deduct marks? What is missing?”
This is uncomfortable. Nobody likes being told their work has gaps. But it is infinitely better to hear it from AI at 11 PM than from the evaluation committee two weeks later.
The feedback is not always accurate. Sometimes it flags things that are actually fine. But about one in three times, it catches something genuinely important — a requirement we addressed weakly, a section that contradicts another, or a claim we made without evidence.
I fix what needs fixing, verify that the fixes do not break anything else, and submit.
The Numbers
I do not have a large enough sample size to claim scientific validity, but here is what I have observed since adopting this approach:
Before AI: Proposal turnaround averaged 7 to 10 working days. Win rate was roughly one in five.
After AI: Turnaround dropped to 3 to 5 working days. Win rate improved to roughly one in three, with consistent top-3 finishes even on losses.
The time savings alone changed our business. We can now respond to more tenders per quarter without burning out the team. And because we are spending less time on the mechanical work, we are spending more time on the strategic work which is what actually wins.
What I Would Tell You If You Were Starting Tomorrow
Invest in your master document. Before you use AI for a single tender, compile everything about your company into one living document. Team profiles, project case studies, methodology frameworks, compliance details. The better your inputs, the better AI’s outputs. Garbage in, garbage out applies more here than anywhere.
Do not let AI write your voice. Evaluators read dozens of proposals. They can sense when something feels generic. Use AI for structure, translation, and polish. But your unique perspective, your specific experience, your honest assessment of risks and those need to come from you.
Pay for the tools. I use ChatGPT Pro. The difference between the free tier and the paid tier for long-document work is enormous. Context window, response quality, ability to handle complex multi-step prompts, it is worth every ringgit (Malaysian dollar 🇲🇾). I wrote about this before: you cannot demand AI-level output without paying for AI-level tools.
Verify everything. AI will occasionally make things up. In a compliance context, a single fabricated detail can disqualify your entire proposal. Trust but verify. Then verify again.
Speed is a competitive advantage. The faster you can produce a quality proposal, the more opportunities you can pursue. AI does not just make you better at individual tenders, it expands the number of tenders you can realistically compete for.
The Uncomfortable Truth About Tenders in 2026
Here is what nobody in the tender space wants to admit: if you are not using AI to assist your proposal process, you are already behind.
Not because AI makes better proposals. It does not. Humans make better proposals. But AI makes the proposal process fast enough that good teams can actually compete at scale.
The team that submits five well-crafted proposals per quarter will statistically outperform the team that submits two perfect ones. Volume matters. And AI is the only way to increase volume without sacrificing quality or burning out your people.
I am not saying this to scare you. I am saying this because I was you two years ago — spending weekends on proposals, wondering why we kept losing to companies that seemed to move impossibly fast.
They were not better than us. They were just faster. And now, so are we.
This article is an expanded version of my earlier piece on how AI became my assistant for winning tenders. If you are interested in the broader conversation about AI in the workplace, check out why you can’t demand AI speed without paying for AI tools and my thoughts on what happens when AI writes code your team doesn’t understand.