Today: March 16. Launch: March 31. Days remaining: 15. Mode: Real launch. Signups open. People can pay. No "request access" theater.
The Honest Assessment
The product is built. The marketing site exists. The pricing is set. You have comparison pages, free tools, and a changelog with 20+ entries.
You don't have a distribution problem. You have an action problem. Everything below is designed to force action — specifically, the kind of action you avoid: talking to strangers, asking for money, and shipping before it's perfect.
Pre-Launch Audit (March 16-17, 2 days)
Before anything goes live, verify these table stakes work flawlessly. This is the only "building" allowed in this plan.
Day 1 — March 16 (Sunday)
- Signup flow end-to-end test. Create account → set up org → install widget → send first message → receive reply. Record yourself doing it. Time it. If it takes more than 3 minutes, fix it.
- Billing flow. Can someone upgrade to Starter ($49) and get charged? Test with a real card. If Stripe isn't wired up, this is the #1 blocker — fix it today.
- Widget install. Copy the embed code, paste it on a test site. Does it load? Does it connect? Does the "Powered by SupportWire" link work?
- Email transactional flow. Signup confirmation, password reset, conversation notifications — do they all send? Do they land in inbox, not spam?
Day 2 — March 17 (Monday)
- Fix anything broken from Day 1. Nothing else. No new features. No polish.
- Write the founding customer offer. One page. Not a landing page — an email you'll send to humans. Include:
- What SupportWire is (2 sentences)
- Why you're reaching out to them specifically (1 sentence)
- The founding customer deal: locked pricing for life, direct access to you, their logo on the site
- A link to sign up
- Your personal email and calendar link
- Build your hit list. 100 companies. Not personas. Names. Find them on:
- Twitter/X: search "intercom pricing" "intercom expensive" "intercom alternative"
- G2/Capterra: 1-2 star Intercom reviews from the last 6 months — these companies are actively unhappy
- Reddit: r/SaaS, r/startups, r/smallbusiness — threads complaining about support tools
- Product Hunt: companies that launched recently and have a chat widget on their site
- Your own FeatureOS customers who use Intercom or Crisp
End of Day 2 deliverable: Working signup + billing, founding customer email draft, 100-company list.
Week 1: First Humans (March 18-22)
Day 3 — March 18 (Tuesday)
- Send 20 founding customer emails. Not a mass email. 20 individual emails. Personalize the "why you specifically" line for each one. Use your personal email, not a marketing address.
- Post in 3 communities. Not "check out my product" spam. Genuine participation:
- Answer a question about customer support tools on Reddit or Indie Hackers
- Share a specific insight in a relevant Slack community (SaaS Twitter, IndieHackers, etc.)
- Reply to someone complaining about Intercom on Twitter with something useful — not a pitch
Day 4 — March 19 (Wednesday)
- Send 20 more emails.
- Ship 5 alternatives pages. You said you planned 15-20. Ship the top 5 today. They don't need to be perfect. They need to exist and be indexable:
/alternatives/intercom/— this is your #1 page, spend the most time here/alternatives/crisp//alternatives/zendesk//alternatives/freshchat//alternatives/help-scout/
- Follow up with anyone who opened your Day 3 emails. If you don't have open tracking, just follow up with all 20.
Day 5 — March 20 (Thursday)
- Send 20 more emails. You're now at 60 outbound.
- Ship 5 more alternatives pages:
/alternatives/tidio//alternatives/livechat//alternatives/tawk-to//alternatives/drift//alternatives/hubspot-chat/
- Post your first "Building SupportWire" blog post. Topic: "Why I'm building a live chat tool in 2026." Raw, honest, founder story. Not SEO content — founder brand content. Share it on Twitter, LinkedIn, Indie Hackers.
Day 6 — March 21 (Friday)
- Send 20 more emails. 80 total.
- Call/DM the 5 warmest leads. Anyone who replied, clicked, or signed up. Have a real conversation. Ask what they need. Listen more than you pitch.
- Set up Google Search Console + submit sitemap. If not already done.
- Create the Product Hunt upcoming page. Get the listing drafted. Don't launch yet.
Day 7 — March 22 (Saturday)
- Send the remaining 20 emails. 100 total.
- Week 1 retrospective. Write down:
- How many emails sent: ___
- How many replies: ___
- How many signups: ___
- How many conversations: ___
- What objections did you hear?
- What surprised you?
End of Week 1 target: 100 outbound emails sent, 5-15 signups, 3-5 real conversations with potential customers, 10 alternatives pages live, Product Hunt upcoming page created.
Week 2: Traction & Proof (March 23-29)
Day 8 — March 23 (Sunday)
- Review and respond to every signup. Personal email from you. "Hey, I saw you signed up. I'm the founder. What are you using for support today?"
- Fix the #1 thing early users complained about. One thing. Not three.
- Ship the
/switch-from-intercom/page. This is your core conversion path. Migration timeline, risk reversal, comparison. Make it real.
Day 9 — March 24 (Monday)
- Second outbound batch. 50 new companies. Same playbook — personalized, from your email, specific "why you" line.
- Ship 5 comparison pages (the "X vs Y" format):
intercom-vs-supportwirecrisp-vs-supportwirezendesk-vs-supportwireintercom-vs-crisp(you're not in this one — you're the referee, which builds trust)freshchat-vs-supportwire
Day 10 — March 25 (Tuesday)
- 50 more outbound emails. 200 total.
- Get your first testimonial. Even if it's "I just switched and it's already faster." A real quote from a real person.
- Finalize Product Hunt assets:
- 5 screenshots/GIFs showing the product
- Tagline (use "Fast support for fast teams")
- Description (3 paragraphs max)
- First comment draft (your founder story — why you built this)
- Line up 5-10 people to upvote and comment at launch (friends, early users, fellow founders)
Day 11 — March 26 (Wednesday)
- 50 more outbound emails. 250 total.
- Write and schedule 3 launch-week social posts:
- "I've been building SupportWire for [X months]. Here's what I've learned." (Twitter/LinkedIn thread)
- A demo GIF or video — 30 seconds, no voiceover, just the product being fast
- The competitive angle — "Intercom charges $0.99 per AI resolution. We don't." (Twitter)
- Reach out to 5 micro-influencers/newsletter writers in the SaaS/startup space. Not asking for a feature. Offering them early access + the founding deal.
Day 12 — March 27 (Thursday)
- 50 more outbound emails. 300 total.
- Get your second and third testimonial.
- Prep the launch day email. For everyone who signed up during the pre-launch push. Subject: "SupportWire is live."
- Submit to directories:
- SaaSHub
- AlternativeTo
- G2 (create your profile)
- Capterra
- There's An AI For That (for the AI assistant feature)
- BetaList (if you haven't already)
Day 13 — March 28 (Friday)
- Final Product Hunt review. Everything uploaded. First comment written. Hunter lined up (ideally someone with a following — if you don't have one, launch yourself).
- Pre-launch tweet/LinkedIn post. "Launching Monday. Here's what we're building and why." Build anticipation.
- Dry-run the launch morning. What will you post, where, at what time?
Day 14 — March 29 (Saturday)
- Rest. Seriously. You have a big week ahead.
- One final end-to-end test. Signup → billing → widget install → conversation. Record it.
End of Week 2 target: 300 outbound emails, 15-30 signups, 1-3 paying customers, all alternatives + comparison pages live, Product Hunt ready, directory submissions done, testimonials collected.
Launch Week (March 30-31)
Day 15 — March 30 (Sunday)
- Pre-game. Queue all social posts. Prep email blast. Test everything one more time.
- Notify your early signups. "We're launching on Product Hunt tomorrow. Would love your support."
Day 16 — March 31 (Monday) — LAUNCH DAY
- Product Hunt launch at 12:01 AM PT.
- Post your first comment immediately. The founder story.
- Share everywhere:
- Twitter (personal + SupportWire account)
- Indie Hackers
- Relevant Slack communities
- Reddit (where appropriate — r/SaaS, r/startups)
- Hacker News (Show HN)
- Email to your 300-person outbound list
- Email to your FeatureOS customer base
- Respond to every Product Hunt comment within 30 minutes.
- Respond to every signup within 1 hour. This is your competitive promise — live it on day one.
- End of day: count. Signups. Conversations. Revenue.
The Rules
- No new features until April 15. Everything is built. If a user asks for something, write it down and keep selling.
- 20 outbound emails minimum per day. This is your distribution. Not SEO (takes months). Not content (takes weeks). Outbound works now.
- Respond to every signup personally. You are the product advantage. The CEO of Intercom doesn't email new users. You do.
- One thing to fix per day, max. You will be tempted to go into build mode when something isn't perfect. Fix the one thing that's actually blocking signups. Leave the rest.
- Track three numbers daily: Emails sent. Signups. Revenue. Everything else is noise.
What Success Looks Like
| Metric | Minimum | Good | Great |
|---|---|---|---|
| Outbound emails sent | 300 | 500 | 500+ |
| Signups (free) | 20 | 50 | 100+ |
| Paying customers | 1 | 3 | 5+ |
| MRR added | $49 | $147 | $500+ |
| Product Hunt upvotes | 50 | 150 | 300+ |
| Alternatives pages live | 10 | 15 | 20 |
| Real conversations had | 10 | 25 | 50+ |
The "minimum" column is what happens if you just follow this plan mechanically. The "great" column is what happens if you bring the same energy to distribution that you bring to design.
The product is done. The plan is written. The only thing left is the part you've been avoiding: putting it in front of strangers and asking them to pay.