(04)Why not just ask AI?
AI gives you exactly what you asked for. That is the problem.
Ask an AI for your Dubsado workflows and you get the workflows you described. Dubsado Alchemy maps the ones your business needs.
It works from the help documentation.
A general AI knows what each Dubsado feature was designed to do. It does not know where Dubsado’s limits are, or how to get the result you want anyway. If what you described will not work the way you picture it, it has no way to tell you.
It sees one piece at a time.
Ask for a workflow, then an email, then a form, and each is written on its own. With several services, the natural move is to duplicate every step. Dubsado Alchemy starts from how your whole business runs, from the first inquiry to project close, then decides what your services share and where they differ.
It uses features the way the help page describes them.
A builder with years in Dubsado finds the route the help page never mentions: a feature designed for one job, doing another. That judgment is the Trigger Mapping Method, built from more than 200 businesses.
From real Dubsado builds
What you ask an AI for, and what it takes to build it.
You asked for
A follow-up email when a client does not book my scheduler.
What it takes
Dubsado has no trigger for a client who does not book, so this takes a workaround, in this order.
- Send the scheduler.
- Send the follow-up email x days after all previous actions complete. This runs no matter what.
- Start a second workflow 0 days after an appointment is scheduled.
- Pause the first workflow 0 days after an appointment is scheduled. This stops the follow-up if the client does book.
Out of order, it does not work.
You asked for
An onboarding workflow.
What it takes
Every action in a workflow sends, applies or assigns something that has to exist already. So the workflow is built last.
- Account settings: business information, email, time zone and payment processor.
- Project statuses.
- Packages and payment plans.
- The canned emails, forms and schedulers this service needs, and only those.
- The workflow itself.
You asked for
A payment plan for each of my services.
What it takes
The obvious build is one plan per service. A plan built around the schedule works better.
- Build payment plans around the payment schedule, not the service.
- A 50/50 split covers most work.
- One plan reused across six services is far less to maintain than six near-identical plans.
- Schedulers work the same way: one per length and location, not one per service.
These come from our published guides: What to set up in Dubsado before you build a single workflow and Follow up after an appointment is not scheduled.
Dubsado Alchemy does use AI. It writes the emails, forms, schedulers, payment plans and to-dos, in your voice, after the decisions are made.
| Asking an AI chat | Dubsado Alchemy | |
|---|---|---|
| What you get | What you asked for | What the workflow needs to run |
| How decisions are made | By what you typed | By a method, with the whole process in view |
| Dubsado’s limits | Not accounted for | Known, with other routes to the same goal |
| Several services | Written separately, which tends to mean duplicated | Read together, then shared or split on purpose |
Compare them yourself. Ask a general AI to write workflows for your services. Run the same services through Dubsado Alchemy, where your first Workflow Map is free. Then decide which one you would trust to hand to a builder.