→ The doctrine

How we build operator cockpits.

Most software shops sell process. We sell shape. The shape of how a real operator actually runs their day — captured in code, fast enough to use tomorrow.

Operators do not need another generic SaaS bent into their workflow at signup. They need a single screen built around their actual workflow — the accounts they actually have, the data they actually move, the decisions they actually make in the next ten minutes. The methodology below is what makes that economically viable for one independent operator running a single-vertical business, not a $10M-ARR enterprise.

The four laws.

→ Law 01

One operator at a time.

Every cockpit gets designed with someone who lives in that workflow daily — never a product manager guessing at requirements, never a steering committee, never a focus group. We sit with the operator (usually their kitchen table or their truck) and watch them run an actual day. The cockpit gets built around what we see, not what they describe — because what hurts most in a workflow is rarely what an operator names when asked. The behavior is the signal.

→ Law 02

Real workflow shape, not generic data model.

The first cockpit version ships with the operator's real account names, their real client list, their real product catalog. Not Lorem Ipsum, not stock photos, not "John Smith." When an HVAC tech opens the cockpit on day one, the screen shows the trucks he drives every day and the customers he visits every week. The accounts are familiar before any feature is. That makes the cockpit recognizable, and recognizable software gets used.

→ Law 03

7-10 day first version. Real software, in your hands.

The first deliverable is a real working cockpit running against your real data on your real device. Not a Figma. Not a wireframe. Not a click-through prototype. The cockpit boots, your accounts load, your workflow runs. Then we sit with you for an hour and watch you use it for the first time. The friction operators actually hit is never where we predicted — so we fix what we see, not what we guessed, and iterate weekly until the cockpit replaces what came before.

Why this works: shipping fast doesn't mean shipping sloppy. It means putting the cockpit in front of the only reviewer who matters — you, using it — while you're still energized about the project. The longer software stays a slide deck, the further it drifts from how you actually work.
→ Law 04

The cockpits are different. The engine underneath is one.

The vertical-by-vertical fragmentation is real on the surface — a salon cockpit doesn't look like an HVAC cockpit. But underneath, the engine is shared: scheduling, dispatch, routing, billing, compliance tracking, customer communication, payments, document storage, AI surfacing. When we improve the route optimizer for home health, plumbing and pool service get the improvement next week. Each vertical adds its own surface area. The engine is what makes the catalog economically possible.

The shared engine, specifically.

What "shared engine" means in practice — the building blocks that show up across most cockpits, even when the surface vocabulary is wildly different:

Identity + multi-tenant
Supabase Auth + Postgres row-level security. Operators own their data. Roles per cockpit (owner / admin / tech / customer).
Scheduling + dispatch
Drag-drop calendar engine with constraint matching (certification, language, location, time window). Powers home health caregiver dispatch, HVAC service routing, pool tech assignment, salon stylist matching, photographer shoot booking.
Route optimization
Constraint-aware multi-stop routing. Drive time, time windows, hours-of-service caps, skill match. Powers HVAC, plumbing, pool, vending, landscape, pet services, real estate showings.
Proof-of-work / verification
GPS-locked + biometric + task-completion proof. Started as federal EVV (home health Medicaid requirement) — same engine powers HVAC billable-hour verification, plumbing punch-list sign-off, pool chemical-test logs.
Compliance + license tracker
Per-person credential expiry tracking with auto-block. HHA training, CPR, TB, background. Same engine: HVAC EPA 608, plumbing master license, auto ASE, dental hygienist, salon, tattoo BBP.
Billing + payment pipeline
Verified-work → invoice / claim / payment. Per-vertical claim formats (CMS-1500 for Medicare home health, state EVV aggregator for Medicaid, Stripe for cards, ACH for B2B). The pipeline shape is the same.
Customer / family comms
HIPAA-grade secure thread (when needed) or normal SMS/email otherwise. Sanitized post-event summaries. Powers home health family updates, pet-services walk reports, contractor daily homeowner updates, dental recall, salon rebook reminders.
Recurring task / care plan
Cadence-driven task generator. Powers pool chemical schedule, HVAC PM, lawn weekly service, pet recurring walks, med-spa treatment series, dental recall, home health patient care plans.
AI surfacing
Anthropic + OpenAI APIs for classification (which email needs reply), summarization (this week's exceptions), drafting (reply to this guest). Always human-in-the-loop on customer-facing output. Deterministic glue stays deterministic; AI does the human-shaped work.
Offline + PWA shell
Service worker + IndexedDB local cache. Cockpit keeps working when the truck loses signal, when the patient's house has no wifi, when the vending warehouse is a Faraday cage.

The commercial doctrine.

Flat fee, no SOW.

Most operators have been quoted custom software at $40k - $250k by agencies. They've learned to flinch. We size the first cockpit at the kickoff call after the discovery — typically between $3,500 and $8,500, one-time payment — and the number is the number. No scope-creep invoices. No change orders. No "professional services" line items. Hosting passes through at the actual cloud cost (usually $30-60/month). After version one ships, the operator decides whether to keep iterating, at what cadence, or just to take the cockpit and run.

No monthly retainer.

Operators run on cash flow. A $400/month retainer for "ongoing maintenance" gets cut the first time a slow month hits. We price to respect that. The cockpit is yours, on a flat fee, like any other piece of equipment your business buys.

You own your data, your domain, your codebase.

Cockpit code lives in your own Git account. Database lives in infrastructure we operate on your behalf but that you can take elsewhere whenever you want. Domain is your domain. Branding is your branding. We don't trap operators in proprietary platforms because operators don't trust software shops that do — for excellent reasons.

Operator? Let's talk shape.

A 30-minute discovery call. We listen. You show us how you actually run the day. We figure out together whether your business is the right fit for the next cockpit, no pitch theater.

Start a project → See production case studies