Small tools are underrated because they do not look serious at first. A tiny canvas toy. A pricing calculator. A dashboard mock that only tracks one workflow. A page that turns text into something you can send to a friend.
They are useful because they force decisions quickly.
You cannot hide behind architecture diagrams when the whole thing is supposed to work in one sitting. The question becomes simple: what does the user type, what changes on screen, and what can they do with the result?
That is why I like building them.
With a small tool, every rough edge is obvious. If the button label is bad, you feel it immediately. If the layout shifts, it annoys you immediately. If the tool technically works but the output is not worth sharing, the whole thing fails.
There is also less room for fake productivity. You either made the thing easier or you did not.
The best small tools usually have a narrow verb:
- write this
- convert this
- preview this
- download this
- compare this
- send this
That narrowness is the feature. A small tool should not try to become a platform before it has earned the right to be useful.
When I build larger products, I still try to keep that habit nearby. Find the smallest useful loop. Make the loop obvious. Make it feel decent. Then decide if the product deserves more machinery.