What we build
Most engagements start with one. Every one of them follows the same four steps: audit, scope, build, handover. Below is what each includes and who it fits.
SaaS, web applications and internal platforms, designed and built so you own and operate them.
A good fit when
You have a product idea or an internal tool that spreadsheets and off-the-shelf software no longer cover.
What's included
AI-assisted tools and automation, built into how your business already works rather than bolted on the side.
A good fit when
A team is doing the same knowledge work by hand, and the inputs already live in systems you control.
What's included
Implementation, integration, customisation, maintenance and support for the systems you already run.
A good fit when
Something exists and works, but not well enough, and you'd rather fix it than replace it.
What's included
Software and skills-based advisory for teams making a technology, systems or process decision.
A good fit when
You're about to spend money on technology and want an independent read before you do.
What's included
Courses, workshops and training in software and technology skills, and the material that goes with them.
A good fit when
Your people need to get good at a tool or a practice, and generic training hasn't stuck.
What's included
How we scope
Scope drift is the single biggest threat to any fixed-price engagement. These four rules go in every proposal.
What's in, what's out, the timeline and the price. Signed off before anything is built.
One design or technical direction is presented and refined, not three to pick from.
The proposal names what we won't do. It is not discovered halfway through.
A recorded walkthrough, documentation and access in your name. The engagement ends when you can run it.
Describe the problem, not the solution. We'll tell you which of the five it is, and whether it's worth doing.