The work before the meeting

Fewer meetings.
Better ones.

prewire prepares your recurring meetings in the 48 hours before they happen. It gathers the context, writes a cited pre-read, asks the two questions that matter, and tells you whether the meeting still needs to exist.

  • Read-only calendar scopes
  • Source material deleted in 24 hours
  • No bot in your meetings

Pre-read

48 hours before

Weekly product sync

Thursday, 10:00 · 6 people · recurring

Open since last time
2 decisions
Answered the questions
4 of 6
Recommendation
Shorten to 20 min

Every claim on the page carries a citation. Nothing that cannot be sourced is written.

The same meeting, twice

The recurring meeting is not the problem. Arriving cold is.

Nothing here needs a new ritual, a new tool for the team to learn, or a change to how the meeting runs. The difference is what everyone knows when they sit down.

Without prewire

  • The first fifteen minutes are spent catching everyone up.
  • The disagreement surfaces at minute forty, with ten minutes left.
  • Last month's decision is re-argued because nobody can find it.
  • The meeting recurs because it is in the calendar, not because it is needed.

With prewire

  • Everyone arrives having read the same page, with its sources attached.
  • The disagreement is on the page before the meeting starts.
  • The decision is cited, with the reasoning that produced it.
  • It is held, shortened or cancelled on the evidence — your call, every time.

How it works

Four steps, and the last one is yours.

prewire runs the same loop before every occurrence of an enrolled series. You see the result 48 hours ahead, with time to change it.

  1. 01

    It gathers the context

    For an enrolled series, prewire collects what the meeting already points at — the documents, the threads, the decisions it has taken before. Everything is read as you, with your own access, at the moment of reading.

  2. 02

    It writes the pre-read

    One page, sent 48 hours ahead. Every claim carries a citation back to the source it came from, and a claim that cannot be cited is dropped rather than guessed. You can edit it before it goes.

  3. 03

    It asks two questions

    Not a survey. At most two questions, delivered in Slack or by email, that surface where people actually disagree. Silence is reported as silence, never filled in.

  4. 04

    You decide what happens

    prewire recommends: hold it, shorten it, or cancel it. The recommendation arrives with its reasoning. The calendar changes only when you press the button, under your own identity.

You choose which series prewire prepares. A meeting you have not enrolled is a meeting prewire does nothing about.

What it does not do

A calendar is a sensitive thing to hand over.

So the limits are built into the system rather than promised in a policy. Each of these is enforced in the code, not configured in a settings page you could turn off by accident.

No bot

It is never in the room

prewire works in the 48 hours before a meeting and stops when it begins. Nothing joins, nothing records, nothing is transcribed.

Your access

It reads only what you can read

Access is checked per document, per reader, at read time, and never cached. There is no crawler and no shared index of your organisation's files.

24 hours

The source material does not stay

Raw context is deleted within a day by two independent mechanisms. What survives is a manifest of which sources were used, so a pre-read keeps its citations without prewire keeping your documents.

One write

One change, and you make it

The single calendar write runs under your own Google identity, after a confirmation dialog, into an audit log. The background worker cannot hold a write client at all.

The full detail is in the privacy policy, which describes the same behaviour in the same terms.

The report, not the promise

It shows you the arithmetic, and where it might be wrong.

Every month prewire reports what it recovered — the meetings shortened, the meetings cancelled, the hours handed back. Attributed and baseline are counted separately, and the regret rate sits beside the total.

An example month

Meetings shortened
9
Meetings cancelled
4
Hours recovered
11.5
Reinstated afterwards
1

Illustrative figures. Your own report shows your workspace’s numbers and the arithmetic behind each one.

Connections

It meets your team where the work already is.

Two connections, and neither of them changes how your team works. prewire delivers into the tools already open.

Required

Google Calendar

Read-only scopes find your recurring series. The one write — shortening or cancelling a meeting — happens under your identity, when you confirm it.

Recommended

Slack

Pre-reads arrive in Slack and questions are answered there. prewire posts as itself and never on your behalf.

Fallback

Email

Anyone not reachable in Slack gets the pre-read by email and can answer by replying. Unreachable is reported as unreachable, not counted as silence.

Questions

The things worth asking before you connect anything.

Start with one meeting

Enrol a single series.
See what it prepares.

Connect your calendar, choose one recurring meeting, and read the pre-read it produces 48 hours before the next occurrence. Nothing else changes until you ask it to.