capabilities
The systems behind the site.
Dashboards, analytics, and the technical program work that keeps it all shipping.
Most people come to me for a site that’s beautiful and gets found. Some of them need the layer underneath it too: the reporting they actually read, the integrations that hold, the operating cadence that ships the work. Fourteen years operating nearly every function of a business means I build the right thing, not just a working thing. Scoped on a call — there’s no package here, because no two of these are the same.
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.
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
Where to start.
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; anything deeper is scoped on its own once the map exists.
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
Full refund if you ask before the audit work begins; once it is underway, case-by-case (see Refunds).
Need the website itself? Sites, from $3,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.
- Discovery
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.
- Start
The Audit
The cleanest way to see the full system without a retainer. Anything deeper is scoped on its own, once the map exists.
- Operate
Working sessions + iteration
Weekly working sessions. Async between. Quarterly step-back to iterate the whole system. Sites handles the surface; this work handles the substrate.
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 do I actually get from the Audit?
A map — one engagement, written deliverable, you implement: current-state map, gap analysis, and a 90-day roadmap you can act on. Anything deeper is scoped on its own once the map exists.
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.
Start with the call.
Fifteen minutes. We look at where the operating system is leaking and whether the Audit is the right entry. If it is not a fit, you leave with a clearer brief.
Book intro call →