stitchwand — Strategy

Strategy Overview

Growth & Revenue Strategy

The complete go-to-market playbook for turning stitchwand into the default DESIGN.md toolkit — using AI agents as distribution channels, not just product features.

AI-First Go-to-Market Philosophy

Traditional developer tools compete for attention through documentation, blog posts, and conference talks. stitchwand operates differently: AI agents are the primary distribution channel. When a developer asks Claude, Gemini, or Copilot how to create a DESIGN.md file, the answer should be "use stitchwand." This inverts the usual GTM funnel.

Traditional GTM

Developer reads blog post → visits docs → tries CLI → adopts tool. You chase the developer.

AI-First GTM

Developer asks AI agent → agent uses MCP tool → developer sees output → adopts tool. The AI brings you the developer.

The Moat

MCP registry presence + Stitch Skill in Google's repo + npm discoverability = embedded in the agent workflow before competitors know the market exists.

Core Insight

Every MCP registry listing is a permanent inbound channel. Every Stitch Skill usage creates familiarity. Every npm install creates lock-in. The product distributes itself through the AI agent ecosystem — your job is to be present in every registry, every listing, every "awesome" list before anyone else occupies the DESIGN.md niche.

First-Mover Position: DESIGN.md Tooling

As of April 2026, there are zero dedicated DESIGN.md tooling products in the market. The competitive landscape:

Category	Players	stitchwand Advantage
Design System Platforms	Supernova, Zeroheight, Knapsack	They manage design systems generically. We specifically output DESIGN.md for AI-native workflows.
Token Tools	Style Dictionary, Tokens Studio	They transform tokens between code formats. We transform them into a semantic document that AI agents understand.
Stitch Ecosystem	Google's own SDK, community snippets	Everything goes Stitch → Code. We go the reverse: Existing Systems → DESIGN.md → Stitch.
MCP Design Tools	None dedicated to design systems	First MCP server purpose-built for design system operations.

The window for establishing category ownership is 6-12 months. Once Stitch graduates from Labs (expected Q4 2026), larger players will notice the market. By then, stitchwand needs to be the default answer to "how do I use my design system with Stitch?"

Key Metrics & KPIs

5,000

NPM Weekly Downloads (12mo)

1,000

GitHub Stars (12mo)

$5.8K

Monthly Recurring Revenue (12mo)

200

Pro Subscribers (12mo)

Leading Indicators (track weekly)

Metric	Source	Target Trend	Why It Matters
npm weekly downloads	npm stats	10% WoW growth	Adoption velocity — direct usage signal
MCP tool invocations	Server telemetry (opt-in)	Growing daily active	AI agent distribution working
Web app unique visitors	Plausible	15% MoM growth	Top-of-funnel health
npm weekly downloads	npm stats	Steady climb	Developer interest signal
CLI → web referrals	UTM tracking	5% of CLI users visit web	CLI-to-website conversion
Chrome ext installs	Chrome Web Store	20/week post-launch	Stitch-specific user capture
Email list growth	Newsletter tool	50/week	Owned audience building

Goals by Horizon

90 Days Foundation

Launch all 3 npm packages + web app
Listed on 4+ MCP registries
Stitch Skill PR merged into Google's repo
500 npm weekly downloads
100 active users
Google Cloud Next demo/networking done
10 blog posts / tutorials published
Email list: 200+ subscribers
Chrome extension submitted

6 Months Revenue

4-tier pricing live (Pro $19/mo, Team $49/mo)
50-100 paying subscribers
$1,500-$3,000 MRR
2,000 npm weekly downloads
500 active users
1 enterprise consulting client ($15-25K)
Figma Bridge shipped
Google DevRel mention or feature
Speaking slot at 1 design system conference

12 Months Scale

200+ Pro subscribers
$5,800+ MRR
5,000 npm weekly downloads
1,000 active users
Enterprise tier launched
3-5 consulting/retainer clients
$50-70K ARR total
Stitch graduated — ride the wave
Category leader: "DESIGN.md tools"

Five Strategic Pillars

1. Registry Saturation

Be listed on every MCP registry, npm search result, and "awesome" list. When anyone searches for DESIGN.md or Stitch tooling, stitchwand appears. Treat registries like SEO backlinks.

2. Content Authority

Own the educational narrative around DESIGN.md. Every tutorial, blog post, and video positions stitchwand as the canonical reference. Publish faster than anyone can catch up.

3. Community Gravity

Build the community around DESIGN.md tooling. Answer every question. Feature every integration. Make users feel ownership. The community becomes the moat.

4. Google Proximity

Maintain visibility with Google DevRel. The Stitch Skill PR, Cloud Next presence, and community contributions keep stitchwand on Google's radar. Goal: get mentioned in official Stitch documentation.

5. Revenue Layering

Stack revenue: Free tier builds awareness, Pro tier ($19/mo) captures self-serve revenue, consulting path ($15-25K/project) captures enterprise value. Each layer feeds the others — consulting clients become case studies, case studies drive Pro signups, Pro usage data informs consulting pitches.

Go-to-Market

Go-to-Market Strategy

Market analysis, target personas, distribution channels, and core value proposition for stitchwand as the definitive design token toolchain for Google Stitch.

Executive Summary

stitchwand is the definitive design token toolchain and companion application for Google Stitch, the AI-native design platform. We convert, validate, and diff design tokens across every format, giving design system teams a single source of truth from Figma to production.

The Opportunity

Google Stitch is creating a new category of AI-native design tooling. As the first dedicated companion app, stitchwand is positioned to become the infrastructure layer that connects Stitch to every design system, codebase, and CI pipeline. We are building the rails.

$4.2B

Design Tools TAM

$680M

Design Systems SAM

$48M

Year 3 SOM Target

14.2%

Market CAGR

Strategic Pillars

Pillar 1

Free CLI & SDK

Ship a best-in-class CLI and TypeScript SDK as free npm packages. Earn trust. Win npm mindshare. Build adoption gravity before monetizing. The CLI is the wedge; the ecosystem is the moat.

Pillar 2

Stitch-Native Experience

Deep integration with Google Stitch via Skills marketplace. First-mover as the token management companion. Ride the Stitch adoption curve with purpose-built workflows that feel native to the platform.

Pillar 3

MCP-First Architecture

Ship an MCP server that lets any AI agent convert, validate, and diff tokens. Position stitchwand as the design token API for the agentic era. Every agent that talks design tokens talks through us.

Go-to-Market Timeline

Phase	Timeline	Focus	Key Milestone
Phase 1	Q2 2026	Free tools foundation	1,000 npm weekly downloads
Phase 2	Q3 2026	Web app + Stitch ecosystem	500 beta users, Stitch Skills listing
Phase 3	Q4 2026	Monetization + MCP	$25K MRR, MCP directory listing
Phase 4	Q1 2027	Team + Enterprise	$100K MRR, 3 enterprise pilots

Core Value Proposition

For Design System Leads

Single Source of Truth

Convert tokens between any format (DTCG, Style Dictionary, Figma Variables, CSS custom properties). Validate against your schema. Diff changes before they ship. Never have a token mismatch in production again.

For Developers

Tokens in Your Workflow

CLI in your terminal, MCP server in your AI editor, web app for visual review. Run npx stitchwand convert and get production-ready output. No config files. No build step. It just works.

Market Analysis

The design tooling market is undergoing a structural shift. AI-native platforms like Google Stitch are rewriting the rules. Design tokens are emerging as the critical interoperability layer, and no dedicated toolchain has captured the category.

Market Sizing

TAM — $4.2B

Global Design Tool Market

The total design tool market includes UI design platforms, prototyping tools, design system management, handoff tools, and design ops infrastructure. Growing at 14.2% CAGR driven by AI-native tooling adoption and enterprise design ops investment.

UI design platforms (Figma, Sketch, Adobe XD)
Design system management (Storybook, Zeroheight)
Design-to-code and handoff tools
Visual testing and QA (Chromatic, Percy)
AI-native design platforms (Google Stitch)

SAM — $680M

Design Token & System Infrastructure

The serviceable market narrows to teams that actively manage design tokens and need tooling for conversion, validation, and synchronization.

~45,000 companies with mature design systems
~12,000 agencies managing multi-brand tokens
Average contract value: $5,200/year
Growing as DTCG standard gains adoption

Growth Drivers

Tailwind

DTCG Standard Adoption

The W3C Design Tokens Community Group specification is reaching maturity. As the standard gets adopted by tools like Figma and Stitch, demand for conversion and validation tooling will surge. stitchwand is built DTCG-first.

Tailwind

AI-Native Design Wave

Google Stitch represents a paradigm shift. AI-generated designs need programmatic token management at a scale human workflows never required. stitchwand automates what would otherwise be manual token cleanup and validation.

Tailwind

MCP Ecosystem Expansion

The Model Context Protocol is becoming the standard for AI tool integration. Every code editor, every agent platform is adopting MCP. An MCP server for design tokens is a greenfield opportunity with zero incumbents.

Market Segments

Segment	Size	Urgency	Willingness to Pay	Our Fit
Enterprise Design Ops	~8,000 companies	High	$$$	Excellent
Mid-Market Product Teams	~22,000 companies	Medium	$$	Strong
Agencies / Studios	~12,000 agencies	Medium	$$	Strong
Indie Developers	~200,000 devs	Low	$	Good (OSS wedge)
Google Stitch Early Adopters	~15,000 users (est.)	High	$$	Excellent

Target Personas

Four primary personas drive adoption and purchasing decisions. Each has distinct pain points and motivations that inform our messaging, channel strategy, and feature prioritization.

Primary Buyer

Design System Lead

Senior IC or manager responsible for the design system at a mid-to-large company. Manages token libraries, component documentation, and cross-team adoption.

Pain Points

Token drift between Figma and code — values diverge after every sprint
No automated validation — broken tokens reach production
Manual conversion between formats takes hours per release
Difficult to audit changes across the full token tree

Motivations

Wants a single source of truth that designers and devs both trust
Needs to prove design system ROI to leadership with metrics
Looking for tools that integrate into existing CI/CD pipelines
Excited by AI-native workflows that reduce manual token management

Primary User

Frontend Developer

Mid-to-senior frontend engineer who consumes design tokens in React, Vue, or native apps. Cares about developer experience, type safety, and clean APIs.

Pain Points

Token files are poorly typed — autocomplete is broken or missing
No way to validate tokens in CI — broken styles ship silently
Converting Figma exports to usable code requires custom scripts
AI coding assistants don't understand the design token context

Motivations

Wants a CLI that fits into existing terminal workflows
Values type-safe TypeScript output with zero config
Excited by MCP integration — tokens accessible to AI editors
Prefers dedicated tools purpose-built for their workflow

Budget Holder

Design Ops Manager

Operations-focused role at an enterprise or large scale-up. Manages tooling budgets, vendor relationships, and workflow automation for 20-100+ designers.

Pain Points

No visibility into token usage across teams and brands
Compliance requirements demand audit trails for design changes
Onboarding new team members to the token workflow takes weeks
Vendor sprawl — too many point solutions, no unified platform

Motivations

Needs team analytics and usage dashboards
Wants SSO and audit logs for enterprise compliance
Looking to consolidate tooling and reduce vendor count
Values solutions that demonstrate clear time savings

Influencer

Agency Creative Director

Leads creative teams at a digital agency or design studio. Manages 3-10 client brands simultaneously, each with their own design system and token library.

Pain Points

Managing tokens across multiple client brands is chaotic
Handoff to client dev teams loses fidelity in token translation
AI-generated designs (Stitch) create tokens that need cleanup
No efficient way to compare token sets between design iterations

Motivations

Wants to position the agency as Stitch-ready for clients
Needs multi-brand workspace to manage client portfolios
Values visual diff tools that clients can understand
Interested in AI-powered token generation and auditing

Persona Prioritization Matrix

Persona	Influence	Budget	Urgency	Phase	Primary Channel
Design System Lead	Very High	Medium	High	Phase 1-2	npm / GitHub / Twitter
Frontend Developer	High	Low	Medium	Phase 1	npm / Dev.to / MCP directory
Design Ops Manager	High	High	Medium	Phase 3-4	Content / Conferences / Sales
Agency Creative Dir.	Medium	Medium	High	Phase 2-3	Stitch community / Dribbble

Distribution Channels

A multi-channel strategy prioritizing developer-led adoption in early phases, expanding to content and partnership-driven growth as the product matures.

Channel Strategy Philosophy

Lead with the free CLI. Earn trust through npm before asking for money. Every channel reinforces the same narrative: stitchwand is the token infrastructure you didn't know you needed.

P0 — Launch Channel

npm Registry

The foundational distribution channel. The CLI and core library published to npm as free packages.

Publish @stitchwand/cli and @stitchwand/core to npm
Docs site with clear examples and API reference
GitHub Actions integration template for CI/CD
Weekly release cadence with semantic versioning
Target: 2,500 npm weekly downloads by end of Phase 2

P0 — Strategic Channel

Google Stitch Ecosystem

First-mover advantage as a Stitch Skills marketplace listing. Direct access to every Stitch user.

Stitch Skills marketplace listing with rich documentation
Pre-built Stitch-to-DTCG conversion workflows
Featured in Stitch community tutorials and guides
Partnership with Google Stitch developer relations
Target: Featured Skill listing by end of Phase 2

P0 — Growth Channel

MCP Ecosystem

List the stitchwand MCP server in every major MCP directory. Get design token capabilities into every AI coding agent.

MCP server published to npm and listed in directories
Integration guides for Cursor, Claude Desktop, Windsurf
Showcase in "awesome-mcp" lists and community resources
"Design tokens for your AI editor" positioning
Target: 500 MCP server installations by end of Phase 3

P1 — Authority Channel

Content Marketing

Technical blog posts, tutorials, and video content establishing stitchwand as the thought leader in design token infrastructure.

Weekly blog: token tutorials, Stitch workflow guides
YouTube: "Token in 60 Seconds" shorts, deep-dive tutorials
Guest posts on Smashing Magazine, CSS-Tricks, Dev.to
SEO targeting: "design token converter", "DTCG validator"
Target: 10K monthly blog visitors by end of Phase 3

P1 — Community Channel

Community

Build a community of design system practitioners and token enthusiasts.

Discord server with channels for support, showcase, RFC
Twitter/X: daily tips, release announcements
Conference talks: Config, Clarity, An Event Apart
Monthly community call with roadmap previews
Target: 1,500 Discord members by end of Phase 3

P2 — Expansion Channel

Partnerships

Strategic integrations with adjacent tools in the design ecosystem.

Figma plugin: export Variables as stitchwand-validated tokens
Storybook addon: display token metadata alongside components
Integration with Vercel, Netlify for preview deploys
Co-marketing with complementary tools
Target: 3 signed partnership deals by Phase 4

Channel Investment by Phase

Channel	Phase 1	Phase 2	Phase 3	Phase 4
npm / Free Tools	Heavy	Heavy	Medium	Medium
Stitch Ecosystem	Medium	Heavy	Heavy	Heavy
MCP Ecosystem	Light	Medium	Heavy	Heavy
Content	Light	Medium	Heavy	Heavy
Community	Medium	Medium	Heavy	Heavy
Partnerships	Light	Light	Medium	Heavy

Growth

Growth Engine

Lead generation, content marketing, and social media strategies to drive developer adoption and build audience.

Lead Generation

Inbound Lead Generation Engine

Every channel optimized to bring developers to stitchwand organically — through search, registries, and free utilities.

Search / Registry Discovery

→

npm install / Web App Visit

→

Free Tool Usage

→

Email Capture

→

Pro Tier Conversion

Each stage has dedicated tactics below. The key insight: the CLI and MCP server ARE the lead generation tools. Every npx @stitchwand/cli convert is a trial that costs us nothing to deliver.

SEO: Own the DESIGN.md Search Landscape

DESIGN.md is a new format with minimal existing content. This is a rare greenfield SEO opportunity.

Priority Keywords (Months 1-3)

Keyword	Search Intent	Content Type	Target URL
DESIGN.md	Informational — "what is this?"	Definitive guide page	/docs/design-md-guide
DESIGN.md template	Transactional — wants a starting point	Template generator tool	/tools/design-md-generator
convert tokens to DESIGN.md	Transactional — wants to convert	Web app + tutorial	/convert
Google Stitch design system	Informational — exploring Stitch	Blog post / guide	/blog/stitch-design-systems
Stitch MCP server	Transactional — wants MCP integration	Setup guide	/docs/mcp-setup
Style Dictionary to DESIGN.md	Transactional — specific conversion	Tutorial + tool	/blog/style-dictionary-to-designmd
AI design tokens	Informational — exploring concept	Thought leadership blog	/blog/ai-design-tokens
validate Stitch output	Transactional — quality control	Web app + tutorial	/validate
Tailwind to DESIGN.md	Transactional — specific conversion	Tutorial + tool	/blog/tailwind-to-designmd
design system migration AI	Informational — exploring approach	Blog post / case study	/blog/design-system-ai-migration

SEO Technical Checklist

Add JSON-LD structured data to all pages

SoftwareApplication schema for the tool, HowTo schema for tutorials

Create /sitemap.xml and /robots.txt

Ensure all public pages are indexed

Add OpenGraph and Twitter cards to every page

Custom OG images for blog posts, generic for tools

Set up canonical URLs for all content

Prevent duplicate content from dev.to cross-posting

Create /docs/design-md-guide as the canonical DESIGN.md resource

3,000+ word definitive guide, interlinked with all tutorials

Add FAQ schema to key pages

Target featured snippets for "what is DESIGN.md" queries

Content Marketing Funnel

Top of Funnel (Awareness)

"What is DESIGN.md?" explainer
"Why Your Design System Needs AI" think piece
Google Stitch ecosystem overview
Design tokens for beginners
Twitter threads on design system trends

Middle of Funnel (Consideration)

"Convert Tailwind to DESIGN.md" tutorial
"Set up Stitch MCP in Claude Code" guide
Comparison: manual vs. stitchwand
Case study: migrating a real project
Video walkthroughs of each feature

Bottom of Funnel (Conversion)

"Pro tier: what you get for $19/mo"
Component generator demo video
ROI calculator for enterprise teams
Testimonials and social proof
Free consultation for enterprise

Free Tools as Lead Generation

The npm packages are not charity — they are the most efficient lead generation tool possible. Every npm install is a zero-cost acquisition.

npm install @stitchwand/cli

→

CLI output includes website URL

→

User visits stitchwand.com

→

Sees Pro features

→

$19/mo conversion

Tactics for npm-to-website conversion

Add post-install message to CLI package

Short message: "stitchwand installed. Try the web app at stitchwand.com for visual conversion and validation."

Include website URL in every CLI output footer

Subtle but persistent: "stitchwand.com | Pro features: component gen, CI/CD webhooks"

Add --upgrade flag to CLI that explains Pro features

When user runs stitch --upgrade, show a comparison of free vs. Pro capabilities

Track CLI version in Plausible via opt-in telemetry

Anonymous usage stats (command counts, token formats used) — must be opt-in with clear disclosure

Add sponsorship/upgrade callout to docs site

Link to Pro tier from docs, makes the commercial model visible and accepted

MCP Registry Listings as Discovery Channels

Every MCP registry is a permanent search engine for AI tools. Being listed early means being recommended early.

Registry	Status	Listing Optimization	Expected Discovery
Smithery	Launch Day	Full description, screenshots, usage examples, tags: design-system, tokens, stitch	High — primary MCP discovery for Claude Code users
mcp.run	Launch Day	Similar optimization, cross-link to Smithery listing	Medium-High — growing registry
Glama MCP directory	Week 1	Detailed capability description with example prompts	Medium — developer-focused discovery
MCP Hub	Week 1	Category: Design & UI, keywords: design tokens, DESIGN.md	Medium — category browsing
awesome-mcp-servers (GitHub)	Week 2	Submit PR to be listed under "Design" category	High — developers browse this list
Google Stitch Skills repo	Launch Day	Full Stitch Skill with SKILL.md, examples, and test cases	Very High — official Google ecosystem visibility

Registry listing template

Use this copy for all registry listings, adapted per platform:

Name: stitchwand MCP Server
One-liner: Convert design tokens to DESIGN.md, validate HTML against design systems, diff design system versions
Tools: convert_tokens (Style Dictionary/Tokens Studio/Tailwind/CSS → DESIGN.md), validate_html (grade HTML compliance against DESIGN.md rules), diff_designmd (compare two DESIGN.md versions)
Use case: Design system teams adopting Google Stitch who need to bridge existing tokens into the DESIGN.md format
Install: npx @stitchwand/mcp

Chrome Extension as User Acquisition

The Chrome extension injects directly into stitch.withgoogle.com, making it visible to every Stitch user at the moment they need it most.

Extension Features (Free)

Side panel with DESIGN.md validator
Real-time accessibility linting (axe-core)
Token extraction from Stitch output
"Default Stitch layout" pattern detection
Quick export to DESIGN.md format

Extension Upsells (Pro)

Component code generation from Stitch output
Design system drift alerts
Team sharing of validation rules
CI/CD integration from extension
"Unlock with Pro" badges on premium features

Free Tools That Capture Emails

Tool	What It Does	Email Gate	Build Effort
DESIGN.md Generator	Interactive form → generates a starter DESIGN.md	Download the file via email	1 day
Design Token Analyzer	Upload any token file → detailed report	Full report emailed as PDF	2 days
WCAG Contrast Checker	Paste color palette → contrast matrix	Exportable report via email	1 day
Stitch Readiness Score	Upload tokens → 0-100 readiness score	Detailed recommendations emailed	1 day
Design System Diff Tool	Compare two versions of any token file	No gate (pure top-of-funnel)	Already built

Email capture best practice

Never gate the core functionality. The convert, validate, and diff tools must always be free with no email required. Only gate supplementary reports, exports, and bonus content.

AI-Powered Lead Scoring & Qualification

Signal	Points	Why
Enterprise email domain (company.com)	+30	Consulting lead potential
Visited /pricing page	+20	Active purchase consideration
Used web app 3+ times	+15	Engaged user, ready for Pro upsell
Downloaded Chrome extension	+15	Active Stitch user — high-value lead
npm install (tracked via opt-in)	+10	Developer adoption signal
Opened 3+ emails	+10	Engaged with content
GitHub star	+5	Interest, but lower intent
Free email domain (gmail, etc.)	+0	Individual user, Pro tier prospect

Lead routing logic

Score 50+: Enterprise lead → personal outreach email from founder within 24 hours
Score 25-49: Pro prospect → automated email sequence highlighting Pro features
Score 1-24: Nurture → weekly newsletter, educational content
Score 0: Passive → monthly digest only

Marketing & Content

Content Pillars

Pillar 1: DESIGN.md Education

What is DESIGN.md, why it matters, how to write one, format specification, best practices. Goal: own the educational narrative for the format.

Pillar 2: Design System Transformation

Converting existing systems to AI-ready formats, migration guides, before/after stories, ROI of modernization. Goal: speak to teams with existing design systems.

Pillar 3: AI-Native Workflows

MCP servers for design, AI agents and design systems, the future of design engineering, Kenos Method. Goal: thought leadership and forward positioning.

30-Day Launch Content Calendar (April 18 – May 18)

Day-by-day content plan for the first month. Each item includes platform, content type, and goal.

Week 1: Launch Week (April 18-24)

Apr 18

LAUNCH DAY
X: Launch thread (5 tweets) at 10am ET
LinkedIn: Launch article (800 words) at 10:30am ET
dev.to: Technical walkthrough post (1,500 words)
Product Hunt: Scheduled submission
Hacker News: "Show HN" post
Reddit: Posts to r/webdev, r/FigmaDesign, r/UIDesign
All Hands

Apr 19

Engagement Day
Respond to every comment, DM, and mention from launch day
X: Share metrics thread ("24 hours since launch...")

Apr 20

Blog: "What is DESIGN.md? The Complete Guide"
3,000-word definitive guide
SEO Pillar

Apr 21

X Thread: "5 Things I Learned Building an MCP Server"
Tag @anthropic, @modelcontextprotocol

Apr 22

Tutorial: "Convert Your Tailwind Config to DESIGN.md in 60 Seconds"
How-To

Apr 23

X Thread: "Why Every AI Coding Agent Needs a Design System"

Apr 24

Week 1 Recap + Newsletter #1
Milestone

Week 2: Tutorial Week (April 25 – May 1)

Apr 25

Tutorial: "Set Up the stitchwand MCP Server in Claude Code"

Apr 26

X: Before/after — design tokens vs DESIGN.md output

Apr 27

Tutorial: "Convert Style Dictionary Tokens to DESIGN.md"

Apr 28

Google Cloud Next prep content

Apr 29

GOOGLE CLOUD NEXT — Live tweet from the conference
Event

Apr 30

Cloud Next Day 2 content

May 1

Blog: Cloud Next Recap + Newsletter #2
Milestone

Week 3: Deep Dive Week (May 2-8)

May 2

Blog: "How DESIGN.md Validation Works Under the Hood"

May 3

X Thread: "The Kenos Method"

May 4

Tutorial: "Validate Google Stitch Output Against Your Design System"

May 5

Blog: "stitchwand vs. Writing DESIGN.md by Hand"

May 6

X: Engagement day — no promotion, just helpful replies

May 7

Tutorial: "Diff Your DESIGN.md"

May 8

Newsletter #3 + Week 3 Recap
Milestone

Week 4: Growth Week (May 9-18)

May 9

Chrome extension submitted
Launch

May 10

Video: Full stitchwand Walkthrough (5 min)

May 11

Blog: "The Future of Design Systems is AI-Native"

May 12

Tutorial: "Using stitchwand MCP in Cursor and Gemini CLI"

May 13-14

Case Study Draft

May 15

Newsletter #4 + Month 1 Retrospective
Milestone

May 16-18

Plan Month 2 content + review analytics

Blog Post Queue (Months 2-6)

Title	Pillar	Target Keywords	Priority
"DESIGN.md Specification: The Definitive Reference"	Education	DESIGN.md spec, format	P0
"10 DESIGN.md Templates for Common Design Systems"	Education	DESIGN.md template, examples	P0
"How Enterprise Teams Are Using DESIGN.md with Stitch"	Transformation	enterprise design system AI	P1
"WCAG Compliance Checking with stitchwand"	Education	WCAG design system tool	P1
"Building a CI/CD Pipeline for Design System Validation"	AI Workflows	design system CI/CD	P1
"MCP Servers for Design: The New Interface"	AI Workflows	MCP design tools	P2
"From Figma to DESIGN.md: The Complete Bridge"	Transformation	Figma design tokens DESIGN.md	P2
"The Kenos Method: Complete Framework Guide"	AI Workflows	Kenos Method, AI design framework	P1

Video Content Strategy

Short-Form (X, YouTube Shorts)

60-second demos: One feature, one use case, clear outcome
Before/After: Raw tokens → beautiful DESIGN.md output
Tips: "Design system tip of the day" series
Cadence: 2x/week

Long-Form (YouTube)

Full tutorials: 5-15 min step-by-step guides
Architecture: How stitchwand works under the hood
Live coding: Building integrations with stitchwand
Cadence: 1x/week to 2x/month

Newsletter Strategy

Newsletter Blueprint

Name: "The DESIGN.md Weekly" or "stitchwand Dispatch"
Tool: Buttondown ($0 for first 100 subs) or Resend (free tier)
Cadence: Weekly (Thursdays)
Format: 3-5 bullet points of value + 1 product update + 1 community highlight
Tone: Personal, from Brian. Not corporate.
Sign-up incentives: DESIGN.md starter template, design system audit checklist

Social Media

Platform Priority Stack

Primary X / Twitter

Where developer tool decisions happen. Highest ROI for solo founder. Target: 1,000+ followers by month 3.

Secondary LinkedIn

Enterprise audience, consulting leads, professional credibility. Target: 500+ connections in design/dev space.

Tertiary YouTube

Long-tail SEO via tutorial videos. Evergreen content that compounds. Target: 10+ tutorials by month 3.

Tactical Reddit + HN

Launch moments and technical deep-dives only. Do not spam. Genuine participation only.

X / Twitter: Complete Playbook

Posting Cadence

Day	Content Type	Example	Best Time (ET)
Monday	Product tip / feature highlight	"Did you know you can convert Tokens Studio files to DESIGN.md in one command?"	9:00 AM
Tuesday	Thread (educational)	"5 reasons your design system needs to be AI-readable"	10:00 AM
Wednesday	Community engagement	Reply to 10+ design system related tweets	Ongoing
Thursday	Building in public	"Here's what I shipped this week + what's coming next"	11:00 AM
Friday	Quick take / hot take	"Unpopular opinion: Design tokens without semantic names are useless for AI"	12:00 PM
Sunday	Week ahead preview	"This week: [tutorial], [feature], [blog post]"	7:00 PM

Hashtag Strategy

Primary Hashtags (use 1-2 per tweet)

#DesignSystems #DESIGNMD #GoogleStitch #MCP #AITools

Secondary Hashtags (rotate)

#DevTools #DesignOps#DesignTokens #WebDev #BuildInPublic

Launch-Specific

#stitchwand #KenosMethod #FieldhausBuilds

LinkedIn Strategy

Launch announcement: 800-word article on launch day
Weekly insights: 2-3 paragraph posts about design systems + AI trends
Case studies: "How [Company] used DESIGN.md to transform their Stitch workflow"
Conference recaps: Photos + professional takeaways
Cadence: 2-3x per week. Best times: Tuesday-Thursday, 8-10am ET.

Reddit & Hacker News

Golden Rule for Reddit & HN

90% of your activity should be genuine participation. 10% can reference your tool — and only when it directly solves the problem being discussed. Never link-drop.

Subreddit	Size	Content That Works	Posting Rules
r/webdev	2M+	Technical tutorials, "I built this" posts with substance	Self-promo OK if it provides value
r/FigmaDesign	100K+	Figma ↔ DESIGN.md bridge content	Be helpful first, tool mention second
r/UIDesign	200K+	Design system methodology, Kenos Method	Conceptual/educational content
r/SideProject	100K+	Launch announcement, progress updates	Welcome self-promotion, be genuine

Influencer & Creator Outreach

Creator / Account	Platform	Relevance	Approach
Design system maintainers at large companies	X, LinkedIn	Direct audience overlap	Engage with their content, share the tool when they discuss pain points
AI coding tool reviewers	YouTube	MCP server audience	Reach out with demo access, offer joint tutorial
Google Developer Experts (GDE)	X, YouTube	Google ecosystem credibility	Connect at Cloud Next, share Stitch Skill contribution
Design system newsletter authors	Email, X	Curated audience of DS practitioners	Pitch as a featured tool in their next issue
Indie hacker accounts	X	Building-in-public community	Share metrics openly, mutual amplification

Sales & Revenue

Sales Funnel & Revenue Strategy

From free-tier users to paid subscribers to enterprise consulting projects — a layered revenue engine.

Free → Pro Conversion Funnel

npm install / Web App Visit — 100% of users

▼

Active Usage (3+ sessions) — ~40% retention

▼

Email Captured (newsletter, tool gate) — ~15% of visitors

▼

Hits Pro Feature Wall — ~20% of active users

▼

Converts to Pro ($19/mo) or Team ($49/mo) — ~5% of wall-hitters

Conversion Tactics at Each Stage

Stage	Tactic	Implementation
Visit → Active	Onboarding flow: paste tokens → see DESIGN.md immediately	Zero-friction first experience, no signup needed
Active → Email	Offer DESIGN.md template download gated behind email	Modal after 3rd use: "Want a starter template?"
Email → Feature Wall	Nurture sequence showing Pro features in context	3-email sequence: Day 1 welcome, Day 3 Pro preview, Day 7 use case
Wall → Convert	Show locked Pro features with "Upgrade" badge	Component generator, CI/CD webhook, saved systems — visible but locked
Wall → Convert	14-day free trial of Pro tier	No credit card required to start trial

Pro Tier ($19/mo) — Value Proposition

Free (Forever)

Convert tokens → DESIGN.md (unlimited)
Validate HTML against DESIGN.md (unlimited)
Diff DESIGN.md versions (unlimited)
CLI — all commands, no restrictions
MCP server — local usage, unlimited
Free core package

Pro ($19/mo)

Everything in Free, plus:
Component generation (HTML → React/Vue/Svelte)
Saved design systems (cloud persistence)
CI/CD webhook (validate on every PR)
API access (1,000 req/hr)
Priority MCP server (faster, more context)
Chrome extension premium features
Early access to new features

Enterprise Consulting Sales Process

Design System Audit & Migration

Price: $15,000-25,000 per project

Full audit of existing design system
DESIGN.md conversion and optimization
Stitch integration setup
MCP server customization
CI/CD pipeline for design validation
2 weeks of hands-on work + documentation

Ongoing Retainer

Price: $3,000-5,000/month

Monthly design system health check
DESIGN.md updates and maintenance
Custom tool development
Priority support and consulting hours
8-12 hours/month of dedicated time

Revenue Milestones & Targets

Milestone	Date	Pro Subs	Pro MRR	Consulting	Total MRR
Launch	April 18	0	$0	$0	$0
Pro + Team Launch	June 6	5	$150	$0	$150
First Consulting Client	July	20	$600	$3,000	$3,600
Paid at Scale	September	100	$2,500	$5,000	$7,500
Stitch Graduation	Q4 2026	200	$5,000	$8,000	$13,000
Year 1 End	April 2027	300+	$7,500	$10,000	$17,500

Revenue breakeven

Monthly operating costs scale from $9/mo (launch) to ~$55/mo (Pro tier infrastructure). Breakeven on Pro tier requires just 2 subscribers. The consulting path reaches meaningful revenue ($15-25K) from a single project.

Churn Reduction Strategies

Strategy	Implementation	Expected Impact
Onboarding email sequence	5-email series over 14 days showing Pro features	Reduce Day-30 churn by 20%
Usage-based check-ins	If Pro user hasn't used in 7 days, send "miss you" email	Reactivate 10-15% of at-risk users
Annual plan discount	$15/mo billed annually ($180/yr)	Eliminates monthly churn for annual users
Community access (Pro channel)	Discord channel exclusive to Pro users	Creates switching cost beyond features
Cancellation survey	Ask why + offer 1 month free to stay	Recover 10-20% of cancellations

Pricing Strategy

Pricing Tiers

Free core model: free CLI and core library for individual developers, paid tiers for teams and enterprises.

Free

For individual developers and personal projects. Full CLI + core library, forever free.

CLI with convert, validate, diff commands
All token format conversions (DTCG, CSS, Style Dictionary, Figma)
Schema validation with built-in rules
Token diffing with visual output
TypeScript SDK (@stitchwand/core)
Community support (Discord, GitHub Issues)
Unlimited local usage

Pro

$19 /mo

For design system leads and power users who need the full web experience.

Everything in Free
Web app with visual token editor
Advanced Tools (Prompt Library, Documents, Design Systems)
Starter Kits, Design Swarm, and Documents
Activity Graph with auto-seeded demo data
99 community design libraries
Custom validation rules
Token history and changelog
Priority support (email)

Team

$49 /mo

For design ops teams that need collaboration, MCP integration, and shared infrastructure.

Everything in Pro
MCP server with full tool access
Agent Hub — AI agent orchestration
Shared design system workspaces
Team member management and roles
Usage analytics and dashboards
CI/CD integration (GitHub Actions, GitLab)
Webhook notifications
Up to 10 team members

Enterprise

Custom

For organizations that need compliance, security, and dedicated support.

Everything in Team
SSO (SAML, OIDC) integration
Full audit log with export
Dedicated customer success manager
Custom integrations and workflows
On-premise / VPC deployment option
SLA with guaranteed uptime
Unlimited team members

Revenue Projections

Metric	Phase 1 (Q2 '26)	Phase 2 (Q3 '26)	Phase 3 (Q4 '26)	Phase 4 (Q1 '27)
Free Users	800	2,500	6,000	12,000
Pro Subscribers	0	40	200	500
Team Subscribers	0	0	25	80
Enterprise Contracts	0	0	0	3
MRR	$0	$1,160	$8,280	$29,420+
ARR Run Rate	$0	$13,920	$99,360	$353,040+

Business Development

Networking & Competitive Landscape

Strategic relationships, conference strategy, thought leadership, and competitive positioning.

Networking & Community

Google Cloud Next 2026 Strategy (April 22, Las Vegas)

Google Cloud Next is 11 days after launch. This is the single highest-leverage networking event of the year.

Pre-Conference (April 18-21)

Email David East (Google DevRel) with launch announcement

Include GitHub link and offer to demo at Next

DM 5-10 known Stitch community members on X

Ask if they're attending Next, offer to demo stitchwand in person

Prepare a 2-minute live demo on laptop

CLI convert → web app validate → MCP in Claude Code. Must work offline.

Print 50 business cards with QR code to stitchwand.com

Identify all Stitch-related sessions in the agenda

Attend every one. Sit near the front. Ask questions that reference DESIGN.md tooling.

At the Conference

Priority	Target	Action	Goal
P0	Google Stitch team members	Approach after Stitch sessions, show tool, give card	Get on their radar, offer to contribute
P0	David East (DevRel)	Pre-scheduled meeting or hallway conversation	Demo the tool, discuss Stitch Skill contribution
P1	Enterprise design system teams	Network at sessions about design + AI	Consulting pipeline
P1	Other MCP / AI tool builders	Developer lounge conversations	Partnership opportunities
P2	DevRel from other companies	Casual networking	Future speaking opportunities

Design System Conferences & Meetups

Event	When	Relevance	Action
Google Cloud Next	April 22, 2026	Critical	Attend. Network. Demo.
Google I/O	May 2026 (TBD)	Critical	Watch remotely. Blog about Stitch announcements.
Config (Figma)	June 2026 (TBD)	High	Figma Bridge launch timing. Submit talk proposal.
Clarity Conference	Q3/Q4 2026	High	Submit Kenos Method talk.
React Summit	Q3 2026	Medium	"From DESIGN.md to React in 30 seconds."

Thought Leadership: The Kenos Method

Kenos Method Positioning Checklist

Publish "The Kenos Method" as a long-form blog post

3,000+ words. Define the methodology. This becomes the canonical reference.

Create a /kenos-method landing page on stitchwand.com

Submit talk proposals to 3 conferences using Kenos Method angle

Reference Kenos Method in consulting proposals

Create a short (2-page) Kenos Method PDF for conference handouts

Community & User Engagement

npm Install

→

Bug Report / Feature Request

→

Active User

→

Community Advocate

→

Paid Customer

Responsive issue triage: Always maintain 3-5 known-issues updates
Fast support responses: Reply to every bug report within 24 hours
Public thanks: Thank active community members in release notes and on X/Twitter
Community Discord channel: Private channel with early access to roadmap

Competitive Landscape

Competitive Matrix

stitchwand operates at the intersection of design token tooling, AI-native design infrastructure, and MCP-enabled developer tools. No existing product covers all three categories.

Product	Type	Token Convert	Validation	Diff	AI Features	MCP	Stitch	Pricing
stitchwand	Us	Yes — all formats	Yes — rules engine	Yes — visual	Yes — native	Yes — first	Yes — companion	Free / $19+
Style Dictionary	Direct	Yes — config-heavy	No	No	No	No	No	Free (OSS)
Specify	Direct	Yes — limited	Basic	No	No	No	No	$200+/mo
Tokens Studio	Direct	Figma-centric	Basic	Basic	No	No	No	Free / $15
Figma Dev Mode	Adjacent	CSS only	No	No	Basic	No	No	$5/editor/mo
Storybook	Adjacent	No	No	No	No	No	No	Free (OSS)

stitchwand Advantages

AI-Native Architecture

Built from day one with AI workflows in mind. Starter Kits, AI Audit, Activity Graph, and more. No competitor has meaningful AI features.

MCP-First Distribution

The only design token tool with an MCP server. Every AI code editor becomes a distribution channel.

Stitch Companion Status

Purpose-built for Google Stitch. First-mover in the Stitch Skills marketplace.

Full-Stack Coverage

CLI for terminals, MCP server for AI editors, web app for visual workflows, TypeScript SDK for programmatic use.

Free Developer Tools

Core library and CLI are free to use. Developers can install, evaluate, and trust the tool with zero friction.

Speed to Value

Under 90 seconds from install to first conversion output. No config files. No build step. No account needed.

Competitive Risk Factors

Risk	Likelihood	Impact	Mitigation
Google builds token tools into Stitch natively	Medium	High	Move fast, build community moat, diversify beyond Stitch
Figma adds DTCG export	High	Medium	Validation + diff + AI features not easily replicated
Style Dictionary v5 modernizes	Medium	Medium	Our AI/MCP/web features create a different category
New VC-funded competitor enters	Low	Medium	First-mover + npm ecosystem presence is defensible
Stitch adoption is slower than expected	Medium	Medium	Tool is platform-agnostic; Stitch is a channel, not a dependency

Operations

Launch Plan & Metrics

Four-phase launch timeline and AARRR metrics framework for tracking progress.

Launch Plan

Four-Phase Launch Timeline

Each phase builds on the prior, with clear milestones that gate advancement.

Phase 1 — Q2 2026

Free Tools Foundation

Ship the CLI and core library as free npm packages. Establish npm presence, build developer adoption. Focus ruthlessly on developer experience.

npm publish @stitchwand/cli npm publish @stitchwand/core Docs site launch README + docs site DTCG, CSS, Style Dictionary conversion Token validation rules engine Product Hunt launch

1,000

npm weekly downloads

500

Active users

Discord members

Phase 2 — Q3 2026

Web App + Stitch Ecosystem

Launch the web app in beta. Submit to Google Stitch Skills marketplace. Begin early adopter program.

Web app beta launch Stitch Skills marketplace listing Figma Bridge integration Starter Kits Activity Graph Free/Pro tier gating Early adopter program (100 seats)

2,500

npm weekly downloads

500

Web app beta users

Stitch Skills listing

Phase 3 — Q4 2026

Pro Tier + MCP Launch

Launch Pro subscription. Publish MCP server. Begin monetization targeting $25K MRR.

Pro tier launch + Stripe billing MCP server npm publish MCP directory listings Custom validation rules YouTube channel launch SEO content push (20 articles)

5,000

npm weekly downloads

$8.3K

Monthly recurring revenue

500

MCP installations

Phase 4 — Q1 2027

Team Tier + Enterprise

Launch Team tier with shared workspaces. Begin enterprise pilot conversations. Target 3 enterprise contracts.

Team tier launch Agent Hub (AI orchestration) Shared workspaces Enterprise SSO (SAML) 3 enterprise pilot programs

10,000

npm weekly downloads

$29K+

Monthly recurring revenue

Enterprise contracts

Launch Readiness Checklist

Product

Before Phase 1 Launch

CLI supports all 4 core token formats
80%+ test coverage on @stitchwand/core
Zero critical bugs in validation engine
README with quickstart, examples, API docs
npm package with correct metadata and keywords
Landing page live at stitchwand.com

Marketing

Before Phase 1 Launch

Product Hunt launch queued and scheduled
3 launch blog posts drafted
Twitter/X account active with 2 weeks of content queued
Discord server set up with channel structure
Email list capture on landing page

Metrics (AARRR Framework)

Acquisition

npm Weekly Downloads

5,000

Target by Q4 2026

GitHub Stars

2,000

Target by Q4 2026

Web App Signups

3,000

Target by Q4 2026

MCP Server Installations

500

Target by Q4 2026

Activation

First Conversion (CLI)

72%

% of installers who run convert

First Validation

58%

% of installers who run validate

First Starter Kit Gen

45%

% of web users who try Starter Kits

Time to First Value

<90s

Install to first conversion output

Revenue

Monthly Recurring Revenue

$29K

Target by Q1 2027

Free-to-Pro Conversion

4.5%

Target conversion rate

Monthly Churn Rate

<5%

Target gross churn

Net Revenue Retention

115%

Target NRR (expansion > churn)

Engagement

DAU / MAU Ratio

28%

Target stickiness ratio

Features Per Session

3.2

Average tool uses per session

MCP Tool Calls / Day

2,400

Target across all MCP users

Session Duration (Web)

8.5m

Average minutes per session

Referral & Growth

Discord Members

1,500

Target by Q4 2026

Twitter/X Followers

5,000

Target by Q4 2026

Organic Referral Rate

22%

% of signups from word-of-mouth

Community Advocates

Target by Q4 2026

Paid Acquisition

Paid Acquisition Strategy

When organic growth plateaus and revenue supports it, paid acquisition accelerates growth. Combined playbook from both long-term and conference-specific campaigns.

When to Start Paid Acquisition

Do NOT start paid acquisition until ALL of these conditions are met:

Prerequisites (All Required)

Pro tier is live and converting at 3%+ from free to paid

You need a working conversion funnel before spending money to fill it

LTV:CAC ratio is calculable and favorable (target 3:1 or better)

Need at least 3 months of churn data to calculate LTV

MRR exceeds $1,000 (organic growth validates the market)

Dedicated budget of $500/mo allocated without impacting operations

Landing pages are optimized with A/B tested copy

Earliest realistic start: September 2026

Given the $358 total budget at launch and $9/mo operating costs, paid acquisition is a Q3-Q4 2026 activity at the earliest. The first 5 months should be 100% organic growth.

Google Ads Strategy

Campaign	Keywords	Landing Page	Daily Budget	Expected CPC
Brand	"stitch wand", "stitchwand"	Homepage	$5	$0.50-1.00
DESIGN.md (low competition)	"DESIGN.md tool", "DESIGN.md template", "create DESIGN.md"	/docs/design-md-guide	$10	$1.00-3.00
Design Tokens (moderate)	"convert design tokens", "design token tool"	/convert	$10	$2.00-5.00
Stitch (niche)	"Google Stitch wand", "Stitch design system"	/	$5	$1.00-3.00

Budget: $500/mo starting allocation

DESIGN.md campaign: $200/mo (greenfield keywords, low competition)
Design Tokens campaign: $200/mo (moderate competition, higher intent)
Brand + Stitch campaigns: $100/mo (defensive + niche)

X / Twitter Ads

Promoted Tweets

Promote your best-performing organic tweets. Target developer accounts and design system interests. Budget: $150/mo.

Follower Campaigns

Build @fieldhaus follower count by targeting followers of design system tools, AI coding tools, and Google DevRel accounts. Budget: $100/mo.

Reddit Ads

Subreddit Target	Ad Format	Copy Angle	Budget
r/webdev	Promoted post	"I built a CLI that converts your design tokens to DESIGN.md for Google Stitch. Free and open to all."	$75/mo
r/FigmaDesign	Promoted post	"Bridge your Figma design system to Google Stitch with DESIGN.md"	$50/mo
r/ExperiencedDevs	Promoted post	"Design system validation for AI-generated code"	$50/mo
r/SideProject	Promoted post	"From 0 to 5,000 npm downloads: building stitchwand in public"	$25/mo

Sponsorship Opportunities

Property	Type	Audience Size	Estimated Cost	Fit
Design System newsletters	Newsletter	5-15K subscribers	$100-300/issue	High
TLDR Newsletter	Newsletter	1M+ subscribers	$2,000-5,000/issue	Medium
Syntax.fm	Podcast	Massive developer audience	$2,000-4,000/episode	Medium
Design systems YouTube channels	Video	10-50K subscribers	$200-800/video	High
AI coding tool reviewers (YouTube)	Video	10-100K subscribers	$300-1,500/video	High

Budget Allocation Recommendations

Phase 1: First $500/mo (Q3-Q4 2026)

Google Ads (DESIGN.md keywords)$200 (40%)

Newsletter Sponsorships$150 (30%)

X/Twitter Promoted Tweets$100 (20%)

Reddit Ads$50 (10%)

ROI Tracking Framework

UTM parameters on every paid link

utm_source, utm_medium, utm_campaign

Plausible goals for conversion events

email signup, Pro trial start, Pro payment, consulting inquiry

Monthly CAC calculation by channel

LTV calculation (update monthly)

Monthly paid acquisition report

Key Metrics Per Channel

Metric	Target	Kill Threshold	Scale Threshold
Cost per Click (CPC)	< $3.00	> $5.00 (pause)	< $1.50 (increase budget)
Click-through Rate (CTR)	> 1.5%	< 0.5% (revise creative)	> 3% (scale)
Cost per Trial Start	< $15	> $30 (pause)	< $8 (increase budget)
Cost per Pro Conversion (CAC)	< $50	> $100 (unprofitable)	< $25 (profitable scale)
LTV:CAC Ratio	> 3:1	< 1.5:1 (losing money)	> 5:1 (scale aggressively)

The $19/mo LTV math

At $19/mo with 5% monthly churn: LTV = $19 / 0.05 = $380.
At $19/mo with 10% monthly churn: LTV = $19 / 0.10 = $190.

With $190 LTV and a 3:1 target ratio, your maximum CAC is ~$63.

Google Cloud Next 2026 Campaign

Conference Paid Advertising Playbook

Full paid advertising playbook for Google Cloud Next April 21-24, 2026 in Las Vegas. Accounts, targeting, geo-fencing, billing, exact spend.

$600-800

Total Budget

$805

Max Spend

$560-685

Realistic Spend

$200

Minimum Viable

Campaign Strategy

Four phases from soft launch to cool down, peaking during Google Cloud Next in Las Vegas. Code ships April 18, ads start April 21. LinkedIn for job-title targeting, X for keyword targeting. Total budget $600-800, with a $200 minimum viable option.

Platform Strategy

Job Title + Skills Targeting

Best for reaching "Senior Frontend Engineers at SaaS companies." Target by job function, skills, and seniority. City-level geo-fencing for conference targeting.

Campaign Manager at linkedin.com/campaignmanager
Min $10/day budget
CPC benchmark: $3-6, CPM: $28-33
Good CTR: 0.5%+

X (Twitter)

Keyword + Interest Targeting

Best for reaching "people who tweeted about Google Stitch." Target by keywords and follower lookalikes. Geo + keyword combo for conference proxy.

Ads Manager at ads.x.com
Autobid recommended
CPC benchmark: ~$0.74, CPM: ~$2
Good CTR: 1%+

Campaign Phases

Phase 1

Soft Launch — Apr 21-25

$15/day total. Test creative, learn what works.

LinkedIn "Design System Pros" — $10/day nationwide
X "Stitch Keywords" — $5/day nationwide
After 3 days: CTR > 0.3%? CPC < $8? Keep it.

Phase 2

Ramp Up — Apr 19-21

$35/day + $75 boost. Double budgets, add demo video.

LinkedIn $10 → $20/day, X $5 → $10/day
Boost best organic post — $75 over 7 days
Add full demo video as second ad

Phase 3

Peak / Geo-Fence — Apr 21-25

$90/day. Conference geo-fencing + nationwide.

LinkedIn geo Las Vegas + tech jobs — $40/day
X geo Las Vegas + #GoogleCloudNext — $20/day
Keep nationwide: LinkedIn $20 + X $10 = $30/day

Phase 4

Cool Down — Apr 26-30

$20/day. Retarget warm visitors.

Pause geo campaigns
Reduce nationwide: LinkedIn $10 + X $5
Launch retargeting — $5/day

Budget Breakdown

Campaign	Dates	$/Day	Days	Max
Soft Launch — LinkedIn	4/21-25	$10	6	$60
Soft Launch — X	4/21-25	$5	6	$30
Ramp — LinkedIn	4/19-21	$20	3	$60
Ramp — X	4/19-21	$10	3	$30
Organic Boost	4/19	—	—	$75
Peak — LinkedIn geo	4/21-25	$40	5	$200
Peak — X geo	4/21-25	$20	5	$100
Peak — LinkedIn nationwide	4/21-25	$20	5	$100
Peak — X nationwide	4/21-25	$10	5	$50
Cool Down — all	4/26-30	$20	5	$100
Maximum Total				$805
Realistic Range				$560-685

Ad Copy Templates

LinkedIn — Nationwide

Soft Launch Copy

Option A: "I tried to build an app in Google Stitch. 10 times. Every version ignored my design system. So I built the bridge between your tokens and Stitch. → stitchwand.dev"

Option B: "Your design system has 2,000 tokens. Google Stitch has no idea they exist. stitchwand converts your tokens into DESIGN.md so Stitch generates on-brand."

LinkedIn — Geo-Fence

Conference Copy

Option A: "At Google Cloud Next? Every AI generator ignores your design system. stitchwand fixes that."

Option B: "Seeing Stitch demos this week? Cool. Now make it respect YOUR brand. → stitchwand.dev"

X — All Campaigns

X Ad Copy

Option A: "npx stitchwand convert ./tokens.json → DESIGN.md. Your design system, Stitch's language."

Conference: "At #GoogleCloudNext? Your design tokens → DESIGN.md → on-brand Stitch. Try it: stitchwand.dev"

Creative Specs

Platform	Format	Size	Notes
LinkedIn	Single image	1200 x 628px	2:1 ratio. PNG or JPG.
LinkedIn	Square video	1080 x 1080px	MP4. Under 10 min. 30-60s ideal.
LinkedIn	Landscape video	1920 x 1080px	16:9. Square gets more feed real estate.
X	Single image	1200 x 675px	16:9. PNG or JPG.
X	Square image	1080 x 1080px	1:1. Works well in mobile feed.
X	Video	1080 x 1080px	MP4. Under 2:20. 30-60s ideal.

Setup Checklist

LinkedIn Setup

Campaign Manager + Insight Tag

linkedin.com/campaignmanager → "Advertise"
Connect Fieldhaus company page
Add credit card — min $10/day
Install Insight Tag on stitchwand.dev
CRITICAL: Disable LinkedIn Audience Network on EVERY campaign

X Setup

X Ads + Pixel

ads.x.com → US, Eastern timezone. Add card.
Install X Pixel on stitchwand.dev

Tracking

UTM Parameters

Format: stitchwand.dev?utm_source=linkedin&utm_medium=paid&utm_campaign=soft-launch
Verify Insight Tag and X Pixel are firing

Monitoring & Optimization

Daily Check (2 min)

Key Metrics

Spend — on budget?
CTR — below 0.3% on LinkedIn or 0.5% on X = swap creative
CPC — above $8 on LinkedIn = broaden targeting
Impressions — under 500/day = audience too small

Stop Thresholds

When to Pause

CTR below 0.2% after 3 days
$100 spent with zero site visits

Go Thresholds

When to Scale

CTR above 1%
CPC under $3 on LinkedIn

A/B Testing

Run 2 ads per campaign with ONE difference. Call a winner after 500+ impressions per variant or 3 days, whichever comes first. Pause the loser, keep the winner, start a new challenger.

Minimum Viable Plan — $200

If you only have $200

1. Install LinkedIn Insight Tag today (free — every organic visitor becomes retargetable).
2. Boost your best organic post — $75 over 7 days.
3. LinkedIn geo-fence during conference — $125 (5 days x $25/day).
Total: $200. If you only do ONE paid thing, boost your best post.

Post-Campaign Analysis

After April 30

Metrics to Pull

Pull from Campaign Manager + PostHog: total spend, total clicks, total impressions, avg CPC, avg CTR, site visits from ads (UTM filtered), npm installs during campaign period, active users during period.

ROI calculation: Total spend / leads = cost per lead
One engagement ($1,800/wk x 12 wks = $21,600) / total spend = ROI multiple
Even one lead from $800 spend = 27x return
Save: which campaign had best CTR, which creative won, which targeting worked

⚠ Confidential

Stealth Marketing & Organic Growth

Everything outside of paid ads. Community seeding, influencer relationships, content, earned media, risks, and reusable templates. Timeline: start now, peak during Google Cloud Next 4/21–25, continue post-conference.

Organic Growth Plan

Build a real organic following. When paid ads start, they land on a populated account with credibility. Seed communities so stitchwand is top-of-mind when conference starts.

Phase 0 Foundation — Before Ads (4/15)

@stitchwand X Account Voice

2-3 posts daily. CLI demos (video GIFs), token conversion live threads, design system hot takes, quotes from founders. Show personality, no sales pitch yet.

Target: 500-1000 followers by 4/21 so ads land on a populated account. 2-3 posts/day = ~700-1400 impressions/day on a new account.

Seed Reddit & Design Communities

Communities: r/webdev, r/frontend, r/designsystems, r/googlecloud, r/javascript. Answer 2-3 questions/week about design tokens, DESIGN.md conversion, CSS-in-JS. Link stitchwand only when directly relevant.

Ratio: 9 helpful posts, 1 product mention. Be genuinely useful first.

Never do this: 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 (Brian's LinkedIn)

3 posts/week. Rotate Mon/Wed/Fri: 1) Technical insight ("Token systems I admire and why"), 2) Founder story ("Why we built this instead of buying"), 3) Product progress ("Shipped: Google Stitch bridge").

LinkedIn rewards founder authenticity. Organic posts that get 20+ comments become your cheapest paid ads when boosted ($75 boost).

Key insight: Organic posts that get 20+ comments become your cheapest paid ads when boosted. You already know they work.

"Zero-to-DESIGN.md" Reference Thread

12-tweet thread: Step-by-step converting design tokens with stitchwand. Live code snippets, before/after Figma screenshots, real CLI output. Cross-post to LinkedIn as long-form article (native, not link). This becomes your most-shared content — 1000s of impressions over months.

npm Download Social Proof

Target: 500+ npm downloads before launch. Add badge in README showing download count. Add "Used by:" section showing early adopters. Link from stitchwand.dev above the fold. Every download is a trust signal.

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". Have 3-4 real users ready to comment with genuine experiences. DO NOT ask for upvotes.

Critical: HN bans accounts that coordinate upvotes or post multiple times per week. One natural launch, genuine comments, that's it.

Product Hunt Launch

Monday 4/28-29. Cool-down week after conference. Prep: Accepted by a Hunter, polished Maker profile, 3+ screenshots, tagline under 60 chars, first comment explaining "Why we built this."

PH is not for going viral, it's for validation. Even 200 upvotes = 3+ weeks of media mentions. Worth the polish.

Discord/Slack Community Presence

3-5 messages/week. Design Systems Slack, Figma Slack, Tailwind Discord, CSS Discord. Join, lurk 2 days, then answer questions. "Hey, ran into this same problem, here's how I'd approach it" — never a sales pitch.

Conference Live-Tweeting

During Google Cloud Next, live-tweet sessions about Stitch, design tokens, integrations. Tag @GoogleCloud, use #GoogleCloudNext. Organic geo-targeting — reaching people IN the room discussing the platform you're building for.

Early User Testimonials

DM early users asking for honest feedback ("No script — just tell me what you actually think"). 3 genuine quotes > 0 quotes. Get these in before Product Hunt launch.

Phase 2 Amplification — May Onwards

Technical Blog Post (dev.to / Hashnode)

"How I built a design token bridge for Google Stitch" — architecture, token parsing, Stitch API, CLI patterns. 4-6min read. Cross-post to Medium. One deep post = passive traffic for 6+ months.

Design System Newsletters

Target: Sidebar.io, CSS Weekly, Frontend Focus, Design Systems Weekly (10K-100K subscribers). Email curator with blog post + 2-3 sentence summary. One newsletter mention = 200-500 click-throughs from trusted readers.

Comparison Guide

"stitchwand vs. manual DESIGN.md: benchmarks" — Before/after time saved, token accuracy, edge cases. Honest comparison with tradeoffs. Drives trust AND SEO.

Influencer & Earned Media

How to work with creators without being creepy. Micro-influencers, design thought leaders, and the rules that keep you compliant.

Micro-Influencers (1K–10K followers) — Best ROI

Why micro: 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.

Identify Targets

Search for Figma creators, CSS/design system educators, Google Cloud builders on X/YouTube.

Design token creators (#figmadesignsystems)
Google Cloud educators
CSS-in-JS / design system writers

Compensation Models

Free product + swag: Early access, nice t-shirt ($0)
Product + honorarium: Free access + $100-300 for their time
Affiliate link: Unique referral code, 10% of annual subs for 2 years

Key Rules

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.

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.

Mid-Tier (10K–50K followers) — Design/Dev Thought Leaders

Strategy: Don't cold-pitch mid-tier. Build a relationship first. Reply to their tweets for 2 weeks, share their work, then reach out.

Relationship First

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 with your pitch

Budget

$500-1000 per post/video depending on audience size and engagement. But the best coverage comes from the product being genuinely good, not paid.

FTC Compliance: Non-negotiable. You MUST disclose all paid endorsements. Failure penalties: $50K+ per incident. Undisclosed paid posts destroy trust when discovered — and they WILL be discovered in niche dev/design communities.

DO NOT

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"

FTC Compliance Checklist

All paid posts include #ad, #sponsored, or "paid partnership"
Written agreement specifying disclosure requirements
Creator must have actually used the product
All claims truthful and substantiated
Keep records: emails, agreements, receipts

Risk Register

Stealth marketing walks a fine line. The moment you cross from "being helpful while having a product" to "pretending to be neutral while secretly promoting" — you've lost.

Core principle: Every tactic is designed to build GENUINE organic presence, not to deceive. When in doubt, disclose. Real relationships scale longer than astroturfing ever will.

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.
Undisclosed paid endorsement	CRITICAL	Low (if rules followed)	FTC fines ($50K+), influencer backlash, permanent trust loss.	Written contracts requiring disclosure. Review all posts before they go live. Keep receipts.
Community backlash	MEDIUM	Medium	"This is just an ad." Downvotes, negative sentiment scares away real users.	10:1 rule — 10 helpful posts per 1 product mention. Build credibility for 3-4 weeks first.
Influencer goes rogue	MEDIUM	Low	Off-brand messaging, controversial statements, inflated metrics.	Vet recent tweets. Written agreements. Kill switch: end partnership + request post removal.
Organic cannibalizes paid	LOW	Medium	Can't attribute conversions. Spend on ads reaching organic converters.	UTM tracking on ALL links. Separate landing pages if possible.
Content burnout	MEDIUM	High	Solo founder: tweets + LinkedIn + communities + product building = burnout.	Batch content creation. Use AI to draft, then edit. Schedule posts. Consistency > volume.
Account suspension	HIGH	Low (if rules followed)	X/Reddit/HN bans. Months of work disappear.	Never use bots, follow/unfollow automation, buy followers, or coordinate with friends.

Red Lines (Do Not Cross)

Never:

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

Flagged for astroturfing on Reddit

Acknowledge it publicly. "I should have been more transparent about being the founder. Here's the honest story." Admit, don't defend. Communities respect humility.

Influencer makes unauthorized claim

Contact them immediately. "Hey, we didn't agree on that claim — can you adjust the post?" Document everything. If they refuse, publicly clarify.

You realize your tactic is astroturfing

STOP. Pivot to transparency. "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."

Reusable Toolkit

Copy these templates, adapt them for your voice, and ship. Each is battle-tested.

Content Calendar Template

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.

Outreach Email Templates

Cold Outreach (Micro-influencer)

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

Warm Outreach (Engaged with you)

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

Hot Outreach (They asked about it)

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

What Gets Upvoted

Posts that solve a real problem
Posts with honest limitations ("Here's what doesn't work")
Posts with live examples / screenshots
Creators engaging genuinely in comments

What Gets Banned

Self-promotional posts from new accounts
Coordinated upvotes from friend accounts
Spammy language ("You won't BELIEVE...")
Links with excessive affiliate codes
Duplicate posts across communities

HN / Reddit Templates

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

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

Claude Prompt for Organic Content Planning

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.

UTM Tracking Setup

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.

Sensitive Strategy Document

AI-First Go-to-Market Philosophy

First-Mover Position: DESIGN.md Tooling

Key Metrics & KPIs

Leading Indicators (track weekly)

Goals by Horizon

Five Strategic Pillars

Executive Summary

Strategic Pillars

Go-to-Market Timeline

Core Value Proposition

Market Analysis

Market Sizing

Growth Drivers

Market Segments

Target Personas

Persona Prioritization Matrix

Distribution Channels

Channel Investment by Phase

Inbound Lead Generation Engine

SEO: Own the DESIGN.md Search Landscape

Priority Keywords (Months 1-3)

SEO Technical Checklist

Content Marketing Funnel

Free Tools as Lead Generation

Tactics for npm-to-website conversion

MCP Registry Listings as Discovery Channels

Chrome Extension as User Acquisition

Free Tools That Capture Emails

AI-Powered Lead Scoring & Qualification

Lead routing logic

Content Pillars

30-Day Launch Content Calendar (April 18 – May 18)

Week 1: Launch Week (April 18-24)

Week 2: Tutorial Week (April 25 – May 1)

Week 3: Deep Dive Week (May 2-8)

Week 4: Growth Week (May 9-18)

Blog Post Queue (Months 2-6)

Video Content Strategy

Newsletter Strategy

Platform Priority Stack

X / Twitter: Complete Playbook

Posting Cadence

Hashtag Strategy

LinkedIn Strategy

Reddit & Hacker News

Influencer & Creator Outreach

Free → Pro Conversion Funnel

Conversion Tactics at Each Stage

Pro Tier ($19/mo) — Value Proposition

Enterprise Consulting Sales Process

Revenue Milestones & Targets

Churn Reduction Strategies

Pricing Tiers

Revenue Projections

Google Cloud Next 2026 Strategy (April 22, Las Vegas)

Pre-Conference (April 18-21)

At the Conference

Design System Conferences & Meetups

Thought Leadership: The Kenos Method

Community & User Engagement

Competitive Matrix

stitchwand Advantages

Competitive Risk Factors

Four-Phase Launch Timeline

Launch Readiness Checklist

When to Start Paid Acquisition

Google Ads Strategy

Budget: $500/mo starting allocation

X / Twitter Ads

Reddit Ads

Sponsorship Opportunities

Budget Allocation Recommendations

Phase 1: First $500/mo (Q3-Q4 2026)

ROI Tracking Framework

Key Metrics Per Channel

Conference Paid Advertising Playbook

Platform Strategy

Campaign Phases

Budget Breakdown