Multi-tenant architecture
One platform, many buildings, full isolation between them.
Each bot below is live, used by real users, and would be missed if it stopped working. They’re shaped completely differently — and together they show what’s possible when an agent is built to ship, not to demo.
The WhatsApp bot for residential building committees / HOAs — by Menti Technologies.
The problem
Every building has the same chaos. A WhatsApp group with 40 neighbors. The committee chair fielding the same questions for the hundredth time — when does the cleaner come, who do we call about the boiler, how much do I owe this month. Tasks that fall through the cracks. Payment reminders nobody wants to send manually.
What Barty does
Lives inside WhatsApp — where the building already talks. Answers questions about the building 24/7. Tracks open issue tickets. Sends building-dues reminders automatically. Each building has its own private context — its own rules, contacts, and history.
Under the hood
One platform, many buildings, full isolation between them.
Production messaging infrastructure, not a chat widget.
Understands how real people actually write WhatsApp messages, typos and all.
Answers when asked, reaches out when something needs attention.
Where this pattern fits
Anywhere a small group of people repeats the same questions, chases the same tasks, and already lives inside a messaging app:
If your users already live in a group chat, that group chat can become a product.
Mazker (Hebrew for “reminder”) — your personal assistant. By Menti Technologies.
The problem
Reminder apps are dumb storage. You pick the date, you pick the time, you type the text — and they parrot it back. That’s not an assistant; it’s a sticky note with a clock. Real life is messier: “remind me to call my dad the day before his flight,” or “every workday at 9, but not when I’m in a meeting.”
What it does
You write to it the way you’d ask a person:
It figures out the schedule, picks sensible times (not 2am, not while you’re in a meeting), and lets you reply “done,” “snooze 1hr,” or “reschedule to tomorrow” in plain language. No forms. No date pickers. No app to install — it lives where you already type.
Who uses it
Right now, me and the people closest to me — family and friends. It’s been quietly running in real lives every day, which is the strictest QA there is. The bugs you find when your mother uses your bot are the bugs that matter.
Under the hood
For fuzzy time expressions like “day before” or “every workday.”
Knows not to interrupt at the wrong moment.
Replies are commands, not just acknowledgments.
Recurring patterns survive between messages.
Where this pattern fits
Any product that today asks users to fill in a form when it could ask them a question:
From “the user does the work” to “the bot does the work, and only asks when it needs to.”
Both ship to the channel where users already are. Both treat memory as a first-class feature, not a bonus. Both do work, not just talk. Both have been running long enough that breaking them is no longer a hypothetical.
If your product has forms, dashboards, or repetitive support questions, there’s a bot pattern hiding inside it. The interesting question isn’t can we build it? — it’s what should the bot do, and what should still stay a button?
Roy personally reads every message. Tell him about your challenge and he'll suggest the best path forward — no commitment required.