The problem nobody wanted to name
DevFlow was generating leads. Good ones, too — 15 or more a month through referrals and LinkedIn, the kind of inbound that most agencies would kill for. But somewhere between the first call and the proposal, something was breaking down. Roughly 60% of prospects would go quiet after receiving a quote. No objections, no counter-offers. Just silence.
The team had started calling it the "proposal graveyard." A folder full of names they'd spent real time on — discovery calls, scoping sessions, custom decks — that had simply stopped responding. The assumption was that pricing was the issue. It wasn't.
"They weren't losing on price. They were losing because their proposals gave people no reason to act now."
What we actually found
We started by going back through the cold deals — not to count them, but to read them. What did the proposals actually say? What was the follow-up sequence? Where did the thread go quiet?
The pattern was clear within a couple of days. DevFlow's proposals were detailed and technically impressive, but they were written like specs, not sales documents. They explained what would be built. They didn't explain what it would cost the client to wait another quarter to build it. There was no urgency. No consequence to inaction. And the follow-up, when it happened, was a single "just checking in" email that gave the prospect nothing new to respond to.
The sprint
We kept the intervention tight — three changes, two weeks.
Reframe the proposal around cost of delay
We added a single section to the proposal template: a plain-English breakdown of what the problem was costing the client each month they didn't solve it. For most, that number was significantly higher than DevFlow's fee.
Build a re-engagement sequence with substance
Instead of a nudge email, we wrote a three-touch sequence that gave each prospect something useful — a relevant observation, a short case example, a specific question. Something worth replying to.
Send it to the 12 coldest leads first
We picked the prospects who'd gone most quiet — some hadn't responded in over two months — and ran the new sequence on them as a test. If it worked here, it would work everywhere.
What happened
Eight of the twelve replied within 48 hours. Not vague replies — actual responses with questions, updated timelines, renewed interest. Three of those conversations moved to contracts within the two-week window.
Total recovered revenue: $45,500. From leads that had already been written off. The proposals hadn't changed in price — just in how they framed the decision.
"On a $2,500 engagement, DevFlow recovered $45,500 before the two weeks were up. The pipeline was never dead — it just needed a reason to move."
DevFlow rolled the new proposal template and follow-up sequence into their standard process. The "graveyard folder" still exists — but it's a lot thinner than it used to be.