Aircon King — ₱30M/Month Operation Digitalizing Toward a ₱100M/Quarter Target

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 demand was already there; the infrastructure underneath it wasn't.

This is the engagement shape that most operators misdiagnose. Businesses in this category don't need more leads — they need the leads they already have to stop leaking out of cracks in the ops layer.

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, no way to know which channel is actually producing the revenue.
• 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, you can't close a month without heroics, and you can't make a confident decision about where to invest in growth because the data isn't legible.
• 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 — every SEO query, every Google Business listing, every schema-indexed service page that would have been compounding demand for free.

We agreed on the diagnosis: to hit ₱100M/quarter reliably, the infrastructure had to scale to match the demand that was already there. The work wasn't generating new customers. It was building the system that stops losing the ones already arriving.

Approach

Digital transformation isn't one project — it's a sequence. We mapped it in dependency order and started shipping, because starting anywhere else would have meant building on foundations that still had to move.

• 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 — finance automation needed structured email, the website needed the domain, the CRM would need group-level permissions. Getting this right first meant every downstream system inherited a clean foundation instead of inheriting the mess.
• 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 — the hours-per-week curve started bending down while the data-legibility curve started climbing.
• 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. The site won't need a retrofit; the organic-discovery layer compounds from launch day.
• 4. Next. Booking pipeline unification (one inbound flow, not three), CRM foundations, service-line analytics. Each phase's exit criteria is the next phase's entry criteria — we don't start on booking unification until finance is legible, and we don't start CRM until booking is unified.

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, no "the website dev said the CRM vendor needs to fix it" pattern. Integrated ownership is what lets the sequence actually run to completion.

What's Running 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. Mechanical work on event triggers; judgment work via Claude Code with human-in-the-loop for anything outside known patterns.
• Website + SEO foundation locked in before the first byte of UI copy. Schema, metadata, content architecture — all in place pre-launch, so launch day ships a site Google can read rather than a site Google has to learn.
• This case study will be updated on website launch with indexing velocity, first inquiry attribution, and quarterly revenue progress against the ₱100M target.

Timeline

Engagement began in 2026 and is ongoing. Phased as:

• Phase 1 — Identity. Google Workspace provisioning, account migrations, groups and permissions, shared drive architecture.
• Phase 2 — Finance automation. n8n workflows, Claude Code integration for judgment-heavy steps, recurring-work audit, hours-saved baseline.
• Phase 3 — Website + SEO (current). Greenfield build, schema architecture, content structure, pre-launch SEO posture.
• Phase 4 — Booking unification. One inbound flow replacing the three uncorrelated channels. CRM foundations. Service-line analytics wired.
• Ongoing. Quarterly review against the ₱100M target, system-level tuning, and expansion of the automation layer into areas the first three phases surfaced as bottlenecks.

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, and no amount of paid acquisition will close the gap if the ops layer underneath is still a person heroically holding the business together on a phone.

What I'd repeat

The sequence matters. Most "digital transformation" engagements fail because the vendor tries to sell the visible piece first — usually the website — while the invisible plumbing (identity, finance, pipeline legibility) stays broken. The visible piece then sits on top of a foundation that can't carry it, and six months in the engagement gets blamed on "the site." The sequence we ran on Aircon King — identity, then finance legibility, then web/SEO, then booking unification — is the order I'd propose again for any business above ₱10M/month that's still running on manual-era ops.