We build the thingSoftware development

How we approach it

Most of what we build is a system somebody runs their business on: a platform with real users, real money moving through it, and a real cost to being down. That shapes everything — schema design, error handling, the boring parts that decide whether it is still working in three years.

We work in whatever the problem needs rather than whatever we sell. Rust where it has to be fast or provably correct, TypeScript and React where the interface is the product, Python where the data and models live, Go and C++ where they fit. Nine languages in production across our own systems, and the choice is argued rather than assumed.

Every build ships with the things that get skipped: automated tests on the paths that matter, structured logging, a deployment that one person can run, and documentation a new developer can start from.

What you get

• Architecture and schema design before any code
• The application, built in reviewable stages
• API design and documentation, OpenAPI where it is public
• Automated tests on the paths where failure costs money
• CI, deployment and rollback that your team can run
• Source code, accounts and domains in your business name

Typical timeline: Six to twenty weeks depending on scope.

What we have built with this

10 of our own systems use this discipline. Every one is ours, and the ones marked open source are yours to read. The whole product line →

Client work and public source

• WeftScript
• MatchPoints

Where this comes up

How we work

We talk it through

A conversation about the problem, not a sales pitch. If we are not the right people for the job we will say so and point you somewhere better. Free, and there is no obligation after it.

You get a written quote

A fixed price for a fixed scope, in plain English, with a delivery date. No hourly billing that quietly doubles. If the scope changes later, you approve the change and its cost before any work starts.

We build it in stages

You see working software every week or two, not a status report. That means you can course-correct early, while it is still cheap to change your mind.

You take ownership

At handover you receive the source code, the accounts, the domains and the documentation, all in your business name. Nothing stays locked to us. You could hire anyone else tomorrow and they could pick it up.

We look after it

An ongoing support agreement, or on-call as you need it. Your choice, and you can change or end it whenever you like.