How we work
A clear first step. Room to learn.
You don’t need to arrive with a technical brief. You do need a problem worth solving, and a willingness to look at how the work happens.
From the problem
to something useful.
Each stage should leave you better informed about what to do next.
Understand
Talk through the business, the people and the process. Work out what is getting in the way and what a better outcome would look like.
Scope
Agree a useful first stage, its deliverables, price and boundaries. Identify anything that needs a closer look before a larger commitment.
Build & test
Try the work with realistic tasks and the people who will use it. Review what works, what needs changing and what is ready to release.
Hand over & improve
Make ownership and support clear. Leave useful documentation, explain how the system works and agree any ongoing care.
A few practical
questions.
How much does a project cost?
It depends on the problem and what needs connecting or building. We agree the scope and price of the first stage before work starts. If there is too much uncertainty to price a build, we propose a discovery stage first.
Can we start small?
Yes. A single workflow, a focused audit or a testable prototype is often a useful first engagement.
Do we need new software?
Not necessarily. A better process, an existing product or a connection between tools may be enough.
What happens after launch?
We agree the handover and any maintenance before launch. Ongoing support or improvements can be scoped separately.
Can you also help with branding and design?
Design work now lives at Datum Works. If the project needs both design and systems work, we can discuss how the two fit together.
Bring the unfinished brief.
A few sentences about the problem are enough to begin a conversation.
Start a project