How to use this template: 12 questions. Each one has three parts: the honest answer to use, the mistake most founders make when answering this question, and a worked example from one of the three archetypes. Replace the worked example with your own version. Delete all
>lines before publishing.
The mistake most founders make: Answering with a category instead of a deliverable. "You get a comprehensive audit" means nothing. "You get a 12-page Google Doc with 15 prioritized recommendations, a rewritten hero section, and a 30-minute Loom walkthrough — delivered within 4 business days" means everything. The honest version: List the outputs. State the format. State when they arrive.
Template: You get: [Deliverable 1 — format]. [Deliverable 2 — format]. [Deliverable 3 — format]. Everything is delivered [how and when].
Worked example — Clara Holt: You get: a rewritten hero section with 5 headline variants (I flag the one I'd ship) and a restructured features section — all in a Google Doc with tracked changes, plus a markdown export ready to paste into your page builder. Delivered within 4 business days of your intake form submission. One round of revisions included, returned within 48 hours of your feedback.
The mistake most founders make: Giving a range so wide it communicates nothing. "2–6 weeks depending on complexity" is useless. Give a specific timeline for the standard case, then state what changes it. The honest version: State the standard timeline. State the one or two things that extend it (late client feedback, missing inputs). State the one condition that could accelerate it.
Template: Standard timeline: [X business days / weeks] from [trigger — booking, intake form submission, deposit receipt].
What extends it: [Condition 1 — e.g., late feedback on the first draft]. [Condition 2 — e.g., missing access credentials at kickoff].
If you need it faster: [Whether you offer rush delivery and at what cost, or whether you don't].
Worked example — Flowmatic: Standard timeline: 5 business days from scoping form submission.
What extends it: If we don't receive CRM and document tool API access within 24 hours of project start, the timeline shifts by the same number of days. If you need to review and approve a mid-project test before we proceed, add 1 business day for each approval step.
Rush delivery (3 business days): +$350. Available on most projects — confirm availability when you submit the scoping form.
The mistake most founders make: Saying "not much — just hop on a kickoff call." This creates ambiguity and delays projects. List the exact inputs required before work can begin. The honest version: List the specific inputs. State the format. State the deadline (when you need them by relative to project start).