Winning Proposals &
Bid Work
Proposal strategy and writing for teams pursuing competitive, high-stakes work. I find the differentiator buried in your team's daily work and make it land inside the page limit, in front of evaluators who are deciding whether you're a safe bet.
Who this is for
This is for you if you need a steady hand before the high-stakes moment, not a scramble during it.
Who this is for
For teams where one win is real money on the table, and the response needs to actually win, not just comply.
BD and proposal leads who need the response to actually win, not just comply.
Founders and small businesses going after federal work, where one win is real money on the table.
Technical teams whose writing is all substance and no story: deep expertise that reads flat on the page.
AI has made words cheap. It'll generate a technically exhaustive draft in seconds: polished, accurate, and completely forgettable.
But polished isn't differentiated, and an evaluator feels the difference on the first page. Your real edge is usually hiding in plain sight, in work so routine to your team they've stopped seeing it as remarkable.
Those are the hardest stories to pull out and the exact ones an evaluator is asking for:
Where have you done this in my environment?
Show me you're not a risk.
What makes you a safe bet?
And all of it has to land inside a hard page limit, where every sentence that isn't earning its place is costing you one that could.
How I work
Structured intake that respects scarce time
Your experts never get a blank page. Intake is scoped to each section and requirement and offered in whatever format fits them, built to pull out the how, why, and so what behind the work.
AI as a baseline; your SMEs as the filter
AI output is a starting scaffold, not the answer. The experts are how we separate what's genuinely differentiated from what only sounds polished.
Solutioning before writing
We pressure-test why your approach is different and what the evaluator actually needs to hear before drafting, so we know what to lead with and what to compress.
Written across the volumes, and written to cohere
Management, technical, transition, quality: authored to tell one consistent story. Where the underlying solution has a gap, I surface it rather than write around it.
Cut to the page limit with discipline
The architectural bones of your solution, written for meaning and positioning, not the technical-standards default that fills space without saying anything.
Built to compound
You come out with a lessons-learned read and reusable intake frameworks, so the next pursuit starts from a foundation instead of from scratch.
What this is, and isn't
Loading your documents into an AI and asking it to sound like a seasoned proposal writer gets you words; it doesn't get you the story only your team can tell.
Judgment, not volume
I work at the solutioning and message layer, not as a pair of hands that prettifies what you already have. The difference between a competent proposal and a winning one isn't more words. It's knowing which differentiator to lead with, what an evaluator needs to hear, and what to cut so it fits.
Compliance with connection
In compliance-heavy work, the temptation is to strip the response of anything human to stay safe. But evaluators are people, deciding whether they can trust you. Compliance doesn't have to cost you connection. A compliant response can still show who you are and why you're the safe bet.
