SaaS Use-Case Page Brief Template

Use-Case Page Brief (fill-in)

When to use: Job, trigger and one row per workflow step, each tied to a shipped capability, screenshot and product sign-off.

Use-case page brief

One brief per page. One job, one trigger, one workflow, one activation CTA. Fill the header first, then one table row per workflow step.

Brief header

• Job (buyer's words): [When [situation], I want to [task], so I can [outcome]]
• Who it is for: [role] at a [team type and size]
• Trigger: [the event that starts the job, such as a new lead, an accepted quote, month end]
• Target query and URL: [[category] for [job]] / [/use-cases/[job]/]
• Activation CTA: [CTA text] that opens [the screen where step 1 happens]
• Activation event: [first_[job]_completed]

Per-row detail (fill for every step)

• Manual or automatic: [user does it / product does it on its own]
• Release status: [Generally available / Beta, labelled on the page]
• Help doc or release note link: [URL]
• Screenshot caption and alt text: [what the user sees at this step]
• Known limit to state on the page: [integration, volume or plan gate]

Next action

• Writer: [name] - action: [draft the page from this brief] by [date]
• Product owner: [name] - action: confirm every row is shipped and sign the Verified column
• Designer or PMM: [name] - action: capture screenshots SS-01 to SS-0[n] from a live account with demo data

Completion check

• The job and trigger are in the buyer's words, taken from calls or tickets.
• Every workflow step names a capability the product ships today.
• No step says "automatically" unless the product does it with no manual click.
• Every row has a screenshot ID and a product sign-off with a date.
• The CTA opens the screen where step 1 happens and fires the named event.

Job and Trigger Builder

When to use: Turn sales and support notes into one job statement and one trigger worth a page.

Start with one job and one trigger

A use-case page answers one question: can this product do my job? Pick the job from sales calls, demos and support tickets, not from the feature list.

Job statement: When [situation], I want to [task], so I can [outcome].

Trigger statement: This starts when [event] happens, usually [how often].

Good job, weak job

Pick the job worth a page

• It comes up again and again on sales or support calls.
• It has a clear trigger and a clear finish.
• The product handles every step today, with or without a manual click.
• People search for it. Check queries like [category] for [job] and [task] software.

Find the phrasing buyers search with Keyword Research, then check which page types rank for it in the SERP Analyzer.

Building the wider plan first? The SaaS SEO Strategy Template covers the whole site. This brief covers one use-case page.

Shipped Capability and Screenshot Checklist

When to use: Let product confirm each step is live today, and capture screenshots that match the page.

Product sign-off: shipped or not?

The page can only describe what a new user can do today. Product, not marketing, signs each row.

Checks per step

1. Open a fresh account on the cheapest plan the page names.
2. Do the step yourself, following only the page copy.
3. If you needed a setting, an add-on or support, write it on the page.
4. Link the help doc or release note in the brief.

Screenshot rules

• Capture from the live product, not a design file.
• Use demo data. No real customer names or emails.
• One screenshot per step, cropped to the action, with the step number in the caption.
• Write alt text that says what the screen shows, not a list of keywords.
• Put each image next to the step it shows. Google uses nearby text to understand images.
• Re-shoot after any UI change and update the date in the brief.

Why this matters

The FTC expects a reasonable basis for an ad claim before it runs. A capability on your page is a claim, so the sign-off is your record.

Activation CTA Planner

When to use: Point the CTA at step 1 of the workflow and name the event that proves the job got done.

The CTA starts the workflow

A use-case page should not end at a generic signup. The CTA should drop the user into step 1 of the job the page just showed.

Fit checks

• The CTA text uses the same verb as the job statement.
• Click it as a new user. You should land on step 1, not a dashboard tour.
• If a step needs an integration, the CTA flow asks for it early.
• The activation event fires when the job is done, not on signup.

Test CTA and H1 options with the Headline Analyzer. Need the product flow built? See SaaS development or book a free consultation with Anatolii Ulitovskyi.

Page Outline Builder

When to use: Turn a verified brief into the section order for a use-case landing page.

Page outline from the brief

1. H1 and intro: the job in the buyer's words and who it is for.
2. The trigger: two or three sentences on the moment the job starts and what goes wrong today.
3. Workflow steps: one block per verified row, with its screenshot and the feature name used in the product.
4. Limits and plans: what each plan includes for this job and any manual step.
5. Proof: a real customer quote or result you have permission to use, about this job only.
6. FAQ: setup time, integrations, data import, who can use it.
7. Activation CTA: repeated after the steps and at the end.

On-page basics

• Title and H1 name the job, not the product category alone.
• Link to the help docs for each step and to one or two related use cases.
• Link to the pricing page where plan gates are mentioned.
• Add a visible "Last checked by product" date.

Turn the outline into a writer brief with Content Brief. Before launch, run the page through the Website Audit to catch broken links and missing alt text.

Writing for buyers switching from a rival tool instead? Use the Alternatives Page Writing Brief Template.

Spreadsheet Header (CSV)

When to use: A paste-ready header row and allowed values to run briefs in Google Sheets or Excel.

Paste-ready spreadsheet header

Paste this row into cell A1 of Google Sheets or Excel, then split text to columns by comma. One row per workflow step.

page_url,job_statement,trigger,step_number,user_action,capability_name,automation,release_status,plan_gate,help_doc_url,screenshot_id,screenshot_date,verified_by,verified_date,activation_cta,activation_event,owner,status

Allowed values

• automation: manual, automatic, mixed
• release_status: ga, beta, flagged, roadmap
• status: draft, in-review, verified, live, re-check

Sheet tips

• Highlight any row where release_status is flagged or roadmap. It cannot go live.
• Highlight rows with an empty verified_date.
• Set status to re-check when the product ships a UI change.
• Filter by page_url to review one page at a time.

Worked Example (fictional field-service SaaS)

When to use: A filled-in brief for an invented scheduling tool, with one cut automation claim and one CTA fix.

Worked example: Kelpmoor field-service software

Example only. Kelpmoor is an invented SaaS product. Its features, people, URLs and dates below are made up to show a filled-in brief.

• Job: When a customer accepts a quote, I want it on a technician's schedule without retyping it, so the job starts this week.
• Who: office managers at HVAC and plumbing firms with a small dispatch team
• Trigger: a customer accepts a quote online
• URL: /use-cases/quote-to-job/
• Activation CTA: "Convert your first quote", opening /app/quotes?status=accepted
• Activation event: first_quote_converted

What product review changed

• The first draft said "Kelpmoor assigns the nearest technician automatically". That feature is on the roadmap, not shipped.
• Step 3 was rewritten as a manual drag on the dispatch board, with its own screenshot.
• The draft CTA was "Start free trial" and landed on a dashboard. It now opens the accepted quotes list.
• The page now says the dispatch board needs the Team plan, next to step 3.

Why this works

• A new user who follows the page can do every step on day one.
• The CTA starts the job the page promised, so the activation event measures the page.
• When auto-assign ships, the team adds it as a new row and re-runs the sign-off.