Every engineering team I’ve worked with has at least one internal tool that someone built because it seemed like a good idea. A custom deployment dashboard. A bespoke admin panel. A homegrown monitoring system. Half the time, nobody uses it. The other half, one person uses it and everyone else uses the thing it was supposed to replace.

Engineers build internal tools because it feels productive. It scratches the creative itch without the messy complexity of customer-facing features. The requirements are clear because you’re building for yourself. It’s fun. That’s the trap.

Meanwhile, the actual product has a backlog of customer requests sitting in a spreadsheet.

Before building an internal tool, ask three questions. Is there an off-the-shelf product that does 80% of this? Will more than three people use this regularly? Does this directly help us ship product faster?

If the answer to any of those is no, buy the tool or skip it entirely. Retool, Airplane, or even a well-structured spreadsheet will get you further than a custom React app that one engineer maintains in their spare time.

Save the engineering effort for things only your team can build. Your customers don’t care about your internal dashboards.