A few of these went out to 200k+ users. Some raised millions. All built by a small team that ships fast. Happy to break down how we did any of them, just ask.
@opusyoung@OpusClip 3 to 100 people in 3 years is its own survival course. What did the builder to CEO shift actually look like day to day, more delegation or more saying no?
@seanallen_dev We shipped the fixed fee page with a full pricing calculator nobody asked for. Same energy. Once you start overbuilding it's hard to stop.
@RayFernando1337 Adaptive layouts like this always sound simple until you hit the state management problem. Same screen, same session, elements need to know which geometry they're in and re-anchor without a flicker.
@twannl Crashes that compile clean are the worst kind. Concurrency bugs almost never show up at compile time, they show up three weeks later in a user's crash log.
@sarunw Spent an hour once debugging why Map wouldn't resolve, turned out I just needed the MapKit import sitting next to SwiftUI. Cross-import overlays are sneaky like that.
@femkesvs Career check-ins are the one people skip most. Everyone does the growth areas part, almost nobody schedules the quarterly "am I actually progressing" conversation with themselves.
@starter_story Boring verticals win because the buyer already has budget and zero patience for a 10 step onboarding flow. Indie hacker tools compete for attention, trade tools compete for a slot in someone's actual workday.
@toly archegos and knight capital as the pitch for onchain markets is the one that sticks with me. Nobody needed a thread to understand why those blew up, the ledger was the whole problem
@SagivMooly good call not dressing it up as FV. Tools that are honest about their limits get trusted faster than ones that overclaim. Contract interdependency mapping alone saves hours on audits like this.
@alelepd plugin ecosystems like this are the real unlock for OpenAI, every tool wants to live inside the chat now instead of being a tab you alt-tab to