One-Page SOW / Proposal Template

Generate a concise, client-ready one-page SOW with scope, 3 deliverables, dated milestones, 2 pricing tiers, acceptance CTA, short terms, risks, proof, and objection rebuttals (...

What You'll Get

One-page SOW in Markdown with professional header (client, project title, start_date)

Scope paragraph (in/out), exactly 3 deliverables with measurable outcomes, 3-5 dated milestones with owners and acceptance criteria

Two clear pricing tiers (fixed price, delivery window, 2-line differentiation) and payment terms

Acceptance section with single CTA (Sign & Return / Approve to Start), concise Terms, Risks & Mitigation, Why Us proof points, and Common Concerns rebuttals

Fillable placeholders for client_name, start_date, timelines/milestones, proof_points, objections, and primary CTA

How to Use

1Provide required inputs exactly: client_name, offer_summary, target_icp, channel_and_stage, timeline_and_milestones (include start_date and named milestones), proof_points, objections, and cta.

2If any required input is missing, the generator will pause and ask up to three targeted clarification questions â€” do not proceed until those are answered.

3Paste the inputs into ChatGPT using the supplied prompt blueprint; receive a ready-to-send one-page SOW in Markdown (~350-450 words).

4Review and replace placeholders (client_name, start_date, milestones) with final values; use the single CTA as the approval action and do not add competing CTAs.

Tip â€” Keep proof & objections concise

Supply 2 short, factual proof points (metrics or brief case notes) and 2-3 common objections with crisp rebuttals. The generator repeats only what you provide â€” concise inputs produce concise, high-impact SOWs.

Works Best With

Works best with these inputs and use cases

Complete ICP details and at least one current campaign or example asset to mirror tone and formatting

Clear start_date and three milestone dates (kickoff, draft delivery, final delivery) to enforce acceptance windows

Concrete deliverable list (counts/types) and 1-2 proof metrics or case summaries to appear verbatim in the 'Why Us' block

Prompt Template


# Revenue Copy Prompt Blueprint (Conversion & Sales)

## Goal
- Produce a concise, one-page Statement of Work / Proposal that makes the client sign or approve next-step (single, measurable CTA: "Sign & Return" or "Approve to Start"). The SOW must lead to a clear decision within the specified timeline and remove negotiation friction.

## Inputs
- Required: {{client_name}}, {{offer_summary}}, {{target_icp}}, {{channel_and_stage}}, {{timeline_and_milestones}}, {{proof_points}}, {{objections}}, {{cta}}.
- If any required input is missing or ambiguous, the generator must pause and ask up to three targeted clarification questions before drafting (do not guess dates, pricing, or client-specific claims).

## Prompt
Use the exact prompt below (copy-paste) to generate the one-page SOW. It must output sections in the order and format specified in "Output Format". Enforce concrete claims, specific deliverables, measurable milestones, explicit acceptance criteria, and direct responses to common objections.

Copy-paste prompt:
Produce a concise, client-ready, one-page Statement of Work / Proposal for this engagement. Use the inputs exactly as provided:
- Client: {{client_name}}
- Project summary / offer: {{offer_summary}} (include primary benefit and what you will deliver in plain language)
- Target audience / buyer: {{target_icp}}
- Channel & funnel stage: {{channel_and_stage}} (e.g., "B2B discovery â†’ proposal", "inbound demo follow-up")
- Timeline & milestones: {{timeline_and_milestones}} (present as a short chronological list including start_date and named milestones)
- Proof points: {{proof_points}} (short bullets: metric-based results, logos, or short case summaries)
- Common objections & quick rebuttals: {{objections}} (format: objection â†’ 1-2 sentence factual rebuttal)
- Primary CTA to accept: {{cta}} (single line: e.g., "Sign & Return to approve")

Draft rules:
1. Produce a single-page SOW in professional tone, max ~350-450 words, formatted with clear headings and short bullets.
2. Header: include professional proposal header with client name, project title (from offer), and start_date (from timeline).
3. Scope (one short paragraph, 2-3 sentences): define what is IN scope and one sentence of what is OUT of scope.
4. Deliverables: list exactly 3 bullet deliverables. Each bullet: deliverable name â€” one measurable outcome (e.g., "Deliverable â€” reduces X by Y% / delivers Z output").
5. Timeline & Milestones: render the {{timeline_and_milestones}} as 3-5 dated milestones with owners and acceptance criteria for each.
6. Pricing: present two clear pricing tiers (Tier A â€” Core Scope; Tier B â€” Core + Accelerated/Expanded). Give: fixed price, delivery window, and 2-line explanation of what differs. Include payment terms (e.g., 50% deposit, remainder on delivery).
7. Acceptance & Next Steps: a single, explicit acceptance CTA using {{cta}} and instructions for sign/return method and timeline for acceptance (e.g., approve within 7 business days).
8. Terms summary: 3 short bullets covering cancellation, change requests, and confidentiality. No full legal boilerplateâ€”keep it client-facing and concise.
9. Risks & Mitigation: 2-3 short risk bullets and specific mitigation steps.
10. Objection handling: include 2-3 one-line rebuttals drawn from {{objections}}, placed under a heading "Common Concerns".
11. Proof placement: insert the most compelling 2 proof points from {{proof_points}} under "Why Us".
12. Tone & constraints: remove marketing fluff and cliches. Use plain, precise language. Do not invent results or logos â€” only repeat what's in {{proof_points}}. One primary CTA only; do not include links or multiple CTAs.

If any required input is missing, ask up to three targeted questions to obtain the missing item(s) before generating the SOW.

## Output Format
Produce the SOW document in this strict section order with these headings (exact wording and order):
1. Proposal Header
2. Scope
3. Deliverables
4. Timeline & Milestones
5. Investment (Pricing Tiers)
6. Acceptance & Next Steps
7. Terms Summary
8. Risks & Mitigation
9. Why Us (Proof)
10. Common Concerns

- Include an "Assumptions" block ONLY if any required input was not provided and you had to infer something; if used, label it "Assumptions" and list any inferred values succinctly.
- Keep the entire output to one page equivalent (concise paragraphs and bullets, ~350-450 words).

## Guardrails
- No hype or generic cliches (ban phrases like "industry-leading", "best-in-class", "game-changer").
- Claim hygiene: do not fabricate metrics, testimonials, or client names. Use only items from {{proof_points}}.
- One primary CTA: use only the {{cta}} for acceptance; do not present multiple competing CTAs.
- Pricing must be presented as fixed amounts or clear ranges; avoid vague "starting at" without concrete numbers.
- If objections cannot be answered from provided {{objections}}, present a factual next-step (e.g., "We'll provide a reference call" or "We will scope a pilot").

## Examples
Headline excerpt (style example):
Proposal Header
- Acme Co. â€” Website Conversion Optimization (Start: 2026-02-15)

Proof block excerpt (style example):
Why Us
- Case study: 18% lift in checkout conversion for a SaaS client (6-month A/B test).
- Reference: On request, contact details provided after NDA.

Variables

Usage Notes

Not for

â€¢ Replacing full legal contracts or master services agreements (this is a concise SOW/proposal, not a contract).

â€¢ Complex multi-phase programs that require >1 page of detailed scope, budgets, or legal terms.

â€¢ Making regulatory, medical, or financial compliance claims â€” do not use this to assert regulated guarantees.

Do not include

â€¢ Marketing fluff, vague 'industry-leading' superlatives, or invented metrics.

â€¢ Multiple competing CTAs or links â€” the prompt enforces one primary acceptance CTA only.

â€¢ Full legal boilerplate â€” the Terms Summary is concise and client-facing, not a substitute for counsel.

One-Page SOW / Proposal Template

Creates a production-ready, ~350-450 word one-page Statement of Work in Markdown that includes header, scope, exactly 3 deliverables, 3-5 dated milestones with owners & acceptance criteria, two fixed pricing tiers, single acceptance CTA, short terms, risks, proof, and objection rebuttals.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

Auto-fill & personalize from your inputs

AI-assisted edits: tone, structure, constraints

Attach context so outputs stay consistent

Iterate and save versions

What you'll get

Output format

Markdown

Best used when

When working on template or detailed.

Avoid when

Replacing full legal contracts or master services agreements (this is a concise SOW/proposal, not a contract).

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Client Name