A collection of product failure cases personally experienced by Wang Kai.Avoiding pitfalls saves more money than taking the right path——This is from posts.md the only few cases explicitly marked as "abandoned due to operational failure", and their value lies in the experience itself.
1. Core Pitfall-Avoidance Mindset
| # | Mindset | Source |
|---|---|---|
| 1 | Do not copy the WeChat ecosystem to overseas markets | WhatsApp Postmortem |
| 2 | Abandon if it cannot work within 6 hours | WhatsApp #439 |
| 3 | Actual habits of overseas users ≠ those of domestic users | All overseas cases |
| 4 | Check the official Pricing page first | Many APIs have hidden costs |
| 5 | Ask people who have already done it first | Save 2 weeks of time |
| 6 | No sunk cost fallacy trap | Pivot once the decision is made |
2. Case 1: WhatsApp Push Bot (Wang Kai #439, 2023-09-25)
2.1 Complete failure chain
graph LR
A[邮箱推送<br/>异步太慢] --> B[WhatsApp Bot<br/>卡 Meta Business]
B --> C[Telegram Bot<br/>5 分钟搞定]
C --> D[最终:Email + Telegram 双通道]
2.2 Starting point: The conversion dilemma of email push
First version of FastFacts:
- Product: Monitor announcements of over 2000 US-listed companies, generate AI summaries and push them
- Push method: Email
- Problem: "Email is an asynchronous tool; few people open an email immediately after receiving it"
- Result: The core value ("2-minute ultra-fast speed") is negated by the asynchronous nature
2.3 Wrong product assumption
Wang Kai's assumption (fundamentally wrong):
"Users add the FastFacts notification bot on WhatsApp (similar to following a service account on WeChat, where the service account pushes messages), and then the bot pushes messages to them."
Fundamental error: Applying the "WeChat service account" model to WhatsApp.WhatsApp is not an official account platform; it is a private chat tool——its business model, technical architecture, and user expectations are completely different.
2.4 Hitting walls in practice
WhatsApp Business API must be applied for through a Meta Business account, and got stuck at the first step:
- Business license (and many countries require a local business registration)
- Domain verification (DNS configuration)
- Facebook Page verification
- Credit card (for Meta billing)
- Customer service process review
2.5 Decision: Abandon after 6 hours
"After checking around and asking around, it seems WhatsApp does not support this kind of function. Abandoned, currently building a Telegram push bot."
The most valuable lesson: Abandon if it cannot work within 6 hours, pivot to Telegram.
2.6 Real costs of WhatsApp Business API (if you insist on doing it)
24-hour window rule(most critical):
- After a user actively sends you a message, you only have a 24-hour window to reply for free
- Beyond 24 hours, you must use paid message templates Message Template(each one must be submitted to Meta for approval in advance)
Billing(per conversation, not per message):
- $0.005–$0.15 per conversation (varies by country)
- More than 100 times more expensive than Telegram
Time cost:
- Business license preparation
- Meta Business account verification: 3–7 days
- WhatsApp Business account application: 3–14 days
- Phone number verification: 1–3 days
- Message Template approval: 24–72 hours per template
- Total: 2–4 weeks
Monetary cost:
- Business license (if you don't have one): starting from several thousand US dollars
- Third-party BSP: starting at $50–500/month (Twilio, MessageBird, 360dialog, Vonage)
- Conversation fees are usage-based
2.7 Applicable scenarios for WhatsApp Business API (rare)
- ✅ Already have an overseas company entity
- ✅ User count ≥ 100,000, product is stable
- ✅ Per-user LTV > $100
- ❌ Solo developers, early-stage products, low LTV: do not do this
3. Telegram alternative (Wang Kai's final choice)
3.1 WhatsApp vs Telegram comparison
| Dimension | WhatsApp Business API | Telegram Bot API |
|---|---|---|
| Registration | 2–4 weeks + business license | 5 minutes, anonymous |
| Proactive push | 24h window + Template | Unlimited, free |
| Billing | $0.005-$0.15/conversation | $0.005–$0.15 per conversation (varies by country) |
| Approval | Each Template is reviewed individually | No approval |
| Documentation quality | Official documentation is complex | Extremely simple and clear |
| Developer community | Commerce-oriented | Extremely active |
| User base | Over 2 billion globally | Over 900 million globally |
| Crypto / Web3 users | Few | Extremely many |
3.2 Set up a Telegram Bot in 5 minutes
# Step 1: 找 @BotFather 创建 bot
# Step 2: 拿到 token
# Step 3: 写代码
import telegram
from telegram.ext import Updater, CommandHandler
def start(update, context):
update.message.reply_text('Hi! I send you stock alerts.')
updater = Updater("YOUR_BOT_TOKEN")
updater.dispatcher.add_handler(CommandHandler("start", start))
updater.start_polling()
Proactive push:
bot = telegram.Bot(token="YOUR_TOKEN")
bot.send_message(chat_id=user_chat_id, text="🚨 New SEC filing!")
Zero cost, zero approval, zero waiting throughout the process.
3.3 Hidden advantages of Telegram
- Powerful group features: can create supergroups of 200,000 people, and use bots to implement "broadcast + interaction"
- Channel one-way broadcast:Perfectly matches the "WeChat Official Account" model
- Supports cryptocurrency / NFT integration(Native to the TON blockchain)
- High concentration of overseas Chinese / crypto circles / users who bypass internet censorship
- Bots can read group messages: enabling more complex intelligent assistants
3.4 Three content formats on Telegram
| Mode | Description | Applicable for |
|---|---|---|
| A. Channel mode(Official account style) | One-way broadcast, visible to all subscribers | News, market updates, reminder-type content |
| B. Bot private chat mode(Personalized) | 1:1 conversation, user-initiated/start |
Personalized recommendations, interactive queries |
| C. Hybrid mode(Strongest) | Channel broadcast + Bot personalization | FastFacts should use this |
3.5 FastFacts-style content template
🚨 [Company Ticker] - [Filing Type]
[1-line AI summary]
📊 Key data:
- Revenue: $X (YoY +Y%)
- Net income: $X
- Guidance: [up/down/maintained]
🔗 Full filing: [link to your product]
3.6 Telegram user growth path
Cold start (0–1k subscriptions):
- Post to introduce the Channel on Reddit r/stocks, r/investing
- Include the Telegram link when promoting the product on Twitter/X
- Find 5–10 crypto / stock KOLs for one round of promotion
Acceleration (1k–10k):
- Produce high-quality content within the Channel (3–5 posts per day)
- Invite active subscribers into groups (small group discussions)
- Cross-post with other Channels
Matrix operation (10k+):
- Split Channels by topic (individual stocks, ETFs, tech stocks, crypto)
- Independent bot for each Channel
- Monitor data on subscriptions / unsubscriptions / link click-through rates
4. Case Study 2: FastFacts Product Hunt Launch Failure (Wang Kai #412–#422, 2023-09)
4.1 Complete failure chain
graph TD
A[发布前推算<br/>拉 1000 票冲榜一] --> B[翻车点 1<br/>时区算错周一发]
B --> C[翻车点 2<br/>拉了 300+ 票只算 103]
C --> D[翻车点 3<br/>95% 投票来自外国人]
D --> E[翻车点 4<br/>遇上市公司公告抽风用户被骚扰]
E --> F[最终日榜第 8]
4.2 Failure point 1: Incorrect time zone calculation
Original quote (#422):"I originally scheduled the launch for midnight Tuesday US time, but something unexpected happened —I selected the wrong time, which caused it to launch on Monday. "
Root cause:PH uses UTC, and a new day starts at UTC 0:00 = 19:00 the previous day Eastern Time / 16:00 the previous day Pacific Time. When setting a Tuesday launch, if you fill in the time using local time, it is easy to be off by one day.
Lesson:Reverse-calculate all times using UTC, and rehearse the setup process with a real account one week before launch.
4.3 Failure point 2: Solicited votes did not count
Original quote (#422):"According to my estimate, getting a thousand votes should be no problem, and I had a shot at first place, but when I had pulled at least over 300 votes, PH still showed 103 votes. "
PH anti-cheating rules:
- Votes from accounts registered for < 7 days are not counted or given low weight
- Votes from "zombie accounts" with no comments/activity records are not counted
- Concentrated voting from the same IP segment is downweighted
- Votes with all sources from Chinese IPs are downweighted
Lesson:When soliciting votes, you must target "old accounts + real active users". "It is best to spend time in PH communities, overseas communities, etc., and get people with old PH accounts to vote for you,my domestic traffic advantage is very hard to translate into direct results. "
4.4 Failure point 3: Domestic traffic advantage became ineffective
Original quote (#422):"Then I observed the upvotes and notification accounts,95% were foreigners, and from that point on it was purely supported by product value."
Underlying reason:PH user profile = product managers / investors / early-stage entrepreneurs mainly from North America + Europe; even domestic WeChat group vote solicitation is almost ineffective.
Lesson:Domestic vote solicitation equals roughly 0 conversion, resources should be spent on participating in the PH community for the prior month.
4.5 Failure point 4: Insufficient product preparation
Original quote (#422):"With only one day left I had to force the launch, and then it just so happened that yesterday listed companies collectively went haywire……on an average day there might be 10 emails, yesterday it shot straight up to 30+."
Result:Users were harassed, and the experience collapsed.
Lesson:The product must be 100% stable on launch day, leave at least a 1-week buffer to handle unexpected issues, and do not bet everything on the launch date.
4.6 Final result
- Goal: #1 on daily leaderboard
- Actual: #8 on daily leaderboard
- User experience: Flooded by a massive volume of emails
- Conversion: Extremely low, 95% of votes came from unknown foreigners
5. Case Study 3: The shift in CryptoZenith's second launch (#685)
After Wang Kai's FastFacts failure, his attitude completely changed when launching CryptoZenith:
Original text:"Next the priority is to complete the cold start first and look at the product's viral coefficient……those of you who have PH accounts, please help vote."
Points of change:
- No longer pursuing first place on the leaderboard
- No longer large-scale vote solicitation
- Focus on the product's own "viral coefficient" (organic growth / total exposure)
- Tone when asking for votes changed from "rushing the leaderboard" to "please help"
This is a mature attitude after stepping on pitfalls:Treat PH as an "honest testing machine" for product quality, not a "traffic engine".
6. Overseas IM ecosystem vs WeChat ecosystem (core pitfalls to avoid)
6.1 Fundamental differences summarized by Wang Kai (original quote #439)
"The maturity of foreign instant messaging tools and the WeChat ecosystem is quite far apart; many scenarios achievable within WeChat are not supported abroad."
6.2 Things WeChat can do that overseas IMs cannot
| WeChat feature | Overseas equivalent | Feasibility |
|---|---|---|
| Official Account subscription push | WhatsApp Channel / Telegram Channel | Telegram ✅ / WhatsApp ⚠️ |
| Service Account replies | WhatsApp Business 24h window | ❌ Strictly restricted |
| Mini Programs | Telegram Mini Apps | ✅ But the ecosystem is weak |
| Group bots | Telegram / Discord Bot | ✅ |
| Moments | Instagram / Facebook | ❌ Completely different form |
| Red packets / transfers | Cash App / Venmo | ❌ Not inside the IM |
| H5 embedded payment | Almost no equivalent | ❌ |
| Channels | YouTube / TikTok | ❌ Completely independent |
6.3 IM selection decision tree for overseas-going products
你需要主动推送给用户?
├── 是
│ ├── 用户是技术 / 加密 / 海外华人 → Telegram ✅
│ ├── 用户是欧美主流消费者 → 邮件 + Push 通知(不要做 IM)
│ └── 用户是企业客户 → Slack Bot / MS Teams Bot
│
└── 否(用户主动来找你)
└── WhatsApp Business App(手机版)即可
7. General pitfall avoidance checklist (applicable to all overseas-going products)
7.1 Assumptions not to make
- ❌ "Overseas users also like Official Account-style subscriptions"
- ❌ "WhatsApp = foreign WeChat"
- ❌ "A product form that is technically feasible definitely has a market"
- ❌ "Just directly copy models that worked domestically"
- ❌ "Meta's API should be similar to WeChat's"
7.2 Must-do things
- ✅ First research users' actual usage habits:European and American users are more accustomed to email, Push, Slack
- ✅ First look at the Pricing page in the official documentation:Many APIs have hidden costs
- ✅ First ask people who have already done it:Saves 2 weeks of time
- ✅ Abandon if it cannot be worked through in 6 hours:Wang Kai #439 reaction speed
7.3 Time-box principle
Wang Kai only spent 6 hours hitting the WhatsApp pitfall before deciding to abandon it:
- Saw the restrictions → researched → switched to Telegram
- No sunk cost fallacy trap
- Did not force it to continue
Applicable to all overseas platforms:If a promotion channel / technical solution shows no possibility of being workable within 1 week,pivot immediately.
8. Alternative solution matrix
8.1 Recommendations by scenario
| Scenario | First choice | Alternative |
|---|---|---|
| News push | Telegram Channel | Email + RSS |
| 1:1 personalized notifications | Telegram Bot | Push notifications (in-product) |
| Crypto / Web3 users | Telegram + Discord | |
| Mainstream European and American consumers | Push notifications | |
| Enterprise customers | Slack Bot / MS Teams | |
| Customer support | Intercom / Zendesk | WhatsApp Business App |
8.2 Multi-channel parallel (optimal solution)
Do not bet on a single channel:
核心通知 → Email(保底)
即时通知 → Telegram Bot(速度)
营销内容 → Twitter/X(曝光)
深度内容 → Newsletter(留存)
社区 → Discord(互动)
9. "If I could do it over" FastFacts checklist
If rebuilding FastFacts today:
- Day 0:Determine push frequency and user expectations (≤3 per day vs push every item)
- Day 1:Start with Email + in-site Push dual channels (lowest cost)
- Day 7:Decide whether to add IM after Email data feedback
- Day 14:If adding, go directly to Telegram Channel (set up in 5 minutes)
- Day 30:Observe the Channel growth curve
- Day 90:Only consider WhatsApp Business API when user volume > 10k
Do not jump down the WhatsApp Business API rabbit hole in the first week.
10. Related Failure Cases (Mentioned in Other Posts)
List of Wang Kai's failed products/projects (see details in Wang Kai's Startup Methodology and Business Judgment Framework in the AI Era §12):
| Project | Time | Failure Lessons |
|---|---|---|
| AI E-commerce Guide Site | 2023 | Early token costs could not be balanced |
| FastFacts SEC Filing Scraper | 2023 | Revenue ceiling of 300,000 yuan for the carrying capital; quantitative teams were 5 seconds faster than us |
| MJ for Feishu | 2023 | Good open-source dissemination but could not sustain the team |
| WhatsApp Push Bot | 2023-09 | Pivoted to Telegram within 6 hours (this wiki §2) |
| FastFacts Product Hunt Failure | 2023-09 | 4 pitfalls led to 8th place on the daily chart (this wiki §4) |
| AiPathly (AI Job Application Report) | 2024 | SEO mismatch for innovative products |
| Quanta Quest (Consumer-facing Wiki AI Search) | 2024 | Blocked by Notion/Gmail data permissions |
11. Wang Kai's Words
"If it can't be validated within 6 hours, give up and pivot to Telegram — that is the most valuable lesson."
"WhatsApp is not an official account platform; it is a private chat tool — the business model, technical architecture, and user expectations are completely different."
"Foreign instant messaging tools are far less mature than the WeChat ecosystem; many scenarios achievable within WeChat are not supported abroad."
"Product Hunt is not a place for chart-rushing; it is a place for free backlinks and product quality validation."
"The mature attitude after stepping on pitfalls: treat Product Hunt as an 'honest testing machine' for product quality, not a 'traffic engine'."
References
- Wang Kai's Startup Methodology and Business Judgment Framework in the AI Era - Startup Methodology (case attribution for this wiki)
- Wang Kai's Overseas Promotion SOP and Multi-Account Matrix Practice - Overseas Promotion (application scenario for the lessons in this wiki)
- Wang Kai's 6-Platform Overseas Operation SOP - 6-Platform SOP (detailed version of PH SOP)
- Wang Kai's RSI AI Investment Strategy and the "Good Asset, Good Price, Good Volatility" Framework - Investment Strategy (FastFacts evolved into the RSI AI strategy)
- Wang Kai's 1000+ AI Product Idea Library and Business Model Analysis - Product Ideas (direction selection after avoiding pitfalls)