Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. How We Build an Automation System, Step by Step
Business Automation

How We Build an Automation System, Step by Step

The exact process we follow from first call to live system, what happens in each phase, and what you do at each stage.

Updated 2 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Four phases: discovery where we watch the work being done, a written scope with a fixed price, a build in two-week increments you can see running, and parallel running against your manual process before cutover. Typically 6–12 weeks for one process.

Phase one: we watch the work happen

We do not start from a requirements document. We start by watching somebody do the task, because what people describe and what people do are reliably different, and the difference is where projects fail.

That means a screen recording, a shadowing session, or sitting with whoever handles the awkward cases. One hour of watching produces more usable specification than a day of meetings.

Phase two: a written scope with a fixed price

You get the workflow written as numbered steps, the exception list, the systems it touches, a phased plan and a fixed price for phase one. You own that document and can take it to another supplier.

The exception list is the part we spend the most time on. A scope with fewer than five exceptions in it is not finished, and we will keep asking until we have them.

Phase three: build, with something running every fortnight

You see working software every two weeks, not a status report. Early demonstrations are rough on purpose — the point is that you can click through the actual path and tell us where it is wrong while changing it is cheap.

  • One named developer, whom you meet before signing
  • Fortnightly demonstration with your team, not just the sponsor
  • Changes logged and priced, including the ones we absorb
  • Code in your repository from day one

Phase four: parallel running, then cutover

For two to four weeks the automation runs alongside your manual process and the outputs are compared. It feels like duplicated effort and it is the cheapest insurance available — it finds the 5% of cases nobody mentioned while they still cost an afternoon rather than a customer.

Only when the comparison is clean do we cut over, and the manual route stays available for a defined period afterwards.

What we need from you

  1. One person who can make decisions, about half a day a week
  2. Questions answered within a day or two
  3. Real data, including the awkward records, for testing
  4. Attendance at the demonstrations with actual feedback

Projects where the client does these finish two to three weeks earlier than identical scopes where they do not. It is the largest variable we do not control.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

How long does a first automation take?

Six to twelve weeks from signed scope for a single process, including the parallel-running period. Faster is possible by cutting scope, never by cutting testing.

What does it cost?

£5,000–£15,000 for one well-defined process. We quote a fixed price against a written scope, so the number does not move mid-project.

Do we have to replace our existing systems?

Usually not. Most of what we build sits alongside what you already run and talks to it. Replacing an ERP and automating a process at the same time is two hard projects blaming each other.

What happens if it does not work?

You will know by the parallel-running stage, which is well before cutover and before the final payment milestone. That is deliberately how the phases are ordered.

Keep reading

More on Business Automation

Start here

Want to see what phase one would look like for you?

Tell us what happens in your business today and we will map the process, the exceptions and a fixed price for the first phase.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →