Spot solution or workflow solution?
Hi fellows!
I have a great convo with @aryan_sinh about the fine tuning of ideas in early stage and I think the community can benefit from it.
Markdown becoming the working format between people and AI tools.
A lot of AI-generated content starts as messy markdown, then needs to become something shareable: a doc, brief, PDF, client note, internal spec, or Google Doc. That workflow is still awkward because most tools either treat Markdown as developer text or as a static publishing format.
With mdtidy.com we solve this problem but noticed that there are plenty of other issues we can help with - so... how would you tackle this branding wise?
Trending on Indie Hackers
I’d frame this less as “Markdown cleanup” and more as the last-mile workflow for AI-generated work.
The bigger problem is not that Markdown is messy. It is that AI gives people semi-structured output, but the next step is usually something human-facing: a client note, internal doc, PDF, brief, spec, or Google Doc.
So mdtidy can either stay a spot tool: “clean and format Markdown.”
Or it can become a workflow product: “turn AI-generated drafts into polished, shareable work assets.”
That second frame gives you more room to expand beyond formatting without confusing people.
If you want, I can turn this into a small written positioning breakdown for mdtidy: category frame, homepage angle, use cases, and the cleanest way to explain the product without making it feel like a developer utility.