You don't need more content advice. You need the person who's built the system. Here's how to access me directly.
Every layer of access below is built around one idea: you get my thinking, my frameworks, and my architecture — at a level that fits where you are right now. No done-for-you. No hand-holding. Just systems access.
See the Access Tiers →Products give you the system. These give you me.
I don't do it for you.
I give you access to how I do it.
My job is to transfer the system, not to run it for you. Every engagement — from a one-off audit to an ongoing retainer — is designed to leave you more capable than when we started. That's what separates a systems architect from a service provider.
The result is that clients who work with me directly tend to move significantly faster than those who self-study alone — not because I'm doing the work, but because they're getting decisions validated, architectures pressure-tested, and blockers cleared in real time.
Five layers. One architect. Your pace.
Each tier gives you a different depth of access — from ongoing strategic thinking published in the open, to private 1:1 architecture work. Start where it makes sense for you.
My thinking, delivered monthly
A private publication where I share what I'm actively building, testing, and revising in my own content engine. Not a course. Not a newsletter. Raw, ongoing access to the decisions behind the system — including what's not working.
A focused session on your specific setup
60 minutes. I review your existing content architecture, identify the structural gaps, and give you a prioritised rebuild plan in writing. Not generic advice — a specific diagnosis of your system with a clear path forward.
Build your full operating system alongside me
We architect your content system together over 4 weeks — strategy, templates, repurposing workflows, and automation. You end the engagement with a running system, not a plan. The 30-day check-in confirms it's working.
Ongoing strategic access without the full-time hire
For operators who want a systems thinker consistently in their corner. One monthly strategy call, structured async support (two threads per week), and ongoing iteration as your system scales. I stay close enough to catch problems before they compound.
Group access for a small cohort of serious builders
A closed group — capped at 8 members — where I run quarterly architecture reviews, share frameworks before they're public, and hold monthly group sessions. You get access to my thinking and the people building alongside me. Application required.
Start where you are.
Upgrade when you're ready.
Every tier is self-contained. You don't need to start at the bottom to work up — pick the level that matches where you are right now.
A private monthly publication covering what I'm actually building and learning in real time. Decisions made, frameworks revised, things that didn't work. The unfiltered view behind the build-in-public philosophy — without the performance.
- Monthly deep-dive on a system, decision, or framework I'm running
- Honest documentation of what's working — and what isn't
- Early access to new frameworks before they're in the products
- Subscriber-only async Q&A window each month
First issue delivered immediately on signup.
A single focused session where I examine your current content setup and give you a written diagnosis with a prioritised action list. You leave with clarity, not homework.
- Pre-session intake form to map your setup
- 60-min live architecture review session
- Written audit with priority action list
- One week of async follow-up via email
Four weeks of direct access to build your full content operating system alongside me. You end with a running system — not a document about one.
- Full system architecture & strategy session
- Custom templates built to your voice & cadence
- Distribution & repurposing workflow
- 4 × weekly calls + structured async support
- 30-day post-build check-in call
Ongoing strategic access for operators who want a systems thinker consistently in their corner — without the overhead of a full-time hire.
- Monthly strategy & architecture review call
- Async support — 2 threads per week, 48hr response
- Ongoing system iteration as you scale
- Priority access to new frameworks & tools
A closed group capped at 8 operators per quarter. Monthly group sessions, quarterly architecture reviews, and ongoing access to frameworks and strategic thinking before they're packaged into products. You also get visibility into what others in the cohort are building — which compounds learning faster than solo study.
- Monthly group strategy & architecture session
- Quarterly deep-dive cohort review
- First access to new frameworks & systems
- Cohort channel for peer accountability & async discussion
- Rolling access — join at the start of any quarter
Applications reviewed within 5 business days.
Not ready for direct access yet? The Content Intelligence System ($497) is the closest thing to having me in your corner without a live engagement.
This works for a specific kind of operator.
Every engagement is intentionally small. That means I can afford to be selective about who I work with. Here's an honest breakdown.
This is for you if
- You're a solo creator or one-person business who thinks in systems
- You want to understand the architecture, not just follow instructions
- You're already executing — you need direction, not motivation
- You want to build something that runs without you in every piece of it
- You document what works and iterate deliberately
- You can handle direct, unfiltered feedback on your setup
This is not for you if
- You want someone to create your content for you
- You're looking for a managed service or agency relationship
- You're not yet sure what your business does or who it's for
- You need high-volume weekly output from me
- You want results without implementing the system yourself
- You're expecting shortcuts — this is architecture, not hacks
What people ask before applying.
What does "access to you" actually mean?
It means you're working with me directly — not a team, not a contractor, not a framework someone else built from my notes. Every call, every async message, every review is me. That's also why spots are limited.
Do I need to have a product or audience already?
For the Audit and Build-Out, some existing content activity helps — even if it's inconsistent. For the Systems Dispatch and Systems Lab, you don't need an established presence. You need the intent to build one with a systematic approach.
What's the difference between the Build-Out and the Retainer?
The Build-Out is a finite sprint — we build a specific system together and you leave with it running. The Retainer is ongoing access for operators whose systems are already in motion and need consistent strategic oversight as they scale. Most people do the Build-Out first.
How does async support work on the Retainer?
Two active threads per week via email or a shared workspace. I respond within 48 hours on business days. It's structured, not open-ended — which keeps it sustainable for both of us. This is not a Slack channel that I'm monitoring all day.
Is the Systems Dispatch different from your free content?
Yes. The free blog and public content document the strategy. The Dispatch covers the live decisions — including what I've revised, what failed, and what I'm unsure about. It's the internal operating log, not the polished framework.
Can I move between tiers?
Yes. Many people start with the Dispatch to follow the thinking, do an Audit when they're ready to pressure-test their own setup, and then move into the Build-Out or Retainer. There's no required sequence — just pick the tier that matches your current stage.
The system is already built.
You just need access to it.
Pick the tier that fits where you are. If you're not sure, start with the Dispatch — it's the lowest-barrier way to see how I think before committing to a deeper engagement.
Choose Your Access Level →Private client spots are reviewed quarterly. Applications are open now.