bcdianco / operator
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.
- No website.
- Every booking came through Facebook messages, SMS, or phone calls.
- Finance ran on manual ledgers and spreadsheets.
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 Challenge
₱30M/month on Gmail and Facebook is a person heroically holding everything together — not a system. Three structural ceilings sat between them and their goal:
- Revenue leakage at booking. With three uncorrelated channels (FB inbox, text, calls), inquiries fall through the cracks the moment one person is busy. No pipeline, no receipts, no way to measure conversion.
- Finance invisibility. At ₱30M/month scale, manual accounting on Gmail is a liability. You can't see margin by service line in time to act on it.
- Zero digital discovery. No website means the only way to find them is if someone tells you. Every growth lever that depends on inbound search was locked off.
We agreed on the diagnosis: to hit ₱100M/quarter reliably, the infrastructure had to scale to match the demand that was already there.
Approach
Digital transformation isn't one project — it's a sequence. We mapped it in dependency order and started shipping.
- 1. Identity (Google Workspace). Nothing else works without it. Provisioned the domain, migrated team accounts off personal Gmail, configured groups, shared drive, role-based access, and ongoing admin. This unblocked every subsequent piece.
- 2. Finance operations automation. Rebuilt the recurring financial work on n8n + Claude Code. Mechanical steps run on event triggers; Claude Code handles the judgement-heavy steps (categorization, anomaly detection, flagging). Manual finance ops began coming off the plate.
- 3. Website + SEO. Greenfield site currently in build. Pre-launch at time of writing. SEO isn't a post-launch phase — it's baked in from day one: schema.org markup, per-page metadata, image optimization, clean URL structure, Search Console submission scheduled for launch, Google Business Profile and local SEO signals configured alongside so the business is findable the moment the domain goes live.
- 4. Next. Booking pipeline unification (one inbound flow, not three), CRM foundations, service-line analytics.
The unlock isn't any single piece — it's one operator across the stack. When the website needs a contact form that writes into a finance workflow, one person already owns both sides. No three-vendor coordination tax.
Results (so far)
- Google Workspace live. Domain, accounts, groups, email routing, shared drive, MDM posture — all stood up and stable.
- Finance automations running. n8n + Claude Code handle recurring work that used to eat hours weekly.
- Website + SEO foundation locked in before the first byte of UI copy. Schema, metadata, content architecture — all in place pre-launch.
- This case study will be updated on website launch with indexing velocity, first inquiry attribution, and quarterly revenue progress against the ₱100M 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 capture demand without dropping anything. Digital infrastructure doesn't create sales; it stops revenue from leaking out of a business that's already winning.
The gap between ₱30M/month and ₱100M/quarter isn't a marketing problem. It's an infrastructure problem. You can't text-message your way into that scale.