How do you do meeting prep for a client without five minutes of scrolling?
Meeting prep for a client meeting means scrolling through email and your package; your AI gets a short overview ready from the email and package data, with what Bombos remembers, which you review and add to.
Works with SharePoint, ANVA, CCS, Convect and your own file and client systems.
The one-pager is the first step; what is discussed and promised stays in one shared memory for every AI your office uses.
Together we map what your AI forgets. Free, and the plan is yours, with or without Bombos. Join the plugin waitlist →
This is how it goes now, and how it goes with Bombos.
The client is on the line in five minutes and you are still scrolling through email.
Today, just before the meeting, you gather what is happening yourself: the latest emails, the details in the package and last year's document. You know the client, but you still need to find what has happened since the previous conversation. In homeowners association management, documents, email and the work in Convect sit side by side. Anything only a colleague knows is missing from those systems.
One overview per meeting: what is going on and what is open, from email and package.
Your AI prepares a concise overview from the available email and package data, with the reason included. You read it before the client meeting and add what you know. An agreement that was never recorded is also missing from the overview. If your AI is unsure, it asks you instead of filling the gaps between messages with assumptions. You decide what to use in the conversation.
After three months, you never enter a client meeting without the overview already waiting, showing what is happening, what is open and what was promised. You lead the conversation instead of catching up. What was agreed today is in the shared memory for the next meeting, with the source beside it.
What's ready for you then
- The overview is ready for every scheduled meeting
- What is happening, open and promised
- You lead the conversation instead of catching up
- Today's agreements carry into the next meeting
Where do you see that?
The overview for your client meeting sits on the list of proposals. You see the reason attached and the status "ready for you" or "waiting on your input". You do not need the package open to read the overview. The list shows which preparation is ready and where your AI still needs something from you.
You review the overview before using it in the meeting. Information you got outside email or the package, you add to your preparation yourself. The overview is not a message that goes to the client and reading it changes nothing in the file. Every overview shows where it came from. A prepared overview is not work carried out.
How does it start?
In the first week we discuss together where you get the preparation for a client meeting from, during a setup conversation of about an hour. You go through the mailbox and package you want to prepare the client meeting from, with the rules that apply for you. You give access to the systems needed for the first task. Your existing records stay where they are. You do not need to move files, learn a new package or take a course. What a colleague once agreed with a client by word of mouth, we also bring up in that conversation.
After that, your AI starts on the first task. Every task starts with proposals: the overview sits ready for review. What is not right in the preparation, you send back as a correction. A correction to the overview becomes the rule for the next preparation; Bombos keeps your explanation; without it, the memory does not hold what you want to see differently. Adjusting is done with settings, without custom work. Once a task type has gone well for a while, you decide how much autonomy you give your AI, with Bombos as the memory underneath. With every proposal you see where it came from. Even if you do not work with computers much, you set it up together.
Preparing the client meeting is the first task, not the whole offer. We take you through the setup. After that, every correction becomes a rule Bombos keeps, so the next task starts from what you already agreed, and you do not need to come back to us. After three months, you never walk into a client meeting without the overview already there. If there is a client meeting on your calendar, the overview is already there the morning before, with the reason attached.
Better prepared, from one shared memory.
An overview for a meeting may seem like a small thing. But a team that enters every conversation prepared delivers higher-quality work, and that preparation needs to know what was agreed before.
Bombos is the memory layer under the AI your team already uses: Claude, Claude Code, ChatGPT, Copilot, Grok, Codex, Cursor or your own agents. One plugin gives them all one shared memory: your team's knowledge, the rules it learns from your corrections, and what is already in your email, documents and business software.
You see where every answer came from. Bombos runs in the cloud or standalone on your own server, and one person can try the plugin with their own agents first.
The pilot runs three months for €2,000 instead of €3,000, then €1,000 per month, excl. VAT. Book your half hour to talk through your situation.
What Bombos does, in three steps
It reads what comes in
An email, a message, a photo or a PDF: your AI reads it, finds the client and the details through Bombos in the systems you already have, and sees what is missing.
It drafts the work, you approve it
The proposal sits on one list with the reasoning next to it. You read it, adjust it and approve. Only then is anything sent, booked or filed.
It remembers what you decide
Every correction becomes the rule for next time. Once it has gone well for a while, you give your AI more autonomy step by step, with Bombos as the memory underneath.
What does Bombos not do here?
Bombos does not act here itself: it gives your AI the memory. Without a connection between your AI and your email and package, it stays a proposal.
An agreement your colleague made by word of mouth does not automatically appear in the overview. That is why your AI asks you once what was discussed with this client and which agreement you want to carry forward, and Bombos keeps the answer. You put that explanation next to the preparation from email and package. That way you have an overview for the meeting that you can check and add to with what your colleague knows. When in doubt, the question sits next to it; a proposed summary can be wrong.
You decide which points you discuss with the client and what you commit to. Reading the overview changes nothing in the client file. You approve before something is kept for good or a message goes to third parties, through any channel. You set that in the AI or agent itself. The overview gives you a starting point for the meeting, with room for what you still want to ask.
What does your AI forget?
- 01You tell us which AI you use and where it keeps starting over.
- 02We show what a shared memory changes there, on your own examples.
- 03You keep the plan, with or without Bombos.
