The 90‑Day Productized Offer Pack

Use this as a public, single‑page artifact that replaces proposals. Keep it to one screen. Link it in your bio, pin it in outreach, and send it after every discovery call.

• Offer Name: [OFFER NAME]
• One‑line Promise (with a number): [WE DELIVER X IN Y DAYS WITH Z% ACCURACY]
• Who It’s For: [ICP ROLE] at [INDUSTRY/NICHE] companies with [TOOL STACK] and [TEAM SIZE/REVENUE RANGE]
• Pain/Trigger: [PRIMARY TRIGGER THAT STARTS THE BUY]
• Outcomes & Proof:
  • Outcome 1: [METRIC + BASELINE → TARGET] (e.g., “Reply rate from 1.2% → 4.0% in 30 days”)
  • Outcome 2: [SECONDARY METRIC]
  • 3x Snapshots: [CLIENT/ANON], [BEFORE → AFTER], [QUOTE OR METRIC]
• Deliverables (fixed scope):
  • [DELIVERABLE 1] — [FORMAT] — [SIZE/TIMEBOX]
  • [DELIVERABLE 2] — [FORMAT] — [SIZE/TIMEBOX]
  • [CADENCE] (e.g., “2 queued requests at a time; 1–2 business‑day turnaround”)
• 30/60/90 Plan (high‑level):
  • Day 0–30: [SETUP + PILOT WITH 3 CLIENTS]
  • Day 31–60: [INSTRUMENT + REFINE + PRUNE]
  • Day 61–90: [RAISE PRICE/LOCK SCOPE + MOAT MOVES]
• Pricing (simple, public):
  • Plan A: [PRICE USD/MO] — includes [KEY LIMITS]
  • Optional Setup: [SETUP FEE USD] (covers [DATA/APPS/WORK])
  • Billing: [MONTHLY/QUARTERLY], auto‑renew; pause available [YES/NO]
• SLAs (enforced):
  • Response Time: < [HOURS] business hours via [CHANNEL]
  • Turnaround: [DAYS/HOURS] per [REQUEST TYPE]
  • Coverage Window: [HOURS + TIME ZONE] (nomad‑friendly; state exceptions)
  • Request Limits: [# CONCURRENT] in queue; [#/WEEK]
• Acceptance Criteria (Definition of Done):
  • [ACCEPTANCE TEST #1]
  • [ACCEPTANCE TEST #2]
  • [QUALITY BAR/QA STEP]
• Exclusions (out‑of‑scope by design):
  • [NOT INCLUDED #1] (e.g., “Custom app development >5 steps or new vendors”)
  • [NOT INCLUDED #2]
• Requirements from Client (before start):
  • Access: [APPS/ACCOUNTS/SEATS]
  • Data: [CSV FIELDS/API KEYS/SAMPLE SIZE]
  • Point Person: [NAME/ROLE]
• Model Costs & Guardrails:
  • Model Stack: [GPT‑4o / Claude / Open‑source LLM / Embeddings]
  • Ceiling: [USD/MO MAX MODEL SPEND] or [USD/REQUEST]
  • Fallback Model: [PROVIDER]
• Refund/Guarantee (simple, enforceable):
  • If [TIME‑TO‑VALUE ≤ DAYS] not met and we miss SLA [X]% in first [N] days → [PARTIAL/PRO‑RATA REFUND] or [FREE EXTENSION]
• Compliance & Data Handling:
  • Data Residency: [REGION], Retention: [DAYS], PII Policy: [LINK/ONE LINE]
• How To Start:
  • Step 1: Book: [LINK]
  • Step 2: Intake form: [LINK]
  • Step 3: Kickoff (async by default): [YES/NO]
• Contact: [EMAIL] • [CALENDAR LINK]

List every request type you’ll see. Decide included vs not, timeboxes, inputs, and change‑order triggers. Keep this internal; mirror the highlights publicly on the one‑pager.

Request Type: [NAME]

• Included: [YES/NO]
• Size/Timebox: [HOURS] or [TOKENS/CALLS] (e.g., “≤5 Make steps” or “≤1M tokens”)
• Turnaround SLA: [DAYS/HOURS]
• Max Frequency: [#/WEEK]
• Required Inputs: [FIELDS/ACCOUNTS/EXAMPLES]
• Output Format: [DOC/LOOM/JSON/FIGMA]
• Revisions: [#] within [DAYS]
• Edges We’ll Decline: [EDGE CASES THAT CREATE VARIANCE]
• Not Included (on purpose): [LIST]
• Change‑Order Trigger: [WHEN THIS HAPPENS → NEW SOW/ADD‑ON]
• Escalation Path: [HOW TO HANDOFF/WHO APPROVES]

Example Rows (customize or delete):

• Automation Build ≤5 steps (Make/Zapier)
  • Included; 2‑day SLA; Max 2/week; Inputs: [App creds, sample record]; Output: [Screenshot + Loom + map]; Revisions: 1; Edges: “Net new vendor,” “OAuth not available” → Decline; Change‑Order if >5 steps.
• LLM Email Reply Assistant v1 (prompt + 3 variants)
  • Included; 2‑day SLA; Inputs: [20 labeled examples, brand voice]; Output: [Prompt pack + JSON schema]; Revisions: 1; Edge: “Cold outreach net‑new ICP” → Decline.
• Data Enrichment (≤500 rows via API)
  • Included; 3‑day SLA; Inputs: [CSV with columns], Output: [CSV + data dictionary]; Revisions: 0; Change‑Order if >500 rows or new provider.

Scope Boundaries Summary (copy to one‑pager):

• We do: [TOP 5 INCLUDED]
• We don’t: [TOP 5 EXCLUDED]
• Queue Rules: [# IN QUEUE], [#/WEEK], [CUT‑OFF TIME/ZONE]
• Holiday/Travel Policy: [NOTICE PERIOD + COVERAGE PLAN]

Track these 10 KPIs weekly for 90 days. Set targets now. Mark Pass/Fail and write the next action. Default targets are starting points—tune by week 4.

How to use:

1. Create a sheet with one row per week. 2) Fill Actuals every Monday. 3) If any Guardrail is red, pause sales or prune a client before adding work.

Weekly Row Template

• Week Of: [YYYY‑MM‑DD]
• Pipeline
  • Demos Booked: [#] (Target: [3])
  • Win Rate: [# Won ÷ # Qualified] (Target: [25%])
  • Sales Cycle: [Median days to close] (Target: [≤14])
• Delivery
  • Time‑to‑Value (TTV): [Median days to first accepted output] (Target: [≤7])
  • SLA Hit Rate: [On‑time requests ÷ total] (Target: [≥95%])
  • Utilization: [Billable hrs ÷ capacity] (Target: [70–85%])
  • Defect Rate: [Rework needed ÷ outputs] (Target: [≤5%])
• Finance
  • Revenue: [$]
  • Direct Costs: [$ MODEL + $ CONTRACTOR + $ TOOLS]
  • Gross Margin %: [(Revenue − Direct Costs) ÷ Revenue] (Target: [≥60%])
  • Model Spend per Client: [$] vs Ceiling: [$/mo or $/request] (Guardrail: [≤80% of ceiling])
• Retention
  • Churn %: [Lost clients ÷ start‑of‑week clients] (Target: [≤4%/mo])
  • Pause Rate %: [Paused ÷ active] (Target: [≤8%/mo])
  • Expansion MRR: [$] (Target: [≥5%/mo])
  • NPS/CSAT: [SCORE] (Target: [≥40 NPS or ≥4.3/5])
• Decision
  • Week Result: [PASS/FAIL]
  • Notes → Next Action (one line): [WHAT YOU’LL CHANGE BY FRIDAY]

Guardrails (automatic FAIL if breached)

• Two consecutive weeks with Gross Margin < [60%]
• SLA Hit Rate < [90%] any week
• Model Spend hits [>90%] of ceiling for [2] clients in a week
• TTV > [10] days for two weeks in a row

30/60/90 Gates (write yes/no + action)

• Day 30: [ICP validated], [3 paying pilots], [TTV ≤ 7 days], [Scope matrix holding]. Action if miss: [PRUNE/REPRICE/REFORMAT].
• Day 60: [GM ≥ 60% for 3 weeks], [SLA ≥ 95%], [Churn ≤ 4%], [One expansion play proven]. Action: [LOCK PRICE + PUBLISH CASES].
• Day 90: [Raise price or add annual], [Moat moves started], [Spinout decision noted: micro‑SaaS or template license Y/N].

Run this before you add a client, raise price, or change scope. Check every box. If you can’t check it, write the fix or say no.

Operational Guardrails

• SLA doc published to clients (response: < [HOURS], turnaround: [HOURS/DAYS])
• Acceptance tests defined for each deliverable: [TEST #1], [TEST #2]
• Request queue rules visible: [# CONCURRENT], [#/WEEK], [HOW TO SUBMIT]
• Revision cap set: [#] within [DAYS]
• Change‑order trigger written and enforced: [RULE]
• Blacklist of out‑of‑scope asks posted: [TOP 5]

Financial Guardrails

• Model spend ceiling set at [$ / mo] and [$ / request]
• Auto‑alerts at [80%] of ceiling to Slack/Email
• Unit economics sheet live: [PRICE], [DIRECT COST/UNIT], [GROSS MARGIN%]
• Pause rule documented (when GM falls below [X%] or SLA < [Y%])

Risk & Resilience (Lisbon‑adjacent)

• Offline capture kit (templates + checklists) works on 3G and mobile
• Fallback model/provider defined: [NAME]
• Data handling policy: retention [DAYS], deletion on cancel [YES/NO]
• DPA/SCCs available on request [YES/NO]
• Incident playbook for SLA breach (> [HOURS] late) with credit/refund rule
• Travel/holiday coverage calendar shared; backup operator named

Client Psychology

• “What we don’t do” email snippet ready
• “How to get great results” onboarding page (inputs, examples, response norms)
• First‑value quick win identified for Week 1: [DELIVERABLE]

Go/No‑Go

• If any Guardrail fails, action by [DATE]: [PRUNE CLIENT / REPRICE / NARROW SCOPE] before new sales.

Score today, then pick one concrete "next move" per category. Aim for ≥3 in two categories by Day 90.

Scoring: 0=none, 1=weak, 2=early, 3=meaningful, 4=strong, 5=enduring advantage.

A) Switching Costs [0–5]

• Evidence: [# ACTIVE AUTOMATIONS], [# USERS TRAINED], [WEEKLY DEPENDENCIES]
• How we embed: [TEMPLATES IN TOOL], [WORKFLOW INSIDE CLIENT STACK]
• Next Move: [E.G., SHIP NATIVE CONNECTOR OR IN‑PRODUCT TEMPLATE]

B) Process Power [0–5]

• Evidence: [SOP COUNT], [QA HARNESS], [PROMPT LIBRARY VERSION]
• High‑variance steps eliminated: [LIST]
• Next Move: [AUTOMATE QA / GOLDEN SETS / CHECKLIST INTAKE]

C) Cornered Data/Resource [0–5]

• Evidence: [UNIQUE DATASET SIZE], [PERMISSIONS], [WHY OTHERS CAN’T GET IT]
• Next Move: [CREATE EMBEDDINGS STORE / LABEL 1K EXAMPLES]

D) Distribution (Owned) [0–5]

• Evidence: [NEWSLETTER SUBS], [SEO PAGES TOP‑3], [MICRO‑DEMO VIEWS]
• Next Move: [PUBLISH TEMPLATE DEMO FOR TOP QUERY]

E) Branding/Trust [0–5]

• Evidence: [BRAND SEARCH VOL], [NPS], [REFERRAL %]
• Next Move: [CASE STUDY WITH METRICS + LOGO PERMISSION]

F) Scale Economies [0–5]

• Evidence: [COST/UNIT VS VOLUME], [MODEL DISCOUNTS/COMMIT]
• Next Move: [NEGOTIATE RATE / BATCH JOBS / CACHING]

G) Counter‑Positioning [0–5]

• Evidence: [WE REFUSE CUSTOM X], [WE PROMISE Y OTHERS WON’T]
• Next Move: [PUBLICLY DROP LOW‑MARGIN FEATURE]

Lisbon Test (Nomad Resilience) — Pass/Fail + Owner

• Works on flaky Wi‑Fi/3G (mobile forms, low‑bandwidth Looms) — Owner: [NAME]
• Async kickoff (no live call required) — Owner: [NAME]
• Single‑pane dashboard (client + internal) — Owner: [NAME]
• Fallback AI model/provider configured — Owner: [NAME]
• Human backup operator on deck (SLA‑trained) — Owner: [NAME]
• Offline playbook printable (PDF) — Owner: [NAME]
• Payment retry + pause function live — Owner: [NAME]
• Daily restore point for prompts/configs — Owner: [NAME]
• Security basics (2FA, least‑privilege, vault) — Owner: [NAME]
• Data deletion on cancel within [DAYS] — Owner: [NAME]