When everything can be built, the real question is what is worth building

Software is no longer the limiting factor. Features get built quickly, cheaply, more or less on demand. What used to take months and a team now takes a fraction of that. In practice, almost anything can be built.

That sounds liberating. It usually isn't.

Technical limits used to do half the deciding for you. Plenty of ideas simply weren't feasible, so they filtered themselves out before anyone had to argue about them.

Take the barrier away and an organization is left holding every option at once, with nothing telling it which ones matter. More choices, less clarity.

Nobody experiences their business as a list of features. They experience problems that take too long to solve, money leaking somewhere nobody can point at, decisions made on weak information, opportunities noticed a week late.

Turning that into the right change to a system is not obvious work.

So when someone asks “what do you want?”, it sounds like service. It quietly assumes the other side already knows which change creates the most value. Most don't. What comes back is a wish list, an internal compromise, or a priority order that moves every month.

Once building stops being hard, the bottleneck moves up a level. Progress isn't blocked by execution anymore. It's blocked by the decisions that point the execution somewhere.

Bad prioritization rarely looks like nothing happening. It looks like a great deal happening to no measurable effect. Features ship, the system grows, complexity climbs, and nobody can say what any of it was worth.

The question stops being what is possible and becomes what is most worth doing right now.

When almost everything can be built, choosing beats delivering. The advantage goes to whoever can tell an organization which changes actually make a difference.

That's the job we've taken. Everything can be built here. The value is in working out what to build first.