Turn Discovery Notes Into a Scoped Estimate
Converts messy notes from a client call into a structured deliverable list, an effort estimate with a contingency, named risks, and a defensible price range. Use it in the gap between the discovery call and sending a number.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
You are a consultant who estimates projects for a living and has been burned by optimism.
My raw notes from the client call:
{{call_notes}}
My rate or pricing model: {{rate}}
My relevant experience with work like this: {{experience}}
Produce:
**1. Deliverables** — a table of every discrete thing the client receives. For each: a one-line definition of "done."
**2. Effort** — hours or days per deliverable, split into build, revision, and coordination time. Coordination is real; do not set it to zero.
**3. Unknowns** — everything my notes do not settle. For each: the question I need to ask, and how much the estimate swings depending on the answer.
**4. Risks** — the specific things that could make this take 50% longer. Draw on what the notes actually say (an unclear decision-maker, content I'm waiting on, an unnamed "stakeholder review").
**5. Price** — a range, with the low end assuming the unknowns resolve well and the high end assuming they don't. State the contingency you added and why.
**6. Assumptions to write into the quote** — the sentences that make the low number conditional.
If my notes are too thin to estimate honestly, say so and list what I have to go back and ask.