There's a pattern I keep noticing in how technical founders operate versus everyone else: the good ones are constantly building the tools they use to build things.
Not big tools. Small ones. Scripts that automate one tedious step. Pipelines that take an idea and turn it into a formatted artefact without friction. Content engines that take raw notes and publish them with consistent structure.
The compounding effect is invisible at first, and then it isn't.
Every tool you build for yourself does two things simultaneously:
- It removes a recurring cost from your workflow
- It sharpens your intuition for what customers actually need
The second is the part most people miss. When you're the user of your own tooling, you feel every friction point. You iterate fast because the feedback loop is tight — you built it, you use it, you fix it. This is the same feedback loop that makes the best consumer products, except you get to run it at speed because you're not waiting for user research or PMs.
Imagine you spend 4 hours building a tool that saves you 20 minutes a day. Break-even is 12 days. After 30 days you're in profit. After a year you've saved something like 80 hours — two full working weeks.
But the real number is bigger, because:
- You built the tool faster than you think (you're better than you give yourself credit for)
- The cognitive overhead of doing things manually is underweighted in most estimates
- You often discover a product opportunity in the process
Scarab HQ started as a script I wrote to manage my content pipeline. I was tired of the friction between having an idea, writing it down, and getting it published with the right structure. So I automated the parts that were purely mechanical.
Three months later it's a product that other people want to use.
This is the pattern. Build the thing you need. Build it well enough to be useful to yourself. Then notice whether other people have the same problem.
Most of the time they do. That's where products come from.
The counterargument is that you should be building your actual product, not internal tooling. This is correct if you're in a race — if speed to market is everything and you have the runway to hire people to do the manual work.
But if you're a solo operator, the small tools are the product infrastructure. They're what make you more capable than a team of three, which is the only competitive position available to you.
Build the small tools.