Internal Tools Are the New Side Project

Last week I shipped three tools for my teams. None of them has a landing page. None of them ever will. And I'd put the combined impact of those three against any public side project I built in the last five years.

The side project used to have a shape. You built something on nights and weekends, put it on the internet, hoped strangers found it. The ambition was a product; the reality was usually a portfolio piece. That model assumed the hard part was getting software in front of people, and for most of us it was. You could build the thing. You could not make anyone care.

AI collapsed the build cost, which everyone noticed. What got less attention is where the energy went. Mine went inside the org. The side project didn't die. It moved to where the users already are.

The audience of twelve

An internal tool inverts every problem that killed side projects. Distribution is solved on day one, because your users already sit in the same meetings you do and will tell you within the hour whether the thing works, no launch post required. The impact is legible too. When a dashboard replaces a weekly email thread of number requests, everyone who lived that thread knows exactly what changed.

The two I'm proudest of this month were unglamorous in the best way. One pulls the client-reporting numbers my team used to request from finance by hand every Friday; it updates itself now and looks better than the deck it replaced. The other turned a recurring resourcing spreadsheet, the one where three people cross-check who's staffed on what, into a single button. There was a third, smaller thing too: a one-click brief generator for account handoffs that took an afternoon to build and saves someone twenty minutes a week. None of it would survive a launch feed. All of it gets opened, which is the thing side projects were supposed to earn and rarely did.

The builders who thrive

The people I see thriving in orgs right now share a habit. They ship something useful every week. Not a deck about what could be built, not a proposal. A working thing. The cadence matters more than the size, because a weekly tool compounds into a reputation: the person who removes friction. That reputation is worth more inside an org than any follower count outside it. It's denominated in hours returned to people you actually work with.

There's a skill shift underneath this. The old side project rewarded marketing as much as building. The internal tool rewards noticing: the manual step everyone quietly accepted, or the question that hits your inbox five times a week and nobody stops to ask why it still needs a human to answer. Judgment about what's worth automating starts with paying attention to your own team, which turns out to be a renewable resource.