I built the tool I was already using
BlogForge started because I needed a faster way to generate structured blog content. It ended up as a proper SaaS product with templates, SEO tools, tone controls, and twelve content niches. The…

Highlight
The best product decisions came from the moments I was annoyed at my own tool.
BlogForge was born from the specific annoyance of having great technical thoughts but zero energy to format them into structured posts. It wasn't supposed to be a SaaS product; it was supposed to be a shell script. But once the prompting logic started hitting 90% accuracy, it felt like a waste to leave it in the code editor.
Using your own tool while building it is a strange, unfiltered feedback loop. I wasn't fixing bugs for users; I was fixing bugs for myself because they were slowing down my own writing. That distinction, building as the primary user, is what turned a simple draft generator into a multi-niche content system.
Using your own tool while building it
There is an odd feedback loop when you are the user and the developer at the same time. I would generate content, notice something that did not feel right, and fix it before the next session. The bugs I cared about most were the ones that made the output less useful, not the ones that broke the UI. That ordering taught me something about what the product actually was.
What twelve niches actually means
The niche system was the most time-consuming part. Generic content generation is straightforward. Content that sounds like it was written for a legal firm rather than a fitness brand requires different vocabulary, different structural expectations, different defaults. Twelve niches meant twelve separate calibrations, not twelve separate prompts.
- AIDA and PAS templates perform better in marketing niches. How-To performs better in technical ones.
- Tone controls matter more in B2B niches where the AI defaults to casualness.
- Internal linking suggestions only work if the tool knows what content you already have.
- SEO integration should influence structure, not just add keywords at the end.
- The rewrite tools ended up being used more than the generation tools, as people wanted to improve, not replace.
You learn more about how people use a tool by watching them ignore the feature you spent the most time on.
BlogForge is still in active use, including for content on this site. There is something satisfying about that. Not because the tool wrote my thoughts, it did not, but because it removed enough friction that writing more became the easier choice.

