Stories A told story · first draft 2026-11-18 — read, not built; every state below is read from the registry and the code, none from production
Sales
Any group on ONE can run one sales path, worked by people and agents together, and read where it leaks.
The seven beats
- Groups
- A group that sells, its sales room, and the record it keeps on every person it has spoken to
- Actors
- The buyer; the setter; the closer; the manager; the five sales agents who can stand in any of those seats
- Events
- A stranger leaves an email on a page. It is captured as a signal and kept
- Things
- One path from that signal to a paid order and a referral, with a script at every station and a number on every edge
- Paths
- frame → set → show → close → refer; each edge marked when the next step happens and warned when it does not
- Outcome
- Open: the stations exist and the room draws what sold, but the Leads stage has no source
- Learning
- Open — not learned yet
Open the sales room and look at the funnel. It has six stages: visitors, chatted, leads, carts, checkouts started, paid. Five of them show a number. The third one, Leads, shows nothing, and says why in one line:
Leads are not recorded per workspace yet, so this stage has no source.
That line is in the code (components/sales/sales-math.ts:183). It is the
most honest thing on the page, and it is where this story starts. ONE can
capture a lead, call them, book them, record the meeting, send a price as a
link, take the money and rank who sold it. It cannot yet tell a group where
its path leaks, because the stage in the middle is not counted, and because
nothing joins the stations into one walk.
Sales is that walk. This file says what the walk is, which parts of it ONE already has, which parts are a prompt and nothing more, and the order to build the rest. It sits above the CRM docs: the CRM is the record of one person, and sales is what a group does with that record on purpose.
Status: red at the making, by law. None of the seven rows in the schedule above is built. Each goes green when its test does.
Where the method comes from
Tony pasted a long public training on building sales teams and asked one question: how do we use our platform for this. The method in it is not new, and that is its strength. People have been persuaded the same way for a long time, and people learn a skill the same way they always have: by watching it done and by doing it. Only the tools change.
So this file takes the method and leaves the tools. Where the training gives a number (a show rate, a count of calls), the number is quoted as the training's own. ONE has not measured any of them. A group sets its own, and reads its own.
The framework
A sale is one path with five stations. A person moves along it. At each station somebody, a person or an agent, does one job and hands on.
a stranger
│ leaves an email on a page
▼
┌─────────┐ told before asked: a video or a
│ FRAME │ letter they finish before anyone
└────┬────┘ speaks to them
▼
┌─────────┐ reached fast, asked four
│ SET │ questions, booked for today
└────┬────┘ or tomorrow
▼
┌─────────┐ they turn up, and the person
│ SHOW │ they meet has read the note
└────┬────┘
▼
┌─────────┐ intro · discovery · pitch · ask,
│ CLOSE │ then silence
└────┬────┘
│ yes │ anything else
▼ ▼
┌─────────┐ ┌──────────────┐
│ REFER │ │ next meeting │
└────┬────┘ │ booked now │
│ └──────┬───────┘
▼ │
a new stranger ◄────────────────┘
back to SHOW
Each box is a workflow step. Each arrow is a path with a weight on it. When the next step happens the arrow is marked; when it does not, it is warned; when nothing happens at all, it fades. After enough walks the weights say which arrow is weak, and that is the leak.
The rules over every sale
Ten rules. The first eight are the method. The last two are ONE's own, and they outrank the eight where they meet.
- Tell before you ask. Nobody is spoken to cold. Before a conversation the person is given something to finish: a video or a letter that makes one promise, names the pain, shows proof, sets out the plan, answers the objections they are about to raise, and asks one small thing back. The more they take in before the call, the less the call has to carry.
- A script comes before a seller. Without a written script there is no definition of a good call, so nothing can be taught, reviewed or improved. The script is short. It is cut until only the words that do a job remain.
- Qualify at the door. Four questions: can they pay, can they decide, do they need it, do they need it now. A person who fails one does not go on to the closer.
- Be fast, and book near. The first touch comes minutes after the lead, and the meeting is booked for today or tomorrow. Both the show and the sale fall off with every day in between.
- Ask, then stop talking. State the price once and wait. The training's own figure is that waiting eight seconds or more closes noticeably more often; ONE has not measured it.
- Anything but yes is a loop. Agree with what they said, tie it to what people who bought also said, and ask again. In a loop the seller asks questions and makes no statements, because a person can argue with a statement and can only answer a question.
- No call ends without a next step. A yes ends in a referral ask. A not-yet ends with the next meeting on both calendars before anyone hangs up.
- Pay on the close. The setter and the closer are both paid when the sale lands, so both want the same thing.
- Consent is the door, for every touch. The method says call twice,
then text, then call again tomorrow. On ONE each of those is a signal
to a person, and a person is reached only on a channel they agreed
to. The check runs once, at the door, before any handler
(
text/crm.mdcard 7). A cadence that outruns consent is refused and the refusal warns the path. This rule wins over rule 4. - People and agents walk the same path. A seat on the path is a
job, not a species. The sales room already ranks sellers in one
column whether the seller is a person or an agent
(
lib/sales/sales-overview.ts:86). An agent in a seat follows the same script, clears the same gate and is reviewed by the same coach. Where money, a signature or a judgment belongs to a person, the agent hands it over.
What the frame holds
The frame is the thing a person finishes before a conversation. One shape serves every station; only the questions it answers change.
promise what this will do for them
pain what staying put costs
proof people like them, before and after
plan the three or four steps
─────────────────────────────────────────────
old way how most people try it
new way why this way works
─────────────────────────────────────────────
objections each one: what they think,
why it is not so, what is so,
and proof
─────────────────────────────────────────────
one ask a small thing to send back, so
the next call feels made for them
more proof as long as they will watch
Length follows friction. Before a form, where every extra minute loses leads, the frame is short. After the form, where the person has already chosen, it is as long as they will watch. A group with three stations has three frames, and each answers the questions of the step that comes next: the first sells the booking, the second sells turning up, the third sells the decision.
What the script holds
Four stations inside one call.
INTRO who is calling, from where, why,
and the agenda. Get a yes to the
agenda. Seconds, not minutes.
│
▼
DISCOVERY where they are · where they want
to be · what is in the way.
Ask why. Ask for an example.
Get a number, a date or a name.
Say it back; they confirm.
│
▼
PITCH three times: their problem, our
answer, what it gives them.
Under two minutes.
│
▼
CLOSE the price, once. Silence.
Then the loop, as often as
it takes.
Discovery is where a sale is won. If a person has no reason to act today, the seller did not dig far enough into what staying put costs them. The pitch is the shortest part because by then the person has already said the problem in their own words, and the seller only has to point each of their problems at one answer.
The loop. Five replies work whatever the objection is, which is why a new seller learns these first:
| Reply | What it does |
|---|---|
| The reason | turns the reason for waiting into the reason to start |
| The hypothetical | "if that were solved, would you?" — finds the one real obstacle |
| The zoom out | steps back from the detail to what they came for |
| One to ten | "what would make it a ten?" — they name the gap themselves |
| Best case, worst case | shows that doing nothing is the only choice with a certain cost |
Behind those sit five families of objection, each with one argument: time is a question of priority; money is a question of value; someone else decides is a question of what that person would object to; I don't like this part is a trade against the result; and let me think is a cost of waiting that nobody has added up.
The path, drawn as ONE runs it
Two workflows and two loops. Every step is one of the eight step kinds,
and every receiver named is in packages/sdk/src/receivers.ts.
The setter path
trigger lead:capture a form on any page
│
condition email left? no → stop here
│
tool visitor:identify the stranger
│ becomes a person
tool entity:tag → lead
│ ─── the four steps above exist today as
│ the lead-follow-up template ───
│
condition pay · decide · need · no → a slower
│ now? list, not a call
│
tool voice:call through the
│ consent door
├── no answer ──► delay ──► email:send ──► retry
│ (the group's cadence,
│ inside consent)
▼
tool booking:list-slots today or tomorrow
tool booking:create first
│
agent discovery-caller writes the
│ hand-off note
▼
the closer path
The first four steps are real: lead-follow-up in
lib/workflow-templates.ts:502 runs them. Everything below the dashed
line is a design. The qualifying step, the call, the retry cadence, the
booking and the note are each a receiver that exists, but no workflow
joins them.
The closer path
trigger the booking comes due
│
tool crm:context stage, recent
│ threads, strength
agent sales-closer intro, discovery,
│ (or a person, with pitch
│ the same script)
│
tool video:start-recording with consent
│
sell checkout:create one price, one
│ link. The run
│ waits here.
├── paid ─────► tool affiliate:join-request
│ (the referral ask)
│
└── not yet ──► tool calendar:schedule-meeting
booked on the call
tool entity:tag → opportunity
sell is a locked step kind: the run suspends on checkout:create and
checkout:resume carries it on once the buyer pays. That is exactly the
silence after the ask, written as a step.
The review loop
a recording is ready
│
tool video:summary the transcript, summed
│
agent sales-call-coach scores each station:
│ intro · discovery ·
│ pitch · close
human the manager picks ONE thing
│
the seller practises it, and next week's
number says whether it worked
One thing, not ten. Even when ten things are wrong, a seller fixes one behaviour at a time, and the behaviour is named in words they can act on: "you spoke over the answer three times in discovery", never "you sounded pushy".
The gate loop
the window closes
│
tool workflow:step-stats the seller's
│ own numbers
condition clear the gate?
├── no ──► same leads, one focus, try again
│
human the manager approves
│
more leads · better leads · the next seat
A new seller, person or agent, starts with few leads and a low ceiling, because a seller who is not ready wastes the most expensive thing a group has. The training's own gates are these: about thirty live connects a day until two or three become bookings, then a cap on bookings until six in ten of them turn up. A group sets its own. What matters is the shape: the ceiling lifts on a measured number, and a person lifts it.
This is the same ladder ONE already uses for autonomy. tool → skill → agent is a ceiling that rises as trust is earned. A seat on the sales
path rises the same way.
The seats
| Seat | The job | A person | An agent |
|---|---|---|---|
| Setter | first touch, four questions, the booking, the note | yes | live-sales-chat in chat, discovery-caller on a call |
| Closer | the call, the ask, the loop, the referral | yes | sales-closer; demo-specialist where the pitch is a demo |
| Coach | reviews every recording against the script | yes | sales-call-coach |
| Manager | holds the standard, opens gates, picks the one fix | yes | never alone: cro routes, a person decides |
Everyone starts as a setter. A seller who cannot book a meeting cannot close one, and finding that out on a setter's leads costs far less than finding it out on a closer's. A closer is a setter whose numbers held for a whole window, promoted when a seat opens. A group that grows its closers this way rarely has to remove one.
The best seller is not the manager. Promote the strongest closer and a group loses its best closes and gains an average manager. The manager is the steady one the others already go to with questions, who can name the numbers they watch and say which behaviour moves each.
The standard is the weakest seller a group keeps. Whatever the lowest-performing person on the path is allowed to do is the real bar. The same holds for an agent left in a seat it has not earned.
The week
A skill that is not practised goes. So practice is on the calendar, one station a day, and the daily meeting is held in the slowest calling hour so it costs the fewest conversations.
Mon intro
Tue discovery
Wed pitch
Thu close
Fri the week's hardest objection
Sat the pipeline, person by person
The meeting has four parts and runs short: a named thing a teammate did well, one buyer's result, the day's station, and role play. Praise names the behaviour ("she stayed in discovery until he gave a number"), because a behaviour can be copied and "a great day" cannot.
Two modes. A closer is either on a call or getting the next one.
OFF A CALL — in this order
1 read the notes for today's meetings
2 new bookings: ring now, offer to meet now
3 meetings with a next step: keep them warm
4 people who showed and did not buy, or
never showed: newest first, sixty days back
5 buyers who were not asked for a referral
6 two hours of first calls, every day
ON A CALL
the script
Line 2 is worth a sentence. A person who has just booked for tomorrow is rung straight away and offered the meeting now. If they say yes, they cannot miss it, they decide while they still care, and tomorrow's slot is free for someone else.
Line 6 keeps a closer honest. A closer who still makes first calls remembers what a booking costs and does not waste one.
The seven numbers
One read, each number with its source and the time it was read. A stage with no source says so; it is never shown as zero.
| Number | What it is | When it is low, look at |
|---|---|---|
| First-touch time | lead → first attempt | whether the workflow fires, and the retry step |
| Connect rate | attempts that reach a person | the hour of the call, the list, the number calling |
| Conversation rate | connects that pass three minutes | the first thirty seconds: tone, and a clear ask |
| Set rate | conversations that end in a booking | discovery: no stated goal, or no named obstacle |
| Show rate | bookings where the person turns up | the four questions, days until the meeting, the frame unread |
| Close rate | shows that pay | the offer first, then the frame, then the script by station |
| Referral share | sales that began as an introduction | whether anyone asked |
Each low number has an order of suspects, and the seller is last. When people show and do not buy, the offer is checked first, then whether they took in the frame, and only then the call. When a call is the cause, the review names the station: an agenda nobody agreed to is an intro fault; a goal left vague is a discovery fault; a pitch past two minutes is a pitch fault; an answer to the first objection and no second ask is a close fault.
The sales room reads none of the seven today. It reads what sold and
how many people stand at five of six stages, each from its own source,
"not traced per person" (sales-math.ts:190). The seven are per-person
walks, so they need the join this story asks for.
What we have, sorted
Legend:
◐in the registry or the code, read this session, not run○a prompt or a design only·not started
Nothing here is marked as seen on production. The one production read tried this session was refused.
A · Frame → funnels.md, sold-vsl.md
| Power | State | Where |
|---|---|---|
| A page for the frame, published | ◐ | pages:create, pages:publish |
| A funnel with a step per station | ◐ | funnel:create, funnel:update-step |
| The video itself, made or uploaded | ◐ | media:generate, media:upload |
| A frame per station, tied to the step that follows it | ○ | this file |
| Knowing whether a person finished the frame | · | no signal records it |
B · Set → leads-how-to.md, lead-engine.md
| Power | State | Where |
|---|---|---|
| Capture a form as a lead | ◐ | lead:capture (public) |
Stranger → known person → stage lead |
◐ | the lead-follow-up template, four steps |
| Leads counted per group | · | the funnel's Leads stage is n: null |
| The four questions as a condition | ○ | this file |
| Call from the path | ◐ | voice:call; logs the call and links the run |
| Text from the path | · | sms:send is not in the registry (text/crm.md card 8) |
| Email from the path | ◐ | email:send |
| Book a slot, move a slot | ◐ | booking:list-slots, booking:create, booking:reschedule |
| Keep unqualified people off the closer's list | ◐ | segment:create, segment:preview |
| The retry cadence inside consent | ○ | this file; the door is text/crm.md card 7 |
C · Show → crm.md
| Power | State | Where |
|---|---|---|
| Everything a person said, before the call | ◐ | crm:context |
| A written hand-off note from setter to closer | ○ | discovery-caller is a prompt; no step writes a note |
| A human joins when a visitor asks for one | ◐ | the meeting-handoff template |
| Offer "now" to someone who just booked | ○ | this file |
D · Close → sell.md, sold.md
| Power | State | Where |
|---|---|---|
| The price as one link | ◐ | checkout:link, links:create |
| A run that waits on the buyer and resumes when paid | ◐ | the sell step kind, checkout:create → checkout:resume |
| Record the meeting and sum it | ◐ | video:start-recording, video:summary |
| An agent that runs the close | ○ | sales-closer is a prompt with a payment-link tool |
| The loop replies as a script the path enforces | · | nothing checks a call against a script |
| The next meeting booked before the call ends | ◐ | calendar:schedule-meeting; no path calls it on a not-yet |
E · Refer → affiliate and rewards docs
| Power | State | Where |
|---|---|---|
| Join a referral program | ◐ | affiliate:join-request, affiliate:approve |
| Reward a buyer | ◐ | rewards:enroll |
| The ask fired by a paid order | · | no step does it |
| A referred lead tied back to who named them | · | VERIFY: not looked for |
F · Review and manage → crm-learns.md
| Power | State | Where |
|---|---|---|
| What sold, on which rail and channel | ◐ | the sales room, lib/sales/sales-overview.ts |
| Who sold it, people and agents in one column | ◐ | Seller, ranked from settled money |
| People at each funnel stage | ◐ six of six on dev | funnelStages; Leads reads contacts tagged lead (tests/unit/vespio/sales-pipeline.test.ts); each stage is counted on its own, not traced per person |
| A stage move that names its rule, and an override that teaches it | ◐ | actor:override, in the registry since 2026-10-06 |
| Per-step numbers for a workflow | ◐ | workflow:step-stats |
| A coach that scores a call by station | ○ | sales-call-coach is a prompt |
| A signal when a recording is ready | · | the agents name call:recording-ready; no receiver has it |
The deal:<id>:… signals the agents pass between them |
· | named in five agent files; none is a receiver |
| The seven numbers | · | not computed |
| A gate that reads them | · | this file |
| A share of the sale paid to the setter and the closer | · | no commission rule |
| Listening to a live call and prompting the seller | · | not started |
| A dialler that rings two lines and rotates numbers | · | not started |
What did not land
Four things in the method have no home on ONE yet, and one of them should not get one as written.
- The agents talk to each other in names nothing answers. The five
sales agents say they emit and subscribe to
deal:<id>:discovery-needed,deal:<id>:qualified,call:recording-readyandcoaching:<rep-id>:feedback-ready. None is a receiver. A signal to a name with no receiver dissolves. Until the hand-offs are workflow edges or real receivers, the five agents are five prompts, not a team. - A lead is not counted. The person exists and carries the
leadtag, but the sales room has no per-group count of them, so the funnel has a hole in the middle and no ratio crosses it. - Nothing pays a seller. The method depends on paying both seats when the sale lands. ONE can rank sellers by settled money and has no rule that sends a share to one.
- The volume in the method outruns ONE's consent law. The training describes hundreds of calls a day and seven attempts per lead. On ONE every attempt passes the consent door, so a group's cadence is what its leads agreed to. This is rule 9, and it is a ruling, not a gap: the dialler and the live listen are built only after the door is green on every channel.
The order we build in
Planned in waves, never in days.
W1 count the lead, and join the setter path:
the four steps that exist + qualify, call,
retry, book, note
│
▼
W2 the closer path: context, the sell step,
next-meeting-on-the-call, the referral ask;
the agents' hand-offs become workflow edges
│
▼
W3 the seven numbers as one read, on the sales
room, the CLI, the chat and MCP
│
▼
W4 the review loop: a recording-ready signal,
the coach scoring by station, one fix a week
│
▼
W5 the gate, then the seller's share of a close
│
▼
W6 a text receiver behind consent; only then
the dialler and the live listen
Wave 1 is the smallest set that lets one group watch one lead walk to a booking. Three rows, to be filed once Tony has read this file:
- Count the lead. A per-group lead count with a source, so the
funnel's third stage shows a number. Deliverable 1. Tags:
sales,crm. - The setter path as a template. Extend
lead-follow-uppastentity:tag: the four questions,voice:callthrough the consent door, the retry withdelayandemail:send,booking:create, and a note written to the person's thread. Deliverables 2 and 7. Tags:sales,workflows. - Run it on ONE's own leads. Group
oneis the first worked example, the way it is for the books. The first report is seven numbers for seven days of our own leads, with the ones that have no source marked as such.
Every surface moves with each row: the receiver contract, the CLI verb,
the MCP tool, the sales room, the chat and llms.txt
(CLAUDE.md § Every surface moves together).
What it defends, and what it accepts
| Surface | Defends | Accepts |
|---|---|---|
| The consent door | no call, text or email on a channel the person did not agree to; a refusal warns the path | a slower cadence than the method teaches |
| The loop | questions only; a person can end the call, and "no" is recorded as an outcome | a seller who asks again; that is the job |
| Proof in the frame | only results a group can show, said with "results vary" where they do | a frame that persuades |
| Recording | a call is recorded only with consent, and the person can read and delete it (text/crm.md cards 26, 27) |
a group that reviews its own calls |
| An agent in a seat | says it is an agent when asked; spends under a ceiling a person set | an agent that sets and closes |
| The price | one price in one link; a paid order is the only thing that marks the close | a buyer who takes days |
| The gate | a seller sees more leads only on measured numbers and a person's approval | a manager who overrides, on the record |
| The buyer who cannot pay | the four questions stop them before the closer; nobody is talked into borrowing | losing sales the method would chase |
The last row is a ruling. The training includes ways to help a person find money they do not have. ONE's path stops at the four questions.
Where this file is looser than the code
- "ONE can capture, call, book, record, price, take the money and rank
who sold it." Each is a receiver or a read that exists by name. None
was called this session, and no two are joined except the four steps
of
lead-follow-up. - "Through the consent door." The door is
text/crm.mdcard 7. Whethervoice:callandemail:sendpass through it when a workflow step calls them, not a button, is unchecked. Deliverable 7 exists because of this. - "An agent in a seat follows the same script." NOT WIRED. The five
agents have prompts and skills (
sales-enablement,copywriting). Nothing scores a run against a script. - "The sell step is the silence after the ask." True of the
mechanism: the run suspends on
checkout:create. It is a metaphor for the call itself, where a person still has to stop talking. - "Who sold it." The room ranks
settlements.payee. That is who was paid, which for a team is the group, not the setter or the closer. - Stage names. This file says stranger, lead, set, shown, won,
referrer. The sales space reads the tags
engage,opportunity,won,lost(lib/in/spaces.ts:37) andlead-follow-upwritesleadin themarketinglifecycle. Nosaleslifecycle definition was found. The mapping is a decision for wave 1. - Locked words used: signal, mark, warn, fade; the eight step kinds by name. Dead names: none. "Workspace" appears only inside a line quoted from the code.
Sentences that would be false if shipped
- "ONE runs your sales team."
- "Leads are tracked from first visit to close." (Each funnel stage is counted on its own; no person is traced from stage to stage.)
- "Our agents qualify, close and coach." (They are prompts; their hand-offs name receivers that do not exist.)
- "Every call is scored against your script."
- "See your show rate and close rate live." (Neither is computed.)
- "Setters and closers are paid automatically on every sale."
- "Text your leads from ONE." (
sms:sendis not a receiver.) - "Waiting eight seconds closes 30% more." (The training's figure, not ours.)
- "Seven touches in four days, automatically." (Only as far as consent allows.)
Where the depth lives
| For | Read |
|---|---|
| The record of one person, and the consent door | text/crm.md |
| The record learning across people: who next, and why | text/crm-learns.md |
| One person's journey, key and meeting | text/crm-journey.md |
| Capturing and qualifying a lead today | text/leads-how-to.md, text/lead-engine.md |
| Pages, funnels and the frame | text/funnels.md, text/sold-vsl.md |
| The price, the link and the order | text/sell.md, text/sold.md |
| The step kinds and how a run suspends | text/workflows-plan.md |
| What the money means once it lands | text/finance.md |
Connected to
Every link here was checked against the repo when the page was built. 1 name the story uses could not be found and is shown without a link.
People
- the buyer
- the setter
- the closer
- the sales manager
- the owner of the group
Agents
Each opens a chat with that agent.
Skills
Each opens the skill's page.
- storytelling
- sell
- copywriting
- planning
- meeting
Paths
The flows this story walks — trigger → step → step.
- trigger: lead:capture → condition: email left? → tool: visitor:identify → tool: entity:tag (lead) → condition: budget, authority, need, timing → tool: voice:call (through consent) → delay: the group's retry window → tool: email:send → tool: booking:create → agent: discovery-caller writes the hand-off note
- trigger: a booking comes due → tool: crm:context → agent: sales-closer runs intro, discovery, pitch → sell: checkout:create → condition: paid? → tool: affiliate:join-request (the referral ask) | tool: calendar:schedule-meeting (the next meeting, booked on the call)
- trigger: a call recording is ready (VERIFY: no receiver handles it) → tool: video:summary → agent: sales-call-coach scores it by station → human: the manager picks the one thing to fix
- trigger: the gate window closes → tool: workflow:step-stats → condition: numbers clear the gate? → human: the manager approves the move
Tools
Receivers and scripts it signals.
- lead:capture
- visitor:identify
- entity:tag
- crm:context
- voice:call
- email:send
- booking:list-slots
- booking:create
- booking:reschedule
- calendar:schedule-meeting
- video:start-recording
- video:summary
- checkout:create
- checkout:link
- links:create
- affiliate:join-request
- rewards:enroll
- segment:create
- funnel:create
- pages:publish
- media:generate
- workflow:step-stats
- human:notify
- human:resolve
- actor:override
- analytics:overview
Promises
What it holds; a told promise opens its own story.
Events
Every event is a signal; each names the path it marks or warns.
- lead:capture · from the page the stranger is on page → lead; marked when a set follows it tags: sales, lead
- voice:call · from the setter, or an agent in the setter's seat lead → connect; warned when nobody answers, marked on a conversation tags: sales, engage
- booking:create · from the setter conversation → set; marked when the person shows tags: sales, opportunity
- checkout:create · from the closer shown → won; marked by the paid order, warned when the link is never opened tags: sales, won
- affiliate:join-request · from the buyer won → referrer; marked when the person they named becomes a lead tags: sales, referral
- actor:override · from the manager rule → stage; warns the stage the rule chose, marks the stage the person chose tags: sales, lifecycle
Transactions
- a paid order through checkout:create or checkout:link
- the seller's share of a close — VERIFY: no commission rule exists
- each agent turn on the path spends group credit
Analytics
- what sold, on which rail and channel, and who sold it — read today in the sales room (lib/sales/sales-overview.ts)
- people at each funnel stage — read today, all six; Leads counts the workspace's contacts tagged lead (lib/sales/sales-overview.ts, on dev 2026-11-19)
- the seven sales numbers — VERIFY: not computed anywhere