Rehearsals

Ready when you are.

A rehearsal is a meeting you can afford to get wrong. Build one from your own brief, or take a written scenario off the shelf.

Last time

No rehearsals on this device yet.

What this is

A counterpart who pushes back, a critic who writes to you afterwards, and nothing kept in between. The rehearsal is spoken, out loud, against the clock.

Rehearsals burn when they end. Analytics keep only counts of your own habits, stored on this device.

Rehearsals

Briefs in progress remain here for two hours after your last edit. What you typed stays on the draft — this list knows only how far along each one is.

Continue a brief

Loading…

Written scenarios

Brief the meeting

Set the particulars below in a few clicks. Then tell us, in your own words, the part no list can supply — what you need from the room, and where they will press.

Meeting type
Sets where the meeting happens — and nothing else. It cannot supply your objective or your concerns.
Your position
Who the meeting is about. Seeking a decision: they hold it and you are moving them — the default. Presenting findings: the meeting is about THEIR organisation — an audit close-out, a review readout, a decision already made — so they respond as the person in the material: defending, contesting, negotiating the record, not examining you from outside it. Negotiating: each of you wants something from the other.
Meeting format
Sparring: they cut in the moment something does not hold. Working session: the middle ground. Formal: they let you finish and note challenges for the end — the notepad is the pressure. Conference talk: you present to a room, and questions come from a queue of audience voices at pauses — what you are managing is the room’s regard, not one person’s decision.
Setting
On a video call they interrupt less — cutting in risks talking over someone who already stopped — but silence gets filled sooner, because a pause looks like a frozen picture.
Disagreement style
Whether the objection gets said out loud or left for you to read in the questions they keep asking. This is not a difficulty setting — the same concerns exist and take the same evidence to close either way.
Audience
Matters most for a Conference talk. Same concerns, same difficulty — different angle: specialists drill how it works, leaders drill what it costs and decides, practitioners drill what happens on an ordinary Tuesday. Mixed rotates all three.
Duration
The counterpart works to this clock and closes the meeting when it runs out.
Everything above is optional and can be changed. None of it builds a counterpart on its own — that takes the three answers below.
Available once the three questions above are answered.
What we have

Nothing yet.

Nothing we suggest is used unless you say yes to it. A counterpart built from our guesses about your industry is a rehearsal for a meeting you are not having — and you would not be able to tell.
Progress

Starting…

Or rehearse one of the written scenarios instead:

—

What this rehearsal will press
Your objective

Before you start

Two things break a rehearsal more than anything else: a muted tab, and laptop speakers feeding the counterpart's voice back into your microphone so they interrupt themselves.

Before you go in — what leaves this browser

Nothing is written on our side — not the audio, not the transcript, not the debrief. On this device: habit counts and a memento (date, room type, ref), unless maximum privacy is on.

Their voice: Run the audio check first. Same meeting as:
——
—
…
listening · nothing you say is stored
— / —
Your materials are rendered in this browser and sent nowhere — arrow keys turn the pages.

No live scoring, no hints. Everything the system notices is held until the debrief — you cannot rehearse while being told how you are doing.

Debrief

Writing the debrief…
Rehearse this again

Same meeting

The same counterpart, the same questions, the same private situation — so a better result means you improved, not that the meeting got easier.

Fresh variation

Same brief, a fresh draw. Tests whether the improvement transfers instead of being memorised.

Keep what you want

The debrief burns with the page. Nothing here reaches our servers — copying and printing happen in this browser only.

Library

Written scenarios, reviewed by hand. Each one states its limits before you go in — none is certified by an outside expert, and each briefing says so.

Loading…

Debriefs

Written by the critic after each meeting, from the meeting's own evidence.

Why there is no archive

Rehearsals burn when they end — the transcript, the audio, and the debrief with them. Nothing you said in a rehearsal is on our servers, so there is nothing here to browse. Copy a debrief before you close it if you want to keep it.

What survives, if you allow it: counts of your own verbal habits, with no words attached, stored on this device. That is what Analytics reads.

Analytics

Habits that keep appearing in the way you speak, and whether they are moving. Counts only — compared to your own history, never to a norm.

Nothing here yet. Analytics fill in after your first rehearsal on this device.

What gets kept: how many times a tracked phrase occurred, and how long you spoke — numbers, never words. It stays on this device and can be cleared in Settings.

We count words and pauses. We do not judge accent, dialect, pronunciation, or identity — and nothing here is scored against other people or an external target.

Settings

Appearance

Obsidian is the room's native dark; Atelier is the same product in daylight.

Analytics

Account

Signed in.

What we keep, in one paragraph

What you say in a rehearsal is processed live and burned when the session ends — it does not touch our disks, our databases, or our logs. The debrief exists only on your screen. Analytics, if enabled, keep counts of tracked phrases and minutes spoken — on this device, never our servers.