It is Sunday evening and you are not designing. You are copying a client's address from an email into a contract, checking whether last week's deposit landed, and writing, for the fourth time this month, the same paragraph about what happens after the agreement is signed. None of this is why you became a designer, and all of it is the reason a studio of any size starts to feel heavier than the work deserves.
Dubsado is the tool many designers reach for at that point. It works best for an interior design business when you build a connected system around the client journey, not a pile of one-off automatic emails. The difference matters, and most of this article is about it.
We will cover which parts of a design business Dubsado handles well, three workflows worth building carefully, where the tool stops being useful, and how to start without rebuilding your whole studio in one weekend.
Can Dubsado automate an interior design business?
Partly, and the "partly" is the useful bit. An interior design project has two halves. The front half, from first enquiry to signed agreement and first payment, is repeatable. The same questions get asked, the same documents get sent, the same reminders get written. The back half, from concept to installation, is full of decisions, products, suppliers and surprises. Dubsado is built for the first half. It can support the second, but it was never designed to run it.
| Stage of a design project | How repeatable it is | Dubsado's role |
|---|---|---|
| Enquiry and qualification | High: same questions every time | Strong fit: forms, scheduler, automatic replies |
| Consultation and proposal | Medium: scope varies, structure does not | Good fit: proposal with contract and invoice attached |
| Agreement, deposit, onboarding | High | Strong fit: contract, invoice, questionnaire, portal |
| Concept and presentation | Medium: the work is custom, the logistics are not | Supporting: share files, request feedback, track status |
| Specification, ordering, procurement | Low: depends on products, suppliers and budget | Weak fit: use a design-specific tool or a manual process |
| Installation and handover | Low to medium | Supporting: tasks, reminders, closing communication |
| Wrap-up and referrals | High | Good fit: thank-you, feedback request, archive |
If you take one idea from this article, take that table. Automation earns its keep where the work repeats. Where each project is different, a person has to be involved, and the honest question is only how much preparation the system can do for that person.
Automation earns its keep where the work repeats.
Dubsado also publishes a page aimed at interior designers describing how it frames the product for the industry. It is worth reading as a statement of what Dubsado says it does, alongside the more cautious view here of where it stops.
What a Dubsado workflow really is
Dubsado calls its automation a workflow, and the name hides how mechanical it is. (In Dubsado 3.0 they are called flows; this article uses "workflow", the term most designers search for.) A workflow is a sequence of actions that starts when something happens, a form submitted or a contract signed for example, and then performs a series of steps in order. Those steps include sending an email, a form, a contract, a scheduler link or an invoice, creating a task, changing the project status, adding a tag, and waiting until a condition is met before carrying on.
Two properties of that model shape everything else. First, the sequence is a line, not a tree. Dubsado's help pages describe waiting steps that stack, so a flow can pause until a contract is signed and a payment is received, but they do not describe an if-this-then-that branch. Independent sources disagree about whether branching is possible, which is itself a reason to build as though it is not. Where you need two paths, such as full-service and e-design, the safer design is two workflows.
Second, a workflow can only act on what the system can see. It knows a form was returned or an invoice was paid. It does not know that the client sounded hesitant on the call. A good workflow design therefore puts a human decision at the points where judgement is needed, and Dubsado supports this: some actions can be set to wait for your manual approval before they go out.
Dubsado's own advice is to write out your process before building anything. That sounds like homework and it is the single most useful step. Software cannot fix a process you cannot describe.
Which workflows come first, and for whom
The order matters more than the number. A designer who builds ten half-tested workflows will have ten problems. A designer who builds two and tests them properly will have a studio that feels calmer within a few weeks. Where to begin depends on what is hurting.
| If your main pain is… | Build first | Why this first |
|---|---|---|
| Enquiries that go cold or get answered late | Enquiry-to-consultation workflow | The cheapest improvement: speed and consistency at the moment of highest intent |
| Chasing signatures and deposits | Proposal, contract and invoice workflow | Removes the most awkward conversations in the business |
| Clients who start projects unprepared | Onboarding workflow | Gathers what you need before the first working session |
| Feedback that drifts or never arrives | Presentation and feedback workflow | Gives approvals a date and a place to live |
| A finished project that just fades out | Wrap-up and referral workflow | Last, because it only matters once the earlier ones work |
The workflow blueprint
Here is the whole front-to-back picture in one place. It lists ten workflow ideas grouped into eight rows. Not every studio needs every row; the starter plan later shows what to skip.
| Workflow | Trigger | What Dubsado does | Where you step in |
|---|---|---|---|
| 1. Enquiry response | Lead capture form submitted | Creates the client and project, sends an acknowledgement, adds a tag | Read the enquiry; decide whether it is a fit |
| 2. Consultation booking | Qualified lead | Sends a scheduler link with buffers and daily limits, attaches a form | Decide who gets the link |
| 3. Proposal and agreement | Consultation held | Sends a proposal with contract and invoice attached | Write the scope and set the fee |
| 4. Deposit and onboarding | Contract signed and deposit paid | Opens the portal, sends the questionnaire, creates tasks | Review answers before the kickoff |
| 5. Questionnaire follow-up | Questionnaire sent | Reminder emails if not returned | Call the client if it stalls |
| 6. Presentation and feedback | Concept ready | Sends feedback form with a due date, creates a task for you | Present the concept; interpret feedback |
| 7. Milestone invoicing | Phase completed | Sends the next invoice, or runs a payment plan | Confirm the phase is truly complete |
| 8. Wrap-up and referral | Project complete | Sends thank-you and review request, archives the project | Choose whether to ask for a referral |
The two missing numbers are deliberate. Procurement and site visit logistics, which a designer might call workflows nine and ten, are covered under "Where Dubsado stops" because they do not belong inside Dubsado for most studios.
Three workflows worth building properly
1. From enquiry to qualified opportunity
This is the workflow that sets the tone. The goal is not to book every enquiry; it is to make sure the right people book and the wrong ones understand quickly why it is not a fit.
- A lead capture form on your website asks the questions that decide fit: location, project type, rooms, rough timing and a budget range if you are comfortable asking. Dubsado's lead capture creates the client and the project at the same moment, so nothing is retyped.
- An acknowledgement email goes out straight away. Keep it short and honest: you have received the enquiry, when they will hear from you, and what happens next. It should read as written by a person.
- A task is created for you, because someone has to decide. Set the workflow to wait here. This is the moment of judgement.
- You approve the next step. If it is a fit, the scheduler link goes out. If it is not, you send a polite decline, ideally with a suggestion of where else to look.
- The scheduler offers consultation times using buffers and daily limits so your calendar does not fill with back-to-back calls. It can carry a form to collect final details, and reminders go by email only, not text message.
One trap is worth knowing about. Dubsado's help pages suggest attaching a lead capture form to a public scheduler so people enter their details before booking, and a project is created as soon as that form is submitted, even if the person never books. The same pages note that a workflow started from a public scheduler cannot use appointment-based triggers, because the appointment already exists before the workflow starts. Those pages were written for Dubsado 2.0, so test the behaviour in the version you use rather than relying on them.
2. From signed agreement to a client who is ready
Most onboarding problems are really information problems. You start the first working session and discover you do not know the budget, the household, the deadlines or what the client actually dislikes. The onboarding workflow exists to make sure that conversation happens on paper first.
- Proposal first. Dubsado lets you connect a contract and invoice to a proposal, so the client sees the scope, the agreement and the deposit in one place and one decision.
- Wait for the signature and the deposit. Dubsado's waiting steps stack, so the workflow can hold until both are done before anything else fires. This replaces the manual checking.
- Open the client portal. Note that activating the portal sends no email by itself, so pair it with an email that tells the client where to look.
- Send the design questionnaire. Ask about how they live, not only what they like: who uses each room, what annoys them now, what they have already bought. Good answers here save hours later and are the content of the kickoff conversation.
- Create tasks for you: review the answers, prepare the kickoff, request the floor plans. Tasks created by a workflow have no due date, so name them clearly and use your calendar for timing. Deleting a task a workflow created can stop the workflow advancing, so complete it rather than delete it.
3. From presentation to decision
Design feedback is where projects lose weeks. Clients say they will look at it over the weekend and then it is three weeks later. A workflow cannot make a client decisive, but it can give the decision a date, a form and a reminder.
- After you present, trigger a feedback form that asks specific questions: what works, what does not, what is missing. Open-ended "thoughts?" produces open-ended replies.
- Set a reminder sequence that is polite and spaced, with the final reminder stating what happens if you do not hear back, such as the schedule moving.
- Create a task for you when the form comes back. Interpreting feedback is design work, not admin.
- Update the project status so your pipeline shows where each project really is.
What to automate and what to keep human
The most common mistake with workflow tools is automating the wrong moment, and it is easy to do because the tool does not know the difference. This table is the test we would use.
| Let the system prepare it | A person decides it |
|---|---|
| Sending forms, contracts, invoices and reminders | Whether to take the project at all |
| Collecting questionnaire answers into one place | What the answers mean for the design |
| Reminding the client about a pending approval | Whether a delayed client needs a phone call instead |
| Creating tasks and updating status | Pricing exceptions, scope changes and refunds |
| Thanking the client at the end | Whether to ask for a referral, and how |
A simple rule follows. If a mistake would be embarrassing, expensive or hard to retract, put a manual approval in front of it. Dubsado supports this on some actions, and using it is a sign of a mature system, not a slow one.
Messages that go to clients also carry legal weight in some places. If your studio emails in bulk or sends text messages, rules such as CAN-SPAM in the United States and consent requirements for texts apply. For ordinary transactional project emails this is rarely an issue, but it is worth knowing before you add marketing sequences.
Where Dubsado stops
Interior design involves a layer of work Dubsado was not built for: specifying products, requesting quotes, raising purchase orders, tracking deliveries and reconciling what was ordered with what arrived. Platforms built for the trade, such as Studio Designer, Houzz Pro, Programa and Ivy, are organised around those jobs. Their own marketing is the main source of comparison material, so treat it as a description of what they say they do, not as a verdict.
This gives most studios three honest options. Keep procurement in a design-specific platform and use Dubsado only for the client journey. Use Dubsado for everything and manage procurement in spreadsheets, which works for small studios with simple projects and gets uncomfortable as volume grows. Or choose a design-specific platform for everything and accept that its client experience may be less tailored. There is no universal answer; it depends on how much procurement your projects involve.
Payments are another boundary worth stating. Dubsado supports Dubsado Payments, Square or PayPal as processors, but Dubsado Payments and Square cannot both be connected, and PayPal does not work with autopay. Dubsado itself charges no platform fee on payments, but the processor does. Dubsado's own guide to connecting a processor sets this out, and payment plans are worth understanding if you invoice by milestone.
E-design and full-service run differently
A full-service project has many phases, suppliers and site visits. An e-design project is shorter, more fixed in scope and often sold at a set price. They deserve different workflows, mainly because the second can be almost fully systematised and the first cannot.
| Full-service | E-design | |
|---|---|---|
| Proposal | Scope varies; fee structure can be complex | Packaged: fixed scope and price |
| Onboarding | Long questionnaire, site details, access arrangements | Questionnaire plus photos, measurements and floor plans |
| Payments | Retainer then milestones | Often one payment, or two |
| Delivery | Presentations, revisions, procurement, installation | Defined deliverables and revision rounds |
| Automation potential | Front half and wrap-up | Nearly the whole journey |
| Suggested build | One workflow per phase, with manual approvals | One workflow end to end |
If you do both, build them as separate workflows from the start. Trying to make one flow handle both is where a branch would be needed, and as discussed, that is the part Dubsado does not clearly offer.
A hypothetical before and after
This is an illustration, not a case study, and it describes no real client. Picture a two-person studio taking on a handful of residential projects at a time. Enquiries arrive by email, Instagram and a contact form. One partner replies when she can. Contracts are Word documents sent as PDFs. Deposits are chased by hand. Onboarding information is gathered over several emails.
After a careful build, the same studio has one enquiry form that feeds one pipeline. Every enquiry gets an acknowledgement. A task asks the partner to qualify the lead. A consultation link goes out on approval. The proposal arrives with its contract and deposit invoice attached. Once both are complete, a portal opens and a questionnaire arrives. The partner reviews the answers before the kickoff, not during it.
Nothing in that picture is clever. The designers still design, still decide and still talk to clients. What changed is that the repeatable parts no longer depend on someone remembering them. That is the realistic ambition, and it needs no promises about hours saved to justify it.
Mistakes that quietly undo the system
| Mistake | What goes wrong | Better approach |
|---|---|---|
| Automating before writing out the process | The workflow encodes confusion | Write the process in plain language first |
| Skipping a manual approval before sending contracts or invoices | A wrong figure reaches the client | Use manual approval on high-stakes actions |
| Importing client lists casually | CSV import duplicates existing clients | Clean the list first and import once |
| Skipping testing | Errors surface in front of real clients | Test as owner and as client, in a private window, with a manual payment |
| One workflow for every project type | Branching is needed, and may not exist | Separate workflows for separate project types |
| Deleting workflow-created tasks | The flow may stop advancing | Complete tasks instead |
| Forgetting the portal email | Clients never find the portal | Pair portal activation with an email |
| Cold, robotic wording | Premium clients feel processed | Write every template as if to one person |
Dubsado's own setup checklist recommends testing as both owner and client, in a private browser window, with a manual payment. It is the least glamorous advice in the documentation and the most valuable.
A starter plan
You do not need all of this at once. This order puts value first and risk last.
- Write down your client journey, from first message to handover. One page is enough.
- Decide the stages you will track in your pipeline and name them in your own words.
- Build the templates you reuse most: acknowledgement, proposal, contract, questionnaire.
- Connect payments and confirm your processor works for your country and your clients.
- Build the enquiry workflow and nothing else. Test it as described above.
- Run it on real enquiries for a few weeks and note what you edit by hand. Those edits are your next improvements.
- Add proposal and onboarding, then presentation and feedback.
- Leave wrap-up and referrals until last. Once the rest is stable, they are easy.
One practical point: Dubsado's pricing page lists automated workflows and scheduling on its Premier plan, not on Starter. Its free trial gives full access to Premier, so you can build and test before paying. Confirm the current plans and prices on the Dubsado site before you commit. Dubsado's newer version is described in its announcement of Dubsado 3.0, and its status is worth checking if you are starting fresh.
Getting help with setup
Most designers can build the enquiry workflow themselves. The harder part is the design of the whole system, which stages exist, what triggers what, where the manual approvals sit, and how the templates sound. That is where outside help earns its place, and it is worth knowing what you are buying. A what a Dubsado consultant actually does overview sets out the work, and the choice between tools is covered in Dubsado vs HoneyBook if you are not yet committed.
Dubsado maintains a directory of Certified Dubsado Specialists. These are independent businesses that set their own prices, so compare more than one. If you want to see what a structured build looks like, Dubsado implementation describes how Sage Kite approaches it. Whoever you choose, ask them to start by writing out your process, not by opening the software.
Quick answers
Is Dubsado good for interior designers?
For the client-facing journey, yes, particularly enquiry, proposal, contract, payment and onboarding. For procurement and specification, a design-specific platform is usually a better fit.
Can Dubsado handle purchase orders?
Not as a core function. Studios that need purchase orders generally use a design-specific platform alongside or instead of it.
Can I automate everything?
You can, but you should not. Keep a person at every decision that is expensive or hard to retract.
Is it worth it for a solo designer?
Often, because the repeatable half of the business is the same size whether there is one person or five. The value depends on how many projects you run, so start small and judge by your own results.
Where this leaves you
The strongest interior design businesses are not the most automated. They are the ones where the repeatable work happens without effort and the human work gets more time. Dubsado can do a great deal for the first of those. It cannot be the second, and the best use of it is to protect your attention for the work only you can do.
Sources and reading
Dubsado capabilities were checked against Dubsado's own pages in October 2026. Several of Dubsado's help articles are still written for version 2.0; they are marked below, and behaviour may differ in 3.0.
- Dubsado: flow actions (3.0)
- Dubsado: pricing and plans
- Dubsado: introducing Dubsado 3.0
- Dubsado: the setup checklist
- Dubsado: writing out your process (2.0)
- Dubsado: connect a contract and invoice to a proposal (2.0)
- Dubsado: start a workflow from a public scheduler (2.0)
- Dubsado: scheduler intervals and buffers (2.0)
- Dubsado: connect a payment processor (2.0)
- Dubsado: payment plans (2.0)
- Dubsado: bulk import a client list (2.0)
- Dubsado: Certified Dubsado Specialists
- Dubsado: Dubsado for interior designers
