Business-First Creatives: Client Experience & Systems for Service Providers

Jocelyn of Scale Your Resonance wants every one of her Best Seller clients making five figures from email, and yes, that includes me. Bold goal? Absolutely. In this episode, we dig into her new app, Email Studio. She built it for herself first, but you don't need to be a Bestie to use it, because it's open to the public and she's on a mission to get 100 users in the first 100 days. It's how I'm making email part of an always-selling marketing plan, and it can be part of yours too.
Because here's my confession: I sometimes email my list multiple times a day, my click rates are in the toilet, and almost none of my sales come from email. Jocelyn, who helped me launch this podcast four years ago, tells me how to fix it. We talk about the missing proof in your emails, why your best emails start out loud, and why "I'll just use Claude" isn't the same thing as a tool built on real expertise.
In this episode:
Why emails without client proof don't convert, and why the small progress wins count just as much as the big results
How a miserable afternoon writing emails in an airport lounge turned into a voice-note-first writing process
The moment a stack of AI skills needed to become an actual app
How to keep AI-assisted emails sounding like you and not like a press release
Why real users and real feedback are what separate a tool that works from a tool that just exists
What you get from a tool built on someone's frameworks that you won't get from plain Claude or ChatGPT

Links mentioned:
Email Studio (my affiliate link) → https://coliejames.com/jocelyn
My episode with Kara on why everyone's an AI expert now → https://coliejames.com/everyones-an-ai-expert-ft-kara-duncan/
My episode with Annemie Tonken on AI and IP → https://coliejames.com/beyond-diy-chatgpt-the-human-first-ai-blogging-tool-for-intentional-creatives/

For a limited time, grab Email Studio for $199 for six months (normally $299) → https://coliejames.com/jocelyn
Curious how I actually use this thing, or where I've written emails lately (volleyball bleachers included)? DM me on Threads: @coliejames

How long does it actually take you to serve one client? Not the session. The whole thing.
If you're not sure, you're not alone. When I review offers, I find the same time leak over and over. It's hiding in emails you write from scratch, proposals you rebuild for every lead, and the "quick" peeks into your CRM that you never count. This one's short, and it comes with homework. Yes, even if you're not my client.
In this episode:
The homework I want every photographer to do before slow season hits
Why your session time is barely part of what your price has to cover
The time suck almost nobody writes down
The phase that takes the least time but has the biggest impact on your revenue
The two templates I'd build first if you're too busy to build anything

Links mentioned:
The Experience Edit → https://coliejames.com/experience
Order of Operations Framework → https://coliejames.com/building-client-experience-systems
Find me on Threads → @coliejames

Do your time audit, then come tell me your number on Threads @coliejames. I really want to know.

What happens when you get tired of forcing your business into software that doesn’t quite work the way you want it to? Apparently, if you’re me, you accidentally spend your birthday sabbatical building your own app. In this episode, Kara Duncan is taking over the mic and interviewing me about how a few experiments with AI tools turned into the Systems Professor app—and eventually opened my eyes to an entirely new direction for my business.
I’m sharing how I went from custom GPTs, Airtable, Notion, and existing CRM tools to building software around the way I actually want my clients to experience Systems in Session. We’re talking about Claude Code, vibe coding, personalization, accountability, AI, client experience, and why having the ability to automate something doesn’t necessarily mean I should.
And yes, we also talk about the fact that I got so absorbed in building the app that my husband handed me coffee on his birthday and I still forgot to tell him happy birthday. 😬

Find It Quickly
01:22 - Birthday Sabbatical Chaos
05:25 - Why Build an App
07:41 - Action Taker ADHD
09:40 - Rolling It Out
14:14 - Welcome Guides Playbooks
16:11 - Better Audit Delivery
18:18 - Accountability Personalization
23:14 - Origins in Custom GPTs
25:39 - Why Build an App
27:19 - Onboarding Intake Flow
28:59 - Offer Scorecard Check
33:11 - App Enhances Coaching
37:18 - One Click Build Debate
41:43 - Tech Stack Behind It
44:57 - Custom Tools for Clients
48:49 - AI Optional Philosophy

Mentioned in this Episode:
Systems in Session: coliejames.com/systems-in-session
Experience Edit: coliejames.com/the-experience-edit
Claude Code: claude.com/product/claude-code
Claude Cowork: claude.com/product/cowork
Hello Stencil: hellostencil.com
Lovable: lovable.dev
Airbase: airbase.com
Supabase: supabase.com
Vercel: vercel.com
Cloudflare: cloudflare.com
Amazon Web Services: aws.amazon.com

Connect with the Guest
Website: thekarareport.com
Instagram: @thekarareport

For five and a half years, I've helped you map your client journey, get excited about what's possible, and then spend the rest of our time together bending that vision to fit inside Dubsado or HoneyBook. As of today, I'm done with that.
This one's short and sweet — part behind the scenes, part building in public. My business has flipped upside down in the last year and a half, and building the Systems Professor app cracked something open that I can't un-see. So here's where I'm going next, and what it means if you want to work with me.
In this episode:
The pivot I've been circling for five years and am finally saying out loud
Why building my own custom tool changed how I think about your tools
What I got wrong with workflows, and then again with Email Like You Mean It
Why the Experience Edit is now the front door to everything I offer
The one step I'll never skip with a client again, no matter what software they use
When a custom-built tool is actually the right move (and when it isn't)

Links mentioned:
The Experience Edit → https://coliejames.com/experience
Order of Operations episode → https://coliejames.com/building-client-experience-systems/
Tomorrow's episode with Kara: how I built the Systems Professor app → https://coliejames.com/everyones-an-ai-expert-ft-kara-duncan/

Ready to map the client experience you actually want, before we ever talk about tools? Solo sprints are open now, and one more group sprint is coming before the end of 2026: coliejames.com/experience

Your client just paid you hundreds, maybe thousands, of dollars. And the only thing that landed in their inbox was a payment receipt and a "your contract has been signed" email. That's not onboarding. That's a transaction.
I've been seeing the same three onboarding mistakes over and over inside my Experience Edit and Systems in Session client accounts, and most of y'all aren't making them on purpose. You want this part to be good. You just don't know what "good" looks like, or you're so focused on making it personal that nothing actually gets sent. So this is a quick and dirty episode answering the three questions I get asked most about the onboarding phase.
In this episode:
Why a booking confirmation email is non-negotiable even when the receipt and contract emails already went out — and why it should land last in their inbox
The "kitchen sink email" problem and what to drip out over time instead
Why I want you to ditch the heavily designed PDF prep guide for a live Canva link
What actually belongs in a welcome or prep guide (hint: everything you were cramming into that one email)
How to decide when to send your client questionnaire based on how far out your clients book and when you need the information

Links mentioned:
The Experience Edit → https://coliejames.com/experience
Come tell me what you fixed on Threads → https://threads.net/@coliejames