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

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

A booking tool is not a CRM. A project management tool is not a CRM. And the $20 to $40 a month you're trying to save by getting rid of yours might end up costing you bookings.
Every single week I see someone on Threads asking if they can replace their CRM with Notion, Airtable, Google Workspace, or Squarespace. I use Notion and Airtable daily in my own business — and neither one of them would have replaced the CRM inside my photography business. So let's talk about what your CRM is actually doing for you before you cancel it.
In this episode:
The four things a tool has to do before it counts as a real CRM
Why conditional logic is the line between a CRM and a very organized file cabinet
What actually happens (and doesn't) when a lead fills out your Squarespace form
Why "I have Dubsado and I'm not using it" is a setup problem, not a CRM problem
Where Notion, Airtable, ClickUp, and Asana genuinely earn their place in your stack

Links mentioned:
The Best CRM for Photographers → https://coliejames.com/best-crm-for-photographers/
Building a Custom Notion Dashboard with Ania Ha → https://coliejames.com/building-a-custom-notion-dashboard-how-i-streamlined-my-entire-business-with-ania-ha/
Systems in Session → https://coliejames.com/systems

Sitting on a CRM you set up but never fully figured out? That's the whole thing I do. Let's talk: coliejames.com/systems

There is no all-in-one software that does everything well. Every single one of them makes you give something up. The only real question is whether you're okay with what you're giving up.
This one is for the photographers. Every time I open Threads, someone is asking how to consolidate their tech stack down to one tool — fewer logins, fewer subscriptions, one connected experience for their clients. I get it. But I'm also going to tell you why gallery software that added CRM features and a CRM that added gallery features are two very different things, and why that difference should decide what you do next.
In this episode:
The three reasons photographers try to consolidate their tech stack
Why I'm fine with Sprout Studio when I'm not an all-in-one person
The one thing Pixieset would have to fix before I'd stop steering people away from it
What HoneyBook and VSCO (formerly Táve) just quietly added to their platforms
The type of photographer who should not touch either one of them yet

Links mentioned:
The all-in-one software blog post (kept updated as features release) → https://coliejames.com/photography-all-in-one-software/
Episode 297: Three Ways Business Systems Can Generate More Revenue → https://coliejames.com/generate-more-revenue-with-systems/
What Pixieset will and won't give you → https://coliejames.com/dubsado-vs-pixieset/
Systems in Session → https://coliejames.com/systems

Looking at a new tool and want the Colie seal of approval before you jump? Come drop it in my DMs — or if you'd rather stop shopping and start using what you already pay for, that's Systems in Session: coliejames.com/systems