Every Step Needs a Trigger: How I Map a Client Workflow

When I map a client’s process, I ask the same question about every single step: what makes this happen? If the honest answer is “I remember to do it,” that step needs a trigger. Dubsado workflow triggers are what turn a list of steps into a system that runs without you, and they’re the first thing I look for when a client tells me their automations “don’t really work.”

Most of the time the automations are fine. The process has steps nothing is actually firing, so the whole thing waits on the owner’s memory. Here’s how I map a client workflow so every step fires the next one, with a real example from inquiry to booking.

Start with the client journey you want

Today’s process is usually the thing that isn’t working, so documenting it carefully gives you an accurate picture of the problem and not much else. I map the journey the client actually wants their clients to have, and use the current process for one job only: showing me where it hurts. If inquiries sit for two days before anyone replies, the ideal journey answers them in minutes. If contracts go out late because someone has to remember to send them, the ideal journey sends them on its own.

Then I make every step in that ideal journey earn its place.

Every client journey has five phases

Every map I build covers the same five phases:

1. Lead: someone inquires
2. Proposal: they decide to hire you
3. Onboarding: they become a client
4. Fulfillment: you do the work
5. Offboarding and aftercare: you wrap up, ask for feedback, and stay in touch

In Dubsado, each phase is normally its own Flow, and the end of one starts the next, so you have five connected Flows instead of one giant one. Smaller Flows are easier to read, easier to fix, and easier to change when your services do.

The trigger types I map with

In Dubsado 3.0, every step in a Flow is an action paired with a trigger, which is the condition that tells Dubsado when to run it. When I map, I sort every step into one of these:

• The Flow starting. A lead capture form or a public proposal can start a Flow on its own, so the first reply goes out the moment someone inquires.
• A client action. The client books an appointment, submits a form, signs the contract, or pays an invoice or an installment.
• A client not acting. A form that hasn’t been completed after a set number of days, which is how reminders work.
• A date. A set time before or after the project’s start or end date, or before or after an appointment.
• You finishing something. A task you check off, which holds the next step until you’ve done your part.

Some steps genuinely need you, like personalizing a follow-up after a call. A to-do that holds the next email until you check it off keeps you in the process without the whole journey depending on your memory.

The two ways a workflow breaks

Every problem I find in a map is one of two things.

A dead end is a step with nothing after it. The proposal gets signed and then nothing happens, because nobody decided what comes next. These are easy to spot once you draw the whole journey, because the line just stops.

A loose end is harder to catch. The next step exists, but nothing carries the client there. The welcome questionnaire is built and ready, and it only goes out when someone remembers to send it. Everything after that step waits too.

A common loose end in Dubsado: you send a scheduler in your Flow, but the client books through the scheduler embedded on your website instead. Appointment triggers only watch a scheduler sent by that same Flow, so the booking happens outside it and the next step has nothing to fire on. The Flow looks complete, and that action errors instead of running.

The other loose end I see constantly is payment. A payment plan is a set of installments, and each one needs its own due date and its own reminders. An installment with nothing chasing it is one of the most common places a booking stalls.

A worked example: inquiry to booked

Here’s a lead and proposal journey for a service business with one main package, mapped the way I’d map it in a session, with each step and what fires it:

1. Lead capture form submitted. The Flow starts and an inquiry reply sends right away, with the scheduler for a discovery call.
2. Appointment booked. The project status updates, so you can see at a glance who has a call coming up.
3. One day before the appointment. A prep email sends with anything the lead should think about before the call.
4. After the appointment ends. A to-do reminds you to personalize the proposal email with what you talked about.
5. To-do checked off. The proposal sends, with the contract and invoice attached so the client can choose, sign and pay on one page.
6. Proposal not completed after 3 days. A reminder sends. If the client accepts first, the reminder is skipped on its own.
7. Contract signed by the client. A thank-you email confirms what happens next.
8. Retainer installment paid. The onboarding Flow starts, and the client is officially booked.

Then I check the gaps. What happens if the lead never books the call? Sometimes the answer is a personal email from you, on a to-do, and that’s a fine answer, as long as it’s on the map. What happens if they sign but never pay the retainer? Each of those questions is a place the journey could stop, and the map is where you decide.

Where the journey splits

When a business has more than one service, the hardest call in mapping is where the journey splits into separate tracks.

The instinct is to split when the steps look different. I split based on what each step sends. Two services can follow the exact same sequence and still need separate tracks, because they use different proposals, packages, contracts or payment plans. That’s why the split usually lands right after the discovery call: everything before it can be a shared path, and everything after it depends on which service the client is buying.

Getting this wrong in either direction costs you. Split too early and you maintain two copies of the same emails forever. Split too late and the wrong client gets the wrong contract.

Simple is the goal

The measure of a good map is how little the owner has to do once it’s running. Every extra step and every extra split is something you have to maintain.

So once every step has a trigger, I go back through and ask whether each one needs to exist. Can two emails be one? Does this wait do anything? Does the client need this form, or did someone add it years ago? Where workflows can be combined, they should be.

The map is finished when you can run the system yourself, with a plain-language summary of what fires what and where the decisions are, and that’s usually a little while after the Flows go live.

Want your workflow mapped?

This is exactly what happens in my Systems Blueprint Intensive: a 2-hour working session where we map your client journey, find the dead ends and loose ends, and leave with a plan for what to build first. If you want to know what to expect going in, I walk through it in what happens in a process mapping session.

If you’d rather have the whole thing mapped and built in Dubsado for you, that’s my Dubsado setup service. And if you’re wondering why my maps hold steps on to-dos instead of approvals, I explain that in why I never use Dubsado workflow approvals.

Frequently asked questions

What are triggers in a Dubsado workflow?

A trigger is the condition that tells Dubsado when to run an action in a Flow. It can be the Flow starting, a client action like signing or paying, a client not completing a form, a date, an appointment, or you checking off a task.

Why did my Dubsado workflow stop?

Usually a step is waiting on something that never happened inside the Flow, like a booking made through a different scheduler or a to-do nobody checked off. Open the Flow inside the project and look for the first action that hasn’t run.

Should I map my process before building in Dubsado?

Yes. Building straight in the software locks in your current habits. A map shows every step, what fires it, and where it could stall before you’ve built anything.

How many workflows should one client journey have?

Usually one per phase: lead, proposal, onboarding, fulfillment, and offboarding, each starting the next. Combine them where you can and split only where services actually send different things.