Tero Admin.
Designing and building a tailor-made property management system from the ground up — leveraging modular architecture, IoT, and AI to automate a vacation rental complex with four houses.
- 227 Commits
- 74 Active hours
- 12 Active days
- WIP Status
Modular architecture for the physical world.
The problem with most off-the-shelf Property Management Systems is bloatware. Paying for a generic SaaS often feels like renting a five-story office building for a three-person team — you pay a premium for features you will never use, yet the system remains completely rigid to your actual needs.
Instead of adapting my operations to third-party software, I built my own to run a vacation rental complex with four houses in La Barra, Uruguay. Tero Admin isn't a traditional "tailor-made" app; it is built on high-efficiency modular architecture. Operating under a "Pod-of-One" model, I leveraged AI, smart automations, and system design principles to execute at the speed of a full team, building only the exact modules needed to eliminate daily friction.
Here are the three core modules running the system:
Automated Hospitality.
- The challenge
- A guest's check-in experience doesn't begin when they get the keys; it starts with the thermal comfort of the house when they walk in.
- The module
- An integrated temperature and humidity control system.
- The philosophy
- Sometimes the best User Interface isn't a glowing screen on a smartphone — it's the perfect physical climate the moment someone crosses the door.
Invisible Operations.
- The challenge
- Manually tracking energy costs and matching them against actual occupancy is a major administrative time-sink.
- The module
- An automated backend flow that intercepts email-forwarded utility bills, extracts the data, and automatically matches it against the complex's real energy usage.
- The philosophy
- Heavy bureaucratic tasks should be resolved by the backend. Fewer manual interfaces, more invisible integrations that protect margins.
Zero-Friction Team UI.
- The challenge
- Forcing maintenance and cleaning staff to download a new app, remember passwords, and learn a foreign system creates unnecessary resistance and errors.
- The module
- Issue report, task assignment, status tracking, and notifications operated entirely through WhatsApp.
- The philosophy
- The best interface is the one the user already knows. Instead of forcing people into a new system, I brought the system to them.
Tero Bot is built on Kapso — a WhatsApp orchestration layer that lets the team distribute tasks, file issues, and log supply intakes without leaving the chat.
Idea → ship in one loop.
The whole product runs on a tight three-step pipeline:
- Linear
- →
- Claude Code
- →
- Vercel
- →
- 🚀 Boom
Linear holds the backlog. Every request, bug, or idea opens an issue. Claude Code reads the issue, writes the patch, opens a commit referencing the issue, and pushes. Vercel deploys every push in under a minute — and auto-closes the Linear issue via the commit link.
What used to be a multi-person handoff — backlog grooming, dev work, code review, QA, deploy ticket — collapses into a single conversation. The cost per shipped change drops far enough that micro-iterations become the default, not the exception.
Learning in public.
I deeply believe in context engineering and the value of learning in public. Tero Admin is the operational engine of my properties, but I am opening the logic and the system because transparency accelerates collective judgment. Code has become a commodity; how we orchestrate the pieces is what truly scales.
View the repository