
We build software, and we run it.
Most of what breaks in a business isn’t the software — it’s the process nobody wrote down. We work that out first, build the system around it, and stay on to run it. Our own products are in production, so we’ve already lived with the decisions.
You don’t need to arrive with a spec. That’s the first thing we do.
Some of the organisations we’ve built for.
We build software for how organisations actually run.




8+
Years building business process automation
Workflows, approvals and internal systems for operating businesses
10+
Clients served
Organisations whose processes we’ve moved into software
100%
Systems we still run
Every system we’ve built, we’re still the ones operating it
We design
and build
software
Design, engineering, and the judgement to say which parts of a problem should not become software at all.
[01]
[02]
[03]
[04]
[05]

A plan you can build from
We map how the work runs now, find where it breaks, and write down what should be built. You get that document whether or not we build it. Sometimes it says build nothing.

Screens before code
We design the screens and the flow between them before anything is built, so you can see the thing and change it while changing it is still cheap.

Sites, portals, internal systems
Anything that runs in a browser — a marketing site, a customer portal, or the system your staff work in all day. Built so your team can change the content without us.

Android and iOS
Apps for people working away from a desk — on patchy connections, older devices, and often one-handed. Built as properly as the web work, not as an afterthought to it.

After launch, indefinitely
Fixes, changes, and the report someone suddenly needs at month-end. The same people who built it stay on it — there is no support tier to be handed to.
What we’ve built
Some of it runs inside other organisations — approvals, procurement, scheduling. Some of it is ours. Requests that took months now take weeks.
Brand Strategy
Web Design
Product Interface (UI)
Visual Storytelling
Creative Campaign
Tell us what's not working.
No pricing page. No fixed package. Just what happens after you get in touch.
We talk about what's actually happening
You describe the process as it runs today — where it breaks, who's chasing what, what's held together by habit. No spec required.
A real conversation, not a sales call
You don't need to know what to build yet
We work out what should exist
We map the process, find where software actually helps, and say plainly if something shouldn't be built at all.
A written account of how the process runs today
A straight answer if the fix isn't software
We scope the build
Once we agree what's worth building, we say what it takes to build it — in writing, before any code starts.
A proposal you can hold us to
Nothing starts until you've seen it
We build it, and stay on it
Design and engineering on the actual system, then we keep running it — fixes, changes, and being reachable after launch.
The people who built it are who you reach afterwards
No support tier to be handed to
Questions people ask before getting in touch
What working with us actually involves, and what to do if you’re not sure what you need.
We know something’s wrong but not what to build. Is that a problem?
No — that’s the normal starting point, and working it out is part of the job. You don’t need a spec.
What if software isn’t the answer?
Sometimes it isn’t. A changed policy, or a tool you already pay for. We’ll say so before you spend anything.
What happens to the system after it’s built?
We stay on to run it. The people who built it are the people you reach afterwards.
Do we have to replace everything we already use?
Usually not. Most work involves making existing tools talk to each other rather than starting over.
What the people we’ve built for say
Some of the people we’ve built for, in their own words.
Stories, strategies, and digital thinking.
-
1 min read
Our creative workflow, defined
[[TODO: placeholder excerpt]] How a project moves from a first conversation to something running in production.
-
1 min read
Digital trends to watch in 2026
[[TODO: placeholder excerpt]] Notes on the tools and habits changing how small engineering teams ship software this year.
-
1 min read
The power of minimalist design
[[TODO: placeholder excerpt]] A short look at why restraint tends to outlast decoration in interfaces that people use every day.














