Dubsado Booking Workflow: Proposals and Follow-Up Emails That Get You Paid

The booking workflow has one job: get paid. Not “keep the conversation going.” Not “get them to consider it.” Get the deposit in your account so you can start the work.

Most photographers make this harder than it needs to be. The booking process should connect your services, contract, and invoice — plus scheduling if you need it — so there’s no booking friction and no email ping pong required. Your client should be able to go from receiving the offer to officially booked in less than five minutes. That’s not a stretch goal. That’s what a well-built booking workflow actually does.

This is post three in my Dubsado Workflow Series. If you haven’t read post two on the inquiry workflow, that’s where this one picks up — this post starts the moment you decide to make someone an offer.

Before we get started — hi, I’m Colie James, Certified Dubsado Specialist and host of the Business-First Creatives podcast.

Let’s build a booking process that actually converts.

Where the Booking Workflow Starts and Ends

The Dubsado booking workflow starts the moment you decide to make someone an offer and you’re ready to present it.

It ends in one of two ways: they pay their deposit, or you’ve decided they’re a cold lead and you close the loop on the offer. Both are valid exits. Both need to be planned for.

What goes in between — the proposal, the contract, the invoice, the follow-ups — that’s what this post is about.

One thing I want to say before we go further: the booking workflow and the inquiry workflow need to be separate. I see photographers combine them constantly, and it creates a mess. When the proposal is part of the inquiry workflow, Dubsado loads it the moment someone inquires — before you’ve qualified them, before you’ve had a call, before you even know if you want to work with them. Now you’ve got incomplete proposals and phantom invoices attached to leads who never booked. When someone picks the wrong session type on the inquiry form and you need to swap it out, you’re cleaning up a half-built proposal instead of just starting the right workflow fresh.

Keep them separate. The booking workflow starts manually — you apply it when you’ve made the decision to move forward with someone.

The Proposal Is the Booking System

Most photographers think of the proposal as the document they send to get paid. It’s actually the entire booking experience compressed into one place.

A well-built Dubsado proposal does five things at once: it presents the offer visually, collects their contact information, delivers the contract, generates the invoice, and gives them one place to say yes and pay. That’s what makes the five-minute booking process possible. Not a great sales call. Not clever email copywriting. The proposal does the work — and then your client doesn’t have to go back and forth over email while they wait for you to manually send the next piece.

I had a client who walked downstairs to make a cup of coffee after sending a proposal and came back to find they’d already been paid. The person had the proposal up on their screen during the call, reviewed it, and paid the moment they hung up. That’s not luck. That’s a proposal that was doing its job.

But here’s the thing I want you to hear clearly: pretty proposals only work when the system around them works. I’ve seen gorgeous, on-brand, impeccably designed proposals fail — not because they looked bad, but because the client got to the end and still didn’t know what happened next. Design speeds up decisions. It doesn’t create clarity. If your proposal is asking your client to make decisions you haven’t already made for them, no amount of beautiful photography is going to fix that.

I had a client — Maddie Peschong, a brand photographer — who came to me wanting a better proposal. In her words, she just needed something that looked more professional. But as we got into the work, it became clear the proposal wasn’t the only thing that needed attention. Her client experience had gaps she hadn’t seen yet — places where communication was missing, where clients weren’t being prepared properly, where things were falling through. She left with a fully automated client experience, more confidence charging $2,500–$5,000, and booked a new client within a week of finishing the setup. The proposal is the gateway, not the fix — but when the system around it works, it works fast.

What a converting proposal actually contains:

A strong header. Above the fold matters here just like it does on your website. The image at the top should make them want to be in those photos immediately.

An about you section. Yes, even if they’ve already been on a call with you. They don’t remember everything. Remind them who you are, what makes your sessions different, and why this is going to be worth it.

Your process laid out as a timeline. From booking to delivery. What are you going to do to prepare them? What happens on session day? How long until they get their photos? Give them the highlights — not 1,500 words, but enough that they remember what they signed up for.

A FAQ section that addresses real objections. What do people ask you on every single discovery call? Put those answers here. What happens if it rains? How many images are included? Can they reschedule? Answer the question before they have to ask it.

The offer — and only the offer that makes sense for this person. No cheesecake factory menu. By the time someone receives your booking proposal, they should already know which session type they want. The proposal confirms the decision, it doesn’t create a new one. If you regularly offer multiple session types and don’t know which one to send, that’s a signal you need to go back and look at your inquiry process.

One more thing: set an expiration date. I expire mine after 72 hours. It creates urgency, it protects your calendar from being held indefinitely, and it gives people a real deadline to say yes.

Send It Through the Workflow. Not Manually.

This is the one I say over and over because it keeps coming up in every audit I do.

If you send your proposal manually — going into the project and clicking send yourself, outside of the workflow — you lose the ability to automate follow-ups. Dubsado can only watch for “form not completed” and trigger a reminder email if the proposal was sent through the workflow in the first place. Send it manually and you’re back to chasing people yourself.

Send. The. Proposal. Through. The. Workflow.

One more thing while we’re here: the payment plan belongs on the workflow, not on the proposal. If the payment plan is on the proposal, you can’t trigger workflow actions based on the first payment being made. Move it to the workflow and you unlock the ability to automate everything that comes after they pay — including the onboarding sequence.

The Follow-Up Sequence

You sent the proposal. Now you wait.

This is where most booking workflows end, and it’s the most expensive gap in the process. People get busy. Life happens. Even someone who got on a call with you and told you they were ready to work with you can let a proposal sit for three days without meaning to. Your booking workflow needs to follow up — automatically, consistently, and without you having to remember to do it.

Minimum three follow-ups after making an offer. Here’s how I do it.

Follow-up 1 — Automated, 24 hours after the proposal is sent

“Just making sure you got this.” That’s the core of it. But this email also includes something worth reading — a client case study, a real transformation from someone I’ve worked with, a podcast episode that speaks directly to the thing they said they needed when they inquired.

The email does two things: it confirms the offer landed, and it reminds them why they wanted to work with you in the first place before they get buried in their inbox and forget.

One note on email tracking: Dubsado’s open rate data is not reliable. Gmail scans incoming emails for viruses, and that scan registers as an open in your CRM. I have watched my own test emails show “opened” before I’d even switched to my inbox tab. Don’t assume someone opened your proposal email and decided not to book. Assume they haven’t seen it until they’ve actually clicked the proposal itself.

Follow-up 2 — Manual, 24-48 hours after the first follow-up

Five minutes. That’s all this takes. I pull up an email template and customize the part that speaks to their specific situation — whatever they told me on the call or in their contact form. What’s the thing they said they were struggling with? What does their life or business look like on the other side of solving that problem? That’s what this email speaks to.

This one is manual because it should feel personal. And it does — because it is.

Follow-up 3 — The magic email

I can’t take credit for this one, but it’s consistently the email that gets the most responses.

The version I send says something like: I haven’t heard back from you, so maybe you’ve decided to go a different direction. I’m going to close out your inquiry so you don’t receive any additional follow-ups. If you’d like to work together in the future, please reach out for updated pricing and availability.

Most people don’t like to be seen as rude. When they get this email, one of two things happens: they finally complete the proposal because they realized it fell off their plate, or they send a note saying they’ve decided to go another direction. Either one is useful. Either one gives you closure so you can stop wondering.

I also add an opt-out line to the very first follow-up: “If you’ve decided not to move forward, just let me know and I’ll close this out.” Some people who’ve already made up their mind will use that opening to give you closure right away, which saves everyone time.

For a deeper look at how to write each of these emails, I covered all three in detail in this post on follow-up emails — including the 2025 update where every follow-up now includes a mini case study.

What the Booking Workflow Actually Contains

Here’s what the workflow looks like step by step inside Dubsado.

Step 1: Send the proposal Through the workflow. Always. The proposal includes the contract and invoice. The payment plan is on the workflow, not the proposal.

Step 2: Automated follow-up if the proposal isn’t completed Set the trigger to watch for “form not completed” and fire at 24 hours. The email resends the proposal link directly — not a vague “just checking in” with no action for them to take. Make it one click to get back to where they left off.

Step 3: The “oops, you missed a step” email This one is for the person who filled out the proposal and signed the contract but didn’t pay. It goes out the morning after the payment was due. “You’re not officially booked yet” — friendly, clear, and it works. This lives on the payment plan, not as a workflow action, which is why the payment plan needs to be on the workflow in the first place.

Step 4: The handoff to onboarding In most cases the booking confirmation lives in the onboarding workflow, not here. The reason is logistical: if you’re sending a client questionnaire immediately after booking, the booking confirmation and the questionnaire need to come from the same workflow so that the follow-up reminders to complete the questionnaire are in the same place. If the confirmation lives in the booking workflow and the questionnaire lives in onboarding, you lose the ability to automate reminders properly.

The exception is if you need to customize the onboarding based on what they booked — in that case, you can add a booking confirmation to the booking workflow as a bridge while you set up the right onboarding workflow. But for most photographers, payment received is the last step here.

The Mistakes I See Most Often

Sending the proposal manually. Kills automated follow-ups. Send it through the workflow.

No follow-ups at all. One proposal sent and then silence. If they haven’t booked in 24 hours, the follow-up sequence should already be running.

Payment plan on the proposal instead of the workflow. You can’t trigger off first payment made if the payment plan lives on the proposal. Move it.

Proposal follow-up reminders using “after all previous actions complete” with an approval instead of “form not completed.” This is one of the most common errors I see in booking workflows. The thinking makes sense — they don’t want reminders to fire if the client already booked, so they add an approval to stop it. But what they don’t realize is that the “form not completed” trigger already handles that. It watches the proposal and only fires if it hasn’t been completed. The moment the client books, the trigger condition is no longer met and the reminder won’t send. Using “all previous actions complete” with an approval means you have to manually approve every follow-up, which defeats the entire purpose of automating it.

Booking confirmation set to fire after “all previous actions complete.” If any step before it hasn’t been completed — a to-do task you forgot to check off, a form that wasn’t submitted — the confirmation never sends. Your client paid you and got nothing. Set the confirmation to trigger after invoice installment paid, not after all previous actions complete.

Inquiry and booking in one workflow. Already covered this, but worth repeating: you can’t swap session types mid-process, you can’t start booking manually, and when something breaks you can’t tell where. Keep them separate.

Too many options on the proposal. Decision fatigue kills conversions. If they have to choose between seven session types, they’re going to close the tab and think about it later. Keep it to the offer that makes sense for this person.

Ready to Build?

The five-minute booking process isn’t a fantasy. It’s what happens when the proposal is built well, the follow-ups are in place, and the system does the work instead of you.

If you want to see what your current booking workflow is actually doing — and where it’s quietly losing bookings — a Client Experience Audit is the fastest way to find out.

If you’re ready to build the whole thing from scratch: Systems in Session.

Not ready for either yet? Start with the Workflows and Automation Guide — it gives you the framework before you build anything.

Next up in the series: the onboarding workflow — what happens between deposit paid and session day.

FAQ

What is a Dubsado booking workflow? A Dubsado booking workflow is the automated sequence that handles everything from sending the proposal to receiving the deposit. It includes the proposal, contract, invoice, automated follow-ups for unbooked leads, and the payment reminder for anyone who signs but doesn’t pay. When it’s built correctly, a client can go from receiving the offer to officially booked in under five minutes — without any back and forth.

What should be in a Dubsado proposal? A strong header image, an about you section, your process laid out as a timeline, a FAQ section that addresses your most common objections, and the offer — kept simple. The proposal should also include the contract and invoice so everything happens in one place. The payment plan belongs on the workflow, not the proposal itself.

How many follow-up emails should I send after a proposal? At minimum, three. The first goes out automatically 24 hours after the proposal is sent. The second is sent manually 24-48 hours after that, customized to the person’s specific situation. The third is the magic email — it signals you’re closing the inquiry, which usually prompts either a booking or a clear no. Both outcomes are more useful than silence.

Should the payment plan go on the proposal or the workflow in Dubsado? The workflow. Always. If the payment plan is on the proposal, you can’t use “first payment made” as a workflow trigger — which means you can’t automate the “oops you missed a step” email or automatically start the onboarding workflow after they pay. Move the payment plan to the workflow and everything else gets easier.

How do I automate follow-ups for an unbooked proposal in Dubsado? Send the proposal through the workflow — not manually. Once it’s sent through the workflow, you can add a follow-up action with the trigger “after form is not completed” set to 24 hours. The follow-up email should resend the proposal link directly so they can complete it in one click. If you send the proposal manually, Dubsado has no way to watch for completion and the automated follow-up won’t work.

What triggers the onboarding workflow in Dubsado? In most cases, the first invoice installment being paid. Once payment is received, the onboarding workflow either starts automatically or you start it manually — depending on whether the onboarding is the same for everyone or needs to be customized based on what they booked. The booking confirmation typically lives in the onboarding workflow rather than the booking workflow, so the questionnaire and the confirmation can come from the same place.