How we work
We do not prescribe software before we understand the business
Good systems come from a clear understanding of how an organisation earns money, serves customers and gets work done. That understanding comes first. Technology follows.
Five steps from problem to result
Each engagement follows the same discipline, scaled to the size of the problem.
Understand the business
We learn how the organisation operates, where value is being lost and what opportunities exist. That means conversations with the people who run the work, a look at the current process and an honest discussion of constraints. You can expect questions, not a sales presentation.
Identify the opportunity
We identify the commercial, customer service or operational problem worth solving, and we say which problems are not worth solving yet. You receive a clear statement of the opportunity, the expected value and the main risks.
Design the solution
We agree the workflow, platform, integrations, responsibilities and measurable objectives. Scope, deliverables, fees and responsibilities on both sides are set out in writing before any build begins.
Build and implement
We develop, configure, integrate, test and deploy. You see working software early and often, so that problems surface while they are cheap to fix. Training and handover are part of implementation, not an afterthought.
Support and improve
Where agreed, we provide ongoing support, management, monitoring and improvement. Systems that serve a business should change as the business changes.
Principles we hold ourselves to
Honest assessment
If an opportunity is not worth building, we will say so, even when it means there is no project for us.
Measurable objectives
We agree what success looks like before we start, and we design the system to show whether it has been achieved.
Responsibilities in writing
Scope, deliverables, fees and who does what are documented and agreed. No surprises.
Security and privacy by design
Access controls, data minimisation and appropriate safeguards are part of the design, not added later.
Your data stays yours
The information in systems we build for you belongs to you, and you can take it with you.
People stay accountable
Automation and AI support decisions. They do not replace the people responsible for them.
How projects are scoped and priced
We scope every project according to the business need, technical complexity, integrations, implementation responsibilities and expected commercial value. A small workflow improvement and a multi-system platform are different undertakings, and we price them honestly as such.
We do not publish fixed packages. We do commit to explaining exactly what is included, what is not and why.
Start with a conversation
Describe the opportunity or challenge. We will tell you how we would approach it.