Template 4: Inputs / Outputs Schema
Template 6: Limitations & Expectations
Template 7: Offer Clarity Score
| File | What it does | Time to complete |
|---|---|---|
01-service-page-template.md |
Your main offer page — headline through CTA | 2–3 hours |
02-pricing-page-template.md |
Tier structure, scope boundaries, inline FAQ | 1–2 hours |
03-faq-template.md |
12 real questions with honest answer templates | 1–2 hours |
04-inputs-outputs-schema-template.md |
What you need, what you deliver, machine-readable JSON-LD | 1 hour |
05-scope-of-work-template.md |
Client-facing SOW with change request policy | 45 min |
06-limitations-expectations-template.md |
What you don't do and why stating it builds trust | 30 min |
07-offer-clarity-score.md |
20-item checklist to grade your page before and after | 20 min |
Total realistic time: One focused weekend. Not a weekend where you also do other things — a weekend where you sit down Saturday morning with coffee and finish by Sunday afternoon.
Read the three descriptions. One of them will feel uncomfortably accurate.
You build automations for small and mid-size businesses. Zapier flows, Make.com pipelines, custom GPT wrappers, maybe some light Python scripting. You sell productized packages — "Starter Automation Pack," "Full Stack AI Setup," something like that.
Your pricing page problem: it lists what tools you use, not what the client gets. Prospects ask "what exactly will you build for me?" on every sales call. You answer it the same way every time and have never written it down.
Your FAQ problem: the questions are about your process ("Do you use Zapier or Make?") not about the buyer's risk ("What if the automation breaks six months from now?").