Automation · Custom software · ERP
Automation between the systems you already use, custom internal tools, ERP customisation and migration, and the integrations that hold them together.
What we do
The work in this practice is almost always inside software that is running, that people depend on daily, and that has to keep working while it is changed. That shapes how we work as much as what we build.
Hand-offs between systems that currently run on people, made to run on their own: scheduled jobs, monitoring, messaging and integrations across Microsoft 365, storage, telephony, the ERP and line-of-business tools.
Purpose-built applications for one team or one process when nothing off the shelf fits, and rebuilding vendor-held or dying systems on platforms the business already pays for.
Features built inside the ERP for how the business actually works: bulk operations, workflow tools, validation and safeguards, reporting.
Moving a business off a legacy system into a modern ERP with the data mapped, ordered, validated and taken through go-live, on hosting we can provision and run; and taking over implementations that have stalled.
How an engagement runs
We assess first, then agree the scope and price in writing before any build starts. Each stage stands on its own.
Enough to tell you whether this is our kind of problem. If it is not, we say so and point you towards what is.
We read the system you have, or the process a new tool has to serve, and hand you a document you own: what exists today, what should change, what that would take, and what to leave alone. You can act on it with or without us.
Quoted from what the assessment found, in writing, with the deliverables named. If the scope changes along the way, it is agreed as a change, with its own cost.
Who this is for
We take a small number of engagements at a time and do them properly. Both lists are here so you can tell quickly whether to write.
Who does the work
The person who reads your first message is the person who reads your code, maps your data, writes the assessment and builds the work. There is no account manager in between and no junior team the work is passed to afterwards.
You work directly with the engineer delivering your project, from the first discussion through implementation and handover. This page stays about the work: we operate under agreement and publish nothing that identifies a client or an employer.
After handover the system is documented and yours, so your own team or any other engineer can maintain it. If you want us to keep looking after it, that is agreed as its own fixed scope. Nothing about the build depends on one person staying available, and that is deliberate.
Start here
The system you have, the process you want to improve, or the tool you need built. If it is not our kind of problem, the reply will say so and point you towards what is.
