Services

Everything a coaching business needs from a tech department, without the department.

Six areas of work. Most clients need three or four of them, in roughly this order. Every one of them ends with documentation you own, in plain language, so you're never dependent on me to understand your own business.

Systems and CRM

The right tools, set up properly, talking to each other.

Most coaching businesses don't have a tool problem. They have a setup problem. The CRM was configured in an afternoon. The course platform was chosen because a friend used it. The two have never met, and every new client gets typed into both by hand.

I start by looking at what you have and what you're paying for. Then I fix the setup, connect the pieces, and write down how it works.

What this includes

  • An audit of what you're running and what you're paying for. You are paying for things you don't use.
  • Picking the right CRM for how you actually sell, or making the one you already own behave. HubSpot, Zoho, monday.com, GoHighLevel, Salesforce if you've somehow ended up there.
  • Pipelines, properties and views that match your real sales process, not the default template.
  • Cleaning and migrating your contacts without losing history.
  • Connecting the CRM to your calendar, payments, email platform and course platform.
  • Documentation a new VA could follow on their first day.

Typical projects

CRM selection and setup: two to four weeks
Migration from one CRM to another: three to six weeks, depending on how messy the data is
Stack cleanup and consolidation: one to two weeks

Good fit if

You have client information living in more than two places, or you've said the words "I think that's in the old spreadsheet" this month.

Tools I've administered

Zoho · HubSpot · Salesforce · monday.com · Notion · Airtable · Google Workspace · Microsoft 365 · SharePoint

Coaching and course platforms

Kajabi · GoHighLevel · Thinkific · Teachable · Circle · Mighty Networks · Practice · Paperbell · Trainual · Calendly · Acuity · Stripe · Kit (ConvertKit) · ActiveCampaign · Mailchimp

Automation

Built once. Runs every time. Nobody has to remember.

An automation is a decision you make one time instead of four hundred times.

Someone books a discovery call. They get a confirmation, a prep questionnaire, a reminder the day before, and a record in your CRM. You get their answers in your inbox an hour before the call, with a note about which program they're probably a fit for. That's six steps. You should be doing zero of them.

I build these with Make, Zapier and native integrations where they're good enough, and with webhooks, direct API work and a bit of Python where they're not. Then I write down what each one does, what breaks it, and how to fix it.

What I build

  • Lead intake and routing: forms, DMs, referrals, all landing in one place with the right tags
  • Client onboarding: contract, invoice, welcome sequence, portal access, calendar link, all triggered by one payment
  • Scheduling, reminders and no-show follow-up
  • Payments, failed-payment recovery, and invoicing that doesn't need you
  • Post-session follow-ups and homework delivery
  • Program completions, renewals, offboarding and testimonial requests
  • Internal handoffs to a VA or an assistant coach, so nothing lives in your head

Good fit if

You or a VA are copying information from one tool into another every week. That's the tell. If it happens every week, it should happen by itself.

A rule I work by

I build what you'd build if you had the time, and I document it so that it's yours. If I disappeared tomorrow, your automations would keep running and your next person could read how.

AI, applied

The useful kind of AI. Not the kind on the conference slide.

Everyone is telling coaches to "use AI." Almost nobody is telling them for what. Here's what actually works in a coaching business right now, and what I'd build first.

What works

  • Intake triage. A form comes in. The AI summarizes it, scores the fit against criteria you set, and drafts a reply for you to approve. You read three lines instead of three pages, and nobody waits four days.
  • Session notes. Recordings become a summary, a list of commitments, and a follow-up email draft in your voice, minutes after the call. Only with the client's consent, only on platforms whose data terms I've actually read.
  • Content repurposing. One recorded workshop becomes a newsletter, a dozen posts, and a lesson outline. It drafts, you edit. You stay the author.
  • A bot trained on your own material. It answers "what's your refund policy" and "where's the module three worksheet" at 2am, from your documents, with a link to the source, and hands off to a human the moment it isn't sure.
  • Agentic workflows. Multi-step processes where the AI makes routing decisions inside guardrails you define. Which program does this lead belong in. Which of these forty support emails needs a person today. I've built these for a service business that now turns customers around in three days with almost no manual work.

What I won't do

Put your clients' private conversations into a tool with data terms neither of us has read.

Automate something that should have your judgment in it.

Ship an AI feature because it's fashionable this quarter.

What you get

An AI opportunities review: the three to five things in your business worth automating, in order, with an honest note on the ones that aren't.

The build, with fallbacks, so a model having a bad day doesn't break your onboarding.

A one-page policy for you and your team on what goes into AI tools and what never does.

Good fit if

You've tried ChatGPT, found it useful, and have no idea how to make it part of how the business runs rather than a tab you sometimes open.

Data and dashboards

The real numbers. One screen. Updated without you.

You probably know your revenue. Do you know your revenue by program? Your show-up rate for discovery calls? How many active clients you can take before the calendar breaks? Most coaches run on a feeling and a Stripe balance.

I've defined KPIs and built executive dashboards for a collection of startups, and reported return on investment to a CEO and a board. Your version is smaller. The discipline is the same: pick the numbers that change decisions, connect the sources, and stop building spreadsheets by hand on Sunday night.

What this includes

  • Choosing the five to ten numbers that actually matter for your business and defining them so they mean the same thing every month
  • Connecting Stripe, your CRM, your calendar and your course platform
  • Building the dashboard in Looker Studio, Power BI, Tableau, or a well-built Google Sheet, depending on your budget and what you'll actually open
  • A monthly fifteen-minute review, if you want one, where I tell you what moved and why

Numbers I usually end up tracking

Leads by source · Discovery call booked and show-up rates · Close rate by program · Revenue by program · Active clients and capacity · Renewals and churn · Failed payments · Time from lead to first session

Good fit if

You make pricing, hiring or launch decisions more than twice a year and you'd like them to be based on something.

Fractional IT

The stuff nobody owns until it breaks.

Who has the password to your domain registrar? What happens to your client files if your laptop is stolen tonight? Why are your emails landing in spam? These aren't interesting questions. They're expensive ones, and in a business of one to five people, nobody's job is to ask them.

I'm not a 24/7 helpdesk and I don't pretend to be one. I'm the person who sets things up so you rarely need one, and who knows who to call when you do.

What I handle

  • Accounts and access: a password manager, two-factor on everything that matters, shared vaults, and a way to offboard a contractor without a panic
  • Google Workspace or Microsoft 365 setup and administration
  • Domains, DNS and email deliverability, including SPF, DKIM and DMARC set up correctly so your emails arrive
  • Backups of the things that would actually hurt to lose
  • Device and security basics for a small team, written as a checklist people will follow
  • Vendor wrangling. I'll sit on hold with support so you don't have to.
  • A one-page recovery plan: if this breaks, do this, call this person

Good fit if

You've ever lost access to something important, or you're not sure you'd know if you had.

Product, launch and team ops

From "I have an idea for an app" to something that ships.

Coaches have product ideas. A membership. An app. A certification program. A group program with a workbook and a portal. The gap between the idea and the launch is where most of them die, usually in a conversation with a developer who quoted $60,000 for something that should have cost $8,000, or $8,000 for something that was going to need $60,000.

I've run product development end to end, from requirements to launch, and I've managed the developers, the vendors and the timelines. I'll do the same for yours, at the size it actually is.

What this includes

  • Turning the idea into requirements and user stories a developer can build from and quote against
  • Vendor selection: proposals, quotes, references, contracts, and the questions you don't know to ask yet
  • Managing the build. I've run software teams using Agile and Lean methods; yours will get the same structure at a smaller scale.
  • Launch readiness: payments, access, support, the email sequence, the thing that always breaks on day one
  • SOPs and playbooks so the program runs the same way with or without you in the room
  • Hiring and onboarding help when you need a VA, an assistant coach or a community manager. I'm PHR certified and ran people operations across several startups, so this is not a side skill.

Good fit if

You've got a product idea you've been carrying around for more than six months, or a team of two or more who each do things a slightly different way.

How we'd work together

Hours by the month. Every tier comes with the same person.

Every engagement starts with a systems check, which is free. After that, it's a monthly tier, a fixed-price project, or something bigger we scope together.

10 hours a month

Keep it running.

For a lean stack that needs an owner: the fixes, the small builds, and the questions you'd otherwise search for at 10pm.

$1,650 a month

  • Ten hours a month, tracked and reported
  • Replies within two business days
  • A short note each month on what moved and why
Start with a systems check

30 hours a month

Run the back office.

For a growing business with a team, several programs, and more data than anyone is reading.

$4,200 a month

  • Thirty hours a month across operations, automation, AI and reporting
  • Replies the same business day
  • A monthly review of the numbers and what's next
  • Room for a project inside the month
Start with a systems check

Projects

A defined piece of work with a start and an end.

A CRM migration, an onboarding automation, a dashboard. Scoped in writing, fixed price, half up front and half on delivery.

From $1,500

More than 30 hours, or full time

For a launch, a rebuild, or a season.

When the work needs more than thirty hours a month, or me full time for a stretch, we scope it together and price it to fit.

Let's talk

How the tiers work

  • The first three months as a block, then month to month.
  • The first month opens with a map of your stack and a priority list, at no extra cost.
  • Up to a quarter of unused hours carry into the next month.
  • Extra hours are $175 each, and only with your OK first.
  • If the thing that takes payments breaks, you get a same-day response on any tier.

Monthly prices are exact. Projects and anything over thirty hours are quoted after the systems check, and the quote is the price.

What the first month looks like

The first month should produce something you can feel, not a strategy deck.

Week 1

Access and audit

I get into your tools, read what's there, and talk to whoever else touches the stack. You do very little except answer questions.

Week 2

The map

You get a one-page map of what you have, what's broken, what's costing you money for nothing, and what I'd do in what order. We agree the order.

Weeks 3 and 4

The first two fixes

Usually the most annoying manual process and the most fragile thing. Shipped, tested, documented.

After that

A rhythm

A short monthly list, a short monthly check-in, and a stack that stops being something you think about.

Questions people actually ask

Questions, answered.

Do I have to give you my passwords?

No. We set up a password manager (if you don't already have one) and you share access to the specific tools I need through it. You can revoke any of it in one click, and we do exactly that when an engagement ends. I'll never ask you to email me a password.

What about my clients' privacy, especially with AI?

Your client conversations are the most sensitive thing in your business, and I treat them that way. Nothing goes into an AI tool without your explicit decision, a look at that tool's data terms, and client consent where it's needed. Part of the AI work is writing a short policy so your team knows the rules too. If you're in a regulated corner of coaching or education, we build to that standard.

I already have a VA. Do I still need this?

Probably, and your VA will be happier for it. VAs execute processes. I build the processes and the systems they run on. Most of what I automate is the work your VA finds least interesting, which frees them for the things that actually need a human.

Do you build websites?

Not as a main service. I'll set up, connect and fix the tools behind a website (forms, CRM, payments, booking, email), and I'll manage a web developer for you if you need one built. If you need a site designed from scratch, I'll point you to people who do that well.

What happens when the engagement ends?

You keep everything. Every automation, dashboard and setup comes with documentation written for a person who has never seen it. We do a handoff call. Your access to me gets revoked. If something breaks six months later and you want help, you book a project.

Which tools do you know?

The list on this page, plus most things with an API. If you're on something I haven't used, I'll say so and tell you how long it'll take me to learn it. It's usually a day or two, because these tools are more alike than their marketing suggests.

Are you actually available full time?

Yes, if the work needs it. Full time is a different arrangement from the monthly hours, so it's priced separately and we'd scope it together on a call first.

Do you work with education businesses that aren't coaches?

Yes. Tutoring companies, small training providers, course creators, certification bodies. Same tools, same problems, same fixes. If you deliver teaching to paying clients and you're too small for a tech department, this is for you.

I'm not sure I'm big enough for this.

Book the systems check anyway. If you're not there yet, I'll tell you, and I'll tell you what to do yourself in the meantime. You'll remember who told you.

Where are you based? Do you work remotely?

Scottsdale, Arizona. Remote by default. I'll come on site for an embedded engagement or a launch if it's useful and you cover travel.

Let's look at your stack.

Thirty minutes. I'll tell you what I'd fix first, what I'd leave alone, and whether you need me at all.