A request for proposal lands. Somewhere, someone opens a blank document, finds the closest proposal they wrote before, and starts the familiar grind: rewriting the scope, rebuilding the fee, reformatting to this client's expectations, pulling boilerplate from three old files. The real skill — knowing how to approach the work and what it's worth — is maybe a fifth of the effort. The rest is reconstruction the firm has done a hundred times.
That reconstruction is exactly the kind of routine work that can start much further along. Not the judgment — the legwork around it. Here's how to think about turning an RFP into a first-draft proposal, and where the line between "helpful" and "reckless" actually sits.
Start from your own work, not a blank page
The blank page is the enemy, but so is the generic template. The goal isn't to generate a proposal — it's to generate a first cut of yours: in your voice, structured the way your clients expect, priced the way your firm prices.
That only works if it's built on your own material:
- Past proposals — the ones you won, and how they were scoped and worded.
- Your boilerplate — the firm overview, the QA approach, the safety statements, the terms you reuse every time.
- Your pricing history — what you quoted for similar scope, and why.
Built on that, a first draft reads like your firm and prices like your firm. Built on a generic model, it reads like everyone's — and that's precisely the proposal a client skims and forgets.
What a good first cut actually contains
A useful first draft isn't "press a button, get a finished bid." It's a structured starting point that removes the cold-start work:
- A scope cut from the RFP — the requirements pulled out, organised, and matched against how you'd actually approach them.
- The structure in place — sections, headings, and a compliance check against what the RFP asked for, so nothing required is missing.
- Boilerplate already dropped in — the standard content assembled and tailored, not copy-pasted from an old file.
- A starting fee — a first pass at the fee structure, built from your past work, ready for a person to pressure-test.
In other words: the proposal arrives at the estimator's desk already at the stage they usually reach after a half-day of setup. The half-day is gone; the judgment is still entirely theirs.
The fee is the sharp edge — handle it honestly
Pricing is where this either earns trust or loses it. A fee "estimated by AI" with no basis is worse than useless. A fee built from your own quoting history is something else: a defensible starting point that reflects your real rates and the scope patterns you've priced before.
The honest framing matters. The draft proposes a number and shows where it came from — which past jobs, which rates, which assumptions. A person then refines it with everything the data can't see: this client's appetite, the strategic value of the win, the risk in the scope, the relationship. The tool gets you to a sound starting number faster; it doesn't decide what to bid.
A person owns every word
This is the part that isn't negotiable. A proposal is a commitment — to scope, to price, to a relationship. The work starts further along, but it's still your estimator who reads it, adjusts it, and signs off. Nothing goes to a client that a person hasn't owned.
Done this way, the benefit isn't "fewer people writing proposals." It's that the people writing them spend their hours on the part that wins work — the approach, the differentiators, the judgment — instead of on reconstruction.
It compounds
There's a quieter benefit. Every finished proposal is a new data point: another example of what you scoped, what you quoted, and whether you won. Feed that back in, and the next first draft starts from a slightly better place than the last. The system gets sharper the more you use it — not because the model is clever, but because your own record keeps growing.
Where Honewright fits
First-draft proposals from an RFP is one of the workflows we build for directly — turning a structured request and its attachments into a first cut of the scope, structure, and fee, built on your own templates and pricing history. It connects to the tools you already use, keeps a person in charge, and keeps your pricing data yours — and in Canada.
If your firm starts too many proposals from a blank page, tell us what's eating your time. We'll tell you honestly whether there's something worth building.