The Selfie Software Era Is Here

A couple years ago, every product announcement was an AI announcement, and it became comical. But it was predictable — the VC tech arena demanded it. Slapping AI on the box was the cheapest hedge against being left behind in the next big payday. Now the next push from the C-suite is here: every employee using agentic coding tools — Claude Code, Cursor, and the rest — to build their own internal software and boost their own output.

The desire isn’t new. The options to boost productivity have always been the same: buy something off the shelf, or build it internally. What’s changed is that building internally now requires a fraction of the staff and budget it used to.

Call it Selfie Software. Quick. Personal. Built by you, for you, on your own terms.

Built For The Way You Actually Work

Getting an internal tool built used to be hard enough that most teams didn’t bother. You’d float the idea, someone would say “yeah we should build that,” and a year later you were still using the same shared spreadsheet. The tools that did get built had to be important enough to justify pulling an engineer off customer-facing work, which wasn’t most of them. And when internal tools did get built, they became the lowest priority for an engineering team to fix defects and polish UX.

Agentic coding changes the math. An employee who knows what their workflow actually needs can build it themselves, without waiting on a platform team that was never going to prioritize it anyway. Some are building for themselves, others for their teams.

This is the genuinely good part. Every team has gaps that no SaaS product is ever going to fill — the connecting tissue between two tools, the report your manager wants every Friday in a format that doesn’t exist in any dashboard, the workflow quirk specific to your industry. These are things employees have always lived with because nobody was going to build them. Now they can be built to reduce headaches and potentially shave an hours of work off their workflow, that’s a meaningful productivity gain.

When The Bill Comes Due

The cost of software was never really the cost to build. It was the cost to maintain. When executives hand out a blank check for everyone to build software, the result is a kind of wild west. Marketers, analysts, ops people, and account managers spin up tools that touch real company data, and almost none of them were built by someone whose job it is to think about what makes software actually work.

Agentic coding tools are excellent at writing code. That was never the hard part. The hard part has always been everything around the code — knowing what to ask for, whether the thing you built is secure, whether it handles private data the way the law says it has to, whether it’s about to silently delete a column someone in finance depends on. These questions don’t go away because the code got easier to write. Engineers and product owners don’t escape the work — they just get pulled in later, usually after something has already gone wrong.

There’s a literal bill too. When every employee is making agent calls throughout the day, token costs add up fast, and operating expenses can climb in ways that weren’t part of the pitch.

Every Selfie Software artifact is a future maintenance burden someone else inherits. The author moves on, dependencies rot, and what looked like a productivity win this quarter starts to look like a pile of abandoned tools, security holes, and quiet data problems three quarters later.

The Boring Companies Win

The companies that get this right won’t be the ones moving fastest to put agentic coding in everyone’s hands. They’ll be the ones moving deliberately — setting guidelines before the gates open. Defining what kinds of tools employees can build, what production data is allowed near them, what counts as a real owner, and what happens when the person who built something leaves. The point isn’t to slow people down. It’s to make sure that what gets built becomes an asset instead of a liability.