Knowledge Base › Building & Owning
Building & Owning AI
What custom AI automation costs
Custom AI automation usually has a one-time setup fee and a monthly retainer. The setup builds and connects the system. The retainer keeps it running, watched, and improved. Scope sets the price, so treat any general range as an illustration, not a quote.
"How much does AI automation cost?" is the right question. It's also hard to answer cleanly. Price follows the work, and the work depends on your systems, your data, and the handover. A CRM cleanup is not the same as a quoting engine. This is how to read a quote without guessing.
Why it's setup plus retainer
A real automation isn't something you buy once and forget. It has to be built, connected to your tools, and tested against messy work. That's setup. Then it needs watching when your data shifts or the AI models change. That's the retainer. If someone sells "one payment, done forever," ask where the maintenance is hiding.
What the setup fee buys
- Scoping one workflow and the number it'll move
- Building the system and connecting it to your tools
- Testing it on real, messy inputs, not demo rows
- Handover: the code, accounts, and docs — so you own it
What the monthly retainer covers
- Monitoring that it's still working as inputs change
- Changes as you learn what staff will use
- Re-measuring the number so value isn't assumed
- Keeping it current when AI models change
A real example of build scope
Illustration — a real DPR engine run, not a client result or a priceThis is a real, sanitized snapshot of one DPR engine run (exported 2026-06-30, no client data). It's here to show the shape of what a build involves — not a quoted price or a promised outcome.
How to estimate your own scope
You can roughly size a build by looking at what makes it heavier. More integrations push setup up. So do messy data and stricter compliance. A single clean workflow, like routing inbound leads, keeps it down. Any specific dollar range you read online is an illustration — the honest number comes from scoping your actual workflow.
For reference, DPR scopes each build around one number instead of a vague "it depends." A first build is fixed-scope and you own it; an optional retainer comes after, only if you want one. Your scope and the number you need to move set the shape of the work — we agree it with you up front.
When automation is worth it
Automation pays off when a task repeats often and has a number attached. Think 300 support tickets a month. It's not worth it when the task is rare, the rules are fuzzy, or nobody will own the result. A good partner will say "don't automate this yet" when that's the honest answer.
Apply this
The clean way to know the cost is to scope one real workflow. DPR quotes a fixed price up front, tied to one honest number. There's no open-ended hourly meter.
See how a build works Scope a build