Checkgrow

Knowledge Center

Use Cases

Document the concrete situations customers use your product in, with a structured 9-field schema the AI uses in campaigns and briefings.

Overview

Use Cases capture the concrete situations customers use your product in — who is doing what, why, and what success looks like. Each use case follows the same 9-field schema, so the AI always has structured, comparable answers instead of loose notes.

Use cases feed campaign creation and marketing briefings, link to your Features & Items, count toward your knowledge score, and appear in the Knowledge Graph.

Structured once, used everywhere

Every use case you define becomes reusable context: campaign builders and marketing briefings pull from these fields, so a well-written use case sharpens every AI output that references it.

Image #1 — Use Cases cards with target roles, examples and keywords, plus the Add Use Case button

Who needs it

Use Cases matter to anyone who explains what your product does in the real world:

  • Marketers — ground campaign messaging in real customer situations instead of feature lists.
  • Founders and product leads — keep a single agreed record of who the product serves and the value it delivers.
  • Sales teams — answer "does this work for a company like ours?" with documented real-life examples.
  • Content writers — pull search keywords and success signals straight into articles and landing pages.

Use cases describe situations; Features & Items describe capabilities. Link the two so every feature is tied to a reason someone needs it.

How to use it

  1. Seed the page with AI CheckIf the page shows "No use cases defined yet", click AI Check. The AI generates a first set of use cases from your website and existing company knowledge — review and refine them rather than starting from a blank page.
  2. Add a use case from a descriptionClick Add Use Case and describe the situation in plain language — for example "Enterprise companies needing to automate their customer onboarding process...". The AI drafts all nine fields from your description.
  3. Or generate from documentsIn the same dialog, upload documentation instead of typing — case studies, sales decks, or process docs. The AI extracts the use case details from the file.
  4. Refine in the detail overlayOpen a use case and click Edit to change any field inline, then save. Manage the "Real-Life Examples" and "Search Keywords" lists, or use Edit with Grow to rewrite a field.
  5. Search and switch viewsUse the "Search use cases..." box to find one quickly, and the card/table toggle to switch between browsing cards and scanning a compact table.

The 9 fields of a use case

Every use case is built from the same nine fields. Filling them all gives the AI the full picture:

Use Case Name

A short, recognisable label for the situation — the name that appears on the card and in the Knowledge Graph.

Business Context

The situation the customer is in: their industry, setup, and the circumstances that make this use case relevant.

Primary Job to Be Done

The one core job the customer is "hiring" your product to do in this situation.

Target Users & Roles

Who is actually using the product here — the roles and job titles involved.

Core Value Delivered

The outcome the customer gets — the value your product delivers in this scenario.

Process Stage / Trigger

When this use case kicks in: the stage of the customer's process, or the event that triggers the need.

Success Signal

How the customer knows it worked — the measurable or observable sign of success.

Search Keywords

The terms people search when they have this problem — useful for content and campaign targeting.

Real-Life Examples

Concrete examples of customers or scenarios where this use case played out, kept as a list you can extend over time.
Image #2 — Use case detail with Business Context, Job to Be Done, Core Value and Success Signal

Campaigns — use cases feed campaign creation and marketing briefings

Features & Items — link features to the use cases they serve