Worked example — a small-team SaaS workspace

First PublishedMay 24, 2026Last UpdatedMay 25, 2026ByAtif Alam

This is what the Workbook looks like filled in for a hypothetical product — the same “small product/engineering teams (1-10) at early-stage SaaS companies” example used in the Strategy chapters, now extended through Marketing, Sales, Customer Success, and Operate.

Treat this as an illustration of shape, not a template to copy. Your ICP, channels, motion, and metrics will look different — but the structure of the answers and the level of specificity are what to mirror.

The fictional product: a unified workspace that lets small product/engineering teams run their whole shipping workflow in one place, instead of stitching together free tiers of three or four point tools.

Phase 1 — Strategy

Filled in verbatim from the Strategy chapters — the through-line starts here.

1a. ICP

ICP: Small product/engineering teams (1-10 people) at early-stage SaaS
     companies experiencing slow time-to-value with their current point
     solutions, currently piecing together free tiers of multiple tools,
     with a champion empowered to install and pay monthly.

We recognize a fit by:   active product usage with real traffic; visible
                         team collaboration; already pays for 2+ SaaS tools;
                         single-decision-maker setup.
We deliberately exclude: pre-product teams with no users; enterprise with a
                         dedicated procurement team; free-tier-only hunters
                         chasing watermark-free outputs.
Primary persona:         the team lead who measures everything in
                         "does this save time without adding workflow?"

Reference: Strategy: ICP.

1b. Positioning

For small product/engineering teams at early-stage SaaS companies
who lose hours stitching together point tools to ship a single workflow,
[Product] is a unified workspace
that runs the whole workflow in one place, with no glue code.
Unlike piecing together free tiers of three separate tools,
[Product] is built around the team's actual workflow
— proven by [X]% reduction in cycle time.

Value prop: “Ship the whole workflow from one tool — not three. No glue code, no context-switching.”

Reference: Strategy: Positioning.

1c. Pricing & Packaging

Value metric:    active seats × workflows run / month
Model:           hybrid — per-seat base + usage overage on workflows
Entry plan:      Free — 3 seats, 100 workflow runs/mo (caps capacity, proves value)
Target plan:     $29/seat/mo — unlimited workflows; the anchor
Premium plan:    $79/seat/mo — SSO, audit log, priority support
Upgrade trigger: team hits the 100-runs/mo cap or adds a 4th teammate

Reference: Strategy: Pricing & Packaging.

Phase 2 — Marketing

The audience reads product blogs and lives in developer-adjacent communities. Paid ads convert poorly here; content, community, and SEO around the specific workflow they hate today are the proven winners.

2a. Audience & message

Primary segment:  small product/engineering teams at early-stage SaaS
Buyer / user:     team lead (buyer) + engineers and PMs (users)
Core message:     "Ship the whole workflow from one tool — not three"
Proof points:     (1) cycle-time reduction from case studies;
                  (2) public usage numbers from design-partner teams;
                  (3) a 60-second demo of the workflow end-to-end

2b. Channel mix

Three channels picked; everything else explicitly not invested in for the first 90 days.

[x] Content / SEO       — workflow-keyword blog (e.g. "how to X without glue code")
                          drives ICP-shaped trials at near-zero CAC.
[x] Social / community  — show-the-work posts in 3-4 communities the persona lives in
                          (HN, dev forums, a few Slack/Discord groups).
[x] Partnerships        — integrate with one widely-used adjacent tool and co-market
                          the use case.
[ ] Paid                — skipped at launch; CAC math doesn't work at $29/seat
                          until activation rate proves out.
[ ] Outbound / ABM      — skipped; ICP is too long-tail and small-ACV for named-account.
[ ] PR                  — episodic only (one launch beat); not a steady channel.
[ ] Referrals           — wait until activation is solid (Phase 4).

2c. KPI baseline

Awareness:    weekly organic traffic to top-3 workflow-keyword pages
Activation:   signup → first-workflow-run rate (proxy for top-of-funnel quality)
Conversion:   free → paid % at day 14 and day 30
Efficiency:   blended CAC and CAC-payback months (target: <12 months)
Brand:        share of voice in target communities (mention count + sentiment)

Reference: Marketing.

Phase 3 — Sales

PLG-led with a thin sales-assist motion for teams that hit the seat threshold. No traditional pipeline or BANT — qualification is usage signals, not budget questions.

3a. Motion choice

Primary motion:    product-led with sales-assist
If hybrid, split:  pure self-serve <5 seats; sales-assist invitation at 5+ seats
                   or workflow cap; named-account for >25 seats
Why this motion:   ICP is small (<10), buyer = user, and the workflow value is
                   visible in-product within an hour — that's tailor-made for PLG.
                   Sales-assist exists only to unblock the small fraction of
                   accounts where seat math justifies a human conversation.

3b. Qualification (usage-signal model, not BANT)

Value-realized: ≥10 successful workflow runs in trial period
Limit-pressure: hit the 100-runs/mo cap OR added a 4th seat
Intent:         visited /pricing twice or opened the upgrade modal
Disqualify if:  single-user account after 30 days (not a team workflow);
                <3 workflow runs in 14 days (not activated, no leverage to assist).

3c. Pipeline stages (collapsed to 3)

1. PQL          — entry: usage signal above clears the bar
2. Trial+assist — entry: sales-assist call accepted; demoing team workflow
3. Paid         — entry: subscription created; exit-won
   (Lost — exit: account fails to convert in 14 days post-trial; recycle to nurture)

3d. Targets baseline

Annual revenue target: $1.2M new ARR (year 1)
Average deal size:     ~$2,500 ACV (avg 7 seats × $29 × 12mo)
Required wins:         ~480 paid accounts / year (40/month)
Assumed conversion:    free → paid at 4% (PLG benchmark midpoint)
Required signups:      ~12,000 signups / year (1,000/month)
Pipeline coverage:     N/A in pure PLG; coverage = sign-up volume, not opps

Reference: Sales.

Phase 4 — Customer Success

The whole product wins or loses on activation rate and seat expansion. CS is built into the product surface (in-app prompts, lifecycle email), with a single CSM owning enterprise accounts only.

4a. Activation definition

Activation = completed 3 successful workflow runs in the first 7 days

Causal:  cohorts who hit activation retain at 4× the rate of those who don't
Early:   measurable inside the first session in most cases
Single:  one observable event — not a "5 things in 30 days" composite

4b. Onboarding flow

Step 1: Sign up (Google SSO) — account created in <30 seconds
Step 2: Connect one source tool (GitHub or Linear) — auto-detected
Step 3: Run the templated starter workflow — first value moment
Step 4: Receive day-2 prompt to run a second workflow on real data
Step 5: Invite a teammate (in-app prompt at day 4 if not yet invited)

4c. Retention baseline

Logo churn target:    <3% / month at year 1 (small accounts churn more)
Revenue churn target: <2% / month (offset by expansion)
GRR target:           >85% annual
NRR target:           >110% annual (expansion-driven; seats grow as teams grow)

4d. Expansion path

Upsell trigger:    team hits the 100-runs/mo cap on Free,
                   OR adds a 4th seat (Free is capped at 3)
Cross-sell motion: not in year 1; one product, deep
Pricing lever:     seats (teams grow), then workspace-tier upgrade at 10+ seats

Reference: Customer Success.

Phase 5 — Operate

Light operating cadence — small team, so the rhythm is mostly automated dashboards plus a single weekly meeting.

5a. Operating rhythm

Weekly:    15-min pipeline + activation review
           (signups, activation rate, free→paid %, paid churn)
Monthly:   funnel cohort read; CAC by channel; NRR/GRR trend
Quarterly: ICP, positioning, and pricing kill/keep/tighten review
Annually:  budget and motion review (still PLG primary? sales-assist ROI?)

5b. Iteration trigger

Re-open ICP when:         activation rate dips for new signups in a segment,
                          OR churn concentrates among >10-seat accounts
                          (signal that ICP has crept up-market without us noticing)
Re-open positioning when: win-loss reasons shift toward "wrong category"
                          OR prospects mis-describe what we do
Re-open pricing when:     >25% of paid accounts cluster on the highest tier
                          (signal we're under-pricing the high end), OR support
                          load is heaviest on the lowest tier (signal the entry
                          tier is too generous)

Back to the empty template

The empty Workbook lives at /library/workbook/. Open it in a new tab and start filling in your own plan, using this example to gauge specificity level. Most teams’ first pass is far more vague than this — that’s normal; the iteration is the point.