These are example scenarios, not customer testimonials. The companies are invented, and each outcome describes what the scenario does rather than a measured result.
Example scenario
Mapleford Accounting
A fictional accounting office · 12 people · finance
Month-end means two days of collecting supplier invoices from a dozen portals and checking expense claims by hand.
- A routine on the last working day signs in to each supplier portal on the coworker's computer and downloads the month's invoices to a shared folder.
- It checks every expense claim in the spreadsheet against the travel policy and lists the ones that break a rule, quoting the rule.
- It ticks off the closing checklist and reports what is still open.
Where a person decides One-time sign-in codes are typed by the bookkeeper on the live screen, and nothing is paid or submitted without approval.
What the scenario shows The collecting and checking happen on their own; the people spend their time on the claims that need a judgement.
Example scenario
Tsubame Travel
A fictional travel agency · 30 people · customer support
The same questions about refunds and luggage arrive every day, and the answers are already in the agency's help articles.
- The help articles are added to Knowledge, and a support coworker drafts each reply from them, quoting the article it used.
- Every morning a routine summarises yesterday's enquiries by topic and sends the summary to the team lead on LINE.
- When the articles do not cover a question, the draft says so and the question goes to a person.
Where a person decides An agent reads and approves every reply before it is sent.
What the scenario shows Agents start from a sourced draft instead of a blank page, and gaps in the help articles become visible.
Example scenario
Brightfield Labs
A fictional software startup · 6 people · product and engineering
Six people ship every week, and nobody has time to write release notes or keep up with competitors.
- After each release, a coworker reads the release page and drafts customer notes grouped into New and Improved.
- Once a month it reads five competitors' websites and writes a one-paragraph brief on each, with the pages it used.
- Their own product starts a routine through the API, and a signed webhook delivers the result.
Where a person decides The founders edit the drafts and publish them themselves.
What the scenario shows Writing that used to be skipped gets a first draft every time.
Example scenario
Aozora Property Management
A fictional property manager · 45 people · operations
Repair requests, listing updates and owner reports are spread across a projects board, a website editor and email.
- Every Friday a routine lists the overdue repair jobs on the projects board, with their owners.
- When a flat is let, the coworker signs in to the website's editor, updates the listing and shows screenshots before and after.
- It drafts the monthly owner report from the board and the notes the team attaches.
Where a person decides Publishing the website change and sending the report each wait for an approval.
What the scenario shows The weekly chasing becomes a list that arrives on its own, and every change is on the record.
Example scenario
Cedar & Pine Recruiting
A fictional recruiting firm · 18 people · people and hiring
Consultants spend evenings turning interview notes into write-ups and finding interview times.
- After an interview, the coworker turns the notes into a write-up under the client's scorecard headings, using only what the notes say.
- With Google Calendar connected, it finds times that suit everyone and proposes them.
- It keeps the candidate's record in the CRM up to date.
Where a person decides It never makes a hiring recommendation, and a meeting is booked only after the consultant approves it.
What the scenario shows The write-up is ready when the consultant is, in the same structure every time.
Example scenario
Hoshizora Town Office
A fictional town office · 80 people · public sector
Staff answer residents' letters and publish notices that have to be clear to everyone.
- The coworker summarises long documents and drafts replies to residents for a member of staff to check.
- It rewrites official notices in plain language and lists any sentence it was unsure about.
- Administrators export the audit trail for the office's own reviews.
Where a person decides Staff send every reply and publish every notice themselves.
What the scenario shows Drafting is quicker, and who decided what can be shown later.