Lead-to-Close: step 4 (proposal from call notes)

Why it works

Step 4 of the chain - the payoff. Takes the call notes from step 3 and produces a one-page proposal: the problem you heard (in their words), your approach, scope and timeline, pricing rationale tied to value (NOT hours), and the explicit next step. The proposal is intentionally one page - longer proposals get read less, not more. The pricing rationale is the most important section: it ties the price to the value the buyer named in the call ('this saves your team 6 hours/week, which at 2 people is 480 hours/year'), not to your hours. Buyers who see hours-based pricing immediately mentally compare your hourly rate to theirs and find a reason it's too high. Tested cleanest on Claude Opus 4.7.

Example output

Proposal: PromptPaste team rollout for Northbeam

The problem you described:
Your cut to a two-person content team made the workflow leaner but exposed how much of your team's best prompt work was buried in ChatGPT history. You estimated each team member loses 30-45 minutes per day re-creating prompts they had already built. Across the team, that's ~6 hours/week of repeated work.

My approach:
- 30-day rollout: I onboard your two team members, audit their existing scattered prompts (Notion docs, chat history, Slack), and build a curated team library of ~40-60 prompts.
- Voice-loaded brand prompts: each high-frequency prompt gets your brand voice baked in, so the output sounds like Northbeam from the first paste.
- Weekly review for the first 4 weeks: I sit with each team member for 20 minutes to refine the library based on what's actually getting used.

Scope and timeline:
- Week 1: prompt audit + library structure.
- Weeks 2-3: build and test the library.
- Week 4: roll out to both team members + first review session.
- Weeks 5-8: weekly refinement sessions.

Pricing rationale:
Flat fee: $4,800.
Value anchor: 6 hours/week × 50 weeks = 300 hours/year of work recovered. At your team's effective marketing-team rate (~$80/hr loaded), that's $24k/year of recovered output. The proposal pays back in roughly 10 weeks.

Not priced as hourly - the value is in the system, not the time spent building it.

Next step:
Reply 'go' by Wednesday and I'll send the kickoff doc within an hour. If you need me to walk through this with anyone else first (procurement, your boss, a teammate), tell me who and I'll send a tailored version.

Common mistakes

Don't skip the 'value anchor' calculation in pricing rationale. It's the single most important sentence in the proposal because it converts the price from a number to a payback period. Buyers approve based on payback, not on price. Also: do not let the proposal exceed one page. If you need two pages, the scope is too big for this stage - propose a smaller phase 1 and reference phase 2 in the next-step section. Third mistake: leaving the next step vague. 'Let me know what you think' kills proposals; 'reply go by Wednesday and I'll send the kickoff doc within an hour' closes them.