tobto.Book a demo

Meeting prep packs

Why a prep pack that lists everything known is worse than one that lists what is not known, and why this is the only capability whose output is meant to be thrown away.

C3 Sell

The operational shape

Trigger
A scheduled meeting — the format is owned here, instances are generated per meeting
Reads
The account, from entities. Competitor context, from the market map. What came up last time, from learnings.
Cadence
Format maintained; instances per meeting
Gate
Approve before publish for the format

Most prep packs answer the wrong question. They assemble everything known about an account, which the person going into the meeting mostly knows already, and they use up the only screen of attention available doing it.

The useful question is what this person does not know and would want to. A recent change, a competitor showing up, a thing said on the last call that was never resolved. Prep is judged by what it adds.

The operational shape

Trigger. A scheduled meeting. The format is owned here; instances are generated per meeting by the sales side — the same boundary that applies to outbound templates and proposals.

Reads. The account, from entities. Competitor context, from the market map. What came up last time, from learnings.

Cadence. Format maintained; instances per meeting.

Gate. Approve before publish for the format.

What good looks like

It leads with what changed. Since the last contact, or since the account was last looked at. A pack that opens with company background opens with the part nobody needed.

It names the open thread. The question left unanswered last time, the objection that was deferred, the person who was supposed to be looped in. This is the single highest-value line in any prep pack and it is usually absent.

Recency beats completeness. A short pack of current facts outperforms a thorough one containing anything more than a few months old, because old context is where wrong assumptions come from.

It says what is unknown. The gaps, explicitly. A pack that presents partial information as complete produces a call where somebody confidently asserts something nobody checked.

One screen. Read in the five minutes before a call, and nothing below the fold exists.

When it goes stale

This is the only capability whose output is meant to be thrown away. An instance is stale the moment the meeting ends, by design, and that is fine — nothing is lost.

The format is what decays, and it does so in three ways. The meeting type changed, so a pack built for discovery is being used for renewals. The sources moved, and a section that used to be filled automatically is now silently empty. The pack stopped being read, which is the signal that matters and the one nobody measures — a format that gets skipped is a format that has been wrong for a while.

What it feeds

  • Learnings — what actually came up, against what was prepped, which is the only way the format improves
  • Battlecards — a competitor appearing repeatedly in prep is a competitor that needs a card
  • The account record — the open thread, closed or carried forward

The feedback loop is the whole value. A prep format that never learns what the meeting actually needed is a guess repeated indefinitely, and it will keep being generated long after it stopped helping.

Frequently asked

How long should a prep pack be?
One screen. A pack read in the five minutes before a call has one screen of attention available, and everything past it is unread regardless of quality.
What should it leave out?
Everything the person already knows. A prep pack is judged by what it adds, and a summary of the account history the rep lived through adds nothing while costing the whole screen.
Who owns the format versus the instances?
The format is owned here. Instances are generated per meeting by the sales side, which is the same boundary that applies to outbound templates and proposals.

See the system running on itself

We read your website to get started.