Bring your idea
You bring the idea. We build your tool, and we keep it running.
You do not pay for development. You subscribe once the tool is live, and we host and operate it on infrastructure we own — self-hosted, EU-resident, the same standard as everything else we run. It is built around your work, it carries your name, and your data stays yours and exportable.
Process
How it works
-
You describe the problem.
Not a specification — the work that is currently being done by hand, in a spreadsheet, or not at all. What it costs you, who does it, and what a better version would look like.
-
We tell you whether we will build it.
Some ideas fit what we already run, some are better solved by software that already exists, and we will say so. We take on a small number of builds at a time, so this is a real answer rather than a formality. Every idea gets an answer with a reason — a no is often “this is a normal paid project”, and we will quote it.
-
We build it.
There is no build fee, because the software stays ours — we own it, host it and operate it, and you subscribe to it. That is the same arrangement behind our own products.
-
We keep it running.
Hosting, updates, monitoring and the model layer underneath are ours to look after. Architecture, build and operations sit with one accountable team, which is how we work on everything.
Routes
Two ways in
Start from something we already run.
Our own products are built on an AI serving stack we own and operate — dictation, secrets management and long-form transcription, all running on our own hardware. If your idea is a version of one of these shaped to your work, most of the engineering already exists and what remains is the part that is specific to you.
Start from nothing.
If the idea does not resemble anything we run, we build it from the ground up. It goes on the same foundation — self-hosted models, infrastructure we control, and an operations team that has run software in regulated environments since 2020.
Operations
What “we run it” actually means
Operating software is the part most build-only arrangements leave to you. It is the part we keep.
Your tool runs on infrastructure we own and operate in the EU. Where it uses AI, the models are open models we serve ourselves — there is no third-party inference API in the data path, which means your data is not handed to anyone to be processed. Access is named, scoped and revocable. Data residency and retention are documented for your deployment rather than assumed.
This is not a special arrangement for this programme. It is the architecture behind our own products and the one we build for clients in banking and insurance, where data protection, availability and auditability are daily delivery constraints.
Fit
What makes an idea a good fit
The ideas that work best are small, specific and expensive to do by hand. A repetitive process somebody does every week. A judgement that needs the same three documents read every time. A recording, a form or a queue that a person is currently shepherding manually.
Two things matter more than how ambitious the idea is. First, that it is yours — you understand the work, so you can tell us when the software is wrong. Second, that it keeps being useful, because both sides only benefit from something that is still running in two years.
The programme rules
- One idea per organisation at a time.
- The scope note defines v1 before we start. Anything discovered later goes on the roadmap, not into the build.
- There is no build fee, because we keep the software and keep it running. There is a subscription with a minimum term, and it starts the day your tool goes live.
- We do not build consumer marketplaces, anything that needs a payments or banking licence, anything that depends on another company’s terms of service, or anything where a wrong output is a clinical or legal decision.
You do not need a specification, a budget or a technical contact. A description of the problem is enough to start.
FAQ
Frequently asked questions
Why is there no build fee?
There is no build fee because we keep the software. We own it, host it and operate it, and you pay a subscription for as long as you use it. You are not buying a codebase and we are not giving one away — you are subscribing to a working tool that somebody else builds and keeps running. If what you need is source code on your own servers, that is our client engineering work, it is a different conversation, and we will quote it.
Why would you build something without being paid for the build?
Because the arrangement only works if the software is still in use in two years, and that puts the risk on the right side. If we build something you stop using, we have spent the engineering and we carry it. That is a strong incentive to be honest with you about whether your idea will work before anyone starts — and to say no when we think it will not.
What does it cost?
A subscription, quoted for your tool once we both know what it is. We do not publish a price for this any more than we publish one for our engineering work, because what it costs depends on what is being built and run. You will have a number before anything is built, and there is nothing to pay before that.
Who owns the software and the data in it?
Your data is yours — all of it, exportable, and EU-resident. The code is ours, and that is why there is no build fee: we keep the software, host it and keep it running, and you subscribe for as long as you use it. Data residency and retention are written down for your deployment rather than assumed. If your idea involves something we can only build with your input, we agree the terms in writing before we start.
Do you build for everyone who asks?
No. We take on a small number of builds at a time, and we want each of them to work. Some ideas are better served by software that already exists, and we will tell you that instead of building a worse version of it. You will get a direct answer either way.
Is this only for AI tools?
No. AI is the part we are best known for — we adapt, serve and operate open models on our own infrastructure — but most useful software is ordinary software. Plenty of good ideas are a web application, an integration between two systems that do not talk, or a process that currently lives in a spreadsheet. If AI genuinely helps, we will use it; if it does not, we will say so.
How long does it take?
That depends entirely on what it is, so we will not give you a number here that we would have to revise. What we will do is tell you the shape of it when we take the idea on: what we build first, what you will be able to try, and what comes after. We would rather set that out once, accurately, than quote a duration before we understand the problem.