Tools · The operating stack

A stack chosen on purpose.

Tools don't fix operations, systems do. But the right stack makes a system cheap to run and hard to break. Every tool below earns its place by solving one business problem well, and I work hands-on in all of them. We start where you already are: no rip-and-replace unless it genuinely helps.

By category

Seven layers of the operating system.

01

CRM & revenue systems

The single source of truth for every lead, deal and client. If the CRM can't be trusted, every downstream decision is a guess. I rebuild data integrity first, then automate the pipeline.

HubSpotGoHighLevelZohoSalesforceActiveCampaign

Solves: leads dying in inboxes, pipeline reviews run on vibes, follow-up that depends on memory.

02

Project management

Where work becomes visible. Owners, deadlines and stage gates live here, so nothing depends on someone remembering. The tool matters less than the discipline, but these are the ones I run.

ClickUpNotionTrelloAsana

Solves: slipping deadlines, invisible workloads, founders as the only source of project status.

03

Communication

Structured channels with clear norms: what belongs in chat, what belongs in the system of record, and what deserves a meeting. Async-first, because I run teams across US, AU and PH time zones.

SlackLoomGoogle WorkspaceMicrosoft 365

Solves: decisions lost in DMs, meeting overload, time zones stalling progress.

04

Documentation

SOPs, playbooks and process maps your team will actually follow: short, owned and versioned. Documentation is how execution survives growth, turnover and vacations.

NotionGoogle WorkspaceLoom

Solves: process living in heads, months-long onboarding, quality that depends on who did the work.

05

Automation

The connective tissue. Handoffs, reminders, intake and data entry move between tools without a human pushing them. Every automation is documented so it never becomes mystery infrastructure.

ZapierGoHighLevelActiveCampaignCalendly

Solves: manual busywork, dropped handoffs, follow-up that only happens when someone has time.

06

Reporting

Leadership should see the whole business on one screen. I build scorecards and dashboards that surface signal weekly, so decisions happen on schedule instead of in panic.

Excel & BI ToolsQuickBooksCRM dashboards

Solves: reporting that takes a day to assemble, decisions made on gut feel, KPIs nobody owns.

07

AI tools

Deployed where they pay, not where they impress. AI receptionists answering real phone lines, AI-assisted reporting and drafting, and automation that thinks. This layer is where AeroReception lives.

AeroReceptionClaudeChatGPTGemini

Solves: missed calls, slow first response, repeatable judgment work eating skilled hours.

Where it all fits

The stack is one system: leads land in the CRM, work flows through project management, process lives in documentation, automation moves things between layers, reporting watches everything, and AI answers the phone. One operating layer, seven tools deep, documented end to end.

The rule: if a tool doesn't remove founder hours or protect revenue, it doesn't make the stack.

Your stack probably isn't the problem. How it's wired is.

Bring your current tools to a call. I'll tell you what to keep, what to connect and what to drop.

Book a Strategy Call → Get a Free Operations Audit