Skip to content

Your consultants know what happens on each engagement. Now your company does.

Client requests, decisions and risks occur in calls and messages during the working day. They are not always written into a document. When a consultant leaves the engagement, the unwritten part leaves with the consultant.

Built by consultants, and used on our own engagements every day. macOS 26 or later, Apple silicon.

Selective by design: the window you work in, in apps you allowText, not video: nothing visual is storedAudio only in meetings: no bot joins your callsPause everything from the app or menu bar

Unrecorded work costs your consultancy three times

Additional work is not billed

A client requests additional work in a call. The consultant agrees. The request is not written down, and the consultancy does not invoice for it.

The consultancy pays for the handover

A new consultant reads previous documents and asks the client to repeat information from earlier discussions. The consultancy pays for that time.

The consultancy can lose a client dispute

A client and the consultancy disagree about what was agreed. Without a dated source record, the consultancy has less supporting evidence.

How it works

Capture: on the consultant's Mac

Overshow sits in the menu bar. Meetings are recorded only while a meeting is happening, and the working window is read at natural moments (a window change, a click, a pause in typing), never as a video. Password managers, private browsing, and excluded apps are never captured.

Timeline
Launch planning callZoom transcript, 10:02
#launch-planSlack on screen, 11:06
Guest listSpreadsheet on screen, 11:41

Attribute: to the right engagement

Calls, documents, and screen work land on the engagement they belong to. Calendar series, repository and ticket links, and app rules do the placing; anything uncertain waits in an unclassified inbox for the consultant. Nothing is guessed into a client record.

Today, attributed
Weekly delivery call, 14:31
Northwind platform review, from its calendar series.
Pull request review, 15:48
Northwind platform review, from its repository rule.
Pricing spreadsheet, 11:41
Unclassified, waiting for the consultant.

Draft: at the end of each day

Overshow drafts the day's record on the consultant's Mac: completed work, commitments, decisions, risks, scope changes, and next actions, each with its date, time, and source excerpt.

Day record, Thu 9 Apr
Scope change
Client asked for the Germany rollout.
Completed work
Finished the data model review.
Sources: call 14:31 and message 15:02.

Approve: ready to share

The consultant corrects, excludes, or deletes items, then approves the record. Approval freezes the record; publication is a separate action. When it is published, the consultancy receives only the approved record. Drafts never leave the Mac.

Day record, review
Reviewed by the consultant
Encrypted on this Mac
Ready to share
Draft items sharedNever

No capture integrations to set up

Overshow works locally with the native apps you choose to include. Nothing to connect, nothing to configure

What Overshow does

Overshow drafts the record on the consultant's computer at the end of each day. The consultant reviews each item, and can correct it, exclude it from the record, or delete it. The record can include:

  • completed work
  • commitments and their dates
  • decisions and their recorded reasons
  • risks and blockers
  • scope changes
  • next actions
Book a 30-minute walkthrough

When it is published, the consultancy receives only the approved record. Each approved item includes its date, time and source excerpt.

You were there for all of it. Now it's findable.

Get back to what you were working on

Half your context is never written down. It just crosses your screen. Overshow reads the useful parts of your working window as text, so the spreadsheet figure, the vendor clause, and the message thread are one search away. Nothing visual is kept.

The Overshow Ask view answering “What did we agree for the launch?” with a grounded answer and four cited sources, each quoted from the meeting it came from.

Every answer links back to the moment it came from.

The context your AI keeps asking for

Every AI session starts blank: your architecture, your decisions, your customers, retyped again. Connect approved clients to Overshow and they can search your work memory: read-only, scoped to what you allow, with every connection listed and revocable. Works with Claude Desktop, Claude Code, Cursor, and local models such as LM Studio.

Private memory

Read-only, scoped to what you allow, and revocable.

Private by design, in ways you can check

A memory of your work is sensitive by definition. So the protection is architecture, not promises:

Encrypted on your Mac

One local database, encrypted with keys held in your Mac's keychain. It is not automatically replicated; only an approved record and source excerpts you choose to publish enter the organisation repository.

Text, not tape

Your working window is read as text; a screenshot is used only when text cannot be read directly, then discarded. Meetings are kept as transcripts, not audio archives.

AI that stays home

Transcription, search, and answers run on Apple silicon. Your work never reaches a cloud model unless you connect one yourself.

Scoped by you

You choose which apps are captured. Password managers, private browsing, and remote desktops are always off the record.

Consent you can see

Capture status is always visible, pause controls stay in the app and menu bar, and every AI client you approve is listed with its scope and an audit trail.

Yours to keep or delete

Inspect everything the app holds, export meetings as markdown, delete anything, or everything. Your memory lives on your Mac, so it outlives any subscription.

Private by architecture, in numbers

100%

of capture and transcription runs on your Mac

256-bit

AES encryption around your local database

0

screen images kept once the text is extracted

1 active Mac

per user under the current licence

An approved record for every engagement

You can bill for scope changes

Overshow marks a client request as a scope change. The day's record lists the changes, each one with its date, time and source excerpt.

A new consultant can read the engagement history

The record belongs to the engagement, not to the consultant. The approved records are held in date order, from the first day of the engagement.

You can check a decision against its source

A decision in the record carries the reason recorded with it. The source excerpt stays with the item after the source data is deleted.

Your company keeps the work

The approved records accumulate for each engagement. The consultancy holds a dated account of the delivered work, separate from what was invoiced.

The approved record is the hand-off.

Management does not receive a live feed of the consultant's day. It receives only the daily record the consultant has reviewed and chosen to publish.

See what the approved record feeds
  • Protect scope and margin
  • See delivery risk earlier
  • Make handovers less dependent on memory
  • Build reporting around delivered work

Try it on one engagement

Run it for 30 days, then look at: captured scope changes, reporting time, and handover readiness.

The questions everyone asks first

Is it recording everything I do?

No. Meeting audio is recorded only while a meeting is on. The window you are working in is read as text at natural moments (a window change, a click, a typing pause); most reads take no picture at all, and when one is needed it is discarded straight after. You choose which apps are included, and can pause all capture from the app or menu-bar controls.

Does anything join or appear in my calls?

No. There is no bot and nothing visible to anyone else. Overshow listens locally on your Mac. Consent stays in your hands: no audio is recorded outside meetings, and nothing is shared unless you share it.

Where does my data live?

Your durable searchable memory lives in one encrypted database on your Mac. During a meeting or interrupted recovery, bounded encrypted audio-recovery files can also exist outside it until terminal processing or replay. Transcription, search, and answers run on-device. Sign-in, billing, and updates use our servers; captured content stays on your Mac by default. Content leaves only when you export or mirror files to a folder you choose (which may be cloud-synced), attach diagnostics to feedback, enable URL enrichment for an allowed site, or approve a cloud client that sends queries and returned snippets to its provider. A separate Publish action sends only the approved record and its approved source excerpts to the organisation repository; it does not copy the local capture index.

What does a connected AI client actually get?

Read-only search over your memory, through three narrow tools, only for clients you have approved. You can see, scope, and revoke every connection.

What happens if Overshow disappears?

Your memory and the app stay on your Mac. Everything you captured is kept, not deleted. For existing Free entitlements, the historical recall window limits how far back you can search; it never removes anything. Capture, transcription, search, and Ask all run on-device, so the app on your machine does not stop working when a server does.

What does it need?

macOS 26 (Tahoe) or later on Apple silicon. One active device per account.

Request a chat or demonstration

A 30-minute walkthrough of an engagement record, or a pilot with one engagement.

Straight to the team, answered in business hours, UK time.