Automation · Deep dive 03
Process Digitisation
Paper forms, email threads, and shared spreadsheets that carry real business weight deserve proper software. We turn ad-hoc processes into systems that remember, enforce, and report.
The scope
When a process is important enough that people work around its limits, we build it the software it deserves — state machines, audit trails, role-based permissions, analytics exports. Small, fit-for-purpose apps that remove the swivel-chair.
Does this sound familiar?
-
The approval flow is an email thread that includes three people in CC and nobody can find the decision later.
-
Operations runs out of a spreadsheet that gets emailed around with 'v7_final_FINAL_really' filenames.
-
Every handover requires someone to explain 'the system' in a 45-minute call.
-
Regulators / auditors / customers need a trail — you've got scattered emails.
-
Three different teams run the same process with slightly different assumptions.
The customer payoff
What changes
What you feel once it’s running.
A system of record — every action logged, every state visible.
-
Enforced process — the software doesn't let you skip the step that matters.
-
Analytics-ready data out of the box.
-
Onboarding that's a 20-minute click-through instead of a 45-minute call.
Phases
⏱ 6–10 weeks typicalHow Process Digitisation actually runs.
-
01
Map
Sit with the team running the current process. Draw the state machine they actually use, not the one on the wiki."
-
02
Define
States, transitions, roles, permissions, notifications. Agreed on paper before anything is built."
-
03
Build
Internal tool (React + API + Postgres typically) with workflow engine. Deploy incrementally — each state transition ships as it's ready."
-
04
Migrate
Current in-flight work is moved into the system with the team. Old spreadsheet is archived, not just ignored."
The hand-off
You'll run with
What lands in your hands — every artefact, nothing hidden.
-
Production internal tool on your infra
-
State machine documented + diagrammed
-
Role-based permissions (who can do what)
-
Audit trail — every action, by whom, when
-
Analytics exports (CSV + direct BI connection)
-
Onboarding guide for new team members
Questions we get
-
Q·01 Isn't this just a workflow tool like Monday or Asana?
Sometimes yes — if your process maps cleanly onto Asana, we'll tell you so and not build you a bespoke tool. We build custom when off-the-shelf rules engines can't express your actual business rules."
-
Q·02 How custom is 'custom'?
We default to well-trodden stack (React, Node, Postgres). Custom is the business logic and data model, not the foundations."
-
Q·03 Can we integrate with our existing ERP/CRM?
Yes — usually critical. Webhooks + API integration are part of scope from day one."
-
Q·04 What about the people who hate software?
We design with them specifically. Minimum friction entry, sensible defaults, bulk operations for power users. If the tool is worse than the spreadsheet, no one will use it — we know."
-
Q·05 Can you train the team?
Two training sessions + written guide included. Optional office-hours retainer for the first 90 days."
Ready to start
Make the process real.
Two-day observation, honest scope, fit-for-purpose build. Tell us which spreadsheet is costing you the most.
Digitise a processThe wider map
Every service page at a glance.
Each link below opens a dedicated page on that specific piece of one of our four service pillars. Jump sideways — different service, same way of working.
Digital Product Strategy
Service overview →Web & Mobile Development
Service overview →Business Automation
Service overview →- 01 Workflow Automation
- 02 AI-Assisted Operations
- 03 Process Digitisation — you’re here
- 04 Custom Internal Tools
- 05 System Integration & APIs
- 06 Data Pipelines & ETL