Context
Aircon King was doing roughly ₱30M (≈$535K USD) a month in revenue with almost no digital infrastructure behind it.
- Email was personal Gmail, not Google Workspace.
- There was no shared company environment — process knowledge lived in individual people's heads, not in systems anyone could hand over.
- The team's AI exposure was near zero.
They weren't broken — they had clear demand and a proven service. But they wanted to lock in ₱100M (≈$1.8M USD) per quarter as a sustainable floor, not a spike. That's a system problem, not a marketing problem. The demand was already there; the infrastructure underneath it wasn't.
The Challenge
₱30M/month on personal Gmail is a person heroically holding everything together — not a system. Two structural ceilings sat between them and their goal:
- No shared operating environment. Personal Gmail means no company identity, no role-based access, no shared drive, no way to onboard someone into a process that only exists verbally. Every workflow depended on the specific person who happened to run it.
- A capability gap. Any system dropped into that environment would rot the moment the builder left, because nobody on the team could operate it, extend it, or build the next one.
We agreed on the diagnosis: to hit ₱100M/quarter reliably, the operation needed a company environment the whole team actually works inside, and a team upskilled enough to keep building after the engagement ended.
Approach
The engagement ran April–May 2026 as one build with two connected pieces — build the environment, train the team — so that what shipped would survive the handoff. It started on-site at their company: the environment was stood up in the room with the team that would live in it, not delivered from a distance.
- 1. Google Workspace from scratch — their company cloud, stood up on-site. Provisioned the environment and migrated the team off personal Gmail: member accounts created one by one, company email set up and organized, groups and role-based access, and a shared Drive architected around how they actually file and share day to day. Then wired it into the way the business already runs — the calendars, the finance flow, the documents every team touches — so Workspace became the company environment itself, not a tool on the side. This is the foundation piece: every process the team runs now has a shared, owned place to live.
- 2. AI training — beginners to builders. Live sessions run with the company: took the core team from introductions to ChatGPT, Gemini, and Claude through to hands-on builds of real systems, websites, and dashboards with AI. The goal wasn't AI literacy — it was a team that ships its own tools.
The unlock is the pairing: the environment shipped together with the training to run it and build on it. That's what makes a handoff real instead of a dependency in disguise.
What Shipped
- Google Workspace live. Domain, member accounts, company email, groups, and the shared Drive the whole team files and shares in — stood up from scratch, on-site, and stable.
- A team that builds. Core staff went from AI beginners to producing their own systems and dashboards with AI.
Timeline
- April – May 2026. Core build: Workspace provisioning and migration, plus the AI training program.
- End of May 2026. Systems handed off running.
- Ongoing. Weekly advisory — reviewing what the team builds and advising against the ₱100M/quarter target.
Reflection
When a business is already at ₱30M/month with manual ops, the growth bottleneck isn't demand — it's the system's ability to run without any single person heroically holding it together. Digital infrastructure doesn't create sales; it stops a winning business from leaking time, data, and decisions.
A system isn't done when it works. It's done when it works without you. The Workspace matters, but the AI training is what made it safe to hand over — the client kept me on weekly advisory because they wanted a thinking partner, not because anything breaks when I'm not there.
What I'd repeat
Pairing the environment with the training. Most digital-transformation engagements fail at handoff: the vendor builds something clever, leaves, and six months later the business has reverted because nobody inside could operate it. The sequence we ran on Aircon King — stand up the environment, then train the team until they can build their own — is the order I'd propose again for any operation still running on manual-era ops.