On this page

The most useful user stories examples are specific ones: a named kind of user, one goal, a reason, and acceptance criteria that say when the work is done. This guide gives 12 examples for a SaaS product, from sign-up and single sign-on to billing, audit logs and an AI feature, and writes three of them out in full.

Every example here is invented for illustration. If your team ships every sprint but nobody can say why those features came first, the gap is in product management more than in writing. A fractional product manager can own the backlog and the specs behind it.

What is a user story?

A user story is a short description of something a user wants to do with a product, and why. It is a reminder to have a conversation, not a full specification: the detail comes from talking it through and from the acceptance criteria attached to it.

The Agile Alliance glossary entry on user stories traces them to Extreme Programming, where they were first described in 1998 as the way customers define project scope. The familiar sentence came later. The role-feature-reason format was invented in 2001 at Connextra, a company in the UK:

As a [kind of user],
I want [something I can do],
so that [the reason it matters].

In the same year Ron Jeffries described a story as three parts in his article "Essential XP: Card, Conversation, Confirmation" (2001). These are often called the three Cs:

  • Card: the short written text, just enough to identify the requirement and remind everyone what the story is.
  • Conversation: the discussion where the team and the customer work out the detail.
  • Confirmation: the acceptance test that shows the story was built as agreed.

The template is an aid, not a rule. The Agile Alliance describes it as training wheels that remind people to say who the work is for and why, and notes that teams often outgrow the exact wording.

12 examples of user stories for a SaaS product

The 12 examples of user stories below cover areas most SaaS products share. Each one names a specific role, one goal and a reason, and each has a single line that says when it is done.

Twelve user stories for a SaaS product, each with the condition that shows it is done
AreaUser storyDone when
Sign-upAs a new visitor, I want to create an account with my work email so that I can try the product before I talk to anyone.A verified email opens an empty workspace.
Single sign-onAs an IT admin, I want my team to sign in through our identity provider so that I control access in one place.A user removed at the provider can no longer sign in.
InvitesAs a workspace admin, I want to invite a teammate by email so that we can work on the same account.The invite works once and expires after 72 hours.
RolesAs a workspace owner, I want to give a contractor view-only access so that they can read reports without changing anything.A viewer who tries to edit is refused.
Plan upgradeAs an account owner, I want to upgrade my plan myself so that I do not wait for a sales call.The new limits apply as soon as payment succeeds.
Failed paymentAs an account owner, I want an email when a payment fails so that I can fix my card before access is paused.The email names the invoice and links to billing.
Data exportAs an analyst, I want to export a report as CSV so that I can work on the numbers in a spreadsheet.The file matches the filters on screen.
Audit logAs a security lead, I want to see who changed a permission and when so that I can answer an auditor.Each change shows who, when, and the old and new value.
NotificationsAs a project member, I want an email when I am mentioned so that I do not miss a question.One email per mention, linking to the comment.
SearchAs a support agent, I want to find a customer by email address so that I can open their account during a call.An exact email match is the first result.
AI summaryAs a support agent, I want an AI summary of a long ticket so that I can reply without reading every message.Each point links to the message it came from.
Account deletionAs an account owner, I want to delete my workspace so that my data is removed when I leave.Deletion asks for confirmation and ends sign-in access.

None of these user stories examples says how to build anything. Each leaves the design open and still gives a tester something to check, which is the balance a story is meant to strike.

User stories examples with acceptance criteria

Acceptance criteria turn a story into something a person or a test can check. The three examples of user stories with acceptance criteria below use the Given, When, Then form, which reads as plain English and can also run as an automated test.

The form comes from Gherkin, the language that the Cucumber testing tool reads. The Gherkin reference defines the three steps: Given describes the initial context, When describes an event or an action, and Then describes an expected outcome.

Example 1: inviting a teammate

Story: as a workspace admin, I want to invite a teammate by email so that we can work on the same account.

Feature: Invite a teammate

  Scenario: A valid invite is accepted
    Given I am an admin of the "Design" workspace
    When I invite "sam@example.com" as a member
    And Sam opens the invite link within 72 hours
    Then Sam joins the "Design" workspace as a member
    And the invite is marked accepted

  Scenario: An expired invite is refused
    Given an invite was sent more than 72 hours ago
    When the recipient opens the invite link
    Then they are told the invite is no longer valid
    And nobody is added to the workspace

Example 2: view-only access

Story: as a workspace owner, I want to give a contractor view-only access so that they can read reports without changing anything.

Feature: View-only access

  Scenario: A viewer can read a report
    Given Dana has the viewer role in the workspace
    When Dana opens the monthly report
    Then the report is shown

  Scenario: A viewer cannot change a report
    Given Dana has the viewer role in the workspace
    When Dana sends a request to rename the monthly report
    Then the request is refused
    And the report name is unchanged

The second scenario is the one teams forget. Hiding the edit button is not enough: the refusal has to hold when the request is sent straight to the server.

Example 3: an AI summary

Story: as a support agent, I want an AI summary of a long ticket so that I can reply without reading every message.

Feature: Ticket summary

  Scenario: A long ticket is summarized
    Given a ticket with more than 10 messages
    When the agent asks for a summary
    Then a summary of no more than 120 words is shown
    And each point links to the message it came from

  Scenario: The summary cannot be produced
    Given the summary service does not answer within 10 seconds
    When the agent asks for a summary
    Then the full ticket is shown
    And the agent is told that no summary is available

The numbers in these scenarios are examples. Yours come from the conversation with the people who will use the feature.

How user stories and acceptance criteria fit together

The story says who wants what and why. The acceptance criteria say how everyone will know it is done. In the three Cs, the story sentence is the card and the criteria are the confirmation.

The Agile Alliance describes Given, When, Then as a template that guides the writing of acceptance tests for a user story: some context, some action, and a particular set of observable consequences. The word that matters is observable. A criterion such as "the page should feel fast" cannot be observed, and "results appear within two seconds" can.

Criteria do not have to be scenarios. A short list of rules also works, and Gherkin has had a Rule keyword since version 6 that groups several scenarios under one business rule. Whichever form you choose, three habits keep user stories and acceptance criteria useful:

  • Write the criteria before the work starts. Criteria written afterwards describe what was built, not what was needed.
  • Cover a success, a refusal and an edge. The invite example shows the first two, an accepted invite and an expired one. A link opened a second time would be its edge.
  • Split the story when the list grows. As a rule of thumb, a story that needs more than six scenarios is usually two stories.

Stories also sit inside a larger document. Our product requirements document template shows the frame around them: the problem, the goals and what is out of scope.

What examples of good user stories have in common

Good user stories pass the INVEST check: independent, negotiable, valuable, estimable, small and testable. Bill Wake published the checklist in 2003 in his article "INVEST in Good Stories, and SMART Tasks", and Mike Cohn's book User Stories Applied (Addison-Wesley, 2004) recommends it.

The Agile Alliance keeps a summary of the INVEST checklist. The table turns each letter into a question and a sign that a story fails it.

The INVEST check: the question each letter asks and a sign that a story fails it
CheckQuestion to askSign it fails
IndependentCan it be built and released without another story?It says "after the redesign ships".
NegotiableIs the design still open to discussion?It names a button, a colour or a database table.
ValuableWould a user or the business notice it?Only the team benefits.
EstimableDoes the team know enough to size it?Nobody can say what done looks like.
SmallDoes it fit in one iteration?The story joins several goals with "and".
TestableCould someone write a test for it today?It uses "fast" or "easy" with no number.

The 12 user stories examples earlier in this guide were written to pass all six. Small is the check teams fail most visibly. Wake wrote that stories typically represent at most a few person-weeks of work, and that some teams restrict them to a few person-days.

A weak user story, rewritten

Most weak stories fail in the same three places: the user is "a user", the goal is a feature, and the reason is missing. Fixing those three usually fixes the story.

Take "As a user, I want notifications." It names nobody, asks for a mechanism and gives no reason, so a developer could build almost anything and call it done. The rewrite from the table reads: "As a project member, I want an email when I am mentioned so that I do not miss a question."

  • The role is specific. A project member has different needs from an account owner or an auditor.
  • The goal is one event. A mention, not every kind of activity.
  • The reason is stated. Missing a question is the problem, so a daily digest would not solve it.

The reason clause should come from evidence. If you cannot fill in "so that" from interviews or data, the gap is in discovery, and our guide to the product discovery process covers how to close it. A jobs to be done template helps as well, because a job statement spells out the situation and the motivation behind the reason clause.

Stories that are too large need splitting, not rewriting. "As an account owner, I want to manage billing" hides at least four stories: upgrade a plan, update a card, download invoices and hear about a failed payment. Split by user goal, never by technical layer. "Build the invoices table" is a task, because no user can see that it is done.

Some work has no user at all. The Scrum Guide (November 2020) never mentions user stories; it speaks only of Product Backlog items. A framework upgrade or a database migration can sit in the backlog as a plain item with its own criteria, without a forced "As a developer" sentence.

User stories for AI features and AI coding tools

Stories for AI features need criteria that bound the output, and stories handed to an AI coding tool need criteria precise enough to become tests. In both cases the acceptance criteria carry more weight than the story sentence.

An AI feature does not return the same words every time, so "the summary is correct" cannot be checked. The AI summary among the user stories examples above sets limits instead: a maximum length, a link from each point to its source, and a defined result when the service does not answer. Those can be tested on every release.

The second case is newer. A person who reads a thin story fills the gaps with judgment or asks a question. An AI coding tool builds what is written and guesses the rest. The cases you left out, such as the expired invite or the viewer who tries to edit, are the ones most likely to be wrong. Three habits help:

  • Write the refusals. Say what must not happen as well as what must.
  • Name every role. "A viewer" and "an admin", never "the user".
  • Give limits as numbers. "Within 72 hours" can be tested, and "soon" cannot.

How we write user stories with your team

We work with founders and product teams that have the product in their heads and a backlog nobody trusts. As your fractional product manager and CPO, we run the interviews behind each reason clause, write the stories and acceptance criteria with your engineers, and keep the backlog in an order the whole team can explain.

Every engagement is under an NDA, and the IP is always yours. Each project is different, so we quote it after a short call.

Frequently asked questions

What is a good example of a user story?

A good example names a specific role, one goal and a reason, and has criteria that can be tested. "As a workspace admin, I want to invite a teammate by email so that we can work on the same account" does all three. "As a user, I want notifications" does none of them.

What are the three Cs of a user story?

Card, conversation and confirmation. Ron Jeffries proposed the model in 2001. The card is the short written story, the conversation is the discussion that fills in the detail, and the confirmation is the acceptance test that shows the story was built as agreed. All three are needed; the card alone is not a requirement.

What is the difference between a user story and acceptance criteria?

The user story says who wants something and why. The acceptance criteria are the conditions that must be true for the story to count as done. One story usually carries several criteria, often written as Given, When, Then scenarios so that they can be checked by a person or run as automated tests.

How many acceptance criteria should a user story have?

Enough to cover a success, a refusal and the edge cases that matter, which in practice is often three to six scenarios. No standard sets a number. When the list keeps growing, treat it as a sign that the story holds more than one goal and split it into smaller stories.

Who writes user stories?

Anyone on the team can write one, and the product owner or product manager decides their order. The Agile Alliance describes the team dividing the work into stories in consultation with the customer or product owner. Stories written by one person and handed over without a conversation lose the detail that makes them work.

Are user stories part of Scrum?

No. The Scrum Guide, in its November 2020 version, does not mention user stories. It refers only to Product Backlog items, and a user story is one common way to write them. User stories come from Extreme Programming, and many Scrum teams use them by choice, not because the framework requires it.

Sources and update history

  1. Agile Alliance glossary, User Storiesagilealliance.orgCHECKED 15 NOV 2026
  2. Agile Alliance glossary, Role-feature-reasonagilealliance.orgCHECKED 15 NOV 2026
  3. Agile Alliance glossary, The Three Csagilealliance.orgCHECKED 15 NOV 2026
  4. Agile Alliance glossary, INVESTagilealliance.orgCHECKED 15 NOV 2026
  5. Agile Alliance glossary, Given - When - Thenagilealliance.orgCHECKED 15 NOV 2026
  6. Cucumber documentation, Gherkin referencecucumber.ioCHECKED 15 NOV 2026
  7. The Scrum Guide (November 2020)scrumguides.orgCHECKED 15 NOV 2026
Update history
  1. First published.