Software a business can still change in five years
What we actually believe
Almost anything can be built once.
The expensive part is never the first version.
A demo takes a fortnight, and a first version that impresses in a meeting stopped being a hard problem some years ago. What is hard is the same system two years later: when the person who wrote it has moved on, when the process it modelled has changed twice since, and when nobody left can say with confidence what breaks if they touch it.
That second cost is the one we design against. It is why we map a process before proposing a system, why documentation and tests are part of delivery rather than the phase that gets cut when the date slips, and why we will say out loud that a client’s existing software is fine and the problem is somewhere else.
It is also why we treat the data as part of the build rather than a by-product of it. A system produces a record whether anyone designed one or not. Designing it deliberately is the difference between a business that can answer a question and one that has to estimate.
How we work
Four commitments, and what each one costs us
None of these are free to hold. Each one is a decision to be slower, smaller or less agreeable than we could be, and each one is why the work is still standing later.
Understand before proposing
The real process includes the parts that live in spreadsheets, side channels and habit. A system designed from the org chart models a business nobody actually works in.
The smallest thing that holds
The smallest system that solves the problem is the one most likely to still be running in five years. Scope is a design decision, not the outcome of a negotiation.
Say the inconvenient thing
Sometimes the recommendation is to improve what exists, buy something off the shelf, or wait. We would rather lose the work than win it on a plan we do not believe in.
Leave it changeable
Tests, documentation and a release anyone on the team can perform are part of delivery. A system nobody dares touch has already begun to rot, however well it runs today.
By omission
Three things you will not find on this site
You have just scrolled past the evidence for all three. Their absence is the argument — it is the part of this page you can check rather than take our word for.
A client logo wall
We publish a client’s name when they have given us permission in writing, and not before. Most of what we build sits inside businesses that would rather it stayed there.
Statistics
No percentages, no uptime figures, no count of businesses served. A number on a page like this is either audited or invented, and ours are not audited.
Certification badges
We describe what we can do and how we do it. Where a compliance standard matters to your engagement, ask directly and you will get a straight answer rather than an icon.
Work with us
We will tell you plainly if we are wrong for it
Describe what you are trying to build or fix. If the honest answer is that you need something smaller, something you already own, or somebody else, that is the answer you will get.