You bring
- Deep knowledge of the problem and the people who have it
- First customers: ideally three or more committed pilots or letters of intent
- A decision-maker available every week
- Part of the build cost in cash
Co-create
For operators and industry experts who have found a problem worth solving, and the customers who will pay for it. We join as co-builders: a lower cash fee, shared upside, and the same accountability as any client build.
Three kinds of people we co-create with.
A business with an internal tool others would buy.
Your team built a process, sheet or system that solves a problem your whole industry has.
Quick Safa started this way, from how a packaging plant prices a carton.
An industry expert with access to the market.
You know the workflow, the buyers and what they pay today. You need a product team you can trust.
A company starting a digital line of business.
A new service, portal or platform alongside your core business, built and run without hiring a full product team.
What each side brings.
We bring
- Product, architecture, engineering and AI
- Hosting, support and the release process we use on every client build
- A named lead, fortnightly demos and a written weekly status
- Lessons from running our own product in production
How it works
From a fit call to paying customers.
Every step has a stop point, and the terms are in writing before anything is built.
Fit call (free)
We look at the problem, the market and who's already paying for a worse answer. If it isn't a fit, you hear it on the call.
Validation sprint (2–3 weeks, fixed price)
Customer interviews, scope, a clickable prototype and the numbers: cost to build, cost to run, and what customers would pay.
Agreement
A reduced build fee in exchange for equity or a revenue share, set out in writing before any build starts.
Build to first paying customers (typically 8–12 weeks)
Small fixed-scope releases, a demo every two weeks, live with your pilot customers.
Grow together
We run, support and improve the product. You can buy out our share at a formula agreed on day one.
What you can count on.
Clear ownership
Who owns the code, the company and the customers is written down before work starts.
A way out for both sides
Agreed stop points after validation and after the first release, and a pre-agreed buy-out.
Same standards as client work
Fixed scope per release, demos, weekly status, a named lead.
Selective by design
We take on a small number of co-create projects each year, so each gets a full team.
What we don’t take on
- Ideas without a clear customer who pays today for a worse answer
- “Build it for free in exchange for equity”
- Projects where you need us to find and sell to the customers
- Anything that only works if a large platform changes its rules for you
Questions people ask
- Who owns the product?
- It's set out in the agreement, usually a shared company or a written IP assignment. Nothing is assumed.
- What if the validation sprint says no?
- Then you've paid a fixed price to avoid a much bigger mistake, and you keep the research and prototype.
- Can I buy you out later?
- Yes, at a formula agreed before the build starts.
- Do you help sell?
- We help with product, pricing and onboarding. Selling is yours; it's why we ask for first customers up front.
Have a problem your industry would pay to solve?
Tell us the problem, who has it, and what they use today. We reply within one business day.
We reply within one business day. If we are not the right fit, we will tell you.