Dubsado Workflows: Plan Before You Build

I was inside a photographer’s Dubsado account not long ago, doing a Dubsado workflows audit, and within about two minutes I could see exactly what had gone wrong.

She had one workflow covering everything — inquiry through gallery delivery — and it was stalling constantly. When one thing didn’t fire, everything after it didn’t fire either. Clients were getting emails out of order. Some weren’t getting them at all.

I see this version of broken. I also see the other version: a photographer who set up workflows a couple of years ago, something didn’t work right, a client got a weird email or no email, and she just gave up. Went back to doing everything manually. The workflows are still sitting in her account — untouched — and the reason they broke in the first place was almost never the logic. It was that nobody tested them properly before a real client went through.

Both are fixable. But the fix isn’t clicking around in Dubsado until something works. It’s planning before you build, and testing before you send a real client through it.

Before we get started — hi, I’m Colie James, Certified Dubsado Specialist and host of the Business-First Creatives podcast. I’ve built Dubsado setups across every photography niche and the patterns I see in broken setups are remarkably consistent. Here’s what I want you to know before you build a single step.

What a Dubsado Workflow Actually Is

Technically: a workflow is a series of automated actions — emails, forms, status changes, to-do tasks, scheduler links — that fire in a set sequence based on triggers you define.

But that’s not really what it is.

A workflow is the structure behind your client experience. It helps you organize every touchpoint, streamline the sequence, and automate the parts that make sense to automate — so nothing falls through the cracks and nothing fires at the wrong time. Every email that sends, every form that goes out, every reminder that fires — that’s what your client sees and feels while working with you. The workflow is the delivery mechanism. Which means if you haven’t thought through the experience first, the workflow is just a series of steps going to the wrong person at the wrong time.

This is why I always say: design the client experience before you build the workflow. The workflow is the output of that thinking. It is not the starting point.

If this is new to you, I’d start with Why We Design the Client Experience Before We Build Workflows in Dubsado — it covers the philosophy behind everything I’m about to walk you through.

Why You Have to Map Before You Build Dubsado Workflows

Here’s the thing about that photographer I mentioned. When I asked her to walk me through her client process — not in Dubsado, just in plain language — she couldn’t quite do it. She knew the general shape of it, but the details were fuzzy. When did she send the questionnaire? How long after booking? What happened if someone didn’t book after the discovery call?

She didn’t know, exactly. So she’d built a workflow based on what Dubsado’s features allowed, not based on what her clients actually needed.

Mapping your process means writing it out as if Dubsado doesn’t exist. What happens — step by step, in order — from the moment someone inquires to the moment they’re done working with you? What does your client need to know at each stage? What do they need to do? How much time should pass between each touchpoint?

That map is what your workflows are built from. Without it, you’re guessing. And guessed workflows break.

The question that unlocks it is this: at every stage of working with me, what does my client need to know, feel, and do — and when?

Write that out for inquiry, for booking, for the weeks before the session, for session day, for delivery, for offboarding. Don’t think about Dubsado yet. Just think about the experience.

Then build the workflows from that map.

I go deep on the mapping process in How to Design Workflows That Enhance Your Client Experience — it’s part three of my Client Experience series and it’s worth reading before you touch anything in Dubsado.

The 5 Dubsado Workflows Every Photography Business Needs

This is where most tutorials start. I think it’s actually step three — after you understand what workflows are and after you’ve mapped your process. But once you’ve done that work, here’s how to think about the five separate workflows your business needs.

Separate. Not one big one. Five focused ones, each with a clear purpose, a clear start, and a clear end.

The reason this matters: when your workflows are separated by phase, a stalled step in one workflow doesn’t take down your entire client journey. You can also apply, pause, or swap workflows as your client’s situation changes — which happens more than you’d think. Clients pick the wrong session type. They upgrade their package. They postpone. A single long workflow makes all of that a mess. Separate phase workflows make it manageable.

1. The Inquiry Workflow

Goal: qualify the lead and get them to the next step without losing them.

This workflow starts the moment someone submits your inquiry form and ends when you’ve qualified them to move to the next stage — whether that’s through a discovery call or an application review. It sends an immediate auto-response, sets expectations for what happens next, and follows up automatically if they haven’t taken action.

The most common mistake: one auto-reply and then silence. If someone doesn’t book a discovery call within a day or two, most photographers just… wait. There’s no automated follow-up, no gentle nudge, nothing. That lead is gone — not because they weren’t interested, but because life happened and you never came back.

A solid inquiry workflow has 2-3 follow-up touchpoints built in. Not aggressive. Just present.

→ [How to Set Up Your Dubsado Inquiry Workflow — coming soon]

2. The Booking Workflow

Goal: get hired. Get the proposal signed, the contract completed, and the payment made — ideally in one sitting.

This workflow starts after you’ve decided to move forward with someone (after a discovery call, or right from inquiry if that’s your process) and ends when they’ve paid their deposit.

The most common mistake here is one I see constantly in audits: photographers manually send the proposal instead of sending it through the workflow. This feels harmless. It’s not. The moment you send a proposal manually, you lose the ability to automate follow-ups. Dubsado can only watch for “form not completed” if the form was sent through the workflow. Send it manually and you’re back to chasing people yourself.

Send. Everything. Through. The. Workflow.

Your booking workflow should also include 2-3 automated follow-ups for anyone who doesn’t complete the proposal. The first one goes out automatically. You can decide on the second and third. But that first one needs to be automatic, because the person who fills out your proposal at 9pm on a Tuesday and then gets distracted before they pay — that person needs a nudge the next morning, not silence.

→ [How to Set Up Your Dubsado Booking Workflow — coming soon]

3. The Onboarding Workflow

Goal: prepare your client for what’s coming and build trust before session day.

This workflow starts after they’ve booked — after they’ve paid their deposit — and runs through session day. It includes your welcome email, your prep guide, your questionnaire, session reminders, and any other touchpoints that help your client arrive feeling ready and taken care of.

The most common mistake: one welcome email and then nothing until a week before the session. That silence feels like abandonment. Clients start wondering if you forgot about them. They start texting to confirm. They show up less prepared than they could have been.

A good onboarding workflow keeps clients warm between booking and session day without requiring you to do anything manually. It’s timed based on the session date, not on what happened before it — so it runs on schedule even if you forget to check off a to-do task.

If you shoot weddings, I mapped out a complete wedding photography onboarding workflow you can use as a starting point.

4. The Delivery Workflow

Goal: deliver the final product in a way that sets up a great offboarding.

This workflow starts when the gallery is ready and ends when they’ve received it and you’ve confirmed delivery. It’s shorter than the others — but the email you send here might be the most important one in your entire client journey.

The most common mistake: a link and a “let me know if you have questions.” That’s not a delivery. That’s a transaction. Your gallery delivery email should acknowledge the session, tell them what to expect in the gallery, give clear download instructions, and — this is the part most photographers skip — ask for the review right now, in this email, with a direct link, at the exact moment they’re opening images of their kid laughing and crying at the same time. That’s peak emotion. That’s when they’ll write the review. Not next week.

I know it seems like I am playing favorites with the wedding photography examples, but review How to Nail Your Photographer Gallery Delivery for specific examples of actions + triggers inside this workflow.

5. The Offboarding Workflow

Goal: close the relationship with this client and open the door to the next one.

This is the workflow most photographers don’t have. At all. And it is — I say this constantly — the most expensive gap in your entire business.

Your offboarding workflow handles the review ask (if you didn’t get it at delivery), the referral ask, and the seed for the next session. It’s what turns a happy client into a repeat client and a referral source. Done well, it’s also what fills your calendar with people who already know what to expect from you, which means fewer difficult sessions, better images, and more of the work you actually want to do.

I’ve written about this at length in How to Get Repeat Clients as a Photographer — start there if offboarding is new territory for you.

→ [How to Set Up Your Dubsado Offboarding Workflow — coming soon]

What You Need Before You Build Anything

I want to be direct about this because it’s the step most people skip entirely.

Before you open the workflow builder in Dubsado, you need:

Your process mapped out. Written down, plain language, no software. What happens at each phase, in what order, with what timing. This is the map everything else is built from.

Your content assets created. Workflows can’t send what doesn’t exist. Before you build, you need your canned emails written, your proposal designed, your contract ready, your questionnaire built, your scheduler set up. If any of those are missing, go build them first. The workflow is last.

A clear trigger for each workflow. What starts it? What ends it? What kicks off the next one? If you can’t answer that for each of the five workflows, you’re not ready to build yet.

One workflow per phase. Not one for everything. Not two big ones. Five focused ones, each handling one stage of the client journey. When a client’s situation changes mid-process, you need to be able to swap or adjust one workflow without touching the others.

A workflow that’s trying to handle inquiry, booking, and onboarding all at once is going to break. And when it breaks, you won’t be able to tell where.

This is also where “after all previous actions complete” gets people into trouble. I see it in almost every audit I do. If you have more than two or three of those triggers in a single workflow, you’re setting yourself up for things to stall — because if any one action before it doesn’t get completed, nothing after it fires. Use it sparingly. Time things off project dates and specific form completions instead.

For a full breakdown of what breaks and why, read my post on common Dubsado workflow mistakes — it goes deep on the specific errors I see most often.

Ready to Build?

You can spend a weekend clicking around in Dubsado and end up with something that technically runs. Or you can spend an hour mapping first and build something that actually works.

The second one takes longer on day one. It saves you everything after that.

If you’ve been in Dubsado for a while, have workflows running, and things mostly work — but you have a nagging feeling something’s off — a Client Experience Audit is the fastest way to find out. I go through your account and your client journey and tell you exactly what needs tweaking and what needs a full rebuild. Most people are surprised by which one it is. And if you’re not sure whether you need an audit or a full setup, that’s kind of exactly what the audit is for. Start there: How to Improve Your Client Experience: A Breakdown of My Audit Process.

If you want to build it right from the start — or rebuild it properly — Systems in Session is my done-with-you Dubsado setup program. We map your client journey, build your workflows, and make sure every phase is connected before you ever send a real client through it.

Not ready for either of those yet? Grab the free Workflows and Automation Guide — it gives you the framework to start mapping on your own.

FAQ for Dubsado Workflows