Workflows / Templates / SaaS docs and use cases

The SaaS docs and use cases template: from one keyword list.

A SaaS keyword list holds two jobs: how-to searches that belong in the docs, and problem searches that belong on use case pages. This workflow template plans the whole list, then splits it by format and writes two sets of briefs, Docs and Use cases, each with its internal links planned.

Every template asks before it spends and never publishes.

Who it is for, and what starts a run.

Who it is for

SaaS content and product marketing teams who own both the docs and the marketing site, and keep finding a help article and a landing page aimed at the same search.

Agencies with software clients, where the docs team and the marketing team need separate files.

What starts it

Manual. A person presses Run and uploads or pastes the keyword list.

At Use template you can take keywords from Ahrefs instead of a file.

Inside the template, block by block.

Each block is a step you can open in the editor. Every step keeps a receipt: inputs, outputs, evidence, provider, cost and timings.

  1. Import keywords

    Reads the list from a file, a paste or Ahrefs.

  2. Engine group

    Plans the whole list: Fetch SERPs, Search volume, Cluster by SERP overlap, Score scope and format, Route around owned pages, Park weak pages and Labs secondary keywords. Score scope and format reads each page's format from its top 10.

  3. If/else

    Sends how-to pages down the Docs branch and every other page down the Use cases branch.

  4. Generate brief (each branch)

    Writes briefs for the top 10 pages on each branch.

  5. Plan internal links (each branch)

    Plans internal links for each briefed page, right before the export.

  6. Export Markdown (each branch)

    Exports each set as Markdown, tagged Docs or Use cases.

  7. Notify by email (each branch)

    Emails the workflow owner when the Docs briefs are exported, and again for the Use cases briefs.

Branches never join, so each branch ends with its own export and its own email. That keeps the docs team's file and the marketing team's file apart.

Before it spends, it asks.

Approvals

A person starts each run and approves its estimate. A Manager above the owner approval line sees Request approval instead.

A run waiting for approval expires after 7 days. No standing approval is needed.

What it costs

SERP fetches and keyword data use your DataForSEO key. Page classification and up to 20 briefs use your AI provider key.

The estimate lists each spending block, your DataForSEO balance and your monthly cap after the run, before anything is fetched.

What you get when the run finishes.

  • A page plan for the whole list, with receipts per decision.
  • Up to 10 Docs briefs and up to 10 Use cases briefs.
  • Internal links planned for every briefed page.
  • Two Markdown exports, tagged Docs and Use cases.
  • Two emails to the workflow owner, one per export.

No workflow can publish to a site. Drafts and tasks wait for a person. Spending waits for an approval, and every run checks your monthly cap first.

Read the workflow docs

Related. Templates and pages that pair with this one.

SerpDad for SaaS and docs

Docs, blog and landing pages that each own a query.

Internal links

How SerpDad plans links between the pages in a plan.

Keyword pile to signed articles

Carry the briefs on to drafts signed by name.

Content briefs

What a brief holds and where its facts come from.

Briefs docs

Brief settings, sections and exports.

All workflow templates

Twelve ready-made workflows, grouped by job.

Docs for the how-to.
Use cases for the rest.

Your first plan is free up to 1,000 keywords, with briefs for the top 5 pages. No card needed.