Two revision rounds, 30 days of fixes.
How changes work after we build: what is included, what counts as a correction, how to ask, and what is quoted separately.
The short version.
Four things worth knowing before you read the detail. Each clause below also starts with its own one-line summary.
Two rounds of revisions to the agreed scope are included in every build.
Anything that does not work as the accepted scope describes is fixed free for 30 days after delivery.
We acknowledge every revision request within 24 hours and tell you when it will be done.
New features and changes outside the scope are quoted before any work, so there are no surprises.
Sort a request in three taps.
Not sure if a change is a revision, a correction or a new request? Pick the closest match.
Choose the closest match on the left.
We will tell you which bucket your request belongs to.
We fix it free.
This is a defect against the accepted scope. Within 30 days of delivery, corrections cost nothing and do not use up a revision round.
- Tell us what you expected and what happened.
- We acknowledge within 24 hours and give you a fix date.
Included in your two rounds.
A change to something we already built, within the agreed routes and tools, is a revision. Two rounds are included, and a round can contain several related changes sent together.
- Send all the changes for a round in one message.
- We confirm what is in the round before starting.
We quote it first.
Adding apps, workflows or triggers changes the scope. We send a short written quote, and nothing starts until you approve it.
- Small additions can often be quoted the same day.
- Larger ones use the quote form so the price is accurate.
Inside 30 days we look at it; after that we quote a repair.
If a platform change breaks something within the correction period, we assess it and tell you honestly what is needed. After the period, we quote a repair or an update.
- Tell us which tool changed and when you noticed.
- Send any error message you can see.
How we keep revisions short.
Revisions should be a polish, not a rebuild. We work to keep them that way.
Confirm the scope first
Before building, we restate the scope in plain words. Disagreements surface at the start.
Show early
For larger builds we show a working route before finishing everything.
Test with real cases
We test the awkward cases up front so they do not appear as ‘bugs’ later.
One message per round
Collect your changes and send them together. We apply and test them as one.
Written confirmation
We confirm what is in each round, so there is no doubt about what was agreed.
Fast acknowledgement
Every request is acknowledged within 24 hours with a date.
Definitions
Three kinds of change: a revision, a correction and a new request.
- Revision
- A change to something already built within the agreed scope: adjusting a rule, renaming a field mapping or reordering steps.
- Correction
- Fixing something that does not work as the accepted scope describes.
- New request
- Anything that adds to or changes the scope, such as another app, workflow, trigger or data type.
- Revision round
- One batch of revision requests sent together and delivered together.
Two included revision rounds
Collect your thoughts, send them in one go, and we apply them together.
Every build includes two revision rounds. Send all changes for a round in a single message so we can apply and test them together. We confirm the contents of the round before we begin. A round may contain several related changes. If a request would change the scope, we tell you before starting and handle it as a new request.
The 30-day correction period
If something isn’t working as the scope says, we fix it free for 30 days.
For 30 days after delivery, we correct at no charge anything that does not work as the accepted scope describes. Corrections do not use a revision round. Report issues through a support request in your customer dashboard with what you expected, what happened and any error message or screenshot. We acknowledge within 24 hours.
The period starts on the day we notify you of delivery and ends 30 days later. If we are waiting on you for information, the time we wait does not extend the period, but we will still look at problems reported during it.
How to submit a revision
One message per round, with specifics.
- Open the contact form and choose ‘Revision or change request’.
- Quote your order reference and list each change.
- We reply within 24 hours with a confirmation and a delivery date.
- We deliver and ask you to test.
- If something is not right, it is corrected; if it is a new change, it joins the next round.
What is not included
New scope, changes after the period and third-party changes are quoted separately.
- New apps, workflows, triggers or data types.
- Rebuilds caused by a platform changing its API, limits, plan or terms after delivery.
- Problems caused by edits made by others to the automation or connected accounts.
- Training sessions beyond the handover document.
- Data cleanup of records that existed before the automation.
We quote these before starting, usually within 24 hours.
Approval
When you approve, or when the period passes, the order is complete.
Delivery is accepted when you approve it, or at the end of the 30-day correction period, or after 30 days without a reply to a delivery notice, whichever comes first. Approving does not remove the right to have genuine defects corrected within the correction period.
Common questions about this policy.
10 short answers to what people ask most. If yours is missing, ask it and a person replies within 24 hours.
Does fixing a bug use one of my revision rounds?
No. Corrections to something that does not match the scope are free and do not count as a round. The two revision rounds are reserved for changes you want to make to something that is working as agreed.
Can I send changes one at a time?
You can, but each message may be treated as a round. Sending them together gets more done within two rounds, and lets us apply and test them as one change, which is safer. Collect your list first, then send it once in your dashboard.
What if I need more than two rounds?
We quote additional rounds in advance, so you know the cost before you ask. Most clients do not need more, particularly if they send complete lists. If you expect many changes, tell us at the start and we can plan for it.
What happens after the 30 days?
You can still ask for changes and fixes. They are quoted before any work starts, so you decide whether they are worth it. If you would like continuing cover, ongoing support can be added as a separate agreement.
Can I send two requests in one message?
Yes. That counts as one round if it is sent together. Group related changes in a single request and number them, so each can be checked off when done.
Does a typo fix count as a revision?
If it is our typo, it is a correction and free. If you want different wording, it is a revision. When in doubt, send it and we tell you which it is, before using a round.
Can I ask for a new feature during a revision?
New features change the scope and are quoted separately. A revision adjusts something that already exists within the agreed scope. If your request is borderline, we tell you which side of the line it falls on and quote it if needed.
What if I do not use both rounds?
Unused rounds expire at the end of the 30-day period. We would rather you use them, so test thoroughly in the first weeks and send your changes while the project is fresh.
What if I am unhappy after two rounds?
Tell us. We will look at what is still off-scope and fix it, and quote anything that is genuinely new. The aim is that you end with what the accepted scope describes, and we take that seriously.
How fast are revisions done?
We give a date when we acknowledge the request. Simple ones are often done within a day or two, while larger ones depend on how many routes they touch. The date appears on the revision request in your dashboard.
Other policies and guides.
Our policies are written to work together. These are the ones most often read alongside this page.
Questions about this policy?
Ask us in plain words and a person will answer within 24 hours. We would rather clarify than leave you guessing.