The Lab · System design

One operator, whole company.

I built my last venture as a deliberate experiment: how much of a real business can software and AI carry, so a single person’s time goes only where judgment lives? Two constellations made it work — a growth engine that turns creators into conversion, and an operating spine that runs the company. The part I care about most is the boundary: deciding what must stay human.

The growth engine — creators to conversion

Discovery to paid distribution: the influencer pipeline that filled the funnel, run on the same one-operator discipline.

Influencer discovery Modash Campaigns & seeding Shopify Collabs UGC production creators on brief Asset library OneDrive · SharePoint Paid distribution Meta · Google · TikTok shortlists briefs & product content in creative out traffic & retargeting — into the storefront below
The operating spine — and the human boundary
Runs itself Waits for judgment
The operator one person · judgment only product & inventory calls exceptions a customer would feel partnerships & relationships queued queued queued Storefront Shopify Lifecycle email Klaviyo Support Gorgias · AfterShip · AI drafts Pipeline HubSpot Executive reporting CAC · LTV · ROAS · MER · NPS order events signals & tickets leads everything reports down · Zapier · Asana · ChatGPT Enterprise

A normal day, as designed: the constellation trades events on its own — orders trigger flows, tickets arrive with context and AI-drafted replies, everything reports down into the dashboards. The operator’s queue holds only what deserves a human.

Architecture shown as designed; tools named, numbers and names left out on purpose.

Automate the repeatable

Every order event, support reply, email flow, and report has a system path. The test is simple: if it happens twice the same way, it gets a path and stops costing attention.

Reserve the human for judgment

The operator’s queue holds three things: exceptions a customer would feel, product and inventory calls, and relationships. Everything else is automation pretending to be work.

Let software absorb the fixed costs

Headcount-shaped problems become subscription-shaped. Capital flows into the product instead of the overhead — the principle the whole company was built around.

What this shows

I design the operating system, not just the process — including the hardest call: deciding what must stay human. The same discipline scales from one operator to a team.