Four steps. The first two are a single fixed-fee pilot: one fee, agreed in writing before anything starts, covering the scope and the build of your first automation.
- Two sessions01 · ScopeThe first half of the fixed-fee pilot. We record the work as it is actually done, name every integration including the systems with no API, and write the payback arithmetic with your own figures in it. You get a written plan and a delivery date before the build starts.
- Two to four weeks02 · BuildThe second half of the pilot, inside the same fee. A working system on your real data, in a staging environment, before anything goes live. You see it running and read the test log before you sign it off. Not slideware, and the pilot has an end date.
- Ongoing03 · RunWe host and monitor it on infrastructure we maintain, in a UK or EU region. Failed runs retry, then queue for a human. We get the alert before you do, and we are the ones who fix it.
- Monthly04 · ReportOne page: runs completed, hours returned, money returned, and every failure with what caused it. If the number stops making sense we tell you, and we will suggest stopping if that is the honest answer.
What we need from you
Someone who does the task today, for about an hour, twice. That is genuinely most of it. You do not need anyone technical in-house — we run and monitor the system, and the documentation is written for whoever comes after us.