Built an AI writing platform with 100+ tools instead of one — here's why that wasn't the obvious choice
letsflw is an AI writing platform 100+ individual tools, plus Workflows that chain a few together for a specific task, plus a handful of Automations that make an actual decision before acting instead of following a fixed script.
The obvious move when building something like this is to pick one thing and do it well one killer tool, sharp positioning, easy to explain in a sentence. I went the opposite direction on purpose. Most people doing real writing work aren't doing one task, they're doing five or six across a session draft something, check the SEO, tighten the tone, write a meta description, maybe humanize it. Scattering that across five different single-purpose tools (and five different subscriptions) is its own kind of tax nobody talks about.
So the actual bet is: one place, wide coverage, and the part I care about more than the tool count genuinely honest about what each piece can and can't do. The humanizer tool says outright that no tool reliably beats AI detectors, because that's true and most competitors in this space just don't say it. Free tier is a real free tier, not a seven-day trial dressed up as one.
Launched on Product Hunt a few weeks back, still early, still figuring out distribution more than the product at this point.
If you've built something with a lot of surface area instead of one narrow feature curious how you've thought about explaining "does a lot" without it sounding like "does nothing well."
One hundred tools can feel like breadth to the builder and decision fatigue to the user. I would organize the experience around a few completed jobs, then reveal tools only as part of each workflow and measure whether users reach a finished output faster.
That's a really clean way to put it breadth to the builder, decision fatigue to the user. Hadn't heard it framed that way but it's exactly right.
The Workflows feature is actually a step toward this already chains a few tools into one "job" instead of making someone pick tools individually. But you've made me realize I still lead with "100+ tools" everywhere, including this post, when I should probably be leading with the finished jobs and letting the tool count stay in the background as a "how it works" detail instead of the headline.
"Measure whether users reach a finished output faster" is the part I don't have good data on yet — curious if you've got a rule of thumb for what that even looks like to track early, before there's much usage volume to work with.