Design partners.

Each month we take on two businesses to build software with. You bring a real problem. We build the software to your specification, properly, and it shapes a product other businesses will use.

Apply

Who fits

A problem you or your team hit every week
You would use the software the day it existed
Others who do your kind of work probably have the same problem
You can tell us honestly what works and what does not, as it is built

We turn down anything illegal, and we tell you plainly when a problem is outside what we do well.

What you get

Software built to your specification, through the factory, ready for real users
Senior engineers you talk to directly, from the first requirement to the release
A say in a product made for people who work like you
A small business pays only the running costs: hosting, app store fees and the like. Larger businesses pay on terms that grow with their size. An enterprise starts with a proof of concept.

What we ask

Your requirements, and your time to get them right. How much depends on how big the build is.
Real use, and honest feedback while we build
The right to turn what we build into a product other businesses can use
The right to show the work and write about what we learned. We take credit for everything we build.

For an enterprise, a design partnership is a proof of concept: a real piece of your problem, built through the factory to your security and compliance standards, as the first step to a larger build, or to a factory of your own.

How it works

Apply, on a short call with our agent or by email: what you would build, who would use it, and what the problem costs you today.
A call, so we understand the work and you can ask us anything.
We choose. We take on at most two new partners a month, and we tell you either way.
We agree the terms in writing, including who owns what. It depends on the partnership, so we settle it before we start.
We write the requirements together.
We build in short cycles, and you use each piece as it lands.
It ships, and it becomes a product.

Why we do this

Our factory gets better every time it builds something real. Each build finds a check it was missing, a requirement nobody wrote down, an edge case that only shows up with real users, and the next build starts from there. We would rather it learned from your problem than from a toy.

Startly, Rhystic Collect and Grain Smith each went from first spec to a usable product in under a week. We want to keep proving that software built this way holds up under the edge cases, the scale, the compliance review and the person using it on a phone, and only real problems can show that.

Tell us what you would build.

Three questions are enough to start: what you would build, who would use it, and what the problem costs you today. Answer them on a short call with our agent, or by email, and an engineer reads every one.

A voice call with our AI agent. It asks three questions and passes your answers to us.

Apply by email