HeavisideOS
The software my agencies run on. One codebase under the websites, CRMs, dashboards, ad pipelines, content tools, and AI agents. Different brands on top.
Why HeavisideOS exists.
What HeavisideOS replaced, and what it does for me now. The internal dashboards stay private, so this is the public version of it.
Here's a summary of this page by my AI Avatar
How this system moves work.
One core, several tools on top
Shared facts, decisions, and evidence
Workflows, approvals, and deliverables
Agents, queues, and scheduled jobs
MarketingOS, PavingOS, GarageDoorOS
One reusable core now sits under the agencies, dashboards, content systems, ad-data workflows, and agent fleet.
The old version of the business depended on scattered SaaS tools, docs, manual reporting, and Monday memory.
What it actually is
Next.js, Postgres, Redis, BullMQ, and a fleet of agents running scheduled jobs. The agency websites are templates of the same codebase. The dashboards read from the same database. When a lead comes in at Paving Marketers, the code that routes it is the same code that routes one at Garage Door Marketers.
Why I run it this way
Every agency I know stitches together GoHighLevel, ClickFunnels, ChatGPT, a couple of Make.com flows, and three dashboards. It works until the volume changes. Then the seams show. One codebase means a fix in one place fixes it everywhere. Same for new features, same for switching an LLM.
- One codebase across the businesses instead of eight SaaS tools per brand
- Niche UIs (PavingOS, GarageDoorOS, MarketingOS) layer industry-specific workflows on top of the same core
- Internal first. The agencies use it before any of it becomes a public product
What I'm working on right now
Tightening the ad-data warehouse so HG PPC runs without manual joins. Moving project notes, decisions, and lessons out of Markdown into something the agents can query. Building the PavingOS and GarageDoorOS UIs on top of the same CRM.