A founder can have a good reason for every feature:
• A user asked for it
• A competitor has it
• It looks good in a demo
But each one still adds something to maintain and explain.
The question is not whether the feature makes sense on its own.
It is whether it makes the product more useful as a whole.
That is a harder bar.
Building in public makes assumptions visible.
You can explain what you believe.
Someone can point out what you missed.
You get to decide what to do with that.
That is better than building around a guess nobody challenged.
If you're building in #buildinpublic, let's #connect!!
A SaaS roadmap gets expensive when every feature serves a different buyer.
1. Write down the buyer and the job each requested feature serves.
2. Circle the buyer who has already paid or committed to a next step.
3. Ask that buyer to rank the requests before you schedule the work.
Today's build-in-public update #2:
- Fixed 3 layout bugs
- Submitted sitemaps for indexing
- 189 unique visitors
- 1 new Pro subscriber
- $39 MRR
Good progress for doc2doodle.com ❤️
Today's build-in-public update #1:
- fixed the zoomed-out layout
- wrote 3 SEO pieces
- 320 unique visitors
- 1 paying customer
- $30 MRR
Good Progress on Day 1 of my Beta Launch!!
Today I'm coming out of stealth to launch the doc2doodle beta.
I've been working on it for the last 3 months. The idea is simple: give us a document, and we'll turn it into a doodle video.
Claude can do this, but it uses a lot of credits and isn't cheap. So I built a template-based rendering system, with AI handling image and library searches.
It's live now. The first 1,000 customers get 25% off their subscription.
doc2doodle.com


