A ticket landed for my team this morning. It was written in plain Vietnamese. It said what changed, why we changed it, and what users will notice. Our support person read it over her coffee and knew exactly what to tell customers. She has never learned a project management tool in her life. And nobody opened one to write that ticket either.
For most of my career, buying software for a team worked one way. You picked the big tool. Then you bent the team around it. Training sessions. Workflows renamed to match the tool’s vocabulary. And when something felt awkward, the answer was always the same: that’s just how the tool works.
I spent years inside that model and never questioned it. The tool was the fixed thing. People were the flexible part. We shaped ourselves around software the way water shapes around a rock.
Then my wife started a company, and I stepped in to support its operations. Five people, none of them engineers. Real users, no time. They needed an admin panel to run the product. A bot to turn team messages into work. Dashboards to figure out why one user in Vietnam saw a blank screen. The old me would have opened a browser and started comparing vendors and per-seat prices.
Instead, we grew them.
Not bought. Grew. An admin panel shaped to our product, in weeks. A bot that speaks our team’s mix of Vietnamese and English. Dashboards that answer the exact questions we ask, because we wrote the questions. When something feels awkward now, we change the tool by dinner.
The ticket from this morning follows one rule I wrote: explain the change in the reader’s words. What changed, why, what users will notice. No jargon, no code names. Because the reader is a support person, not an engineer. No off-the-shelf product would ever phrase things for her. Ours does, because it grew up next to her.
Here’s what I think is actually happening. One-size-fits-all software existed for a good reason: custom was expensive. Building your own admin panel used to mean a team and a budget. So we all bought the same tools and learned to live inside them, and the size of that compromise was just the cost of doing business. Then AI changed the economics.
I don’t think the big tools disappear. Somebody still has to hold the record of what happened, and hold it reliably. That part stays, the way a database stays. What fades is the part everyone quietly struggled with: the interface nobody chose, and the workflows you adopted because the tool said so.
Software used to be something a business bought and adapted to. I think it’s becoming something a business grows, shaped by its people and its language, a little more every week. I watch it happen in my own five-person team every day, and honestly, it’s the most natural way of working I’ve ever felt.
The best tool for your team might be the one that grows up inside it.