A clear scope, a simple plan, and a date that holds.
No hourly billing, no surprise invoices, no discovery phase that quietly becomes the project. Here is the whole engagement, start to finish.
Six stages, front to back.
Most projects run from first message to launch in four to eight weeks.
-
First message
You describe the task that is eating time. A reply lands within one working day saying whether it is something worth building, and what would need to be true for it to pay for itself.
-
Scope call
Forty-five minutes, usually on a video call, walking through the process exactly as it runs today, who touches it, which tools are involved, where it stalls, how often it happens. Screens shared, real examples, no slides.
-
Written proposal
A short document: what will be built, what it will and will not do, which systems it connects to, which plan it falls under, the launch date, and any third-party running costs. Nothing starts until you have agreed it in writing.
-
Build
The system is built against the agreed spec. You get a short written update at the end of each week and access to working versions as they land, so nothing is a surprise at the end. Larger additions are agreed within your plan, or quoted where they go beyond it.
-
Testing on real data
Run against your actual records, not a demo set, including the awkward edge cases every business has. You test it too, and anything that does not behave is fixed before launch, not after.
-
Launch and ongoing service
A walkthrough for whoever uses it day to day, written documentation, and the system goes live. From that point it is monitored, maintained and improved every month as part of your plan.
How long each build takes.
Measured from signed proposal to live, assuming access to the systems involved and one person on your side who can answer questions within a day or two.
AI chatbot
2–4 weeks. Longer if the source material needs writing from scratch rather than gathering.
Workflow automation
2–4 weeks. Driven mostly by how many systems have to talk to each other.
Live dashboard
4–6 weeks. Add time if the underlying data needs cleaning before it can be trusted.
CRM system
4–8 weeks. Pipeline complexity and migrating existing records are the two variables.
What every plan comes with.
These are not add-ons and they are not line items. They are part of the plan.
- A written spec agreed before any code is written, so "done" is defined by a document rather than a feeling.
- A flat monthly price for your tier. If a request goes beyond the plan, it is quoted before it is built, never absorbed silently and invoiced later.
- Weekly written updates during the build, what moved, what is next, anything that needs a decision from you.
- Testing against your real data, including the edge cases that break demos.
- Documentation in plain English, written for the person who has to use it, not for a developer.
- A live walkthrough with your team, recorded so new staff can watch it later.
- Monitoring and maintenance, the systems are watched, patched and kept running as part of the service, not left to rot after launch.
- Improvements every month, refinements and changes within your tier, so the system keeps pace with the business.
What happens once you are live.
It is watched, not abandoned
Launch is the start of the service, not the end of it. The systems are monitored and maintained as part of your plan, when a third-party service changes something or an edge case appears, it gets handled, usually before you notice.
Fixes are included
Anything that does not behave as the spec describes is fixed as part of the plan, for as long as the plan runs. There is no separate support contract and no hourly rate for putting things right.
It keeps improving
Every tier includes ongoing improvements, refinements, adjustments and, on Pro and Enterprise, new automation requests each month. The system you have in six months should be better than the one that launched.
Leaving is simple
Cancel on 30 days' notice, any time. Your data comes back to you in a standard format, and if you want to keep the systems running without us, a one-off transfer of the build can be agreed, nothing is held hostage.
Currently taking on new projects.
Send over the task that keeps coming back. You will get a reply within one working day and a straight answer on whether it is worth building.
See the services