Company
Partner with us.
Refer the work, or build alongside us.
Two ways this works.
Both are straightforward, and both are written down before anything starts. We already work this way with a handful of partners.
For people with the relationship, not the delivery team
Refer business
You know an organisation with a problem we are built for. Introduce us, stay as involved as you want to be, and take a significant share of the deal when it signs.
- A significant share of the engagement value, agreed in writing before the introduction
- You choose how involved you stay, from an introduction to sitting in every review
- We tell you early and plainly when a referral is not a fit, rather than sitting on it
For firms with complementary services
Partner on delivery
You do something we do not, and the client needs both. We are glad to build alongside firms whose work complements ours: design, domain consultancy, hardware, regulatory. We already do with a handful of partners.
- Clear split of scope and accountability, set before the engagement starts
- Our engineering standard applies to our side of the line, whoever leads the client relationship
- Joint pursuit where it makes sense, and a straight answer where it does not
What our partners say.
Engineering standards
SDLC, code review, security controls, data residency by hub, how AI tooling is used on your code and what is excluded. Enough to pre-answer most of a standard security questionnaire.
Request the standards pack →Commercials
Rate bands, which legal entity contracts by region, IP ownership, notice periods and engagement minimums, stated plainly, so you can qualify us before a call.
Ask for the rate card →Apply.
A few lines is plenty. It reaches the people who would run the partnership, and they will come back to you directly.


