Three things I do. Yours to run, or mine to keep running.

Pick the one that's not working. The usual place to start is measurement. Everything is built so your team could take it over. Or I stay on and run it.

Measure

Which of your marketing actually sent buyers? Most small businesses pay for ads, post on social, and get referrals, with no way to tell which one produced the customer. I build the measurement so you can.

What it looks like when it's done. After each campaign or event, a written read-out of which channel sent buyers and which sent traffic, so the next one is planned on evidence. Rising Stars Muay Thai is the worked example.

A typical first project

A tracking plan in plain English: what counts as a conversion, and why.
Google Tag Manager and GA4 set up to match it, with every raw event exported so the numbers can be recomputed instead of trusted.
A dashboard you can open on your phone and actually read.
A written read-out after each campaign, event, or month: what happened, what it means, what I'd change next.
If the website itself is the problem, the website first, built to be measured from day one.

Build

The website, the tools around it, and when you have the bigger idea, the product itself. Automated where it should be, AI where it makes sense. Documented so your team can run it without me.

What it looks like when it's done. A live thing with your name on it, on accounts you own, with a written handover and a walkthrough with whoever will run it. SectorPrompts is the worked example.

Three shapes this usually takes

A website that sells and can be measured. Fast, yours, with tracking built in from the first day. Changes by email if you want them: you describe it, you get a preview link, you reply YES.
One tedious task, automated. The thing someone does every week by copying between tools. It reads the form, the inbox, or the spreadsheet, drafts the reply or the entry, and waits for your approval before anything goes out.
The bigger idea. You have the domain knowledge and a budget and no engineer. I build the product end to end: the app, the sign-in, the checkout, the deployment, and the numbers behind it.

The rules for anything with AI in it, every time. You approve. You can see what it did, in a plain-language log. You own it: your accounts, your code, your data. Where the data is sensitive, it can run on a machine in your building, one you buy instead of a service you rent. AI, used like a tool →

Teach

Hands-on sessions so your team can run what I built without me. Thirteen so far, for graduate students and working marketers. The recordings have been watched 19,000+ times, and a graduate course made the series a prerequisite.

What it looks like when it's done. The person who will actually do the work has done it once, on your data, with me in the room, and has a recording for the second time. The teaching page has the workshops.

A typical first session

A half-day or full-day session, in person or on a call, using your data and your tools rather than a demo dataset.
A recording and a written walkthrough so the person who missed it can catch up.
A follow-up a few weeks later, once people have tried it on their own.

Topics I've taught: Google Analytics and Tag Manager for people who aren't analysts, dashboards and reports that don't need a developer, R and Quarto, HubSpot email, and building a site that sells with AI tools. In one session, people who had never built anything left with a live site and a working checkout.

A written scope and a price up front. Then a flat monthly rate, if you want one.

No surprise invoices.

I'll show up. Sacramento, the Bay Area, Los Angeles, Orange County, the Inland Empire, San Diego. Meeting in person, or coming to your event, is part of how I work.

Start with a quote.You describe the problem in the form below. I come back with a written scope, one price, and what your team will be able to do when it's done.
The project, at that price.If the scope changes along the way, you get a new number before I do the work, not after. I build it, document it, and train your team as part of the work. Everything is handed over: the accounts, the code, the data.
Then a flat monthly rate, or nothing.A set number of days a month to run it and keep improving it. Small one-off things by the hour. Or don't. Nothing locks you in.

Questions people ask

Do I have to be technical?

No. You have to be able to tell me what's not working. I write the read-outs and the handover in plain English, and I'll walk your team through anything they'll touch.

What if I already have a website?

Then I probably won't replace it. Most measurement work happens on top of what you have. If the site is actually the problem, I'll say so and quote it separately.

What if I don't want to run it myself?

Then I run it. A set number of days a month, a written read-out after each campaign or month, and you still own all of it. Everything is built so your team could take over whenever you decide to.

Will you train my staff?

Yes. That's the Teach lane, and it's usually the last step of a Measure or Build project, so the thing I built doesn't depend on me.

What if I want to stop?

You keep everything: the site, the data, the dashboards, the code, and the documentation. Nothing is rented from me, and nothing runs on a subscription you can't cancel.

What happens to my data with the AI parts?

It stays yours. Where the data is sensitive, the software runs on your own machine. Where a model is used, it never gets to invent a number and never sends anything without a person approving it.

Where are you?

Southern California. I'll travel for a meeting, an event, or a workshop wherever it's useful. The day-to-day happens on a call.

Tell me what's not working.

I'll tell you what I'd build, what it costs, and what you'll be able to do when it's done. Every quote is a real one, which is why there are no prices on this site. The form is the way to reach me.

Services