Operating cadence

Meeting reduction & async decision system

Meetings multiply because there is no rule for which conversations need to be live. We classify each recurring meeting and move status to a written async cadence — AI drafts the pre-read and the decision record, while a person decides what stays live.

Book a 30-min call

Who this is for

B2B

Founders and Heads of Ops whose week is eaten by recurring status and decision meetings.

Engineering and delivery managers running standups, syncs, and reviews that overlap and rarely end in a decision.

Teams where "let's have a meeting" is the default because there is no written async alternative.

Leaders who attend meetings to stay informed, not to decide — and know that information could be read instead of attended.

Operators who have tried no-meeting days and watched the meetings come back because nothing replaced them.

Common pain points

Why meetings usually fail

Recurring meetings are never re-examined: they were added once for a reason that may no longer hold, and nobody owns the decision to end them.

Status and information meetings exist because there is no written async cadence, so the only way to share an update is to gather everyone live.

Decision meetings start without a pre-read, so the first twenty minutes go to getting everyone to the same context and the decision slips to next time.

Decisions taken in a meeting are not recorded, so the same topic returns weeks later and the meeting repeats.

There is no rule for which meetings need to be live, so coordination, information, and decision all get the same default: a recurring slot on the calendar.

Blanket fixes — no-meeting days, shorter slots, fewer attendees — fade because they trim the symptom without changing what earns a meeting.

Book a 30-min call

A rule for which conversations need a meeting — and a written cadence for the rest

A meeting reduction system classifies every recurring meeting by what it is actually for — deciding, informing, or coordinating — and gives each one a verdict: keep, kill, or convert. Information and status meetings convert to a written async cadence with a named owner and a rhythm. True decision meetings stay, but only with a pre-read and a decision captured on record. AI drafts the pre-reads, the async updates, and the decision records; the decision itself stays with a person.

How we work

1
We inventory every recurring meeting and classify each one by its real purpose — decision, information, or coordination — with the people who attend it.
2
We give each meeting a verdict — keep, kill, or convert — and design the written async cadence that replaces the ones we convert: what moves to writing, on what rhythm, and who owns it.
3
We set the pre-read and decision-record standard for the meetings that stay, connect AI to draft them, and hand over a runbook the team operates and edits.

Next step

Talk through which meetings are worth keeping

Book a 30-min call

What we build

What this work includes

Area 1

A meeting inventory with a keep / kill / convert verdict per meeting

We list every recurring meeting, classify it by purpose with the people who attend, and give each one a verdict — keep it live, kill it, or convert it to writing — with the reason written down. The verdict is a decision the team can defend, not a vibe: a meeting stays live only when a real-time exchange changes the outcome.

Deliverable

A meeting inventory: every recurring meeting with its purpose, owner, and a keep / kill / convert verdict and reason.

Area 2

An async cadence that replaces the meetings we convert

For every meeting we convert, we design the written cadence that replaces it: what information moves to writing, in what format, on what rhythm, and who owns posting and reading it. The cadence is specific — a named channel, a named owner, a set time — so async is an actual routine, not a hope that people will read more.

Deliverable

An async cadence document: per converted meeting, what moves to writing, the format, the rhythm, and the named owner.

Area 3

A pre-read standard for the meetings that stay

The meetings that survive the verdict keep happening only with a pre-read: the context, the options, and the decision to be made, written before the meeting. The standard says what a pre-read must contain and when it is due, so the live time is spent deciding, not catching everyone up.

Deliverable

A pre-read standard: the required structure, the deadline before each meeting, and an example for the team's most common decision.

Area 4

A decision-capture template wired to where the team works

Every decision meeting ends with a record: what was decided, who owns it, by when, and whether it can be reversed. We define the template and place it where the team already works, so a decision is captured in the moment and does not have to be reconstructed — or re-argued — later.

Deliverable

A decision-capture template (decision, owner, date, reversible?) placed in the team's existing tools.

Area 5

AI connected to draft the pre-reads, updates, and records — within written limits

We connect AI to the team's tools to draft the async updates, assemble the pre-reads from existing context, and write the first version of each decision record. What AI may draft and what it may never do — decide, or record a decision a person has not confirmed — is written down. AI prepares; a person decides and confirms.

Deliverable

An AI capability map with the limits written: what AI drafts, what a person must confirm, and what AI does not touch.

Area 6

A runbook the team operates and edits

We hand the system over as a runbook: the classification rule, the verdicts, the async cadence, the pre-read and decision-record standards, and the AI limits. The goal is for the system to live without us — the team can re-run the classification when the work changes, and a new lead can pick it up without rebuilding it.

Deliverable

A runbook with the classification rule, the cadence, the standards, and a periodic re-review agenda the team owns.

Book a 30-min call

Every recurring meeting has a reason on record, so the calendar reflects decisions the team can defend — not slots nobody remembers adding.

Status and information move on a written cadence with a named owner, so people stay informed without attending a meeting to do it.

The meetings that stay begin with a pre-read, so live time is spent deciding, not getting everyone to the same context.

Decisions are captured in the moment — what, who, by when, reversible — so the same topic stops coming back as a new meeting.

AI does the drafting — updates, pre-reads, decision records — and the decision itself stays with a person, with the limit written down.

The rule, the cadence, and the standards live in a runbook the team operates and edits, not in one person's calendar habits.

Book a 30-min call

Answers before we start

Are you going to delete all our meetings?

No. The goal is fewer meetings that earn the time, not zero. Some conversations genuinely need to be live — a hard decision with real disagreement, a sensitive conversation, a first alignment on something ambiguous. The system keeps those and removes the default that everything else also becomes a recurring slot.

Does AI sit in our meetings or decide for us?

No. AI drafts the pre-reads, the async updates, and the first version of each decision record from context the team already has. It does not decide, and it does not record a decision a person has not confirmed. The line between what AI drafts and what a person decides is written into the system, not left to default.

Do you promise to cut our meeting time by a specific percentage?

No. Promising a number before seeing your calendar and your decisions is not honest. What we promise is a rule for which meetings earn the time, a written cadence for the rest, and decisions that get captured instead of repeated. How much time that frees depends on your team and your work, not on a figure we commit to up front.

Is this a scheduling or calendar tool?

No. We do not sell or build a scheduling app. This is the rule, the cadence, the standards, and the AI limits — the operating system for which conversations need a meeting. It runs inside the calendar and tools you already use; if a specific tool would help, we will say so without a referral fee.

What if the real problem is unclear ownership, not too many meetings?

Often it is — meetings multiply when nobody owns a decision. If the diagnostic shows the issue is ownership or how decisions are recorded, we will say so and point you to the decision-capture and workflow work that fits, rather than trimming meetings that are a symptom. We do not sell a meeting audit as the answer to a different problem.

What does this work NOT include?

It does not include a scheduling or calendar tool, meeting-culture coaching or facilitation training, removing the meetings that genuinely need to be live, or an AI that runs meetings or makes decisions for the team. It also does not include reorganising the team or rewriting the operating model. If what you need is one of those, we will tell you and point you to the right partner.

Ready to keep only the meetings that earn the time?

Book a 30-minute call to look at where your week goes. We will talk through which recurring meetings decide something, which only inform, and what could move to a written cadence — and what the team can realistically run. If the real problem is ownership or how decisions are recorded, we will tell you and point you to the work that fits.

Book a 30-min call

Meeting reduction & async decision system

Why meetings usually fail

A rule for which conversations need a meeting — and a written cadence for the rest

What this work includes

A meeting inventory with a keep / kill / convert verdict per meeting

An async cadence that replaces the meetings we convert

A pre-read standard for the meetings that stay

A decision-capture template wired to where the team works

AI connected to draft the pre-reads, updates, and records — within written limits

A runbook the team operates and edits

Answers before we start

Are you going to delete all our meetings?

Does AI sit in our meetings or decide for us?

Do you promise to cut our meeting time by a specific percentage?

Is this a scheduling or calendar tool?

What if the real problem is unclear ownership, not too many meetings?

What does this work NOT include?

Related solutions

Decision capture system

Operational reporting system

Meeting notes to action system

More operating cadence solutions

Decision capture system

Operational reporting system

Meeting notes to action system

Decision memory system

Ready to keep only the meetings that earn the time?