Crafted software to dissolve complexity.
Every business signal — IoT, invisible integrations, a WhatsApp bot — collapsed into a single interface. Thin, replaceable layers that minimize the product surface and keep operational entropy under control.
The trap of packaged software.
Hiring a generic SaaS to manage your rentals is like renting a five-story building for a team of three. You pay through the nose for tools you don't need, while your day-to-day is still full of manual tasks.
That's why I built tero.bot. Instead of fighting rigid third-party systems, I built a modular architecture. It's a ‘Pod-of-One’ model: I operate solo but leveraged by AI and automations. Only the modules that solve real problems. No junk.
Three modules. One system.
Thin, composable, replaceable layers — each solves a real operational problem.
Automatic hospitality
- The problem
- The guest experience doesn't start with the keys — it starts with thermal comfort the moment they walk in.
- The module
- Integrated temperature and humidity control. Pre-conditioning 2 hours before check-in.
- The philosophy
- Most times, the best UX isn't on a screen — it's the perfect climate when someone walks in.
Invisible operations
- The problem
- Tracking energy costs by hand and matching them against real occupancy is an administrative time sink.
- The module
- A backend flow that intercepts utility bills via email, parses the data, and matches them automatically against real consumption.
- The philosophy
- The bureaucratic tasks are solved by the backend. Fewer manual interfaces, more invisible integrations.
Zero-friction UI
- The problem
- Forcing staff to download another app and learn a new system creates resistance and errors.
- The module
- Incident reports, task assignment, tracking, and notifications — all via WhatsApp.
- The philosophy
- The best tool is the one we all use. Instead of forcing people into a new system, I brought the system to them.
Code available.
I believe in context engineering and learning in public. tero.bot is the real operational engine of my complex — the code is open to share the system design and accelerate collective learning.
It is not a community-maintained open-source project. Feel free to explore the code, fork it, and use the concepts to build your own systems.