How to use this template: This schema has two jobs. First, it's a client-facing document that answers "what do you need from me?" and "what will I receive?" with no ambiguity. Second, it's the foundation for the JSON-LD block at the bottom — the machine-readable version of your offer. Fill in the tables, then customize the JSON-LD block. Delete all >  lines before publishing.


INPUTS TABLE

Decision guide — how to figure out what your inputs are: Ask yourself: "What would make me unable to start this project?" List everything. CRM access, brand guidelines, existing copy, analytics access, answered questionnaire, signed contract. Then ask: "What would make me produce a worse deliverable if I didn't have it?" List that too. Examples: customer interviews, existing customer data, competitor list, previous version of the page. Required = can't start without it. Helpful = makes the output better. Format column is important: "Google Doc link" vs. "PDF" vs. "admin-level login" prevents back-and-forth later.


Three worked examples:

Flowmatic (AI automation agency):

Input Required or Helpful Format When needed
HubSpot or Pipedrive admin access Required Admin-level login or API key Before project start
PandaDoc or DocuSign admin access Required Admin-level login or API key Before project start
3 real proposal examples Required PDF or Word files Before project start
Current manual process description Required Completed scoping form (15 min) At booking
Deal stage names and CRM field list Helpful CSV export or screenshot Before project start
Existing proposal template Helpful PDF or Word Before project start

Meridian (B2B SaaS — inputs for onboarding):

Input Required or Helpful Format When needed
Project list Required CSV (name, status, due date, assignee) During onboarding
Team member email list Required Plain text list or CSV During onboarding
Billing email and payment method Required Stripe checkout At sign-up
Time entry history Helpful CSV from previous tool Within first week
Client list Helpful CSV (name, email) Within first week

Clara Holt (landing page copywriter):

Input Required or Helpful Format When needed
Completed intake form Required Link sent at booking (30 min to complete) Before work starts
Current page URL Required URL In intake form
Customer research Helpful Interview notes, survey results, NPS comments — any format In intake form
Existing copy document Helpful Google Doc, Notion page, or plain text In intake form
3 competitor pages you respect Helpful URLs In intake form

Your inputs table:

Input Required or Helpful Format When needed
[Input 1] Required [Format] [When]
[Input 2] Required [Format] [When]
[Input 3] Helpful [Format] [When]
[Input 4] Helpful [Format] [When]
[Input 5] Helpful [Format] [When]

OUTPUTS TABLE

Decision guide — how to figure out what your outputs are: List every file you send at the end of an engagement. That's your output list. Now add the format and where it lives. "Final copy" → "Google Doc (shared link, you own the copy)." "Working automation" → "Make.com scenario (transferred to your account)." "Audit report" → "12-page PDF, emailed to you." Now add anything you deliver during the project, not just at the end — Loom walkthroughs, check-in calls, draft versions for review. Output format is as important as the output itself. "A Google Doc" tells the buyer nothing about where they paste it or who owns it. "A Google Doc shared as 'anyone with link can edit,' transferred to your Google Drive on request" tells them everything.


Three worked examples: