# A guide to get started

## What should you record first?

Let us offer some suggestions based on your function:

### What kind of function?
- **Operations**: The work behind the customer-facing queue — fulfilment, scheduling, exceptions.
- **Customer service**: The customer-facing queue — tickets, escalations, refunds, renewals.
- **Sales & marketing**: Pipeline, campaigns, qualification, proposals, handoffs to delivery.
- **Finance & accounting**: Close, reconciliation, billing, collections, reporting.
- **Something else**: Anything at all — these work whatever you spend your day on.

1. **Update a tracker**  Aim for 5 minutes
2. **Prepare a status report**  Aim for 5 minutes

### Then ask your AI assistant…
- `Write an SOP for this that includes the exceptions I described, not just the standard path.`
- `Which steps in what I just recorded depend on one specific person?`
- `Where in this process am I entering the same information more than once?`

1. **Triage a support request**  Aim for 5 minutes

### Then ask your AI assistant…
- `Write up the criteria I'm actually using to decide when to make an exception to policy.`
- `Develop a step-by-step guide a new hire could follow on their first day.`
- `Where am I looking up the same customer information in more than one system?`

1. **Qualify an inbound lead**  Aim for 5 minutes
2. **Personalize an outreach message**  Aim for 5 minutes

### Then ask your AI assistant…
- `Turn this into qualification criteria explicit enough for someone else to apply.`
- `Which parts of this process are just moving data between systems?`
- `What did I check that isn't in our documented qualification framework?`

1. **Review an expense submission**  Aim for 5 minutes
2. **Prepare an invoice**  Aim for 5 minutes

### Then ask your AI assistant…
- `Document how I work through this, including the order I check things and when I escalate.`
- `Where did what I just did diverge from our written procedure?`
- `Which of these steps are mechanical enough to hand to someone more junior?`

1. **How you typically start your day**  Aim for 5 minutes
2. **The thing people always ask you how to do**  Aim for 5 minutes
3. **Something you do weekly that only you know**  Aim for 5 minutes
4. **A report or update you assemble by hand**  Aim for 5 minutes
5. **Showing someone new how to do one task**  Aim for 5 minutes

### Then ask your AI assistant…
- `Write up what I just did and why each step matters.`
- `Which of these steps could run automatically before I sit down?`
- `What did I do that I'd have forgotten to mention if you'd just asked me?`

## Rolling this out to a team

### One recording is useful. _A team's worth is a different thing entirely._

Everything above works on a single machine with a free account. What changes when several people record is that you stop looking at one process and start seeing how work actually moves between them.

### Example workspace

#### Company insights
- 148 recordings across 12 workspaces
- **63 Workflows modeled** 11 added in the last 90 days
- **291 Decisions documented** from 148 recordings
- **17 Single-owner workflows** only one person recorded these
- **24 Automation ready** 38% of modeled work

#### Automation pipeline
- **Modeled:** 63 recorded and mapped
- **Automation ready:** 24 38% of modeled work
- **In development:** 6 25% of automation-ready
- **In use:** live 3 50% of in development

### Single-owner workflows

Only one person has ever recorded these

| Workflow | Team | Exposure |
| --- | --- | --- |
| Scheduling rush production orders | Production ops | High |
| Processing RMAs and return dispositions | Returns and RMA | High |
| Month-end margin reconciliation | Finance | High |
| Vendor credit disputes | Returns and RMA | Moderate |

### Needs attention
- Production ops has 6 workflows with one owner and no SOP The highest concentration of unrecorded knowledge in the company.
- 8 workflows have drifted from the version first recorded On 4 teams, the SOP on file no longer matches what people actually do.
- 3 workspaces have recorded nothing in 60 days People ops, legal, and IT.

### Process variance
Record several people doing nominally the same job and you get several different processes. Seeing them side by side tells you which version is best — and which differences are improvements rather than drift.

### The seams between people
A single recording ends where one person's part ends. Recordings either side of a handoff show what falls into the gap between them.

### Single-owner exposure
Which workflows exactly one person has ever recorded, and how long it's been. That's your concentration of unwritten knowledge, ranked.

### Drift from the SOP
Where what people actually do has moved away from the version on file, so the document can be corrected rather than trusted.

## Talk through a team rollout
Tell us a little about the team and we'll walk through what multi-recorder capture looks like on your operation — usually 30 minutes.
- Multi-recorder synthesis across the same process
- Shared team library and pooled credits
- Role-based access for who can see what.