use case · 09

the proposal problemEvery proposal starts from a blank page.

Meet Greg Sutcliffe, managing partner at Meridian Commercial Interiors — twenty-five people who build offices, and six to ten hours of Sunday-night proposal work for every one of them. Every pitch starts from a blank page, and the blank page is where deals go to die.

the story

fictional · illustrative pattern

Greg's proposal.

A tenant fit-out comes in: two floors, forty desks, a café build. Greg has built fifty jobs like it — but every proposal starts from zero, pricing dug out of an estimator's memory, scope rewritten by hand. Two proposals this quarter were late. One of them lost the job.

Run FlowHealth to confirm →
01

Six to ten hours per proposal

Rebuilt from scratch, because 'every job is different.'

02

Pricing takes forever to dig up

The number lives in the estimator's head, the old quote, or the supplier's email — never in one place.

03

Inconsistent by default

Three partners, three formats. Clients notice when the deck doesn't match the pitch.

04

Late proposals lose

The job goes to the firm that was ready Thursday, not the one that shipped Tuesday.

what they'd tried

The honest attempts.

01

The master template

Built once, abandoned after the third job — too rigid for real projects.

02

Copy-paste from old proposals

Sections reused from past jobs, complete with the wrong client names until caught.

03

The pricing spreadsheet

It worked. It was also only on Greg's laptop, and only Greg knew how to drive it.

what they assumed

The quiet beliefs.

01

Every job is different, so every proposal must be custom

Custom became a synonym for from-scratch.

02

Templates make us look generic

He'd seen bad templates and concluded all of them were bad.

03

Speed is a sales problem, not a proposal problem

The pitch was the fun part; the proposal was the paperwork between him and it.

what plainworks did

The proposal became a build, not a blank page.

● before
blank page every timepricing in one headtwo late proposalsdeck vs. pitch mismatch
● after
Past jobs + pricing library in one system
AI drafts the narrative from the intake
Scope assembly in 90 minutes
Proposals out in 24 hours
hrs

40 hours a month

Eight-hour proposals down to ninety minutes — and the saved time went into the jobs that needed it.

%

Win rate up on the jobs they were first to

Being fast didn't win every deal. It stopped losing the ones they were right for.

$

~$60,000 a year in won work

One more won job a quarter, conservatively, from proposals that arrived on time.

The proposal stopped being the weakest part of the pitch.

why it mattered

Intrinsic, then direct.

The fix didn't make proposals cheaper. It made them faster and more honest — which is how Greg found out what the drag had really been costing.

01

Intrinsic value

Greg stopped spending Sunday nights rebuilding what he'd already built fifty times. And the partners stopped shipping decks that didn't match the pitch.

02

Direct value

40 hours a month back, proposals out in 24 hours instead of four days, and a win rate that stopped leaking to faster firms.

how they see it now

Custom never meant slow. It meant specific.

When the machine knew his numbers, custom became fast. Greg stopped conflating craftsmanship with starting over — and the P&L agreed.

— Greg, after the first quarter of on-time proposals

which offering fixes this

This is a _growth problem.

Also common

is this your leak?

Win the deal you're losing to slowness.

Run the free FlowHealth diagnostic or talk to the consultant. We'll confirm the fix and hand a clear concept to Nathan.