Most service business owners who open Dubsado for the first time already have pieces built. A contract is saved. A few packages exist. The workflows tab is empty, because building a workflow means making every decision about the client journey at once, on a blank screen. A well-structured Dubsado proposal template takes most of those decisions off that screen. It asks the client to choose a package, sign the contract, and pay, all from one link, so the workflow that follows has far less to do.
This post walks through what a structured proposal includes, in the order the client sees it, and how it hands the project to the workflow once the client is done.
Why the proposal comes before the workflow
In Dubsado, a proposal can include a contract and an invoice. The client selects their packages, signs the contract after submitting the proposal, and then reaches the invoice. Dubsado builds that invoice from the packages the client picked.
That sequence replaces three separate steps you would otherwise schedule by hand or build into a workflow: sending a quote, sending a contract, and creating an invoice. When the proposal is set up correctly, the workflow only has to cover what happens after the client books. That is a much smaller set of decisions, and a smaller set is easier to finish.
What a structured Dubsado proposal template includes
Packages built as templates first
Dubsado requires at least one package template before a proposal can show packages, and packages are created under Invoicing, then Packages. Build them there before you open the proposal builder. Each package should have a name a client would recognize, a price, and a description that states what is included.
Editing a package from inside a proposal does not change the original package template. If you fix a price inside one proposal, the template still has the old price for every proposal after it. Keep your changes in the package templates.
A clear selection rule
The proposal settings include a toggle called “Multiple packages can be selected.” It is set to Yes by default. Set it to No and the client can choose only one package.
This toggle applies to the whole proposal, so decide what the client is choosing before you lay out the page:
- If every client picks exactly one package, set the toggle to No.
- If clients pick a main package and then add extras, leave it on Yes, and label each section clearly so the client knows to choose one main package and any add-ons they want.
- If one item is required on every booking, mark that package as pre-selected and disable its selection button, which is how Dubsado lets you require a specific package.
One conflict to avoid: if the toggle is set to No and more than one package is pre-selected, the client gets an error when they submit.
Scope in plain language
Package descriptions are where you state scope. A client reading the proposal should be able to tell what each package covers and what costs extra without asking you. If a question comes up on most calls, answer it in the description or in a short FAQ section further down the page.
One contract, attached
Turn on “Include contract” in the proposal settings and select your contract template. Each proposal supports one contract, and the contract cannot change based on the package the client picks.
That limit shapes how you write the contract. Write one contract that covers every package on the proposal, and use invoice smart fields in the contract to pull in the packages the client actually selected. The contract then reflects their booking without you maintaining a separate contract per package.
The invoice and the payment plan
Dubsado always generates an invoice from the client’s package selections when a proposal is submitted. The “Include invoice” toggle only controls whether the client sees that invoice as part of the proposal. Paying from the proposal requires a connected payment processor.
Decide where the payment plan goes. You can set one on the proposal or on the workflow that sends it, never both. Dubsado’s help center notes that a payment plan on both causes a conflict and the workflow errors, even when the two plans are identical. If you plan to send the proposal from a workflow, leave the proposal’s payment plan field blank and set the plan in the workflow.
How the proposal hands off to the workflow
Once the contract and invoice are attached to the proposal, the workflow becomes a short list of steps tied to what the client has finished. Dubsado’s newer help articles call these flows. The triggers that matter here are:
- After a form is completed. This trigger works with proposals, so a workflow step can wait until the client submits theirs.
- After the contract is signed by the client. This watches only the client’s signature, so your countersignature does not affect it.
- After a primary invoice installment is paid. This is the trigger for a deposit or retainer, and the workflow needs a payment plan attached to use it.
- After the primary invoice is paid in full. This fires once the balance reaches zero.
To send a proposal with a contract or invoice attached from a workflow, use the Send Form action. Dubsado’s documentation specifically warns against Send Contract or Send Primary Invoice for this, and notes that adding a Create Invoice action alongside the proposal creates a duplicate invoice.
If the next step should wait for both a signed contract and a paid deposit, stack two Hold Actions Until steps, one for each. Chained holds work as “all of the above,” so the workflow continues only when both are done.
If you have not mapped what happens after booking yet, start with how to map a Dubsado workflow before you build it. The proposal is the first step on that map.
A worked example: flexible packages
Consider a wedding venue that sells a venue-only package and an all-inclusive package, with add-ons such as extended hours or a rehearsal slot. A structured proposal for that venue settles five things:
- Packages: two main packages and a package template for each add-on, all built under Invoicing.
- Selection rule: multiple selection stays on, because clients choose add-ons. The page shows the two main packages side by side in one section, labeled “Choose one,” and the add-ons in a second section below.
- Contract: one contract that covers both main packages, with invoice smart fields listing what the couple chose.
- Payment plan: set on the workflow, with the proposal’s payment plan field left blank.
- Handoff: the workflow sends the proposal with Send Form, holds until the contract is signed and the deposit is paid, then starts the planning questionnaire.
The proposal settles what the couple bought and what they agreed to, so the workflow only has to act on it. If your offers change by service, customizing Dubsado templates by service covers how to keep one structure across several proposals.
What if you only sell one package?
If every client buys the same thing, there is nothing for them to choose, and it can look like you can skip the proposal. You still use a proposal, contract and invoice, for two reasons: it is the best way to move a client through booking, and it keeps your books clean.
Make a package for what the client is purchasing and mark it pre-selected. Remove the select button from the proposal by deleting it, then structure the rest of the page more like a welcome: what happens next, what you need from them, and how to reach you.
The invoice only shows as open once the client accepts the proposal, and the client still reviews, signs and pays from one screen.
Test it before a client sees it
Preview in Dubsado is for visual checks only. It does not run the full submission, so it will not show you whether the contract attaches, the selection rule behaves, or the invoice builds correctly. Create a test project with yourself as the client, apply the proposal, and complete it in a logged-out browser window. Check the invoice that comes out of it against the packages you chose.
Where to start
If you want the structure already in place, start with the Forms & Flows proposal templates. Peony, for example, includes package and add-on sections, an FAQ, a client details section, and a matching contract template, so the proposal and the contract read as one document. For the workflow that runs after the proposal, the Flow Kits are mapped by industry. If you would rather build your system with guidance, Cait Potter’s done-with-you Dubsado setup walks you through it.
FAQ
Can a Dubsado proposal use a different contract for each package?
No. Each proposal supports one contract. Write one contract that covers every package on the proposal and use invoice smart fields to show what the client selected.
Does Dubsado create an invoice if I turn off “Include invoice”?
Yes. An invoice is always generated from the client’s package selections when the proposal is submitted. The toggle only controls whether the client sees it in the proposal.
Should the payment plan go on the proposal or the workflow?
One or the other. If the workflow sends the proposal and has its own payment plan, leave the proposal’s payment plan field blank. Setting both causes the workflow to error.
Can clients choose one main package and several add-ons?
Yes, with “Multiple packages can be selected” set to Yes. That setting applies to the whole proposal, so label each section clearly and check the invoice in your test project.
Do I need a workflow to send a proposal?
No. You can send a proposal from a project directly. A workflow becomes useful for what happens after the client signs and pays, and the proposal setup decides how short that workflow can be.