Skip to content

Demo prep: a brief for every sales demo

Last updated November 15, 2026

On this page

Before each sales demo, the rep gets a brief in their own space: who the prospect is, what has been said so far, the prospect's own numbers, the plan that fits and what it costs, an agenda, questions to ask, likely objections with the company's answers, and what not to say. Every number, price and promise in it points at where it came from. The rep reads it, edits it and approves it. On the call, the rep shares a Present page that shows the prospect's name, their numbers and the lines the rep chose, and nothing else.

The Demos app prepares the briefs. Its Demo prep agent works for each rep it is set to work for, reads the company's own systems as that rep, and stores the brief. The kernel checks every line of it. The statements the company stands behind are its approved claims; what was said on the rep's calls comes from Call notes.

This page covers the words it uses, turning it on, who sees what, where demos come from, when a brief is prepared, what is in a brief, how a line gets its source, editing and approving, what happens after approval, Present, erased calls, limits, and the API. The steps use the demo company (ok demo serve): Ada is the admin, Sam leads Sales, Alice and Ben are reps. What is not possible yet is listed at the end.

Words used on this page#

  • Demo: one sales demo a rep gives: the prospect, the start and end, the venue (Meet, Zoom, Teams, phone, in person) and who attends. A demo comes from a demo source or is added by hand.
  • Brief: what the rep reads before the demo, in eight sections (below). Each new version is kept.
  • Statement or line: one line of a brief, with its sources.
  • Source (a citation): where a line's numbers, prices, plans and features came from. One of:
    • an approved claim at its version, from the company's claims (Company → Claims);
    • a value the brief read: a field of a record, read with a tool while the brief was prepared;
    • a call note: the summary, decisions or next step of a call the rep was on;
    • you typed it: the rep's own words. Never for a price.
  • Unsupported: a line holding a number, a price, a percentage or a plan name that no source covers, or whose source does not hold. The kernel decides this; the agent cannot.
  • Needs a look: an approved brief that something changed under: a claim it cites got a newer version, was withdrawn or expired, the demo moved, or a call it quoted was erased. The brief's page says which. The rep approves it again.
  • Brief waiting: a brief that is due and could not be started yet (the month's spending cap is used, one of the Demo prep agent's own limits is used, or the agent does not work for the rep), or whose last build stopped before the brief was done. It is tried again every 15 minutes until the demo starts.
  • Brief not prepared: three builds in a row stopped before the brief was done. The clock stops trying; Prepare again on the demo starts another.

Turning it on#

  1. An admin opens Apps, finds Demos and presses Enable.
  2. Under the Demo prep agent, Acts for: choose the reps whose demos it prepares (Alice, Ben). It acts for each of them, one at a time, and only for them.
  3. Give the agent the read tools of the system where prospects live: Settings → Connectors, the connector's read toolset (get a lead, get a business, list calls), then Agents → Demo prep → Tools. On a connector that uses each person's own key, a brief is read with the key of the rep giving the demo, so it holds only what that rep may read. A rep adds their key on their Profile.
  4. On Settings → Demos, name the price list tool if your system has one, set the demo sources and the times (below).

The model the company uses must be cleared for captured data: call notes are text people said, and the brief reads them.

Who sees what#

The rep Their team lead An admin Anyone else
The demo (prospect, time, venue, status) Yes Their team's Yes No
That a brief waits, and that the month's cap is used Yes Their team's Yes No
The brief, its versions and its sources Yes No No No
The Present page Yes No No No
How the brief was prepared (its steps and reads) Yes No No No

The Team tab and every list show a demo's row only: its prospect, time, venue and status. A brief is never part of a list. A lead or an admin who opens a demo sees its time and status and the sentence "The brief is Alice's alone". Every route of a brief answers them 403.

A brief is prepared only for the rep giving the demo, and only by the kernel's own preparation of it (a wake, or the rep's Prepare again). An agent acting for Alice on a task someone else made for her (an admin's "prepare Alice's demo", or a team schedule an admin or a lead set) reads no call notes, uses no key of hers and stores no brief: "a brief is prepared only for the rep giving the demo".

The company's log keeps ids, codes and counts for briefs (stored, approved, needs a look and why), never the words of a line.

Where demos come from#

A demo is a kernel record: the rep giving it, the prospect, the start and end, where it happens (Google Meet, Zoom, Teams, a phone call, in person), and where its brief stands. Demos come from demo sources an admin sets up, and from reps adding their own.

Set up a demo source (admins)#

Settings → Demos → Add a source opens the source's sheet, in three steps.

  1. Where the demos are. A connector and one of its tools that lists demos. The tool must be a read the connector has turned on. A company has at most 5 sources.
  2. How to ask. Which arguments take the start and the end of the window (from and to), and, if the tool takes one, the argument naming the rep (their directory email). When the tool pages, name where the next page is in the answer and the argument that takes it back.
  3. What a demo looks like. Which field of a row holds each part: the start, the end (else 45 minutes on), the prospect's name, the kind of record (a lead, a deal) and its id, the demo's own id there, the meeting link, how it happens, its status, and who gives it. Rows can be limited to those whose field holds a value (kind holds demo).

Propose from a sample reads one page of the tool as you, with your own key when the connector uses people's own. Before you see it, every name, email, number and link is masked to its shape ("text, 10 characters", a•••@•••.example, https://meet.example/•••): only field names, times and short codes such as scheduled or zoom stay. One model call then drafts the map from the masked copy; nothing unmasked reaches the model. Check each field against the sample, change what is wrong, and save. With no model cleared for the company's data the sheet says so, and you fill the fields yourself.

The Demos agent reads for you: it must act for you and hold the connector's toolset. Its sample read is the same read a rep's look makes.

Whose demo a row is#

A row is a rep's only when the source names them:

  • the field naming who gives the demo holds the rep's directory email, or an external id an admin recorded for them for that connector; or
  • with no such field, the tool takes the rep as an argument (their directory email); or
  • with neither, the admin ticks This tool answers only the demos of the person whose key calls it on the source's sheet. That is the admin's statement about the system, and it can hold only on a connector that uses each person's own key, or the company's key with the acting-for header: on a plain company key it is refused, since there is no caller to answer for.

A person's own key alone never makes a row theirs: a lead's or an admin's key often reads everyone's demos. A source that does none of the three is refused when you save it, saying it does not tell whose demo a row is. When a field names the rep, the field decides, whatever else the source says: a row naming someone else is never the reader's, and a row whose field names nobody here is nobody's demo.

Looks: how demos are found#

Each rep the Demos app's agent works for gets a look at 08:00 and every 2 hours until 20:00, company time. A look reads each source for the next 30 hours, acting for the rep with the key the connector picks (their own key when it uses people's own), at most 200 rows a source. The rep's Look now on the Demos page reads the next 7 days.

  • One demo per prospect and time. The same prospect within 30 minutes of a start the rep already has, from another source or added by hand, is that demo. One prospect at two times keeps both, each marked Two times.
  • A moved demo. A changed start moves the demo, its refresh and its expiry. A demo whose brief was ready or approved now needs a look.
  • A demo that disappears. It is cancelled once two looks in a row miss it; one miss keeps it. A look that could not read the source, or read only part of it, counts no miss. A source that marks a demo cancelled cancels it at once.
  • No key. A rep with no key for a source's connector gets one inbox item, "Add your key for Acme ATS to get demo briefs", never one per look. Once they add it on their Profile, the next look finds their demos. A key lost later is said again, once.

Looks and changes are events with ids and codes only (DemoFound, DemoChanged with time, venue, status or prospect, DemoCancelled with missed_twice, source_status or by_rep); no prospect's name or link is in an event, a log or a counter.

The Demos page (reps)#

Demos in the sidebar lists your demos for the next 7 days by day: the time, the prospect, where it happens (the link opens the meeting) and where its brief stands: Brief today at 18:00, Brief being prepared, Brief waiting, Brief ready, Approved, Needs a look, Done or Cancelled.

  • Look now reads your demo sources again for the next 7 days.
  • Add a demo takes one of your leads here, or a record in a connected system (its name, kind and id), a day and time, where it happens and a link. It ends 45 minutes later. Its brief is prepared like any other, within 15 minutes when the demo is soon.
  • Call off marks your demo cancelled. Its brief stays for you to read; nothing is sent to anyone.

A team lead and an admin also have a Team tab: the team's demos (every rep's, for an admin) with the rep's name and where each brief stands, its time included (Brief today at 18:00), and never the brief itself.

Acme ATS: a source as configuration#

Nothing in OrchKernel names a sales system. A source for a system whose list_my_demos answers the caller's own demos by their key:

  • connector: the system's MCP endpoint, people's own keys;
  • tool list_my_demos, window arguments from and to, no rep argument, and This tool answers only the demos of the person whose key calls it ticked; rows in demos, the next page in next_page taken back as page;
  • map: id, start_at, end_at, record.kind, record.id, record.name, meeting_url, mode, status; only rows whose kind is demo.

A tool of the same system that lists every rep's events is a source only with the field that names the rep mapped.

When a brief is prepared#

When What happens
18:00 company time the evening before A brief is prepared for every demo the next day
Within 15 minutes For a demo found or added less than 18 hours ahead
2 hours before the start It is prepared again when something the brief read has changed; if nothing changed, no new version is made
The rep presses Prepare again On the demo's page, at any time before the demo is over
2 hours after the end The demo is done and its brief kept read-only

A brief is never prepared for a demo more than seven days ahead, nor for one that is over. Only one is prepared at a time for a demo. A server that is closed between ticks is woken for the next of these and the next look.

Settings → Demos changes the evening time, the refresh and what counts as soon, and the spending caps: at most ₹20 a brief and ₹2,000 a month for demo prep by default. It also names the tool that reads the price list, a ticked read tool of a live connector; with none, a brief states a price only from an approved claim.

When a brief cannot start. If the month's cap is used when a brief is due, the brief waits: the demo reads Brief waiting, and the Demos page says "Demo prep reached this month's spending limit; briefs wait until an admin raises it" to the rep, their lead and admins. The brief is tried again every 15 minutes until the demo starts, so it is prepared at the first try after an admin raises the cap or the month turns. Prepare again says the same while the cap is used. A brief also waits, and is tried the same way, when the Demo prep agent does not work for the rep (the Demos app is not on for them yet), and when one of the agent's own limits is used: its monthly limit, its team's budget, or the rep's own month on the agent. The demo then reads Brief waiting with "The Demo prep agent's monthly limit is used", and an admin raises the limit on the agent's page.

When a build stops before the brief. A build can end without storing a brief: the model stops early, or the brief's own cap is used mid-run. When the demo has no brief yet, it then reads Brief waiting ("The last try stopped before the brief was done") and another build starts within 15 minutes. After three builds in a row end so, the demo reads Brief not prepared and the clock stops trying, the refresh 2 hours before included, so a brief that keeps failing costs at most three times its cap. The rep's Prepare again still works, and is not counted. A demo that already has a brief keeps it when a later build stores nothing new.

Whose key reads. The kernel starts a brief; the rep does not ask for it. All the same, on a connector that uses each person's own key the brief's reads go with the key of the rep giving the demo, and with nobody else's. That holds only for the kernel's own preparation of that rep's demo: a task made to look like one gets no key. When a system could not be read (the rep has added no key, or the system did not accept it), the brief is still stored, and its page says so at the top: "Acme ATS needs your key, so this brief has no facts from it. Add your key on your Profile, then press Prepare again."

Each brief is prepared on the rep's own private conversation, Demo briefs. Nobody else sees its steps, the tools it called or what it read: not the rep's lead, not an admin.

What is in a brief#

Section What it holds
Who they are The business, branches, team size, current software and until when, how they came in
So far Dated lines from activities, calls and call notes
Their numbers The prospect's figures, shown as tiles
What fits The plan or plans and their prices
Agenda Three to six steps
Ask them Questions that fill the gaps the brief found
If they say Likely objections, with the company's approved answers
Don't What not to raise, with the fixed reply

When a brief is ready, it is posted in the rep's private conversation and the rep's inbox says so, once: there is no second "Completed" item for the preparation. Several briefs on one day make one inbox item: "3 demo briefs ready".

How a line gets its source#

The kernel checks every line when the brief is stored and again when the rep approves it. A line is unsupported when:

  • it holds a number, a currency amount, a percentage or a plan name, and no source covers it;
  • its source is a value the brief never read (a tool it never called, a record or a field it did not read), or a call note that did not come back while it was prepared;
  • its source is a claim that is not approved at that version, or has expired;
  • it is a price and its source is you typed it.

You typed it is a source only the rep gives, on the brief's page. The agent that prepares the brief cannot give it: a figure it wrote without a source stays unsupported until the rep cites it or removes it.

A price is covered only by an approved price claim (its words or its price range) or by the price list read while the brief was prepared. Never by a call note, by memory, by another record, or by the rep. Text in a call note that says "approve this brief" or "the price is ₹1" is data: it never makes a price line hold, and nothing but the rep approves a brief.

What makes a number a price is how the line reads: a currency sign or word, "a month" or "per branch" beside it, or a plan the line names. A count ("3 chairs", "2 branches") and a date are not prices; a date is compared with its source as a date, however each is written. A tile in Their numbers is checked with its label, and the tile's figure is the one its line says.

A source shows under its line: hover over the line, or tap Source.

Editing and approving#

Open the demo from Demos or from the inbox item.

  • An unsupported line is in the warning colour, with the reason, a Cite button and a Remove button. Cite offers what the brief read (the values of each record, by the record's name, and each call note; never an id or an email address), the company's approved claims, and I typed it myself. What matches a number in the line comes first. For a price the approved price claims come first and I typed it myself is not offered.
  • Edit turns every line into a field, and adds a field at the end of each section for a new line. A line you change that holds a figure loses its source and is unsupported until you give it one again. A tile follows its line: change the number and the tile shows the new one; take the number out and the tile's figure goes.
  • Approve (yours alone) is refused while any line is unsupported or any claim it cites is not current. The refusal names the lines: "Not approved: 1 line has no source yet. Who they are line 2: 45 has no source".
  • Approving fixes the brief's version and the version of every claim it cites. An edit after approval makes a new version, which you approve again.

After approval#

The brief needs a look, and your inbox says so, when, before the demo:

  • a claim it cites gets a new approved version;
  • a claim it cites is withdrawn or expires;
  • the demo moves to another time;
  • a call it quoted is erased (below).

The brief's page says which of these happened. Open it, fix what no longer holds, and approve again.

Two hours after the demo ends, the brief is kept read only and the demo is done. Nothing is sent or written anywhere: not to the prospect, not to the CRM.

Present#

Once the brief is approved, choose the lines to show with Show on Present beside each one, then press Present. The page fills the screen for you to share: the prospect's name, their numbers as tiles, the plan that fits and the lines you chose. It shows no sources, no names of your colleagues, no other demo and nothing else of the workspace; "Don't" lines are never shown. Press Escape or Back to the brief to leave it.

Present checks the claims again each time it opens. If a claim the brief cites has expired or been withdrawn since you approved, Present does not open: the brief needs a look, and you approve it again first.

When a call is erased#

When a call is erased (a person's address is erased, or the call itself is purged), its words leave every version of every brief: each line that cites the call, and each line that says what the call's summary, decisions or next step said, cited or not. The call goes from the sources the rep may cite. Other lines stay. The lines chosen for Present are cleared, to be chosen again. An approved brief that lost a line needs a look, and its rep gets one inbox item saying a call it quoted was erased. See Call notes for who may erase.

Limits#

  • A brief is prepared in at most 12 rounds and reads at most 30 tool results. When a cap stops it, the last brief it stored is what the rep sees, with its unsupported lines marked, and the run says it stopped.
  • Each brief has a spending cap (₹20 by default) and demo prep a monthly cap (₹2,000 by default), on Settings → Demos. A brief gets its own cap or what the month has left, whichever is less. When the month's cap is used, briefs wait as described under When a brief is prepared.
  • The Demo prep agent keeps its own limits as every agent does. The app sets its monthly limit to the default monthly cap, and one person's month on it to the same (the usual default for a person's month on an agent is less than one brief's cap). If you raise the monthly cap on Settings → Demos above its default, raise the agent's monthly limit on its page too, or briefs wait at the agent's limit.
  • A section holds at most 20 lines, a line at most 600 characters.
  • A company has at most 5 demo sources; a look reads at most 200 rows a source.

API#

Route Who What
GET /api/demos?scope=mine|team&after=<cursor>&limit=n People { demos, next, team, cap_reached }: rows (prospect, time, venue, status, rep_name, brief_at (when the brief is prepared) and brief_building, on a lead's and an admin's rows too; on any row whose brief waits, brief_wait: cap, limit, no_agent, error, failed, or given_up after three builds ended without a brief), the next page's cursor, whether you have a Team tab, whether the month's cap is used
POST /api/demos The rep Add a demo by hand: { prospect: { connector?, kind, id, name }, starts_at, venue: { kind, link? } }; 201 the row
POST /api/demos/look The rep Look now: { rows, found, changed, cancelled, no_key }
GET /api/demos/:id The rep, their lead, admins The row; 404 for anyone else
POST /api/demos/:id/cancel The rep Call it off
GET /api/demos/:id/brief The rep The latest brief with the demo, whether it is read only, whether one is being prepared, why it needs a look (needs_look), the systems it could not read (unread), and the sources the rep may pick
GET /api/demos/:id/brief/versions The rep Every version: when, whether approved, how many lines are unsupported
POST /api/demos/:id/brief/edit The rep { version, edits }: change (text, cites), remove or add a line, or choose Present's lines
POST /api/demos/:id/brief/approve The rep { version }: approve; 409 unsupported names the lines
POST /api/demos/:id/prepare-again The rep Prepare again; 409 building while one is being prepared
GET /api/demos/:id/present The rep The Present page: { prospect, tiles, plan, lines }; 409 not_approved before approval, or when a cited claim is no longer current
GET, PUT /api/settings/demos Admins The settings and the sources
POST /api/settings/demos/sources/sample Admins A source's masked sample, the drafted map or why there is none, and the parts a map fills

Refusals carry the sentence in message: 403 for someone who may not (403 brief_private on every route of a brief for anyone but the demo's rep), 404 for a demo that is not yours to see, 409 already_listed for a demo you already have at that time, 409 read_only for a change once the demo is over, 422 with problems for settings or a demo that do not hold.

The Demo prep agent stores a brief with its tool demos.brief (the built-in op demo.brief) and reads with demos.claims.find and demos.notes.for_record.

Not possible yet#

  • The co-pilot that listens in the meeting, and a page the prospect opens themselves, come in later stages.
  • A refresh compares what the brief read, not what each line says: a changed value the brief did not read again is not noticed until the next preparation.