What "unlimited development" actually means
Unlimited development means no cap on how many requests you queue or how many get completed in a month, with the practical limit being how fast you can review work rather than how fast anyone can build it.
“Unlimited” is doing a lot of work in that phrase, so it is worth saying plainly what it does and does not mean, including where our own version of it is a bad fit.
What is actually unlimited?
Two things: how many requests you put in the queue, and how many get finished in a month. Neither is capped, and neither is metered.
What is not unlimited is simultaneity. Work goes through a queue, in the order you set. You can reorder it whenever you like, and adding something urgent costs nothing, but it does not make everything happen at once.
If that sounds like a caveat that swallows the promise, consider the alternative: a cap. Ten requests a month means someone counts, and once someone counts you start rationing. You stop asking for the small annoying fix because you are saving your allowance for something bigger, which is exactly the behaviour that leaves software half-finished.
So where is the real limit?
You. Almost always.
Work comes back and someone has to look at it, decide whether it is right, and say so. In practice that is the bottleneck in nearly every engagement: not building capacity, but review capacity. A client who reviews daily gets several times the throughput of one who reviews when they remember, on identical terms.
This is worth knowing before you buy, because it tells you what you need to bring: one person with authority who can look at things quickly. Not a committee.
Is it cheaper?
Sometimes. That is not really the argument.
The argument is that it removes the negotiation. Under a fixed scope, every change of mind is a commercial event: a change order, an estimate, a conversation about what was agreed in March. That friction has a cost you never see on an invoice: it makes you stop asking for things.
Under a subscription, changing your mind in week two is free. You reorder the queue. Nobody has to be right about the plan.
Who is it wrong for?
Genuinely several situations, and we would rather say so now.
- You need someone embedded. In standups every morning, in the internal Slack all day, part of the team. Hire.
- Nobody can review. If the person who has to approve things is travelling three weeks a month, the queue stalls and you are paying for capacity you cannot consume.
- The work is genuinely finished. Some software is done. Paying monthly for a system that needs nothing is a subscription to nothing.
What does the month actually look like?
A call, then a shared board. You add requests however suits you: a paragraph, a screenshot, a voice note. We work down the list in your order, first delivery usually within a few working days. You review, send things back as many times as needed, and revisions are never treated as new requests.
If priorities change, you drag things around. Nobody has to be told.
The honest summary
Unlimited means the commercial friction is gone, not that physics is. You get a team’s continuous attention for a known monthly number, and the constraint moves from “what did we agree” to “how fast can you look at things”.
For most small businesses that is a much better constraint to have, whether you need a month of it or a year of it.