One operator. Six businesses. One operating system.

The story

Too many fronts for one head.

Sergio Baños directs development at Reserva Catorce, a 213-hectare, 1,598-lot master development with three hard milestones between October and December 2026. That alone is a full job. He is also the change agent for a 20-room boutique hotel in operational crisis, the person a modular housing manufacturer depends on right after replacing its leadership, the sponsor of a golf club remodel, the owner of Momentum, his property management firm in Los Cabos, and the likely director of an expansion into a new market.

His information lived everywhere except one place: WhatsApp threads, voice notes, an assistant's memory, a Trello board he could not see, and physical plans in a workshop in Hermosillo. His own rule was clear, what is not in OneDrive is not official, but nothing enforced it. He had been waiting a month for six basic deliverables from one company, with no formal deadline, and that silence was quietly blocking two other ventures.

He did not ask for a CRM. He asked, in his words, for commercial and operational intelligent memory. Something built around how he works, not around any one of his companies.

What we built

The architecture we run our own company on.

Search Visionary Tech runs on a lane system inside Claude Code: a constitution file every session rereads, one lane per area of work, a governed database as the only source of truth, and a master developer lane that changes the system without operating it. We gave Sergio the same thing, sized for one person.

• A constitution. One file, short enough to reread every session. Who he is, what each front is for, six hard lines that never move, and a voice rule: answer first, then what it means, then stop.
• Seven fronts. Reserva Catorce, the golf club, the hotel and restaurant group, the housing manufacturer, Momentum, the new-market expansion, and an admin desk that sees all six at once. Each is a session with its own standing context and its own first-session script.
• A database that refuses things. 19 tables in his own Supabase organization, deny-by-default. Documents are stored as pointers to OneDrive, never as content. Categories he marks as restricted are rejected at intake, not stored and hidden.
• Zero shared credentials. The repository is his. The database organization is his. Microsoft 365 and Google are authorized from his own screen. We maintain the system by committing to his repo; his Claude Code environment picks it up. Nothing secret ever crosses.
• A voice that holds. A hook restates the register before every single turn, because a rule that loads once at boot is forgotten by the second hour.

The whole thing was built in Claude Code sessions on our side, applied through his repository, and handed over as seven pre-primed sessions. His first move was not configuration. It was answering questions.

Day one

The system told him what he already suspected, with dates.

Before Sergio typed anything, the base held six pillars, eighteen people with reporting lines, three dated milestones and thirty-six commitments, all parsed from three briefs he had written himself. Seven of those commitments were already overdue. All seven sat on one person. And for the first time the dependency chain was explicit: those seven items were what stood between him and the bungalows, the lakeside villas and the entire expansion.

Within 24 hours of going live, the branding board he had been asking a third party to compile for him had a direct read agreed by email. Six deliverables that had been verbal and 33 days old became rows with an owner, a gate and a date.

The numbers he cares about are his, not ours, and they get measured at 30 and 90 days: 80 percent less time compiling context before a decision, the hotel's daily close arriving automatically before 7am, and a quotation turnaround at the housing manufacturer going from a week to a day.

The lesson

Build the OS for the person, connect it to the business.

Every earlier system we built was for a company: a yacht charter portal, a coffee shop's WhatsApp order desk, a dealership's back office. Sergio's is the first one built for an operator, and it is connected to his companies rather than owned by any of them. When he moves between fronts, the system moves with him. When a venture ends, its lane closes and the rest stays.

The second lesson is smaller and more useful: the repository is the interface. We never needed his passwords, his laptop or a shared screen to build, load and maintain his system. We needed write access to a private repo. That is the whole integration surface, and it is why the build took a week instead of a quarter.

Sergio has been a partner of ours since early 2026, first as our commercial ally in Mexico, then as the person who put us on stage at ExpoRV Los Cabos in July. This is the first product he bought for himself.