A custom assistant. A shared brain.
A WhatsApp assistant and a shared external brain for a small team that already lives in chat. It removes the mechanical bits — tracking, drafting, reminding, scheduling — so your specialists get their judgement back.
For teams of 5–25 in advisory, design, law, family office, indie funds, small studios. Self-hosted on a server you own.
Your team thinks. Kazimir handles the rest.
The bill of daily frictions
Each one is small. Each one drains ten minutes of a specialist's day. Multiply by five people and 220 working days. The bill is bigger than you think.
"Who replied to Ana?"
"Did we send the quote to Munich?"
"What did the client say on the call last Thursday?"
"Who's covering Laurent's clients next week?"
"Did anyone thank Maria for the intro?"
"When did we agree to that delivery?"
"What was the account number for the invoice?"
"Did we follow up on the Zurich opportunity?"
Every one of these drains ten minutes of a specialist's day.
Kazimir removes most of them.
A real feature, not a demo
Commit — for the meeting nobody can schedule.
You need a 90-minute slot across five collaborators in three time zones. Or three suppliers and a client. Or a quarterly review with your three partners.
Tell Kazimir who, when, and how long. It DMs each person privately — no group spam — and waits.
Some people are key — the meeting can't happen without them. Others are flexible. The brain weighs the votes, applies a quorum bonus, and proposes the time that maximises real attendance.
You confirm. The calendar invite goes out. Done.
Nothing without a human tap
Kazimir never posts to a group chat or sends an external email by itself. Approval is a small ritual — a single tap from any of the named approvers — and it can be rotated, paused, or escalated.
Any named approver can tap ok — rotatable, pausable, auditable.
An email arrives. A reminder fires. A client question comes in.
Kazimir writes a short reply privately to whichever approver is on duty.
Approver edits or accepts on their phone. Two seconds. Logged forever.
Reply goes out from the right inbox or chat. Audit log stamped.
The honest math
This isn't about catching one missed handoff. It's about removing forty-five minutes a day, per person, of mechanical work that any decent assistant should do.
Of specialist time, paid at specialist rates, spent on work any assistant could do. Kazimir for team costs less than half that — and the time goes back to your specialists, who use it on the things only they can do.
Where it lives
On a server in your name. Not ours. Not anyone's.
The assistant your team talks to in WhatsApp is called Kazimir. The same assistant in Telegram is called Stepan. Both run on the same reasoning brain — installed on your server — that remembers the team's life and connects the dots. We sell them as one product, install them as one product, and hand the whole stack over to the company on day one. None of it is hosted by us. None of it is licensed. It's yours.
Who builds this
I'm Roman Selivan. For about twenty years I built communications campaigns and the systems that ran them — for Mercedes-Benz, Prada, Coca-Cola, Cartier, Chanel, and a charity foundation that ended up raising close to a million dollars for autism research. I rebranded the bus network of an entire region. I opened bars and a clinic. I taught physics for a year at twenty-three.
Somewhere in the middle of all that I started writing the software myself, because the off-the-shelf tools never quite fit the people I worked with. I now run the technology side of Moscow Art Magazine from my flat in Barcelona, and I build Kazimir for one team at a time, by hand, on purpose.
For now, that means I install it personally — start to finish — for every team that buys it. That's a deliberate constraint. It also means there's a real human on the other end of WhatsApp when something needs to change.
Three ways in
Most teams start with a paid pilot — small money, small risk, refundable. The full install only happens after we've both decided it works. Bespoke is for teams that need integrations beyond the standard set.
Running care is €1,800/month after month three — half the cost of a single junior assistant, for the whole team. Pause or cancel anytime, you keep everything.
The procurement questions
Enterprise vendors (Sierra, Decagon, eragon.ai etc.) charge €50K–€200K+ a year, lock you into their cloud, and require months of integration work. Kazimir is roughly two orders of magnitude cheaper, installs in days, lives on a server you own, and ships you the source code on day one. Different product, different buyer, different math.
You choose the VPS provider and the region. Hetzner Helsinki, OVH Strasbourg, AWS Frankfurt — whatever your compliance team prefers. We never touch the box. Your data residency is whatever your VPS region is. We can sign a DPA if your client demands one, but legally we're not a processor — there's no processing on our side.
The brain knows about every team member. When someone leaves, you mark them as departed and Kazimir wipes their personal context within 24 hours, while keeping the team-wide knowledge that's still relevant. Their drafts, their threads, their reminders — gone. The team keeps working.
Yes — for teams up to about 25. The three-month care period is exactly so you don't need an admin: Roman is the admin while you learn the system. After that, the day-to-day is a few taps a day from your approvers, and the running care covers anything technical.
No. It removes the work nobody wanted to do anyway — the tracking, the chasing, the "did we send the quote", the calendar tetris. Specialists keep doing specialist work. Junior staff get to do harder, more interesting work because the mechanical layer is handled.
Because at this scale it's better. Each install is bespoke enough that handing it off to a junior would lose the point. The constraint is real — there are only so many teams I can install per quarter. When I hit the ceiling, I'll hire carefully. For now, you get me on WhatsApp, full stop.
You keep everything. The source code is in your possession from day one — not in escrow, in your hands. Your VPS is in your name. Your data is on your box. Your LLM keys are yours. The worst case is "we lose our outside maintainer" — which is the same risk as any small vendor, except here the lights stay on by default.
Four weeks. One workflow. €3,000 — with €2,000 refunded if you don't continue. The fastest way to find out whether this fits your team is to install it on a real box and try it on real work.
Talk about a pilot →