From brief to bundle: the document stack that wins enterprise work
Enterprise buyers don't buy proposals. They buy reassurance that you've done this before. Here's the document stack that signals it.
When I left consulting to go solo, I assumed the polished proposal that had won me work at Deloitte would work just as well on my own. It didn't. Same template, same writing, suddenly a bunch of polite nos.
Took me about a year to figure out why. At Deloitte, my proposal landed on a buyer's desk surrounded by an entire firm's worth of implied paperwork. The MSA was already in place. Procurement knew us. There were eight previous SOWs on file. The proposal was the tip of an iceberg, and the iceberg did most of the selling.
On my own, I was sending just the tip. To buyers whose default setting is 'this person might disappear.'
So I started bringing the iceberg with me. Win rate roughly doubled inside six months.
Before the first call
- A capabilities one-pager. 60 seconds of skim, focused on their domain. Not your bio.
- Two case studies. Same industry, similar engagement size. Not your three flashiest wins from five years ago.
These get attached to your intro email. They're not the pitch — they're the credentials that earn you the pitch meeting.
After the discovery call
- Discovery summary, one page. Mirror their language back to them. The first time you do this, you'll be amazed how much credit you get for what is essentially good note-taking.
- Proposal with three scope tiers. Always three. Single-price proposals get haggled. Three-tier proposals get chosen.
- Draft SOW for the recommended tier. Sends the signal that you're serious and that you've done this before.
The draft SOW is the unlock. Most consultants wait until the proposal is signed to write one. By the time you produce it, the buyer has already lost a week of momentum. Send it with the proposal and you compress the decision cycle by two weeks. I know — I tracked it.
When they say 'send paper'
- Final SOW
- MSA, or your red-line of theirs
- Project plan with milestones and dependencies
- Risk register
- RACI matrix
- Communication plan
Six documents at signature is not overkill. It's the floor for anything above about $50k. Buyers who've been burned before look for this stack. Buyers who haven't been burned learn very quickly that the consultants who bring it are the ones who actually deliver.
The risk register in particular punches above its weight. It's the single document that most clearly separates senior consultants from juniors. By naming what could go wrong, you make those things governable instead of catastrophic. You also signal that you've been around long enough to have a list.
The honest part
Producing all this used to take me two days per proposal. Two days for a deal that might not close. Brutal math.
I now use PenSow's suite generator and it takes about ten minutes. I still edit every document — most of them substantially — but the structure and 80% of the language is there. The point isn't to skip the thinking. It's to stop doing the formatting at 11 PM.