How This Founder's Obsession with Simplicity Built $250K/Month App
TL;DR: Anton spent 15 years failing at 6-7 startups. Two years ago saw ChatGPT voice-to-text apps emerging - all prototypes, poorly implemented. 'So powerful and simple idea. I need this but can't use them.' Had team from previous failed startup, pivoted to build Letterly. Philosophy: extreme simplicity as competitive advantage. 'Everyone can build product. Few are very simple and easy to use.' Asked customers why use Letterly vs free ChatGPT - 'Don't know, just feels much easier. Click button widget, click stop, text is ready.' Zero friction. Now: $250K/month revenue, 30K monthly active users, 20K paid subscribers, 150K downloads. Team of 10, $30K/mo salaries, $5K/mo AI costs, $200K/mo ad spend (massive growth investment). Building for simplicity is expensive: 'Treat it as separate feature.' Multiple iteration levels: (1) Prototypes - draw, discuss, simplify before building. (2) During build - stop and think 'is it really simple?' even if delays promised features. (3) Post-release - feedback reveals more friction to remove. Spent 'thousands of hours to make it look simple.' User experience is 'multiplier to everything' - helps onboard, retain, convert, get recommendations. Features: one-click recording, instant real-time transcription, multiple rewrite options, scroll between versions, one-click copy/share to Google Docs/Notion. Advice: Work with co-founders day one, build something launchable in 1-2 months, choose novel but validated idea (don't validate completely new), when you see traction/revenue go all-in and leave jobs, build something generating money day one. Tech: Started React Native, switched to Swift (iOS), Kotlin (Android), Python backend.
Key Insights
- Simplicity is expensive competitive moat - most can build features, few can eliminate friction
- User experience multiplies everything - onboarding, retention, conversion, word-of-mouth
- Delay feature releases to perfect simplicity - even when users ask for features
- Users choose paid simple app over free complex alternative - convenience beats free
- Thousands of hours required to make product look simple - treat simplicity as separate feature
Actionable Takeaways
- Ask users why they use your paid product vs free alternative - reveals friction differences
- Iterate simplicity at 3 levels: prototypes (draw/discuss), during build (stop to assess), post-release (user feedback)
- Choose novel but validated ideas - someone else proves demand, you execute better through simplicity
- Stop building before release to ask 'is it really simple as I dreamed?' - delay if not
- Build one-click workflows (widget, instant results) instead of multi-step processes