01
We read it first
Before a line changes, we map what is already there. One week, one fixed fee, and the document is yours whether or not you hire us for the build.
We take on the systems other people have stopped maintaining. Java, mostly. A small team, a long horizon, and a written record of why every part of it works.
Before a line changes, we map what is already there. One week, one fixed fee, and the document is yours whether or not you hire us for the build.
Java, Kotlin, Postgres, and as little else as we can get away with. Fewer moving parts means fewer people are needed to keep it moving at three in the morning.
Every engagement ends with your people able to run it without us. If you still need us in year three, we did the first year badly.
RiggsSoft is a four-person engineering practice in Ealing. Between us we have spent the better part of fifteen years inside payment rails, freight scheduling and the sort of back-office Java that a business only notices on the day it stops. That work is where our habits come from.
We keep the team small on purpose. Four people can hold an entire system in their heads; twelve cannot, and the difference shows up in the handover document. We don't do brand work, design sprints, or apps built to impress an investor. If the problem isn't a system that has to keep running on Monday, we're the wrong firm and we'll say so on the call.
Everything we ship is written down: what it does, what it assumes, and what breaks it. Not because auditors ask, but because the person on call in two years won't be able to ask us.
Tick anything that sounds like your problem — it carries through to the form at the bottom of the page.
Prices are a guide. The audit fixes them in writing before anything is built. We quote for the work, not the hours — you'll know the number before we start.
A thirty-minute call, no charge and no deck. If we're not the right firm for it, we'll tell you who is.