Skip to content

Custom software

Theproductaroundthemodel

Interfaces, integrations, permissions and billing — the platform that turns a capability into something you can sell.

A model that works is not a product. Someone has to review its output, correct it, and be accountable for it. That surface is where most of the actual engineering lives, and it is what customers are buying.

You might recognise

  • The AI works but there is no interface anyone could operate
  • Every customer needs a slightly different integration
  • No audit trail, which blocks every enterprise deal
  • Permissions were an afterthought and now block the roadmap

How we work through it

  1. 01

    Design for correction

    Any system with a probabilistic component needs a human path to review and override. Designing that in from the start is far cheaper than retrofitting it.

  2. 02

    Make the audit trail primary

    Who saw what, who changed what, what the system decided and on what basis. Enterprise buyers ask, and it is painful to add later.

  3. 03

    Integrate once

    One well-designed integration layer rather than a bespoke connector per customer.

  4. 04

    Ship in slices

    Something usable in production every two weeks, so feedback arrives while it can still change the design.

What you are left holding

Everything ships into your repositories and your cloud. There is no runtime dependency on us after handover — that is the point.

  • The application, in your repos, with tests
  • Integration layer and API documentation
  • Role-based permissions and a complete audit trail
  • Deployment pipeline and environments
  • Handover to the team who will maintain it

Questions we get

What stack do you build on?
TypeScript end to end by default — Next.js and Postgres unless there is a reason not to. If your team already has a stack they maintain, we build in that instead. Handover matters more than our preferences.
Do you do design as well?
Yes. Interface design is part of the engagement rather than a separate phase, because for this kind of product the interaction design and the system design constrain each other.

Have a problem shaped like this?

Thirty minutes, no deck. Bring the thing that is not working and we will tell you what we would do about it — including when the answer is that you do not need us.

We reply within one business day