Good to see you.

Rehearse the meeting before it happens — out loud, with someone who pushes back.

Business case interview

Read a short case, uncover what the client really needs, then brief your engagement lead and the technical team. A new case every time.

Recent rehearsals

No rehearsals on this device yet.

Business case interview.

The interviewer plays a client with a business problem. You read a short case about the company, then uncover what they really need — and brief your own people on it.

Read the caseAbout five minutes. Then it closes.
Discovery with the clientYou ask; they answer only what you ask. What they asked for is not the whole story.
Brief your engagement leadThe real problem, what it costs, the business requirements.
Debrief the technical teamSystems, data, integrations, technical requirements, what's unknown.

The company

Give as much or as little as you like. Leave it all blank and the desk invents a company.

Company name

Annual revenue

What the client says they need

Everything else — people, systems, figures, the real problem — is invented, and none of it is a claim about a real organisation.

Steer the case Industry, kind of problem

Industry

Kind of problem

Difficulty

Hard: a terser client with a fix already in mind, more that is guarded, less reading time.

Length

Client 22 · your lead 8 · technical team 10.

What you type goes to the reasoning service once, to write the case. Nothing is stored.

Tell us about the meeting.

Three short questions, in your own words. We build your counterpart from the answers.

Add a document Starting…

How the meeting runs

Set from your answers

How they respond

Formal holds challenges for the pauses. A talk puts you in front of a room, with questions from several voices.

Where

On video they cut in less, and fill a silence sooner.

Length

They close the meeting when the time runs out.

Objections

Not a difficulty setting. The same concerns need the same evidence either way.

Kind of meeting

Your position

Presenting findings: the meeting is about their organisation, so they defend and contest the record.

Audience (for a talk)

All optional. None of these builds a counterpart on its own — your answers do.

—

Your goal

What they will press on

What this rehearsal can't tell you Limits

Built from your answers in a few minutes rather than written in advance for this kind of meeting. It can still give you a rehearsal. It is thinner than a written scenario in these specific ways:

What leaves this browser Nothing is stored

Your audio passes through these three services while you speak. Nothing is written on our side — not the audio, not the transcript, not the debrief. On this device: counts of your speaking habits and a short history (date, meeting, ref), unless maximum privacy is on.

Ready when you are

Sound check

Thirty seconds: two test tones, then say something. Headphones on.

Voice

Maximum privacy Nothing kept on this device either — no transcript on screen, no history, no habit counts.

Run the sound check first.

Ref

——

—

…

Listening · nothing you say is stored

— / —

Shown in this browser and sent nowhere. Arrow keys turn the pages.

No live scoring and no hints. Everything is held for the debrief.

Debrief

Writing the debrief…

Library

Written scenarios, ready to rehearse. Each tells you its limits before you go in; none has been reviewed by an outside expert.

Business case interview

Not a written scenario: a new case each time. Read about the company, run discovery with the client, then brief your engagement lead and the technical team.

Loading…

Your debriefs

Written after each meeting, from that meeting's own evidence.

Why there is no archive

A rehearsal is gone when it ends — the audio, the transcript and the debrief with it. Nothing you said is on our servers, so there is nothing here to browse. Copy a debrief or save it as a PDF before you close it.

What this device keeps, if you allow it: counts of your speaking habits, with no words attached. That is what Progress reads.

Progress

Habits that keep showing up in how you speak, and whether they are moving. Compared with your own history, never with anyone else.

Nothing here yet. This fills in after your first rehearsal on this device.

What gets kept: how often a tracked phrase came up, 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 outside target.

Settings

Appearance

What this device keeps

Keep no habit counts. Rehearsals still run and debriefs still arrive; nothing is counted afterwards.

Account

Signed in.

What we keep In one paragraph

What you say in a rehearsal passes through the three services that transcribe it, reason about it and voice the reply, and is gone when the rehearsal ends — it is not written to our disks, our databases or our logs. The debrief exists only on your screen. Habit counts, if you allow them, stay on this device, never on our servers.

The meeting before
the Meeting.

They push back

The debrief is evidence

The room burns

Inside the desk

Brief the meeting

Rehearse out loud

Read the debrief

Watch your own habits

Take a seat

This browser cannot run the room

Good to see you.

Pick up where you left off

Recent rehearsals

Business case interview.

Tell us about the meeting.

—

Debrief

Library

Your debriefs

Progress

Settings

The meeting beforethe Meeting.

They push back

The debrief is evidence

The room burns

Inside the desk

Brief the meeting

Rehearse out loud

Read the debrief

Watch your own habits

Take a seat

This browser cannot run the room

Good to see you.

Pick up where you left off

Recent rehearsals

Business case interview.

Tell us about the meeting.

—

Debrief

Library

Your debriefs

Progress

Settings

The meeting before
the Meeting.