Companies

The stand-up, the review, and the thing nobody wrote down

Most of what a company loses to meetings is not the hour. It is the half-hour afterwards writing up what was decided, and the fortnight later when nobody can find it.

Nobody volunteers to take the minutes

So they do not get taken, or they get taken badly by whoever felt worst about the silence. A fortnight later the only record of a decision is two people remembering it differently.

Every meeting here can write its own — the summary, what was decided, and who undertook what, each item checked back against what was actually said rather than asserted. They arrive by email a few minutes after the meeting ends, with nobody asked to do anything.

“When did we agree that?”

The transcript is searchable across every meeting, so that question is a search rather than an afternoon of asking people. It is kept only for the meetings you choose to keep it for, and an administrator can delete it properly — which takes the minutes and the summary with it, because a summary written from words you have deleted still contains the words.

It fits the calendar you already have

Meetings are created from your own software through our API, appear with the right people already invited, and send back what happened. Everybody signs in with the account they already use.

And a meeting that has to move stays the same meeting — same link, same people — because a link that breaks is a meeting somebody misses.

The parts that matter most to you

Out of about a hundred. Each one has a page saying what it does and what it will not do.

  • A recap with decisions and actions

    On the meeting’s own page afterwards — and every item checked back against the transcript rather than asserted.

  • A searchable transcript

    Kept only when the host asks for it — and then searchable, so “when did we agree that” is a search rather than an afternoon.

  • Minutes, written and emailed

    Produced from the transcript a few minutes after the meeting ends, and emailed to the people who were in it.

  • A real API

    Create meetings, add people, read attendance and sign somebody in — versioned, and documented by a specification that cannot drift from the implementation.

  • Moving a meeting

    Change the date, the time, the length or the zone. Same link, same code, same people — and everybody invited is told, with the old time struck through.

  • Handing over control of your screen

    They click and type on your machine rather than pointing at it. No web page can ever do this, which is the whole reason the desktop app exists.

  • The Studio

    Scenes, virtual sets, a place to wait before going on, talkback to whoever is presenting, name captions, audience overlays and a vertical cut for phones.

  • One organisation can never see another’s data

    Enforced by the database itself, not by remembering to write the right query. A mistake fails closed instead of leaking.

Everything it does

What you can ignore

A good deal of this product was built for places that teach, and you can ignore most of it: the tests, the lesson library, the shared code and science workspace, the register with its arithmetic. None of it is in your way — the tools that are not switched on are not drawn.

Not quite you?

Tell us how your organisation actually runs

We will answer with what this would look like for you — which parts you would use, which you would never touch, and what it would take to connect it to what you already have.

info@seeuall.com