Skip to main content

Here’s the manual.

Read this before you book the call. If any of it sounds wrong for how your team operates, I’m probably not the right operator. Better to know now than in week three.

§ 01

What I actually do

I run the full GTM motion — from demand generation to the operational backbone that keeps revenue moving. That means I design and run inbound programs (paid search, paid social, SEO, content), rebuild outbound, fix the attribution and pipeline governance underneath it all, and leave your team with working systems when I’m done.

I’m an AI marketing operator, not a consultant. A consultant hands you a deck. An operator ships working systems. If you want slides, hire McKinsey — they’re better at it than I am.

  • I do: build and run demand gen programs (paid search, paid social, SEO, content), design and rebuild outbound (sequences, ICP targeting, cadence), fix attribution, rebuild pipeline governance and forecasting, set up weekly pipeline reviews, write playbooks your team owns at handoff.
  • I don't do: write strategy decks, run your LinkedIn ads in isolation, sit in a titled seat indefinitely, onboard a fractional team on top of yours, take clients below $5M ARR.

§ 02

My value system at work

  • Install, don't advise. If the engagement ends with a deck and a Slack goodbye, I failed. It ends with working systems and a team running them.
  • Outcome over activity. Busy-work is cheap, outcomes are expensive. Every week I ask two questions: did the leading indicator move, and if not, what changes Monday.
  • Ownership beats alignment. “Aligned” is the word that precedes a dead initiative. One name, one calendar, one metric, one cadence.
  • Never-ask-twice. If you ask me for something manually and it’ll happen again, I automate it. Your time shouldn’t be spent on the same ask more than once.
  • Transparent pricing. No “schedule a call to discuss.” Every price is on the menu. If we need custom scope, we quote it in writing before we start.
  • Short feedback loops over perfect plans. Working ugly beats polished dead. Ship it Monday, iterate Thursday.

§ 03

How I operate

  • Async-first, sync where it matters. Weekly Looms replace weekly status calls. Synchronous time is reserved for decisions, not updates. You get your mornings back, I can serve more clients without dropping quality.
  • Week-one shipping. Most fractional CMOs serve six clients by spreading thin. I serve four by running the platform — my own production infrastructure that plugs into your stack on day one and runs the optimization loops in the background. You get senior judgment at fractional economics because the system absorbs the load.
  • Direct, no fluff. I don’t soften hard feedback. If your forecast is a Ouija board, I’ll say that. If your ICP is three ICPs pretending to be one, I’ll say that too. This is what you’re paying me for.
  • Claude-native delivery. AI is in the work path, not a bullet point. Research, copy drafts, data reconciliation, weekly narration — all AI-assisted. Judgment calls stay with me.
  • Hands-on in the weeds. I’m not a Strategy Partner who shows up for the quarterly review. I build the thing.
  • Weekly shipping log. Every Monday, I publish what shipped across all engagements on /shipping. Public or client-private. You always know what you’re paying for this week.

§ 04

What I expect from you

  • One internal owner. A named person on your team who can make decisions when I need them made. Not a committee.
  • Access on day one. HubSpot / Salesforce / Google Ads / whatever we’re touching. The platform lets me move fast only if the OAuth handshake happens on day one, not week three.
  • A weekly 30-minute review. Same day, same time. Non-negotiable. The rhythm is the engagement.
  • Honest answers about what's broken. If you hired me to fix it, you have to be willing to say it’s broken — publicly, to your team. I can’t install discipline around a problem no one will name.
  • Respect for the handoff. The goal is that your team runs the systems after I leave. That means your team does the work during the engagement, not a fractional bench I bring with me.

§ 05

What you can expect from me

  • First working system in week one. Not an audit. A shipped system you can see running in your stack.
  • Refundable diagnostic. If after the 30-day diagnostic you don’t want to proceed, full refund. No awkward conversations.
  • No contracts beyond the 3-month retainer minimum. Fractional retainers are month-to-month after that. If month one isn’t working, full refund on that month.
  • A written playbook at handoff. Every engagement ends with your team holding a documented playbook. If they can’t run it without me, I didn’t finish.
  • Async availability, sync where it matters. Slack DM response within a business day. Calls when decisions need them. No “quick sync” meetings.

§ 06

Anti-patterns I won't take on

Some engagements are set up to fail before they start. These are the ones I walk away from.

  • “We need someone to run our GTM for six months while we search for a permanent CMO.” That’s not what fractional is for. Hire a recruiter.
  • “Can you write us a strategy document we can present to the board?” I don’t sell slides.
  • Companies below $5M ARR or pre-product-market-fit. The work I do assumes you have a working business. If you don’t, fractional GTM isn’t your problem yet.
  • No single named owner on your team. If five people are “aligned” on this, zero own it.
  • You want me to run something in isolation — just ads, just content, just outbound — without any of the upstream systems that make them work. That’s an agency engagement, not a fractional operator engagement.

§ 07

How the system stays safe

One gateway reaches every tool in your stack. Every write is previewed, approved by you, then logged.

  • One gateway, every system. Ad platforms, CRM, analytics, outreach tools connect through one gateway, isolated per client. 25+ live connections run across active engagements today.
  • Dry-run by default. Every write is previewed first. You see the change before it happens. That’s not a setting. It’s how it’s built.
  • One-tap approval, full audit trail. A preview goes live only after you approve it, even from your phone. Every change lands in an append-only log.
  • Your credentials, not ours. Every connector runs on your own accounts. Handoff is a credential transfer, not a migration.
  • Built to fail safe. Read access is broad. Write access is narrow and gated. A bad call becomes an unapproved preview, never a live surprise.
live connections across active client engagements
25+

Still here? Book the call.

If the above sounds like the operator you want installed in your portco, book a diagnostic. 30 minutes, no sales pitch. If it’s not a fit, I’ll say so on the call. That’s worth 30 minutes of your time too.

Start with proof

Working session.
No pitch.

Where your pipeline leaks, what each leak costs per month, and the first fix that pays for itself — built from your actual data, with a firm price on the fix.