You bought Dubsado. You built a lead form, a contract template and an invoice. Each one works. And then you stall, because the next questions aren't really about Dubsado at all.
What should happen when a lead goes quiet? Does the questionnaire go out before the call or after the deposit? What if someone signs but doesn't pay? Who decides?
That gap is where a Dubsado setup consultant earns their fee, and it's why the job is mostly not clicking. A good one spends a surprising amount of time asking how your business actually runs, then translates the answers into forms, documents, scheduling, payments and automation that work together. The software is the easy part. The decisions are the work.
This guide walks through what that looks like: what "Dubsado setup services" covers (it varies a lot), what a consultant does at each stage, what you still have to bring yourself, what it tends to cost and how long it takes, how to tell whether a consultant is any good, and when doing it yourself is perfectly sensible.
What do "Dubsado setup services" actually include?
There's no standard. One person's "Dubsado setup" is a full build of every client journey in your business. Another's is a two-hour strategy call and a template. A third is an audit of what you've already built. So before comparing prices, find out which kind of service is being offered.
| Kind of service | What it usually means |
|---|---|
| Done-for-you setup | The consultant maps your process and builds it: account settings, forms, templates, workflows, scheduler, payment plans, then training. Often capped by the number of services or workflows included. |
| Done-with-you setup | The consultant provides the strategy and structure, and you do more of the hands-on building, with guidance. |
| Audit or review | You already have an account. The consultant reviews it, finds what's broken or confusing, and gives you a list of fixes (and sometimes does them). |
| Add-ons | Extra workflows, custom-designed forms, copywriting for emails, connections to other tools. Frequently priced separately. |
| Migration help | Moving clients and records in from another system. Scope varies widely, and often means contacts plus rebuilding the rest. |
| Training or ongoing support | Teaching you to run it, or being on call after launch. |
One more thing worth knowing. Dubsado runs a Certified Specialist program, and the specialists are independent small-business owners rather than Dubsado employees. Dubsado says each sets their own prices and that it doesn't guarantee service outcomes (Dubsado's page on certified specialists). Certification is useful evidence that someone knows the platform. It isn't a promise they'll understand your business.
Software capability is one thing. Consultant work is another.
Here's the distinction the rest of this article depends on. Dubsado, the software, provides things like workflows. A workflow is a set of instructions that tells Dubsado what to do after a specific event: after a new enquiry, send an acknowledgement, wait two days, then send a follow-up. (Dubsado's current version calls them Flows.) It matters because the software will happily run whatever you build, whether or not it matches how you really handle leads.
The consultant's job is the part Dubsado can't do. Which event starts the workflow? What should be said, and when? What if the client doesn't respond? When should it stop? Which kinds of client should enter it at all? And what should stay manual because a person should be the one to say it? The platform gives you the building blocks. Deciding how to use them is the consulting.
The software is the easy part. The decisions are the work.
What does a Dubsado consultant actually do?
In short: they translate the way your business already works into a system that runs it. The shape of the work looks like this:
Notice how little of that is software.
Notice how little of that is software. Notice, too, that the thing at the start, your process, is the thing most people haven't written down. Let's go through it step by step.
1. They start with questions, not settings
Setup usually begins before anyone opens a workflow builder. Dubsado's own help centre says a detailed process outline is the foundation for any good workflow, and it suggests questions to answer first (writing out your process). What's the first thing that happens when a lead arrives? What gets them booked? When do you consider them a client? What happens next, when does the work end, and do you follow up afterwards?
These sound obvious. They usually aren't. Many owners discover mid-conversation that they handle a discovery call differently depending on the client, or that "booked" means a signed contract for one service and a paid deposit for another. A system can only follow rules someone has defined, so those definitions have to come first.
2. They draw the journey before they build any of it
A client journey is the route someone takes from first contact to the end of the work, and then perhaps beyond. For one business it might be enquiry, consultation, proposal, contract, deposit, onboarding, project, delivery, follow-up. For another it's shorter. A photographer's journey and a consultant's aren't the same, and a consultant who hands you a standard template without asking is skipping the step that matters.
In Dubsado, this journey becomes project statuses, which show where a client currently is (say, Consultation Booked, Proposal Sent, Deposit Paid), and tags, which show what type of client or project it is. Dubsado's checklist describes exactly that split (setup checklist). Getting those right early makes everything after it easier to read.
3. They set the foundations
Some of the work is plain configuration, and it's still worth doing deliberately. Dubsado's checklist lists branding, international settings, the payment processor, email connection, calendar connection and optionally a custom domain, then your services as packages, plus bookkeeping categories. None of it is difficult. But a wrong currency setting, an email that sends from the wrong address, or a package that doesn't match your pricing will surface later, in front of a client.
4. They don't "just add forms"
Dubsado has five form types: lead captures, questionnaires, proposals, contracts and sub-agreements (Dubsado's form guide). Building them is the easy bit. The thinking is in deciding what to ask, and when.
A lead capture is the front door: when someone fills it in, Dubsado creates a project with their details. A consultant has to decide what that first form should collect. Too little and you chase information later. Too much and people give up before you've spoken. The same applies to every later form: which questions are required, which are optional, and why do you need the answer at all?
Proposals deserve a separate mention. In Dubsado a proposal can have a contract and an invoice attached, so a client can choose a package, sign and pay in one flow (connecting a contract and invoice to a proposal). Whether that suits you depends on your business. If every project needs a conversation first, a one-click booking might be the wrong design. That's a commercial decision, not a software one.
5. They design the automation, then build it
These are two different jobs, and a lot of confusion comes from mixing them up. Automation design is deciding what should happen, when, what starts it, what stops it and what stays manual. Automation building is entering those rules into Dubsado. Building is skilled but mechanical. Design is where the judgment lives.
In practice, a Dubsado flow is a series of steps, and each step pairs one action with one trigger: the action is what Dubsado does, and the trigger is when (Dubsado's flow actions reference). Dubsado documents 15 actions, including sending an email, form, contract, scheduler or invoice, creating a task, changing a project's status, and activating the client portal. Timing can be relative ("two days after the contract is signed") or tied to a fixed date. Events such as a form being completed, a contract being signed or an invoice being paid can start the clock (client progress triggers).
A few details show why design matters. A Hold Actions Until step can make a flow wait for a condition, and two of them in a row mean both conditions must be met. Dubsado's own example holds a project until the client has signed the contract and made their first payment, and only then moves it into production. Several email, form and invoice actions can also require manual approval, so a flow pauses until you've reviewed the message. That's a design choice about what you want a person to look at.
Two holds in a row mean both conditions must be met.
There's also a limit worth knowing about. Dubsado's documented actions don't include an if/else branching step. Independent writers disagree on whether conditional logic exists in flows today. A good consultant will tell you plainly what the platform can and can't do in your case, then design around it, instead of promising something they haven't checked. (Automated flows are also on the Premier plan, according to independent reviews, so check Dubsado's pricing page for your plan.)
6. Scheduling and payments are where the details bite
Dubsado doesn't process payments itself. You connect Dubsado Payments (powered by Stripe), Square or PayPal. You can connect Dubsado Payments or Square but not both, and PayPal doesn't work with autopay (Dubsado's payment processor guide). Dubsado says it doesn't add its own payment fees, but your processor's fees still apply. A consultant should explain that choice before building a payment plan around it.
Payment plans are templates that define instalments, due dates and reminders, and they can be tied to what happens in a flow. A deposit due on signing, a balance due 30 days before the event and a late-payment reminder are all design questions: when does the client owe what, and what should they hear when they're late? Scheduling works the same way. A scheduler template holds your availability for each type of appointment, and a flow can send the booking link and then act on whether the appointment happens. Consultants configure the mechanics. You decide the rules: how much notice, how long a call lasts, what you do about no-shows.
7. They build what happens after "yes"
This is the stage clients feel most. Someone says yes, signs and pays. What now? A well-designed onboarding sends a welcome, gives access to the client portal, delivers the questionnaire and says clearly what happens next.
There's a nice detail in Dubsado's documentation. The action that activates the client portal doesn't send anything by itself, and the portal password is set manually, so a consultant has to add a separate email that tells the client how to log in. It's a tiny thing, and it's exactly the kind of gap that makes a new client feel lost on day one. The goal isn't to replace personal communication. It's to make sure the routine messages never get forgotten, so your own attention can go to the parts that need you.
8. They test like a client, not like the person who built it
Building the system isn't the last step. Dubsado's own checklist says to walk through the whole process manually first, as both the business owner and the client, using a private browser window so Dubsado doesn't recognise you as the owner, and to apply a payment manually instead of really paying. Only then do you automate, and then test the workflow on a sample project. It also says, in so many words, that the importance of testing workflows can't be overstated (setup checklist).
Here's why a flow that "fires" isn't proof it works. Dubsado's documentation warns that stacking several actions that all trigger "immediately after the previous one" sends them all at once, so a client could receive a booking invite, a proposal and a questionnaire in the same minute (flow triggers). Every action ran. The client experience is still wrong. Deleting a task a flow created doesn't move the flow on either, so a later email can silently never send (flow actions). Neither shows up unless someone tests it as a client would.
Neither shows up unless someone tests it as a client would.
So a competent consultant tests the awkward cases too. What if the client submits the form twice? Pays only part of the deposit? Never signs? Replies in the middle of a sequence? Books a call and then cancels it? A list of "what happens if" questions is often more valuable than the build itself.
9. They leave you able to run it
A system only the builder understands isn't finished. Good handoff usually means documentation of how it works, often a map of your workflows, a walkthrough (live or recorded) and some support while you start using it with real clients. Public packages commonly include recorded training and a short support window, though the length varies. Ask what you'll actually have in your hands at the end.
What do you still have to bring?
A consultant can't invent your business. They can only translate it. That means some of the work is yours, and it's worth knowing before you start:
| What the consultant does | What you provide | Why it can't be swapped |
|---|---|---|
| Configures Dubsado and builds forms and templates | Your services, packages and pricing | They can't decide what you sell or for how much. |
| Designs workflow logic and builds it | Approval of the logic, and the exceptions you handle | Only you know where clients really get stuck. |
| Builds contract templates in the system | Your contract terms, reviewed by a lawyer if needed | The legal wording is yours. They configure how it's delivered and signed. |
| Formats and schedules emails | The words, or approval of drafts, in your voice | Some offer copywriting at extra cost. |
| Tests the system | Real-world scenarios and edge cases from your history | You've seen the strange cases they haven't. |
| Documents and trains | Time to learn it and keep it current | It's your system once they leave. |
What is usually included, and what usually isn't?
Based on how public packages describe themselves, here's a realistic picture. Don't assume any single consultant provides all of it.
| Often included | What it means | Often not included |
|---|---|---|
| Strategy or process-mapping session | Working out your journey before building | Your Dubsado subscription |
| Account setup and branding | Settings, domain, portal look | Copywriting for every email and form |
| Forms and templates | Lead capture, questionnaires, proposals, contracts, emails | Legal review of contracts |
| A set number of workflows | Frequently capped, such as "up to three" | Extra workflows beyond the cap |
| Scheduler, packages, payment plans | Configured to your services | Custom-coded form design (sometimes extra) |
| Testing | Before launch | Integrations with other tools (often priced per connection) |
| Training and documentation | Recorded walkthrough or call | Ongoing support beyond a short window |
| Short post-launch support | Typically weeks, not months | Business strategy, lead generation, or any promised result |
That last point is worth underlining. A consultant can't guarantee more leads, more revenue or better retention. They can make your process clearer and more consistent. Whether that helps your business depends on whether the process was a good one to begin with.
Automation doesn't fix a bad process. It repeats it.
Picture a manual process. A lead enquires. You send three separate emails, update a spreadsheet, schedule the call by hand, and then send a duplicate follow-up because you forgot you'd already sent one. A consultant who simply automates every step has built a faster version of the same mess. The better move is to ask a very boring question first: why do those steps exist?
Maybe the three emails collapse into one. Maybe the spreadsheet existed only because nothing else tracked lead status, which Dubsado's project statuses now do. Maybe the follow-up was a fix for the missed one. Asking why is where the real value comes from. It's also why a consultant who starts building before asking questions deserves some suspicion.
Asking why is where the real value comes from.
Common setup mistakes, and what to check
| Problem | Why it happens | What to check |
|---|---|---|
| Workflows built before the process is clear | Building feels like progress. | Can you describe every step of the journey on one page? |
| Too much automation | Every step looks automatable. | Which messages should come from you personally? Use manual approval where you want to look first. |
| Duplicate or overlapping workflows | A new workflow per service, copied and tweaked. | Do two flows ever send to the same client at once? |
| Forms that ask for too much | Everything seemed useful at the time. | For each question: what will we do with this answer? |
| No exceptions planned | Only the happy path was designed. | What happens when someone doesn't reply, pay or sign? |
| Old inefficiencies recreated | The existing process was never questioned. | Why does each step exist? |
| No testing, or testing as the owner | It looks fine from the builder's side. | Has someone gone through it in a private window as a client? |
| Nothing documented | The builder is the only one who knows. | Could you explain this to a new team member? |
| Messy imported data | Contacts were imported as-is. | Dubsado's import is a CSV (not .xlsx) and will duplicate existing clients, so clean the file first. |
Can you set up Dubsado yourself?
Often, yes. Dubsado has its own setup checklist, a library of help articles, and a free trial. New trials include a 21-day trial period, according to Dubsado's 3.0 announcement (Dubsado 3.0 page). Plenty of businesses build their own, and they learn how the system works in the process, which has real value.
| DIY may be enough when… | Professional help may make sense when… |
|---|---|
| You offer one or a few simple services | You have several services with different journeys |
| Your client journey is short and straightforward | The journey has many steps, exceptions or handoffs |
| You're comfortable learning software and have the time | Your time is the scarcest thing you have |
| You want limited automation | You want a lot of automation, or have tried and it isn't working |
| You're starting fresh | You're migrating from another system or have a tangled existing account |
| It's just you | Several team members will use it |
Neither column is better. A common middle path is to build the basics yourself and pay for a one-off audit later, or to take a strategy session to design the journey and then build it yourself. If your setup is more involved, with process mapping, workflow design, migration and testing, that's the point where professional Dubsado implementation support tends to earn its place.
How much does Dubsado setup cost, and how long does it take?
Honestly, it varies too much to give you an average, and any page that offers one is guessing. Here's what public listings show, with limits. They're in dollars (USD or CAD as listed), from different dates, and cover very different scopes, so don't treat them as a market rate.
| Type of service | What public pages list (examples, not averages) |
|---|---|
| Audit or review | Roughly US$200 to $350 for a call or a written review. |
| Done-with-you | One specialist lists $1,297. |
| Done-for-you full setup | Listed starting points range from about US$2,500 to $4,000, with at least one starting at CAD 5,000 for up to four services. |
| Add-ons | Integrations listed from about $300 to $500 each, and copywriting often priced separately. |
| Ongoing management | One provider lists packages from $499. |
Price tends to rise with the number of services and workflows, how much copywriting you want done, whether there's migration, custom form design and how many integrations you need. Your Dubsado subscription is a separate cost, and some consultants state that explicitly. On timing, listed timelines range from under a week to about four weeks, and many don't state one. It depends on how quickly you answer questions and approve drafts as much as on the build.
How do you tell whether a Dubsado consultant is any good?
You can learn a lot from the questions a consultant asks you. A good one wants to know:
- What do you sell, and how do leads reach you today?
- What happens after someone enquires? After they become a client?
- Where do leads get stuck, and where do clients get confused?
- What's manual and repetitive right now?
- What should happen automatically, and what should stay with you?
- What happens when a client doesn't respond?
And you can ask them, in turn:
- Can you explain what you'll build, in plain English, before you build it?
- What's included, what isn't, and what do extras cost?
- How do you test, and who tests?
- What documentation and training will I get, and what support after launch?
- Which version of Dubsado will you build in? Dubsado said it would retire the older 2.0 version during 2026, so check where your account stands.
- What can't this setup do for me?
Be wary of anyone who promises more leads, more revenue or that everything will be "fully automated". Those aren't things a setup controls.
What a complete setup might look like (a hypothetical)
Imagine a solo brand consultant. Here's one way her journey could be set up, and where the decisions sit. It's an illustration, not a template.
| Stage | What gets configured | Decision only she can make |
|---|---|---|
| Enquiry | Lead capture form on her website, an acknowledgement email, project created with status "New enquiry" | What to ask up front, and which enquiries aren't a fit |
| Consultation | Scheduler template, reminder emails, calendar sync | Call length, notice period, what happens on no-shows |
| Proposal | Packages, a proposal form with contract and invoice attached | Whether to allow instant booking or review each case |
| Contract and payment | Contract template, payment plan with a deposit and instalments | Her terms and payment schedule |
| Onboarding | Welcome email, portal access, intake questionnaire sent once contract and deposit are in | What she needs to know before starting |
| Project and finish | Status updates, a wrap-up email, a follow-up check-in | How she closes work and keeps in touch |
| Handoff | Workflow map, a recorded walkthrough, a short support window | Who maintains it, and how often it's reviewed |
Two shorter variations help show how much depends on the business. A wedding professional needs payment schedules tied to a date months away, plus planning communication over a long engagement, so the design is about timing and reminders over time. An existing Dubsado user may not need a build at all. They have duplicate workflows, confusing emails and manual workarounds. A consultant would audit the account first, map what's actually happening, remove what's redundant and rebuild only what needs it. A photographer with a simple booking journey might need little more than a well-built lead form, proposal, contract and deposit.
When shouldn't Dubsado own everything?
A consultant should design the system around your business, not push every function into Dubsado. It handles client management, forms, contracts, invoicing, scheduling and workflows. But other things usually live elsewhere. Card payments run through Stripe, Square or PayPal. Accounting can connect to QuickBooks or Xero, which Dubsado's changelogs describe. Project delivery often sits in a task tool, and Dubsado connects to tools like ClickUp, Asana and Harvest through Zapier, which needs a Zapier account. Email marketing, your website and file storage also tend to stay separate.
A consultant shouldn't push every function into Dubsado.
If you're choosing between Dubsado and another platform in the first place, our Dubsado vs HoneyBook comparison covers the differences. This article assumes you've already decided.
So where does that leave you?
Back at the stall from the start: you've got Dubsado, and you don't quite know what should happen next. That feeling is the sign that the missing piece is a decision, not a setting. A consultant's real contribution is helping you make those decisions in the right order, then building them so they hold up when a real client does something unexpected.
If your business is simple, you can do much of that yourself. If it's tangled, or you'd rather spend your time with clients, hire help, and judge them by the questions they ask. Either way, write the process down first. It's the one step no software, and no consultant, can skip.
Questions people ask about Dubsado setup
What does a Dubsado consultant do?
They turn your existing client process into a working Dubsado system. That means mapping your journey, configuring the account, building forms, contracts and templates, designing and building workflows, setting up scheduling and payments, testing, and handing the system over with documentation and training.
What is included in Dubsado setup services?
It varies by consultant. Common inclusions are a strategy session, account setup, forms and templates, a limited number of workflows, a scheduler, payment plans, testing, training and short post-launch support. Copywriting, integrations and extra workflows are often priced separately.
Do I need a Dubsado consultant?
Not always. A simple business with a short client journey can often set Dubsado up itself. Help is more useful with several services, many workflows, migration or an account that already isn't working.
How long does Dubsado setup take?
There's no universal answer. Listed timelines run from under a week to around four weeks, and they depend on the number of services and workflows, any migration, copywriting, integrations, testing and how quickly you give feedback.
How much does Dubsado setup cost?
Public listings range from a few hundred dollars for an audit to several thousand for a full build, in mixed currencies and scopes. We don't think a reliable average exists, so compare what's included, not just the price.
Can I set up Dubsado myself?
Yes. Dubsado provides a setup checklist, help articles and a trial. Many people do, particularly when their process is simple.
What does a Dubsado consultant need from me?
Your services, packages and pricing, contract terms, brand assets, email wording or approval of drafts, scheduling rules, and a clear description of how you currently work, including exceptions.
What should a Dubsado consultant deliver?
A working, tested system, plus documentation and training so you can run it. Agree in writing what's included, what isn't, and what support follows launch.
Sources and reading
Dubsado capabilities were checked against Dubsado's own documentation. Pricing and package examples come from public consultant pages and are listed in the research notes below, not here, so no individual provider is promoted.
- Dubsado: the setup checklist
- Dubsado: writing out your process
- Dubsado: form types
- Dubsado: flow actions and flow triggers
- Dubsado: client progress triggers
- Dubsado: payment processors
- Dubsado: migrating existing clients and bulk import
- Dubsado: partner with a certified specialist
- Dubsado 3.0 announcement and Dubsado news and changelogs
