Delivery you can plan around.
How long builds take, how we count the days, what starts the clock and what can pause it. Plus a small tool to estimate your delivery date.
The short version.
Four things worth knowing before you read the detail. Each clause below also starts with its own one-line summary.
Each service page shows its own window. Simple routes sit at the short end; multi-system builds at the long end.
We count Monday to Friday. The work itself runs around the clock, so weekends never slow a build we are already running.
Payment received, a complete brief, and the access we need.
The clock pauses after 5 business days of waiting for something only you can provide.
When would delivery land?
Pick the day the clock starts and the delivery window shown on your service page. This tool counts Monday to Friday and shows the last day of the window.
Estimates only. Your quote or service page states the binding window.
—
Delivery you can plan around.
A delivery date is a promise. We make it carefully and tell you at once if it moves.
A stated window
Every service page shows its delivery window, from two to twenty-four business days.
A visible clock
The clock starts when payment, a complete brief and access are in place, and we tell you the date.
No silent delays
If something will slip, you hear about it when we know, with a new date.
Work runs every day
Business days measure the window. The work itself continues over weekends.
Sooner on request
Ask for expedited delivery on the quote form and we reply with what is possible.
Clear handover
Delivery means built, tested and documented, not ‘nearly done’.
What a business day is
Monday to Friday. Work keeps going between them.
We count Monday to Friday as business days. We operate every day of the year, so a build in progress continues over weekends and public holidays, but the delivery window itself is measured in business days so it is easy to predict.
Delivery windows
From two to twenty-four business days, depending on the service.
| Type of work | Typical window |
|---|---|
| Single-route automations between two well-documented tools | 2 to 5 business days |
| Multi-step workflows with branching and exception handling | 5 to 10 business days |
| Full builds with monitoring, reconciliation and handover documentation | 10 to 24 business days |
| Custom projects | Stated in your written quote |
These are ranges. The window on your service page or quote is the one that applies to your order.
When the clock starts
Payment, a complete brief and access. All three.
- We have received payment.
- We have a complete brief: the information on the order form is enough to build from.
- We have the access we need, as described in access and requirements.
The clock starts on the business day after the last of these is in place. If you can arrange access before you order, the clock starts as soon as you pay.
When the clock pauses
If we need something only you can give and it takes more than five business days.
If we are waiting for information, approvals, access or test data that only you can provide, the clock keeps running for the first five business days and then pauses until we receive it. We tell you when we pause and when we restart. The 30-day correction period is not extended by pauses.
What can lengthen delivery
Things we cannot control, and we tell you straight away.
- Slow approval for access on your side.
- Platform outages, review queues for new apps or API access, or plan changes.
- Changes in scope after the order.
- Test data that does not exist yet.
We tell you as soon as we know and give a new date.
Expedited delivery
Need it sooner? Ask before you order.
Some orders can be prioritized. Tell us your deadline on the quote form or in the contact form and we reply with what is possible and any difference in price. We never promise an impossible date to win an order.
What delivery means
Built, tested and handed over with documentation.
Delivery is the point at which the automation is built, tested against the agreed scope and handed over to you with a handover document, and we notify you. Revisions and corrections follow the revision policy.
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.
Do you work on weekends?
Yes. We operate every day of the year, and messages are answered on weekends and public holidays. What differs is how delivery windows are counted: they are stated in business days, Monday to Friday, so that the date you are given is realistic. Work may well be completed sooner than the window suggests.
Why does my delivery window differ from another service’s?
Because the effort is different. The number of systems, workflows and exception paths decides how long a build and its testing take, and the window on each service page reflects that. A simple one-way sync can take a couple of days, while a two-way sync with refunds, retries and reconciliation takes considerably longer to build and prove.
Can you deliver faster?
Sometimes. Tell us your date when you request a quote, and we will say whether we can meet it, what it depends on and whether it changes the price. Deadline work displaces other projects, so we quote it plainly. We never promise a date that we cannot meet just to win an order.
What if a platform delays me?
We tell you at once, adjust the date and keep working on everything that does not depend on the delay. Platform delays include app review times, rate limits that force a slower run, outages and approvals that wait on a third party. Your dashboard milestone shows what is waiting and why, so you always know the real position.
Do public holidays count as business days?
Business days are Monday to Friday, and public holidays are not subtracted, because they differ by country and we work through them anyway. If the window counts ten business days, the date is simply ten weekdays out. Our delivery estimator shows the date for any start day.
What if the platform delays approval of my app?
We keep working on everything else, such as the logic, the field mapping and the sandbox tests, so that the project is ready the moment approval arrives. We update the date in your dashboard and tell you what the platform is reviewing, so you can chase it from your side if that helps.
Can delivery be faster than the window?
Often, when access is ready on day one and the platforms behave. The window is a ceiling we are confident of, not a target we aim to use up. We never promise less than we can deliver, and if we finish early, we tell you and move to your review straight away.
How will I know when it is delivered?
You receive a handover message in your dashboard with the documentation and a short test checklist, and the milestone is marked complete. The checklist walks you through checking each route yourself. Delivery also starts your 30-day correction period, during which anything that does not match the accepted scope is fixed free.
What if I am slow to reply?
The delivery clock pauses after five business days of waiting on you, for example for access or an answer, and restarts the day we hear from you. Before that, the window is unaffected. We tell you in your dashboard when something is waiting on you, so a delay never comes as a surprise.
Is the 30-day correction period part of the window?
No. The delivery window ends when we hand the automation over. The 30-day correction period begins after delivery and is separate, so it never shortens the time we have to build. During it, we fix anything that does not work as the accepted scope describes, at no charge.
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.