You know the number before anything gets built. No hourly billing, and no surprise at the end.
Not sure what this is worth to you? Work out what the admin is costing you first
Build
$7,500
First automation live in 2 to 3 weeks
Book a callRecommended
$13,500
First automation live in 2 to 3 weeks, all six inside 6
Book a callBuild
from $20,000
First automation live in 2 to 3 weeks, then staged over 8 to 12
Book a callOngoing
$500/month
Cancel any time
You do not have to take this. You own the system, so looking after it yourself is a real option. This is for owners who would rather noticing a problem was somebody else’s job.
Most builds cost something small every month to keep running. That is the AI usage and any subscriptions the automation needs.
It is paid to those providers, not to us, and you get the number in writing before you commit to anything. Some builds cost nothing at all beyond what you already pay. Anything that sends text messages has a real per message cost, and that account goes in your name with a spend cap on it, so you are never exposed to a bill you did not set.
For most builds it lands somewhere between $100 and $200 a month. What moves it is how many automations you have running and how often they run. A few that fire a handful of times a day sits at the bottom of that range. A larger set, or anything reading and writing all day, sits at the top.
Most of what we build is shaped to the business anyway. Custom systems, a CRM built around how you work, or something that only makes sense for you.
Because it is built for your business rather than configured from a template, and because the price includes the parts people usually skip. Scoping it properly, testing it against your real data, writing the procedures, and fixing it free for a period afterwards. A cheaper build that nobody documented is the one that stops working in March and nobody knows why.
Say so on the call. The tiers are the common shapes, not a rule. If one automation is genuinely all you need, we will quote that instead of talking you into a bigger build.
Mostly no, and nothing from us. We build inside the tools you already pay for, and if something you own would already do the job we will say so rather than build on top of it.
Being straight about it though: most builds do need somewhere to run. That usually means an automation platform, and credit with an AI provider where the build uses AI. It is normally a small monthly amount, the accounts go in your name so you keep control of the spend, and you get the actual numbers in writing before you agree to anything. See what it costs to run above.
You do. It is built on your accounts, with your logins, and your data stays where it already is. There is no login to a TradeBetter system, because there is not one. Nothing is hosted by us that you cannot get to.
No. You own the system, so looking after it yourself is a genuine option and nothing about your build changes if you decline. It is there for owners who would rather noticing a problem was somebody else's job, and because a small fault caught early is cheaper than a quiet one found a month later.
The Rebuild includes it for your first three months. After that it continues at the monthly rate if you want it, and stops if you do not. We will ask you, rather than letting it roll on quietly.
Changing something one of your signed off automations already does. New wording in an email it sends, a different person copied in, a new step in a list it already checks, a threshold moved. You get two a month, and they roll over for up to three months, so a quiet month is not money wasted.
Fixing things does not use them up. If an automation breaks, or a platform changes something at their end and we have to update your build to match, that is our job and it does not touch your two. The allowance is only for changes you ask for.
A new automation is a new build, and it gets quoted like one. The line is whether we are adjusting something that already exists or building something that does not. If it is ever unclear, we will tell you which side it falls on before doing the work, not after.
Every build comes with a period of free fixes, and that includes rebuilding anything that stops working because a platform changed something at their end. After that period you either look after it yourself using the written instructions, or you take the care plan.
It keeps running. That is the point of building it on your infrastructure. You have the logins and the written procedures, so another person could pick it up. We do not hold anything hostage because there is nothing to hold.
Yes. Ask on the call and we will show you a real automation running end to end, rather than a slide about one.
Tell us what your week looks like. We will tell you what could run without you, what could not, and what it would cost.
Book a call