Phase 0: Foundation Now — Before Ads (4/15)
Build a small but real organic following. When paid ads start, they land on a non-empty account with credibility signals. Seed communities so stitchwand is top-of-mind when conference starts.
Establish @stitchwand X Account Voice
Cadence: 2–3 posts daily. CLI demos (video GIFs), token conversion live threads, design system hot takes, quotes from founders building design systems. Show personality. No sales pitch yet.
Target: 500–1,000 followers by 4/21 so ads land on a populated account, not a ghost town. 2–3 posts/day = ~700–1,400 impressions/day on a new account.
Platforms prioritize accounts with engagement history. An ad from @stitchwand with followers performs better than an ad from a day-old account.
Seed Reddit & Design Communities
Communities: r/webdev, r/frontend, r/designsystems, r/googlecloud, r/javascript.
Approach: Answer 2–3 questions/week about design tokens, DESIGN.md conversion, CSS-in-JS. Link stitchwand only when directly relevant. Do NOT astroturf.
Red flag: If you mention your product in every reply, moderators will flag you. Ratio: 9 helpful posts, 1 product mention. Be genuinely useful first.
Create fake accounts to upvote your own comments or fabricate a discussion about stitchwand. Reddit & HN have bot detection. You WILL be caught and shadowbanned.
Build-in-Public Cadence (Brian's LinkedIn)
Content rotation Mon/Wed/Fri:
- Technical insight ("Token systems I admire and why")
- Founder story ("Why we built this instead of buying")
- Product progress ("Shipped: Google Stitch bridge")
Why LinkedIn: Organic posts that perform well can be boosted with paid later ($75 boost = cheap advertising). LinkedIn rewards founder authenticity. Higher avg deal size than X.
Organic posts that get 20+ comments become your cheapest paid ads when boosted. You already know they work.
Create a "Zero-to-DESIGN.md" Reference Thread
12-tweet thread: Step-by-step showing how to convert design tokens using stitchwand. Live code snippets, before/after Figma screenshots, real CLI output. This thread becomes your most-shared content. People RT this for months.
Cross-post to LinkedIn as a long-form article (LinkedIn native, not link). This gets 2x reach and becomes a reference document people link to in discussions.
One great thread = 1,000s of impressions over months. Costs you a few hours now.
Open Source Social Proof
Target: 100+ GitHub stars before launch. Add badge in README showing star count. Add "Used by:" section showing early design system adopters. Add link to GitHub from landing page.
Every star is a trust signal. Influencers look at GitHub. Conference attendees look at GitHub. "Used by 127 design teams" sounds way more legit than "just launched."
- Share GitHub link in the reference thread
- Ask early design system users for a quote + GitHub follow
- Link from stitchwand.dev landing page above the fold
Phase 1: Community Seeding Week of 4/21–25 (Conference)
Hacker News Launch Post
Timing: Tuesday–Thursday morning (8–9am ET). Title: "Show HN: stitchwand – convert design tokens for Google Stitch". Link to landing page.
Prep: Have 3–4 real users ready to comment with genuine experiences ("We used this to migrate 200 tokens in 2 hours"). DO NOT ask for upvotes. HN detects vote rings and kills the post. Organic voting only.
HN bans accounts that coordinate upvotes or post multiple times per week. Your post will be flagged if it smells coordinated. One natural launch, genuine comments, that's it.
Product Hunt Launch
Target date: Monday 4/28–29. Cool-down week after conference. People are reflecting. Launch early (8am PT), have 3–4 shots of demo GIFs, press "Publish" and tell your audience. Your X followers + LinkedIn followers = first-day traffic.
Prep checklist: Accepted by a Hunter (ask Figma/design communities), polished Maker profile (1 photo, bio, links), 3+ screenshots showing before/after, tagline under 60 chars, first comment explaining "Why we built this."
It's for validation. Even 200 upvotes = 3+ weeks of media mentions ("top product on Product Hunt"). Worth the polish.
Discord/Slack Community Presence
Communities: Design Systems Slack (if you get invited), Figma community Slack, Tailwind Discord, CSS Discord. Join, lurk for 2 days, then start answering questions.
Tone: "Hey, ran into this same problem, here's how I'd approach it" — never a sales pitch. When stitchwand is genuinely relevant, mention it casually: "We built a tool for exactly this."
- Share your reference thread from Phase 0
- Link stitchwand GitHub in your community profile bio, not in posts
- Help 3–4 people before mentioning the product once
Conference Live-Tweeting
During Google Cloud Next (April 21–25), live-tweet sessions about Stitch, design tokens, integrations. Genuine reactions. Tag @GoogleCloud, use #GoogleCloudNext. @stitchwand retweets your best ones. This is organic geo-targeting — you're reaching people IN the room discussing the platform you're building for.
- Screenshot key quotes from sessions
- Post genuine insights ("The new Stitch API means teams can finally..." without mentioning stitchwand)
- Retweet speakers and add value
Collect & Publish Early User Testimonials
Process: DM early users asking for honest feedback ("No script — just tell me what you actually think"). If they say something great, ask permission to quote on landing page. Full name + title + company + Twitter if possible.
3 genuine quotes (even from lesser-known people) > 0 quotes. "Saved us 2 weeks" from a real designer is worth 10x more credibility than any marketing copy you write.
Get these in before Product Hunt launch. They anchor your value prop.
Phase 2: Amplification May Onwards
Technical Blog Post (dev.to / Hashnode)
Topic: "How I built a design token bridge for Google Stitch" — walk through the architecture, token parsing, Stitch API integration, CLI patterns. Honest challenges too. This should be 4–6min read, not a 30min epic.
Cross-post: dev.to → link from Medium (get it re-shared) → link from stitchwand blog. Each post drives long-tail SEO traffic for months ("how to convert design tokens").
One deep post = passive traffic for 6+ months. Worth the work now.
Submit to Design System Newsletters
Target newsletters: Sidebar.io, CSS Weekly, Frontend Focus, Design Systems Weekly. These have 10K–100K subscribers who actively look for tools.
Pitch: Email the curator with your blog post + 2–3 sentence summary. "I wrote about building a token bridge for Stitch, thought your readers would find it useful." 20% submission rate.
One newsletter mention = 200–500 click-throughs from trusted readers.
Create a Comparison Guide
Title: "stitchwand vs. manual DESIGN.md: benchmarks" — Show before/after time saved, token accuracy, edge cases handled. Honest comparison, not a hit piece. Include scenarios where manual is better.
People respect comparison guides that admit tradeoffs. Drives trust AND SEO (ranks for "token conversion tools" searches).
- Link from both blog posts
- Update benchmarks quarterly (shows you care)
- Share in communities when directly asked "What tool should I use?"
Micro-Influencers (1K–10K followers) Best ROI
Their audiences trust them WAY more. A micro-influencer with 5K followers will generate 3–5x more conversions than a 100K follower macro. Their people actually know them.
Search for Figma creators, CSS/design system educators, Google Cloud builders on X/YouTube. Look for: realistic engagement (not bot-like), actual technical tweets, 3–5K followers sweet spot.
- Design token creators (#figmadesignsystems)
- Google Cloud educators
- CSS-in-JS / design system writers
Personalize this — do NOT send copy-paste:
Hey [Name], saw your post about [specific thing they tweeted]. I built stitchwand to bridge design tokens and Stitch, and I think you'd find it genuinely useful. Happy to give you early access, no asks. Just looking for honest feedback.
- Free product + swag: Send a nice t-shirt, early access. Many micro-influencers just want to be heard. ($0)
- Product + honorarium: Free access + $100–300 for their time. Keeps it ethical and disclosed. ($100–300)
- Affiliate link: Give them a unique referral code. They get 10% of annual subscriptions for 2 years. (upside share)
- Only reach out to people whose work you actually admire
- No "just asking for a favor" on a DM to a stranger
- Never ask them to keep it quiet. All paid work must be disclosed.
- Expect 70% rejection rate. That's normal.
Mid-Tier (10K–50K followers) Design/Dev Thought Leaders
Don't cold-pitch mid-tier. Build a relationship first. Reply to their tweets for 2 weeks, share their work, then reach out.
- Reply thoughtfully to their tweets (not "nice" — add value)
- Share one of their posts per week to your audience
- After 3–4 weeks, send a DM: "I've been following your work, love what you're doing with [topic]. Built something I think aligns with it."
Keep it 2–3 sentences. "Created a design token bridge for Stitch. Would love your honest take. Happy to work something out." Let them respond with interest before discussing pay.
If they're interested: $500–1,000 per post/video depending on their audience size and engagement. But honestly, the best coverage comes from the product being genuinely good, not paid.
What NOT to Do
You MUST disclose all paid endorsements. Failure penalties: $50K+ per incident. Beyond the legal risk, undisclosed paid posts destroy trust when discovered — and they WILL be discovered in niche dev/design communities.
- Pay for undisclosed endorsements
- Buy fake followers or engagement
- Create alt accounts to post about stitchwand
- Incentivize reviews without explicit disclosure
- Work with influencers who refuse to disclose
- Tell creators "just mention it naturally, people will understand"
- All paid posts must include #ad, #sponsored, or "paid partnership" in a visible place (not buried in 20 hashtags)
- Written agreement with the creator specifying disclosure requirements
- Creator must have actually used the product
- All claims must be truthful and substantiated
- Keep records: emails, agreements, transaction receipts
Every tactic in this document is designed to build GENUINE organic presence, not to deceive. When in doubt, disclose. When in doubt, ask. Real relationships scale longer than astroturfing ever will.
Risk Assessment Matrix
| Risk | Severity | Likelihood | Impact | Mitigation |
|---|---|---|---|---|
| Astroturfing detection | HIGH | Medium | Community bans, posts removed, reputation destroyed permanently. | Only post genuinely useful content. Never coordinate upvotes. Never use alt accounts. If caught, recovery takes months. Accept that some posts will flop — that's normal. |
| Undisclosed paid endorsement | CRITICAL | Low (if rules followed) | FTC fines ($50K+), influencer backlash, permanent trust loss in community. | Written contracts requiring disclosure. Review all posts before they go live. Use platform partnership tools (LinkedIn, X both have native "sponsored post" features). Keep receipts. |
| Community backlash | MEDIUM | Medium | "This is just an ad." Comments, downvotes, negative sentiment scare away real users. | Earn credibility before promoting. 10:1 rule — 10 helpful non-promotional interactions per 1 product mention. Build for 3–4 weeks before linking stitchwand in communities. |
| Influencer goes rogue | MEDIUM | Low | Off-brand messaging, controversial statements, inflated metrics. | Vet influencers' recent tweets. Written agreements with content guidelines. Kill switch: ability to end partnership immediately and request post removal. |
| Organic efforts cannibalize paid | LOW | Medium | Can't attribute conversions. Spend money on ads reaching people who'd convert organically. | UTM tracking on ALL links (organic posts get utm_source=organic, paid get utm_source=x/linkedin). Separate landing pages if possible. Accept that some overlap is inevitable and OK. |
| Content burnout | MEDIUM | High | You're one person. 2–3x daily tweets + 3x weekly LinkedIn + community engagement + influencer management + product building = burnout. | Batch content creation. Use AI (Claude) to draft content, then edit for voice. Schedule posts. It's OK to reduce cadence — consistency beats volume. 1 great post per week > 7 mediocre ones. |
| Negative honest reviews | LOW | Medium | Influencer or community member gives negative feedback publicly. | This is GOOD for credibility. Thank them publicly, fix the issue, follow up. Turns critics into advocates. People respect companies that listen. |
| Account suspension | HIGH | Low (if rules followed) | X/Reddit/HN bans your account. Months of work disappear. | Never use bots. Never follow/unfollow automation. Never buy followers. Never coordinate with friend accounts. Treat account like it matters (it does). |
Red Lines (Do Not Cross)
- Create fake reviews or testimonials
- Pay for reviews without FTC disclosure
- Coordinate upvotes from friend accounts
- Post the same content from multiple accounts
- Use bots to auto-reply or engage
- Ask influencers to hide paid relationships
- Claim your product does something it doesn't
- Use misleading metrics ("Used by 1000+ developers" if that includes free tier signups)
If Something Goes Wrong
Acknowledge it publicly. "I should have been more transparent about being the founder. Here's the honest story." Admit, don't defend. Mods and communities respect humility more than excuses.
Contact them immediately. "Hey, we didn't agree on that claim — can you adjust the post?" Document everything. If they refuse, publicly clarify your actual product position.
STOP. Pivot to being transparent. "Hey, I've been posting here as a community member, and I actually built a tool [for this]. Here's what it does, no ask, just thought you'd find it useful."
Content Calendar Template
Weekly rotation (X / LinkedIn):
| Day | Content Theme |
|---|---|
| Monday | Technical insight or hot take |
| Tuesday | CLI demo or code walkthrough (GIF) |
| Wednesday | Community engagement / RT retweet |
| Thursday | Founder story (why you built this) |
| Friday | Weekly wins / shipping update |
Batch create all 5 posts on Friday afternoon. Schedule them out. Frees you to just engage, not create.
Outreach Email Templates
Subject: Built something for your audience Hi [Name], Saw your tweet about [specific thing]. I built stitchwand to bridge design tokens + Stitch, and I think your audience would find it genuinely useful. Happy to give you early access, no strings. Just looking for honest feedback. [link] – Brian
Hey [Name], Been following your work on [topic] and really respect your take. Built a tool that solves the exact problem you were talking about last week. Would love your honest opinion. Happy to offer [product + swag / honorarium] for your time. No pressure if not interested. Either way, keep shipping. – Brian
Hey [Name], Just saw your question about [problem]. Literally just shipped something that solves this. Early access link below. Fair warning: it's raw, but it works. Happy to hear what breaks. [link] – Brian
Reddit / HN Post Guidelines
- Posts that solve a real problem people have
- Posts with honest limitations ("Here's what doesn't work")
- Posts with live examples / screenshots
- Creators engaging genuinely in comments
- Obviously self-promotional posts from new accounts
- Coordinated upvotes from friend accounts
- Spammy language ("You won't BELIEVE..." "Startup founders hate this")
- Links with excessive affiliate codes
- Duplicate posts across multiple communities
Post Templates
Show HN: [product name] – [one sentence value prop] Example: "Show HN: stitchwand – Convert design tokens to Google Stitch in 30 seconds"
Title: [Problem you solve] Built [product] after getting frustrated with [problem]. Spent 3 months on [what makes it good]. Would love feedback from this community. [Link] Limitations: [be honest about edge cases]
Testimonial Request Template
Hey [Name], You're using stitchwand and I genuinely respect your work. Would you be open to a 1–2 sentence quote we could share on the landing page? Something honest about your experience, even if it's "got the job done but needs X." No script, just your actual take. Happy to reciprocate if helpful. – Brian
Keep it: Short (max 1–2 sentences), honest (even "good tool but steep learning curve" works), attributed (name + title + company + Twitter if they want)
Claude Prompt for Organic Content Planning
Reusable for any product:
I'm launching [product]. Help me create a 4-week organic growth plan covering: 1) Twitter content themes (3 posts/day), 2) Reddit communities to seed, 3) one launch post for HN, 4) one technical blog post topic, 5) influencer targets (10 micro-influencers in [space]). The product: [2-3 sentence description] My audience: [who cares about this] My unique angle: [why we're different] Constraints: I'm solo. 5 hours/week max. No budget for paid until week 4.
This prompt works for any project. Adapt it, run it every month.
UTM Tracking Setup
Use these URL parameters consistently:
Base: stitchwand.dev/?utm_source=[source]&utm_medium=[medium]&utm_campaign=[campaign] Examples: ?utm_source=x&utm_medium=organic&utm_campaign=soft-launch ?utm_source=reddit&utm_medium=organic&utm_campaign=design-systems ?utm_source=hn&utm_medium=organic&utm_campaign=show-hn ?utm_source=linkedin&utm_medium=organic&utm_campaign=build-in-public ?utm_source=newsletter&utm_medium=referral&utm_campaign=sidebar-io For influencers with affiliate codes: ?utm_source=influencer&utm_medium=affiliate&utm_campaign=[name]&ref=[code]
Track all of these in PostHog/Plausible. You'll see which channels actually convert.