返回列表
🧠 阿头学 · 🪞 Uota学

83 天做到每月 $20k——我们犯过的 4 个错误

早期创业最贵的学费不是钱，是注意力——FOMO 驱动的广撒网和功能堆砌，本质上是用"忙"来逃避"想清楚"。

2026-02-24 原文链接 ↗
阅读简报
双语对照
完整翻译
原文
讨论归档

核心观点

  • FOMO 是注意力的最大杀手4 周试6 个渠道不叫"快速验证"，叫"什么都没验证"。每个渠道至少给一个月，才能区分"渠道不行"和"你没做到位"。读到 ≠ 做到，体感差距巨大。
  • 5 天规则：实验要有截止日 创始人最容易被"下一个大机会"点燃，兴奋两周然后翻车是经典剧本。硬性约束——5 天内发布并拿到数据，超过就砍。这不是限制创造力，是保护执行力。
  • 抄功能是最懒的产品决策 失败功能的两大来源：拍脑袋 + 照抄竞品。每个新功能都是复杂度负债，消费品尤其要克制。验证手段只有一个：拿去问用户，不是问自己。
  • 省钱省到基础设施上是最蠢的省法 服务器没冗余、凌晨宕机、用户退款——这种错误的 ROI 是负无穷。有收入之后，该花的buffer 不是成本，是保险。

跟我们的关联

这篇的核心教训和Neta/Uota 的产品节奏直接相关：我们自己在做功能迭代和渠道测试时，是否也在犯"广撒网"和"功能堆砌"的错？值得对照自检。接下来可以把"5 天实验规则"和"单渠道深耕一个月"作为内部执行原则试跑一轮。

讨论引子

1. "至少测一个月"和"最多花 5 天"看起来矛盾——渠道要耐心，功能要快刀，你怎么判断一个事情属于哪类？ 2. 你有没有过"照抄竞品功能结果翻车"的经历？回头看，当时缺的是用户反馈还是产品判断力？ 3. 83 天 $20k MRR 的速度其实很快了——这些"错误"是真的拖了后腿，还是快速试错本身就是达到这个速度的原因？

--- > 原文：

83 天做到每月 $20k：我们犯过的 4 个错误

不写我们做对了什么，先把我们犯过的错误列出来（让你别再犯！）：

  1. 在最初的阶段，因为 FOMO（害怕错过），我们尝试了太多营销渠道。

  2. 我们真的在 4 周内把 SEO、pSEO、Meta 广告、Google 关键词广告、TikTok 视频和冷邮件全都试了一遍，哈哈

  3. 即使最后证明这个渠道行不通，我们也认为至少投入并测试一个月才值得——这样才能真正理解它

  4. 尤其如此，因为有些东西只有你不断尝试、熬过去一段时间才会看见。亲自去做，和只是读到它，是两回事。

  5. 不要在一个新功能或实验上花超过几天时间

  6. 这既适用于产品决策，也适用于营销决策

  7. 说实话，我很容易被一个新点子点燃，作为创始人你大概率也是
  8. 但模式总是一遍又一遍：我对“下一个大机会”兴奋得不行，花 2 周去做，结果彻底翻车

  9. 不管看起来多有前景，最多花 5 天把它发布出来并测试。如果需要更久，它很可能就已经大到不适合用来做实验了。

  10. 别再照抄，学会倾听

  11. 百分之百准确：所有失败的功能都属于两类：1）凭空想象“灵机一动”的点子；2）受其他产品启发的点子

  12. 当然，灵感很好，但你一定要拿去和用户验证。你的用户真的需要那个功能吗？
  13. 记住：产品是给用户的，不是给你自己的。如果你想做的是面向真实业务的严肃产品，而不是一个玩票项目，这一点很重要
  14. 表面上看，每个点子都像好点子。但新增一个功能 = 更多复杂度。一定要非常严格地想清楚：为什么这个功能必须出现在你的产品里？

  15. 我觉得这一点对面向消费者的产品尤其如此。简单，才是关键。

  16. 一旦开始有收入，就在需要的地方多花点钱

  17. 两周前，我们的应用因为服务器顶到上限而直接罢工了。CPU 使用率超过了 100%。

  18. 当时真的已经凌晨 1 点，用户不停给我们发邮件，要求退款。我慌了。
  19. 这是个愚蠢的错误。只要多留一点冗余，就能避免一大堆用户遭遇糟糕体验

眼下我能想到的就这 4 个错误；如果之后想起更多，我会继续补到这个推文串里

相关笔记

we crossed $20k/mo in 83 days

不写我们做对了什么，先把我们犯过的错误列出来（让你别再犯！）：

instead of everything that went right, here are the mistakes we made (so you don't make them!) :

  1. 在最初的阶段，因为 FOMO（害怕错过），我们尝试了太多营销渠道。
  1. During the early days, we tried too many marketing channels due to fomo.
  • 我们真的在 4 周内把 SEO、pSEO、Meta 广告、Google 关键词广告、TikTok 视频和冷邮件全都试了一遍，哈哈
  • 即使最后证明这个渠道行不通，我们也认为至少投入并测试一个月才值得——这样才能真正理解它
  • 尤其如此，因为有些东西只有你不断尝试、熬过去一段时间才会看见。亲自去做，和只是读到它，是两回事。
  • we literally tried SEO, pSEO, meta ads, google keyword ads, tiktok video, and cold email all within 4 weeks lol
  1. 不要在一个新功能或实验上花超过几天时间
  • even if the channel turns out to not work, we think it's worth committing and testing for at least a month to get a good understanding of it
  • 这既适用于产品决策，也适用于营销决策
  • 说实话，我很容易被一个新点子点燃，作为创始人你大概率也是
  • 但模式总是一遍又一遍：我对“下一个大机会”兴奋得不行，花 2 周去做，结果彻底翻车
  • 不管看起来多有前景，最多花 5 天把它发布出来并测试。如果需要更久，它很可能就已经大到不适合用来做实验了。
  • this is especially true because there are things you start to see the more you try and bear through it. trying is different from reading about it.
  1. 别再照抄，学会倾听
  1. Don't spend more than a few days on a new feature or experiment
  • 百分之百准确：所有失败的功能都属于两类：1）凭空想象“灵机一动”的点子；2）受其他产品启发的点子
  • 当然，灵感很好，但你一定要拿去和用户验证。你的用户真的需要那个功能吗？
  • 记住：产品是给用户的，不是给你自己的。如果你想做的是面向真实业务的严肃产品，而不是一个玩票项目，这一点很重要
  • 表面上看，每个点子都像好点子。但新增一个功能 = 更多复杂度。一定要非常严格地想清楚：为什么这个功能必须出现在你的产品里？
  • 我觉得这一点对面向消费者的产品尤其如此。简单，才是关键。
  • this pertains to both product decisions and marketing decisions
  1. 一旦开始有收入，就在需要的地方多花点钱
  • honestly i get easily excited about a new idea, and as a founder you probably do too
  • 两周前，我们的应用因为服务器顶到上限而直接罢工了。CPU 使用率超过了 100%。
  • 当时真的已经凌晨 1 点，用户不停给我们发邮件，要求退款。我慌了。
  • 这是个愚蠢的错误。只要多留一点冗余，就能避免一大堆用户遭遇糟糕体验
  • but it's always the same pattern again and again: i get super excited about the "next big thing", spend 2 weeks on it, and totally flunk

眼下我能想到的就这 4 个错误；如果之后想起更多，我会继续补到这个推文串里

  • no matter how promising the idea seems, spend max 5 days on it to release and test. if it takes more than that, it's probably too big for experimenting.

  1. Stop copying and listen

相关笔记

  • with 100% accuracy, all of the features that failed were 1) ideas that just magically came from imagination and 2) ideas that were inspired from other products
  • ofc inspiration is good, but you HAVE TO verify it with your users. do your users really need that feature?
  • keep in mind the product is for your user, not for you. if you're trying to build a serious product for a real business and not a play project, this is important
  • on the surface, every idea seems like a good idea. but adding a new feature = more complexity. be very strict about why that feature needs to be in your product
  • i think this is especially true for consumer products. simplicity is key.
  1. Once you start making revenue, spend more where it's needed
  • 2 weeks ago, our app just flat out stopped working because our servers maxed out. CPU usage went over 100%.
  • it was literally 1am, users emailing us nonstop, requesting refunds. i panicked.
  • this was a stupid mistake. a small buffer would have saved us from a bunch of users having a bad experience

these are the 4 mistakes on the top of my head but as I remember more, I'll add it to the thread

Brian Shin (@brianshinsh): we crossed $20k/mo in 83 days instead of everything that went right, here are th

  • Source: https://x.com/brianshinsh/status/2026182925264585113?s=46
  • Mirror: https://x.com/brianshinsh/status/2026182925264585113?s=46
  • Published: 2026-02-24T06:30:28+00:00
  • Saved: 2026-02-24

Content

we crossed $20k/mo in 83 days

instead of everything that went right, here are the mistakes we made (so you don't make them!) :

  1. During the early days, we tried too many marketing channels due to fomo.

  2. we literally tried SEO, pSEO, meta ads, google keyword ads, tiktok video, and cold email all within 4 weeks lol

  3. even if the channel turns out to not work, we think it's worth committing and testing for at least a month to get a good understanding of it

  4. this is especially true because there are things you start to see the more you try and bear through it. trying is different from reading about it.

  5. Don't spend more than a few days on a new feature or experiment

  6. this pertains to both product decisions and marketing decisions

  7. honestly i get easily excited about a new idea, and as a founder you probably do too

  8. but it's always the same pattern again and again: i get super excited about the "next big thing", spend 2 weeks on it, and totally flunk

  9. no matter how promising the idea seems, spend max 5 days on it to release and test. if it takes more than that, it's probably too big for experimenting.

  10. Stop copying and listen

  11. with 100% accuracy, all of the features that failed were 1) ideas that just magically came from imagination and 2) ideas that were inspired from other products

  12. ofc inspiration is good, but you HAVE TO verify it with your users. do your users really need that feature?

  13. keep in mind the product is for your user, not for you. if you're trying to build a serious product for a real business and not a play project, this is important

  14. on the surface, every idea seems like a good idea. but adding a new feature = more complexity. be very strict about why that feature needs to be in your product

  15. i think this is especially true for consumer products. simplicity is key.

  16. Once you start making revenue, spend more where it's needed

  17. 2 weeks ago, our app just flat out stopped working because our servers maxed out. CPU usage went over 100%.

  18. it was literally 1am, users emailing us nonstop, requesting refunds. i panicked.

  19. this was a stupid mistake. a small buffer would have saved us from a bunch of users having a bad experience

these are the 4 mistakes on the top of my head but as I remember more, I'll add it to the thread

📋 讨论归档

讨论进行中…