Every automation we build comes with a 30-day warranty. If something we built breaks within 30 days of launch, we fix it at no charge. That one sentence is the promise, and this post explains what sits behind it: what counts as broken, what does not, how to report a problem, and what happens on day 31.
We also explain why we offer a warranty instead of refunds, because the two are often confused. Terms were last reviewed on October 29, 2026.
What counts as launch
Launch is the day the automation starts doing real work in your business, after testing and after the handover call. It is not the day the code was written or the day of the first test run. If we roll out in stages, for example one location first and then the rest, the 30 days start when the last stage goes live.
What the warranty covers
The warranty covers anything that does not do what the agreed scope says it will do. In practice that means:
- Bugs. A step that throws an error, skips records or writes the wrong value.
- Failed runs. An automation that stops running when nothing in your systems changed.
- Wrong behavior against the scope. A reply that goes to the wrong person, a rule applied in the wrong order, a field mapped to the wrong place.
- Gaps in the handover. Documentation that does not match what was built, or a control that does not work as shown.
Fixes under warranty are free, with no cap on the number of fixes within the 30 days.
What it does not cover
The warranty is about our work, so some things sit outside it.
- New features. Asking for a new step, a new report or a new tool connection is a change, not a fix. We quote it separately.
- Changes to how you work. If your team changes a process after launch, the automation needs updating, which is also quoted.
- Changes made by someone else. If another person edits the automation or the systems it uses in a way that breaks it, we will help, but the fix is billed.
- Vendor costs. Model usage and tool subscriptions are paid to those vendors directly and are not part of the warranty.
When something is borderline, we look at the written scope. If the scope says it should work and it does not, it is ours to fix.
Tell us what you want automated and we'll explain what the 30 days would cover for it.
How to report a problem
Email or message us with what happened, when, and a screenshot or record ID if you have one. We confirm we have it, tell you whether it is a warranty fix, and give you a time for the fix. Most fixes are small, and we aim to finish them the same week. If an automation is causing harm, such as sending wrong messages to customers, pause it with the off switch from the handover and tell us right away.
Why a warranty and not a refund
We do not offer refunds, and there is no cancellation window. Most of the cost of a build is time spent mapping your process, connecting your accounts and testing on your data. That time cannot be handed back. What we can do is stand behind the result, which is what the warranty does.
Payments are staged so you never pay far ahead of what you can see. On a larger build, you pay a third at the start, a third when the work is 30% done, and the last part at 60% done and handover. The full schedule is in how automation pricing and payment work. Between staged payments and the warranty, you are never stuck paying for something that does not work.
What happens on day 31
After the warranty ends, you choose how the system is looked after.
- 1Run it yourself. The handover documentation shows how each part works, how to pause it, and where the logs are. Many teams handle small changes on their own.
- 2The care plan. $350 a month, month to month, with 30 days' notice to stop. It covers monitoring, fixes and small changes, so problems get caught before your team notices them.
- 3A managed plan. For businesses running several AI agents, managed plans from $4,000 a month mean we run, watch and improve the agents for you.
- 4Pay as you go. Pair-build time is $250 an hour, or prepaid in blocks of 4, 10 or 20 hours.
Our post on what automations cost after they are built explains why systems need looking after at all, and how to plan for it.
What makes a warranty claim less likely
Most problems in the first month come from three places: data that looks different in real life than in the samples, a vendor that changes something, and a case nobody mentioned during mapping. We reduce all three by testing on your real records, adding alerts for failed runs from day one, and watching the first real runs closely before handover. Our write-up on automations that silently stop working covers the alerting side.
How we compare with other firms
Warranty terms vary across the industry. Some firms include 14 days of fixes, some 30, some 90, and some offer refunds within a window instead of a warranty. Some include nothing and bill every fix from day one. Compare the length, what counts as a fix, and whether fixes are capped before you compare prices.
Questions to ask any builder
- When does the warranty start, and when does it end?
- Is there a limit on the number of fixes?
- What happens if a vendor changes their app during the warranty?
- What does support cost after the warranty?
If you want to see how the warranty applies to a specific project, describe it in the form below and we reply within one business day. You work directly with Shariq, the founder, who builds and supports what he quotes. For costs, the AI agent cost guide and the pricing page have the numbers.
