$0 to build
No deposit. No build invoice. You pay nothing while we build it.
Custom software. $0 to build. Pay monthly, only after it works.
You get the software. We keep the rights and may offer it to other businesses. Cancel at the end of any month and take your data with you.
Build it yourself, and you carry the risk.
Software costs almost nothing to start now. Then it breaks. The fixes and the upkeep land on you. Nobody is paid to talk you out of a bad build either. Our answer: your software has one owner responsible for keeping it running: the one who's paid monthly for it.
What the deal gives you.
One monthly price, written before we start
The monthly price, and how long it stays fixed, go on paper before any work starts.
Leave any month
Cancel at the end of any month, no fee. Your data comes out within 7 days, as CSV or JSON.
We turn work down on purpose.
Three things have to be true before we take a build. Miss one and we say no in writing. It saves us both a bad project.
What we take
- An industry with at least a few hundred similar businesses.
- A problem those businesses share, not a quirk of one firm.
- A client who accepts that we own the software and may resell it, even to competitors.
What we turn away
- Venture builds where the code itself is your edge.
- Regulated and procurement-bound firms that need to own the code.
- One-time payers who want to buy the code outright.
- Industries without a few hundred similar companies.
- One-off features the rest of your industry would not fund.
Not a fit? We'll say so quickly, in writing.
How a build runs.
Five steps. You pay nothing until step four.
-
We talk.
We check the three things above. Wrong fit, we say no.
-
We write it down.
A signed spec, a written acceptance test, and the monthly price.
-
We build it.
You pay nothing. No deposit, no build invoice.
-
The test passes.
The subscription starts that day, and not before.
-
We keep it running.
Cancel at the end of any month. Your data leaves with you.
Case studies and blog.
One case study per product, as they ship. Plus posts about how this works and why.
Case studies
The first case study lands after the first product passes its acceptance test.
It will say what the problem was, and what the acceptance test required. Then it will say what the product now does for a second company in the same industry.
Still the one keeping it alive?
Tell us what the software should do. We'll tell you if we'll build it, and what it costs a month.
Book a call