Workflow automation
Approvals, handoffs and multi-team processes with state, retries and audit trails.
- Engagement
- Fixed-scope build, priced per workflow
- Typical timeline
- 5–7 weeks
- Starts with
- A whiteboard session where we draw the workflow including every path you would rather not think about.
The automation works until the day a supplier’s system returns nothing, the approver is on leave, and the same order gets created twice. Edge cases are where automation either earns its keep or quietly destroys trust.
Processes that cannot silently stall.
What we build
Concrete artefacts, handed over and documented.
Workflow definitions with every branch drawn explicitly, each yes, each no, and each neither-of-those path named rather than assumed
Approval steps with delegates, timeouts and a record of who decided what, so annual leave does not halt the business
Retries with backoff and idempotency keys, so a slow external system produces one order instead of three
A state store that survives restarts, letting a workflow pause for two days waiting on a person and resume exactly where it stopped
An audit trail per run that a non-technical manager can read: inputs, decisions, outputs
Alerting that separates a failure needing a human from a retry that will resolve itself
What changes
Long processes finish without anyone shepherding them through
Failures become visible events with an owner, instead of gaps discovered weeks later
‘What happened to that one?’ is answered with a link rather than an investigation
How it runs
01Model the flow
We write the workflow as a diagram covering every branch and failure path, and you correct it before any code exists.
02Build and break
Built step by step, then deliberately broken: timeouts, duplicates, malformed data, an approver who never answers.
03Run in parallel
Live alongside the current way of working, with alerting tuned until it only fires when it matters.
Chosen per project. Named here so you can see the shape of it.
- n8n
- Temporal
- Postgres
- Slack
- Sentry
Questions we get asked
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.