Boiler is a simple command-line tool that helps developers generate clean, consistent boilerplate code from a shared Git repo. I built it because we constantly run into inconsistencies at work — and I got tired of watching teams start from scratch and build similar things in very different ways or struggle with how to start every time they spun up a project.
It’s the kind of problem you don’t notice until it wastes an afternoon — and then you wonder why it wasn’t solved already.
I built Boiler in Go. It’s a relatively small, straightforward tool. I started building it before I ever read Million Dollar Weekend, but as I read the book, I realized I had done things out of order. I built the tool before trying to sell it. That’s something I keep doing — and something I want to change.
The Million Dollar Weekend method teaches you to start by finding a buyer. Sell it before you build it. Talk to people. Find the pain. Propose a solution. Then build it if they want it.
I didn’t do that. I had the idea, built the tool, and only after the fact did I realize how much easier it might have been to get early feedback — and early sales — if I’d talked to people first.
I’ve worked in software for a long time, and as a director, I’ve seen how much money gets spent on developer tools. If something saves time, reduces friction, and makes developers more productive, $400 is a no-brainer for most teams.
Boiler fits that mold. It’s easy to set up. It standardizes code and docs. It’s version controlled and locally cached. And it solves a problem I know is real — because I deal with it myself.
I haven’t had any sales yet, but that’s on me. I’ve been hesitant to share Boiler with coworkers — not because it wouldn’t help them, but because I’m wary of crossing ethical boundaries at work. I built it on my own time, but I’m still figuring out if and how I can safely introduce it in the workplace.
I’ll reach out to 100 people with the goal of either getting a sale or getting rejected. I need to validate the market and find early adopters outside my personal hesitation zone.
I might also quietly test it internally at work (without selling it) to see how well it solves the problem it was made for. That would give me confidence, case studies, and maybe even some public wins I can point to.
I can launch small tools quickly. But I still struggle with identifying which ideas are actually good — and more importantly, which ones people will pay for.
Boiler is live. It’s useful. Now I need to find its customers — or learn why it’s not a fit. Either way, I’ll be better prepared for the next idea.
Written by Joel Dare with the help of AI on May 7, 2025.