# Revenue: one page per customer

> A scenario: an account lead asks their agent for a customer onboarding page shared with named contacts, sees who read it and answers their questions.

*A scenario, not a customer story. No company, person or figure here is real; every step is something the product does today.*

## An account lead, a new customer

A customer just signed. What they need first is one page: what happens next, who to talk to, what they have to do. Here, that page is shared with exactly the people on their side.

## Where they are

Onboarding a new customer means a kickoff deck, a follow-up email with six attachments, and a spreadsheet of who on their side has done what.

A week later you want to know whether anyone over there has read any of it, and what they are stuck on.

## What they ask for

- An onboarding page for one customer
- Answer what they asked

Each request is a Copy prompt button on the page.

## What the agent builds

One page per customer, shared with their people by name, with a form for what they are stuck on.

- The plan: Your first month, Who to talk to
- Your steps: Invite your team, Connect your data, First review call
- Questions: What are you stuck on?

## What happens next

1. **Shared with exactly the people on their side.** Each contact is invited by email and signs in to open it. A forwarded link opens for nobody else; they can ask you for access instead.
2. **See who has read it.** The artifact's Analytics tab shows views by day and names the readers who opened it, because they signed in and are on its access list. It does not show scroll depth or time on page.
3. **Questions come back as data.** What they type into the form lands as rows your agent reads back, so "what are they stuck on" is a question you ask it.
4. **Update it in place.** The answers go onto the same page as a new version. The link they have does not change, and every earlier version is kept.

## What it replaces

- A kickoff deck and a follow-up email with attachments
- Asking on a call whether anyone read the plan
- A spreadsheet of who on their side has done what

## What it does not do

- It is not a CRM. Your pipeline stays where it is.
- It sends no reminders. A weekly account update means asking your agent each week.
- Readers on a public link are counted but never named. Naming needs the people you invited to sign in.

## The same move, elsewhere

Collecting feedback from a customer, or sending them a weekly update, is the same page with a different form on it.

## The other case studies

- [Founders](https://superartifacts.app/case-studies/founders.md): A projection you can edit, and an update for investors that is a link rather than a deck.
- [Engineering](https://superartifacts.app/case-studies/engineering.md): A sprint review or a retrospective your agent assembles from the work it just did.
- [Product](https://superartifacts.app/case-studies/product.md): A feedback survey for users, and the answers read back in one place.
- [People](https://superartifacts.app/case-studies/people.md): A hiring board for one role, and an onboarding checklist for the person you hired.