What Makes an Automation Partner Worth Keeping

Ten years, a thousand clients, and a habit of saying no

SpiderHunts has been building custom software and automation since 2015, for more than a thousand clients across the UK, USA, UAE, Canada and Europe. The delivered work includes order automation that took a UK wholesaler from 3.5 days to 18 hours, an AI support layer resolving 67% of tickets for an HR SaaS, and a booking system for a Danish field-service firm that removed manual re-entry entirely.

What we would rather be judged on is how the projects ran, not the numbers at the end of them.

What we commit to

1. A fixed price against a written scope you own and can take elsewhere
2. Working software you can click through every fortnight
3. Exception handling and testing priced in, not offered as an upgrade
4. Code in your repository and accounts in your name from day one
5. Bad news early, with options attached
6. An honest recommendation not to build, where that is the answer

Questions worth asking us

• Who specifically will do the work, and can we meet them?
• What is explicitly out of scope?
• What would make this project late?
• What would you not automate here?
• What do you think is wrong with our brief?

Ask that last one of every supplier you are considering. Anyone who says “it all looks fine” either has not read it or will not tell you when something is wrong later.

What we ask in return

One decision-maker with about half a day a week, questions answered within a day or two, honesty about the awkward parts, and attendance at the demonstrations with real feedback.

Clients who do these finish earlier and pay less for identical scopes. It is the most consistent pattern we see across ten years.

Start small

One process, four to twelve weeks, a number you agreed before it started. Measure before, measure after, and let the result decide whether there is a phase two.

That sequence means being wrong costs weeks rather than a year, which is the point.

Frequently asked questions