Skip to content
Matt Zimak Book an intro call (opens in a new tab)

Matt Zimak Case studies A CEO's terminal

One question, answers with sources.

The CEO of a family business group asks a question in Czech and gets the answer from the whole group's email, Slack, Notion, meeting transcripts and payment list, with every claim linked to where it came from. Live since September 2026, for one person.

Built for

Built with

Book an intro call (opens in a new tab)

What travels where.

EmailSlackNotionMeetingsPaymentsOne indexSynced every minuteOpenAI GPTReads, then answersThe terminalBuilt with Claude CodeMAILTHREADPAGEMEETINGPAYMENTQUESTIONSOURCESANSWEREvery minute, new mail, Slack threads,Notion pages, meetings and payments go intoone index.The CEO asks a question in the terminal, inplain Czech.GPT plans the searches and reads the bestmatching conversations, whole.The answer comes back with every claimlinked to its email, thread, page ormeeting.Nothing in the sources? The answer says soinstead of guessing.
  1. MAIL THREAD PAGE MEETING PAYMENT into one index, every minute
  2. QUESTION from the CEO, in Czech
  3. SOURCES the best matching conversations, read whole
  4. ANSWER with a source for every claim

Who is this for?

What problem does it solve?

The answer to a plain question ("what did we agree with this supplier?") is spread across an email thread, a Slack channel, a Notion page and a meeting. Each tool searches only itself, so the answer takes four searches, or a call to whoever might remember.

What it does.

Five sources
Seven mailboxes across the group's companies, the Slack channels the CEO is in, the whole Notion workspace, every recorded meeting and the payment list: about 60,000 emails since 2021 at the start.
One index
New mail, threads, pages, meetings and payments are searchable within minutes. Passwords and login details are stripped before anything is stored, and a deleted message drops out of search while older answers keep their citations.
The question
Asked in plain Czech. Switches under the question box narrow it to email, Slack, Notion, meetings or payments, and a deep mode reads more before it answers.
Payments as numbers
Totals come from the payment list, added up by the database, and the answer has to quote them. No account numbers are stored.
The answer
GPT plans the searches, reads the best matching conversations whole, and links every claim to its email, thread, page or meeting. Under each answer it lists what it searched.

How it was built.

  1. 21 September 2026

    Live on the group's mailboxes: about 60,000 emails and their PDF attachments, answers in Czech with sources.

  2. 22 to 24 September

    Slack, Notion and the meeting transcripts joined the same index. From the 24th, the whole Notion workspace.

  3. 28 September

    An audit against real questions. The payment list joined as a table of numbers, so totals are computed, never estimated.

  4. 29 September

    The sync split into three jobs that each run every minute, and the terminal shows when each source last synced.

What broke, and the fix.

An old meeting for the latest one
Asked about the last meeting, it answered from one in August while three newer ones were indexed. When a question asks for the latest state, newer sources now win.
Keywords outvoting the question
After 41 more Slack channels were added, a question about checking a payment in Slack lost the right announcement to a dozen payment threads, and the answer said the command did not exist. Results are now ranked against the question itself.
A total made of reminders
Asked for a total, the model added up old payment reminders. Totals now come from the payment list, computed by the database.
Passwords in old mail
Old sign-up emails carried passwords in plain text. Credentials are now removed from every source before anything is stored or searched.
Slow sources holding up mail
In one sync job, slow Slack and Notion reads held up the one-minute mail check for up to four minutes. Three separate jobs now run every minute.

What the CEO has now.

One box for any question
About customers, suppliers, people, projects or payments, across every company in the group.
Answers to check
Every claim with its source, one click from the original email, thread, page or meeting.
Fresh by default
Each source shows when it last synced, so an answer is never older than it looks.
Private by design
Access for the CEO alone. Named employee mailboxes stay out of the index, and every question and opened source is logged.

Built to run again.

Nothing in the engine is specific to this group. Companies, mailboxes and channels are rows in a table, so a second company gets its own index, its own sources and its own login. Two of the sources come from other systems on this site: the meeting transcripts arrive through the company brain's n8n pipeline, and the payment list is the one the invoice pipeline fills. More in the AI concierge for executives, founders and operators.

Start with a call.

Fifteen minutes, on me. Bring the question you ask most often and cannot answer with one search.