capabilities
I build across the whole stack — and I've sat in nearly every seat to know why it matters.
You hire one builder — who ships it, and runs it.
Websites, web apps, data and reporting, and AI tools — designed and built by me (Astro, TypeScript, Cloudflare, Stripe). Fourteen years operating nearly every function of a business means I build the right thing, not just a thing. A vetted bench extends capacity when a build needs more hands — on call, not on payroll.
the operator
I build it myself — and I've run the business around it.
Most technical people work one layer. I build across all of them — front end, back end, reporting, and AI tools — and I've operated the business functions they serve, so I build the right thing, not just a working thing.
That's the edge: I build it and I understand where it fits, because I've sat in those seats myself — not just managed people who have.
the capability map
Every seat, with receipts.
Cyan — led or owned. Amber — hands-on inside a broader role. Purple — my bench brings it. Each tile names where I earned it.
the bench
More hands than mine — on call, not on payroll.
When scope outgrows one operator, I bring people I've worked with and trust — front-end and back-end engineers, data scientists, QA, a full camera crew and editors, and social media managers. You get senior specialists for exactly as long as you need them, coordinated by someone who's done their job too. No agency retainer, no bloat.
receipts
consulting
Two ways in.
I've built operating systems for myself and for founders, paid and unpaid. Now it's productized. Start with a one-time audit for the map, or take a seat if you want a builder in the room.
Founder Operating-System Audit
Productized entry · ~10 days.
Ten days. I audit your current systems and deliver a 10–20 page written playbook, closed with a 1-hour walkthrough. No retainer, no commitment beyond the engagement.
- Current-state map (stack, workflows, surfaces)
- Gap analysis (missing / redundant / broken)
- 90-day roadmap: 3 priorities, ordered, with implementation guidance
- Curated tool + template recommendations
- 1-hr walkthrough + 30-min follow-up Q&A
Not the right fit after the kickoff call? Full refund, no questions. And if you move to a Seat, the audit fee is credited toward your Operator Seat engagement.
Second-Brain Operator Seat
Project-based · 3 seats total.
One of three concurrent seats. Pricing flexes to the engagement — a fixed per-project scope, or an hourly retainer to hold your seat month to month, whichever fits the work. Roughly 8–10 hrs/month — weekly sessions, async between, quarterly system iteration. Application + intro call required before we start.
- Weekly working sessions (~60–90 min)
- Capture, decision velocity, ops baseline
- Financial visibility — cash flow, runway, sequencing
- AI integration as multiplier, not substitute
- Body baseline for founders running hot
- Slack/Notion async between sessions
- Quarterly system iteration
Need the website itself? Sites, from $2,000 →
- Indie SaaS and product builders — solo or two-person shops
- Solo consultants and fractional execs running their own book
- Creator-economy operators with revenue and operations to organize
- Newly-funded founders pre-first-hire who need the system before the team
- Builders working through volatility who want a builder who gets it, not a vendor
Not for large teams (they need a fractional COO or CMO, not a second-brain operator) or big companies (they need McKinsey or Bain). Pure artists who want a website + brand go to Sites.
Intro call
Fifteen minutes. We look at where the system is leaking and which engagement fits the moment. Not a fit? You leave with a clearer brief.
Audit, or graduate to Seat
Most founders start with the Audit — the cleanest way to see the full system without a retainer. If the work benefits from ongoing iteration, the Audit fee credits toward your Operator Seat engagement.
Working sessions + iteration
Weekly working sessions. Async between. Quarterly step-back to iterate the whole system. Sites handles the surface; the Seat handles the substrate.
Three concurrent seats. When they fill, the page swaps to a waitlist.
Current availability: 1 of 3 seats open · 3 of 6 Audit slots open.
Qualification. Solo or near-solo operator. Revenue or runway to invest in the system. You're the bottleneck — the work is the system around you. You'll actually use it, not just buy it. Application on the intro call.
What's the difference between an Audit and a Seat?
The Audit is a map — one engagement, written deliverable, you implement. The Seat is a builder in the room — ongoing weekly sessions, we build and iterate together. Most founders start with the Audit; some never need the Seat. If you do graduate, the Audit fee credits toward your Operator Seat engagement.
Is this coaching, consulting, or fractional work?
Fractional consulting with a builder bias. Not coaching — I'll tell you what to do, not ask you what you think. Not pure consulting either — I build alongside you, in your tools, with your data. Closest analogue: a fractional COO who specializes in the operating-system layer, not the people-management layer.
Why capped at 3 seats?
Because the work compounds only if I'm actually in your head — not skimming your Notion at the top of each session. Three is the honest number for that. When seats fill, the next opens by waitlist; the price goes up when demand says so.
How long does an Operator engagement run?
Each engagement is scoped to a project; most founders start another or graduate to a quarterly check-in once the system holds. No lock-in.
Start with the call.
Fifteen minutes. We look at where the operating system is leaking and whether the Audit or the Seat is the right entry. If neither fits, you leave with a clearer brief.
Book intro call →