From first message to handover, step by step.
A clear path, with no surprises: what happens, in what order, what we need from you and what you get at each stage.
Six stages, no guesswork.
Open any stage to see exactly what happens, what we need from you and what you receive.
Choose a service or ask for a quote
Pick a fixed-price package from the catalog, or send the five-step quote form if your setup is not listed. Either way, you see the scope and price before you pay.
If you are unsure, use the contact form. A person replies within 24 hours.
Approve and pay securely
Approve the order and pay securely by card, Apple Pay, Google Pay or PayPal. After payment you are redirected to log in to your secure customer dashboard. Full refund is available any time before work starts, with nothing deducted.
Payment unlocks kickoff. Our payment terms explain taxes, receipts and milestones for custom work.
Kickoff: the brief and access
We confirm your brief and request the access we need inside your customer dashboard, using each platform’s own sharing tools where they exist. Requests for access, login details and API keys come through the dashboard and are answered there only, never by message, form or email.
A good project brief and early access save days. See access and requirements for each platform.
We build and test
We build in a sandbox where possible, test the normal route and the awkward ones, such as duplicates, retries, rate limits and out-of-order events, and then promote to live with your approval.
Delivery windows run from two to twenty-four business days. The delivery policy explains how days are counted.
Handover
You receive the working automation, a handover document, the list of permissions we used and how to revoke them, and a short checklist to test it yourself.
From here, the 30-day correction period and two revision rounds begin.
Support and changes
Report anything that does not match the scope within 30 days and we fix it free. After that, platform changes and new ideas are quoted before any work starts.
Optional monitoring and support after launch can be added at any time.
Which way should you start?
Three ways in. Answer one question and we point you to the best starting place.
Choose the closest match on the left.
Answer one question and we will point you to the best starting place.
Order a fixed-price service.
Find your platform in the catalog, choose the package that fits, and see the price and delivery window before you pay.
- Three package levels: core route, branching and exceptions, full build with monitoring.
- Delivery in two to twenty-four business days.
Request a custom quote.
Five short steps collect everything needed to price your automation properly, so you get a number rather than a questionnaire.
- Required budget range keeps the proposal realistic.
- Written quote within 24 hours, valid for 14 days.
Describe the problem.
Send a message with what is happening today. We will recommend a service, a custom build, or tell you honestly if automation is not the right answer.
- Choose the topic ‘A custom automation idea’.
- A person replies within 24 hours.
What we handle and what we need from you.
A good project is a partnership with clear halves. Here is who does what, so nothing falls between the two.
We handle
The technical work, start to finish.
- Design of the workflow and field mapping
- Building with official APIs and connectors
- Testing normal and awkward cases
- Duplicate, retry and rate-limit protection
- Handover document and permission list
- Corrections for 30 days
We need from you
A few things only you can provide.
- A brief that says what should happen
- Access granted through each platform’s sharing tools
- Test records or a sandbox account
- Decisions when we hit a real choice
- Approval to move from test to live
- Your own backups of important data
Seven safety nets in every build.
These are the unglamorous parts that decide whether an automation is still working in six months.
Duplicate protection
Every event is recognized if it arrives again, so repeats change nothing.
Retries with backoff
Temporary failures are retried patiently instead of hammering a struggling system.
Rate-limit awareness
Requests are paced under each platform’s limits, with a queue for bursts.
Signature checks
Inbound webhooks are verified where the platform signs them.
Clear error trails
Failures are logged with enough detail to diagnose them, and alerts reach a person.
Reconciliation
On full builds, a scheduled comparison between systems reports any differences.
Safe rollback
We note how to switch the automation off and what it changed, so you can always step back.
How long does it take?
The window depends on the number of systems and exception paths. The one on your service page or quote is the one that applies.
2–5 days
Single-route automations between two well-documented tools.
5–10 days
Multi-step workflows with branching, filters and exception paths.
10–24 days
Full builds with monitoring, reconciliation and complete documentation.
The clock starts when
Payment is received, the brief is complete and access is in place. Business days are Monday to Friday. The delivery policy has an estimator.
What you receive when we finish.
Delivery is not ‘it is live’. It is a working automation, plus everything you need to run it without us.
The working automation
Built, tested and live in your accounts, with your approval to switch on.
Handover document
A plain-language description of what it does, how it is built and what to check first if something looks wrong.
Permission list
Every connection, key, role and webhook we used, with the steps to revoke each one.
Test checklist
A short list so you can prove for yourself that it works.
Revision rounds
Two included rounds for adjustments within the agreed scope.
Correction period
Thirty days to report anything off-scope, fixed at no charge.
Questions about the process.
What people ask between ‘I am interested’ and ‘let’s start’.
Do I need to be technical?
No. We ask in plain language and explain every permission before you approve it. If you can open a platform’s settings and approve a request, you can work with us. We handle the technical design, the testing and the handover document, and we write that document so that a non-technical person can follow the checklist.
What if I do not have a test account?
Many platforms offer a free sandbox or test mode, and we help you switch it on. If yours does not, we agree a safe way to test with a small set of real records you choose, labeled so they are easy to find and clean up, and the first run is read-only. You approve the move to live data.
Can I see progress?
Yes. We update you at each milestone and whenever a decision is needed, and your customer dashboard shows every milestone with a countdown to its target time. Ask for more frequent updates on the quote form if you prefer, and message us in the dashboard at any time to ask where things stand.
What if the scope changes midway?
We pause the affected part, quote the change in writing with its price and effect on the date, and continue only when you approve it. Nothing extra is ever added to your bill without your agreement. If the change is small and fits inside your revision rounds, we tell you, and it costs nothing.
Who owns the automation?
You do, on full payment. The configured automation and the materials built specifically for you are yours to use, change and keep running. We keep our general methods and templates. The licensing and usage page has the full terms.
How do I give access?
Where a platform offers invitations or app authorization, you approve them in the platform. Anything that needs a login detail or an API key goes into your secure customer dashboard, in the access request we post there, never by message, form or email. See access and requirements for platform-by-platform instructions.
What if something breaks after delivery?
Report it within 30 days through a support request in your dashboard and we fix it free if it does not match the accepted scope. After that, we quote a repair before starting. Tell us what you expected, what happened and any error message, and we acknowledge within 24 hours.
Can I speak to someone during the build?
Yes, in writing. Message the team in your customer dashboard, where the conversation stays attached to your project, or use the contact form before you have a dashboard. We reply within 24 hours, any day of the year, and writing means decisions are recorded for you and for us.
What happens if I go quiet?
The delivery clock pauses after five business days of waiting for you, and restarts the day you reply. Before that, nothing changes. We send reminders in your dashboard saying exactly what we are waiting for, so a pause is never a surprise.
Can I pause or stop a project?
Before work starts, you can cancel with a full refund. After it starts, tell us and we will agree what to do with the remaining work: pause it, finish a reduced scope or complete it. Refunds are not available once work has begun, but we will not leave you with a half-finished build without a plan.
Who tests the automation?
We do, in a sandbox and with sample records, covering the normal route and the unusual cases the scope names. You approve the move to live data, and you receive a short test checklist so you can run the key checks yourself before accepting. Your 30-day correction period covers anything that slips through.
Do you document everything?
Yes. Every build ends with a handover document, a permission list and a test checklist. The document describes the workflow, the connections, the keys and webhooks created, how to test it, where to look when it fails and how to revoke each permission. You receive it in your dashboard.
Ready to start step one?
Choose a fixed-price service or tell us about your setup. Either way, you see the price before you pay.