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

Matt Zimak Automations A CEO's AI assistant

A CEO's AI assistant: one question, answers with sources.

EMAILSLACKNOTIONMEETINGPAYMENTQUESTIONSOURCESANSWEREmailSlackNotionMeetingsPaymentsOne indexSynced every minuteOpenAI APIGPT reads, then answersThe terminalBuilt with Claude Code

The CEO of a family business group asks a question in Czech, and the terminal answers 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.

The problem.

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.

How it works.

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.
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, over OpenAI's API, 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.

What you need.

The mailboxes
Admin access to the mailboxes that should be searchable: Google Workspace delegation for most, IMAP for the rest.
Slack and Notion
A Slack app in the channels the CEO is in, and a Notion integration for the workspace.
Meeting transcripts
Fireflies, or any recorder that writes a transcript. Here they arrive through the meeting pipeline that also feeds the company brain.
The payment list
Optional: the Google Sheet the invoice automation fills, so totals are numbers, not guesses.
One person
The CEO, or whoever gets the login. Access is per person, and every question is logged.

What it takes.

  • Days per source, not months.

    Here the mail was live on 21 September 2026; Slack, Notion and meetings joined the next day, payments a week later.

  • The CEO's first questions.

    The CEO chooses what the assistant may read, then asks it real questions; the answers are tuned on those.

  • Priced after the sources are known.

    The sources and the index size set the work. You hear the numbers on the intro call, before anything starts.

Running today.

  • 60,000 emails, 68 Slack channels, 4,646 Notion pages, 298 meetings.

    Indexed for one family business group, searchable within minutes of arriving.

  • Every claim with its source.

    One click from the answer to the email, thread, page or meeting it came from, and a list of what was searched under every answer.

  • One login, every question logged.

    Access for the CEO alone; named employee mailboxes stay out of the index.

Nothing in the engine is specific to this group. The meeting transcripts arrive through the company brain's pipeline, and the payment list is the one the invoice automation fills. More in the AI concierge for executives, founders and operators.

Questions executives ask.

Does it make things up?

It answers only from what it finds, and says so when it finds nothing. Every claim carries a source, and totals come from the payment list, computed by the database, never added up by the model.

What about passwords and private mail?

Credentials are stripped from every source before anything is stored or searched. Named employee mailboxes are not indexed, a deleted message drops out of search, and every question and opened source is logged.

How fresh is it?

New mail, threads, pages, meetings and payments are searchable within minutes, and each source shows when it last synced, so an answer is never older than it looks.

Can it run on our tools?

The sources are rows in a table: mailboxes, channels, Notion roots, a transcript folder, a sheet. A second company gets its own index, its own sources and its own login.

Start with a call.

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

Book an intro call (opens in a new tab)All three ways to work with me