Software Was Built for Everyone. Soon It's Built for You.

Every piece of software you use was designed for a crowd. Your email app, your calendar, your accounting tool, the spreadsheet you've bent into a shape it was never meant to hold. None of it was built for you. It was built for a million people who are roughly, approximately, sort of like you.

That's the deal we've all quietly accepted for about 40 years. You find the tool that fits best, and then you spend the rest of your time molding your work to fit the tool. The gap between "what I actually need" and "what the software does" is just the cost of doing business.

Here's the thing worth paying attention to right now: that gap is starting to close. And not in the way software companies usually promise.

The old bargain

Think about why software works the way it does. Building an app is expensive and slow. To justify the cost, a company has to sell it to as many people as possible. So every feature is a compromise. It has to be useful to the freelancer in Ohio and the 200-person firm in Munich and the guy who bought it by accident and never opened it.

The result is software that's a little too much and a little too little at the same time. Fourteen buttons you'll never touch, and the one thing you actually want buried three menus deep or missing entirely. You adapt. Everyone adapts. It's so normal we stopped noticing we were doing it.

The whole industry of "workflows" and "integrations" and "power user tips" exists because the tools don't quite fit, and we've all agreed to meet them halfway.

What's actually changing

Over the past year, something small but genuinely new started showing up. People with no technical background are building their own software. Not buying it. Building it. And not because they learned to code, but because they can now describe what they want in plain English and get something working back.

TechCrunch has a name for it: micro apps, or sometimes "fleeting apps." Little tools built for one person or one small group, used for as long as they're useful, then thrown away without a second thought. A woman named Rebecca Yu built an app in a week to help her friends stop arguing about where to eat. A guy in San Francisco built himself a tool to automatically deal with parking tickets. People are building personal trackers, tiny internal tools for their teams, one-off calculators for a specific decision they're facing this month.

None of these would ever exist as commercial products. The market for "help my specific friend group pick a restaurant" is exactly zero. But that was always the point of the crowd model: if a problem only affects you, nobody was ever going to build the fix. Now you can.

The tools making this possible have unglamorous names, Claude, ChatGPT, Replit, Bolt, Lovable, and a growing pile of others. What they share is a simple shift. You stop clicking through someone else's menus and start describing the thing you wish existed.

Why this is a bigger deal than it looks

It's easy to file this under "neat, another tech thing." But step back and the implication is larger than any single app.

For four decades, software has been a product. Something made by a company, packaged, sold, and shipped to you. What's starting now is software as something closer to a sentence. You say what you want, and the thing appears. The distance between having an idea and having a tool that does it is collapsing from months and a budget down to an afternoon and a clear description.

That changes what's scarce. When building was the hard part, the people who could build held all the power. When building gets easy, the bottleneck moves somewhere else entirely: knowing exactly what you want. Being able to describe the problem clearly. Having the taste to know when the answer is right and the judgment to know when it's wrong.

If that sounds familiar, it's a pattern that shows up everywhere AI touches. The tools get more capable, and the advantage shifts from technical skill toward clear thinking and good questions. It's why the same AI can make one person sharper and another duller. The tool doesn't decide the outcome. What you bring to it does.

There's another quiet consequence: software gets to be disposable. We treat apps like furniture, something you buy, keep, and feel vaguely guilty about replacing. But a tool you can build in an hour is a tool you can throw away in a second. You make the thing for the problem in front of you, and when the problem's gone, so is the tool. No subscription, no migration, no "well, we're already paying for it, so we'll keep using it." That alone rewires how you think about what software is for.

The honest limits

Now, the part the excited headlines skip.

Personal software is fantastic for personal problems. It is not the answer to everything, and pretending otherwise will burn you.

A few places to be careful:

• Anything with real data or money. If a tool touches customer information, payments, or private records, "I built it myself in an afternoon" is a sentence that should make you nervous, not proud. Security and reliability are hard for reasons that don't go away just because building got easy.
• Anything that has to keep working. The magic of a fleeting app is that it's fleeting. The moment other people depend on your tool every day, you've quietly become responsible for maintaining software, and maintenance is where the real cost has always lived.
• Anything you don't understand. Getting a working tool without understanding what it does is a trap. If something breaks and you have no idea why, you don't have a tool. You have a liability with a nice interface.

The right instinct is the same one that applies to automation versus delegation: match the approach to the job. Build the throwaway tool for the throwaway problem. For the thing your business actually runs on, boring and proven still wins.

The mental model to carry out of here

You don't need to build anything this week to get value from this shift. You mostly need to change one question.

For 40 years, the question has been: "What tool does this?" You had a need, and you went shopping for the closest match, then made peace with the gap.

The new question is: "What would the perfect tool for exactly this look like?" Ask that honestly, without assuming it has to already exist, and you'll notice something. Half your daily friction comes from tools that almost fit. The report you rebuild by hand every month. The spreadsheet held together with tape and hope. The three apps you copy and paste between because none of them talk to each other.

Some of that is now buildable. Not all of it, not today, and not by everyone. But enough of it that "I wish there were a tool that just did X" is no longer the end of the sentence. It might be the start of one.

The generalists saw this coming, by the way. It's a big part of why "jack of all trades" stopped being an insult. When you can build the thing yourself, being the person who knows a little about a lot, and can describe exactly what you want, turns out to be worth quite a bit.

The interesting question

The tech press will spend the next year arguing about which app builder wins, which company gets bought, whose valuation is insane. That's the boring version of this story.

The interesting version is quieter and it's about you. For your entire working life, software has been something that arrived from somewhere else, shaped by strangers, and your job was to adapt to it. That arrangement is loosening. Not vanishing, not overnight, but loosening.

So the question worth sitting with isn't which tool to buy. It's this: what would you make if software finally bent to you, instead of the other way around?

Most people have never had reason to even ask. That's about to be the more interesting half of the job.