✦ Partnerships

Three ways we work together.

We co-build with institutions, founders and platform teams who need systems that hold up under regulation.

Start a conversation →See a build

Venture co-build

We take a product from architecture to production and stay on the hook for how it runs. Equity or a build fee, decided before the first commit.

  • Architecture owned end to end
  • Shared upside on what ships
  • A team that stays past launch

Systems rebuild

Your operation has outgrown its tooling. We read the workflow, redraw the boundaries, and rebuild the parts that carry the load.

  • Diagnostic before any code
  • Rebuild in place, no big bang cutover
  • Your team runs it at handover

Platform partnership

You have the distribution, we have the rails. Treasury, identity and health infrastructure built to sit behind your brand.

  • White label surfaces
  • Typed API contracts
  • Isolation you can show a regulator
The engagement

How the work actually runs.

  1. 01One to two weeks

    Diagnostic

    We sit with the operation and follow one real case end to end. What we produce is a map of where the work leaks, and a written recommendation you can act on with or without us.

  2. 02Two to three weeks

    Architecture

    Boundaries, data model, failure paths and the decisions we are deliberately rejecting. This is where we choose what the system will make impossible rather than merely discourage.

  3. 03Twelve weeks and up

    Build

    Interface, backend, data model and the automated layer shipped as one system. You see working software every two weeks, running against real data, not a staging fiction.

  4. 04Four weeks, overlapping

    Handover

    Your team runs it with us in the room, then without us. Runbooks, architecture notes and the reasoning behind each decision go with the code.

The fit

Where we help, and where we do not.

This is our work

  • The workflow is the product, and it is currently held together by people remembering things.
  • Money moves, records are kept, or a regulator can ask you to prove what happened.
  • You have an operation running today, with real users and real data behind it.
  • Someone on your side can make architectural decisions without a committee.

This is not

  • A design refresh over a system nobody has agreed on yet.
  • Staff augmentation, where the architecture is decided elsewhere and we only type.
  • A fixed scope written before anyone has looked at how the work actually runs.
  • Anything where the deadline is fixed, the scope is fixed, and neither can move.
Commercials

How the money is arranged.

Build fee
Fixed monthly, scoped in phases
A funded team that wants the system owned outright at the end.
Equity co-build
Reduced fee against equity
A venture at the start, where we carry part of the risk and share the upside.
Platform partnership
Licence plus integration fee
You hold the distribution and want our rails behind your brand.

Every arrangement is written down before the first commit: scope, ownership, what happens if we stop, and who runs it afterwards.

Questions

Asked before every build.

Do you work with teams that already have engineers?

Most of the time, yes. We take the parts that carry the load and the boundaries between them. Your engineers keep shipping product on top, and they are in the architecture conversations from the first week.

What happens to the code at the end?

You own it. Repositories, infrastructure, deployment and documentation transfer at handover. On equity co-builds the ownership question is settled in writing before the first commit.

Can we start with the diagnostic only?

Yes, and a good number of engagements end there. You get the map and the recommendation. If the right answer is that you do not need a rebuild, that is what the document will say.

How small is too small?

If the work fits inside a few weeks and does not change how the operation runs, we are the wrong shape for it. We are built for systems that have to hold up for years.

Have a problem worth solving?

Tell us what is not working, what you are trying to build, or where you want to go next.

Talk to us →Run a diagnostic
What happens next
01You describe the operation.
02We reply within one business day.
03If there is a fit, we tell you what the next step looks like.