Suede Free-Tool Growth Strategy
Suede uses engineering as marketing when a genuinely useful tool can create qualified discovery and a natural bridge to the paid product. Select, score, and scope the smallest maintainable calculator, grader, generator, or utility whose output earns attention rather than merely capturing it.
Initial Assessment
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before designing a tool strategy, understand:
Business Context - What's the core product? Who is the target audience? What problems do they have?
Goals - Lead generation? SEO/traffic? Brand awareness? Product education?
Resources - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?
Core Principles
1. Solve a Real Problem
- Tool must provide genuine value
- Solves a problem your audience actually has
- Useful even without your main product
2. Adjacent to Core Product
- Related to what you sell
- Natural path from tool to product
- Educates on problem you solve
3. Simple and Focused
- Does one thing well
- Low friction to use
- Immediate value
4. Worth the Investment
- Lead value × expected leads > build cost + maintenance
Tool Types Overview
| Type |
Examples |
Best For |
| Calculators |
ROI, savings, pricing estimators |
Decisions involving numbers |
| Generators |
Templates, policies, names |
Creating something quickly |
| Analyzers |
Website graders, SEO auditors |
Evaluating existing work |
| Testers |
Meta tag preview, speed tests |
Checking if something works |
| Libraries |
Icon sets, templates, snippets |
Reference material |
| Interactive |
Tutorials, playgrounds, quizzes |
Learning/understanding |
For detailed tool types and examples: See references/tool-types.md
Ideation Framework
Start with Pain Points
What problems does your audience Google? - Search query research, common questions
What manual processes are tedious? - Spreadsheet tasks, repetitive calculations
What do they need before buying your product? - Assessments, planning, comparisons
What information do they wish they had? - Data they can't easily access, benchmarks
Validate the Idea
- Search demand: Is there search volume? How competitive?
- Uniqueness: What exists? How can you be 10x better?
- Lead quality: Does this audience match buyers?
- Build feasibility: How complex? Can you scope an MVP?
Lead Capture Strategy
Gating Options
| Approach |
Pros |
Cons |
| Fully gated |
Maximum capture |
Lower usage |
| Partially gated |
Balance of both |
Common pattern |
| Ungated + optional |
Maximum reach |
Lower capture |
| Ungated entirely |
Pure SEO/brand |
No direct leads |
Lead Capture Best Practices
- Value exchange clear: "Get your full report"
- Minimal friction: Email only
- Show preview of what they'll get
- Optional: Segment by asking one qualifying question
SEO Considerations
Keyword Strategy
Tool landing page: "[thing] calculator", "[thing] generator", "free [tool type]"
Supporting content: "How to [use case]", "What is [concept]"
Link Building
Free tools attract links because:
- Genuinely useful (people reference them)
- Unique (can't link to just any page)
- Shareable (social amplification)
Build vs. Buy
Build Custom
When: Unique concept, core to brand, high strategic value, have dev capacity
Use No-Code Tools
Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow
When: Speed to market, limited dev resources, testing concept
Embed Existing
When: Something good exists, white-label available, not core differentiator
MVP Scope
Minimum Viable Tool
- Core functionality only—does the one thing, works reliably
- Essential UX—clear input, obvious output, mobile works
- Basic lead capture—email collection, leads go somewhere useful
What to Skip Initially
Account creation, saving results, advanced features, perfect design, every edge case
Evaluation Scorecard
Rate each factor 1-5:
| Factor |
Score |
| Search demand exists |
___ |
| Audience match to buyers |
___ |
| Uniqueness vs. existing |
___ |
| Natural path to product |
___ |
| Build feasibility |
___ |
| Maintenance burden (inverse) |
___ |
| Link-building potential |
___ |
| Share-worthiness |
___ |
25+: Strong candidate | 15-24: Promising | <15: Reconsider
Task-Specific Questions
- What existing tools does your audience use for workarounds?
- How do you currently generate leads?
- What technical resources are available?
- What's the timeline and budget?
Boundaries
- Do not claim search demand, lead volume, link potential, or build feasibility without evidence and dated assumptions.
- Do not build, deploy, publish, collect leads, or connect production data unless the user authorizes implementation.
- Do not invent tool outputs or use a calculator as disguised professional, legal, medical, or financial advice.
- Do not decide pricing, data-retention, or consent policy for the user.
Routing
- Use
suede-lead-magnets for downloadable assets and suede-site-alchemy for the public conversion surface.
- Use
suede-seo-audit for search validation and suede-analytics for usage measurement.
- Use
suede-emails for the post-capture lifecycle sequence.
1---2name: suede-free-tools3description: Suede-affiliated engineering-as-marketing strategy for selecting, scoring, and scoping calculators, graders, generators, and other free interactive tools. Use when the user wants a lead, link, education, or product-adoption asset with a measurable path to the paid product. NOT FOR: downloadable lead assets (use suede-lead-magnets), implementation of a full website (use suede-site-alchemy), or search diagnostics (use suede-seo-audit).4---5
6# Suede Free-Tool Growth Strategy
7
8Suede uses engineering as marketing when a genuinely useful tool can create qualified discovery and a natural bridge to the paid product. Select, score, and scope the smallest maintainable calculator, grader, generator, or utility whose output earns attention rather than merely capturing it.
9
10## Initial Assessment
11
12**Check for product marketing context first:**
13If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
14
15Before designing a tool strategy, understand:
16
171. **Business Context** - What's the core product? Who is the target audience? What problems do they have?
18
192. **Goals** - Lead generation? SEO/traffic? Brand awareness? Product education?
20
213. **Resources** - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?
22
23---
24
25## Core Principles
26
27### 1. Solve a Real Problem
28- Tool must provide genuine value
29- Solves a problem your audience actually has
30- Useful even without your main product
31
32### 2. Adjacent to Core Product
33- Related to what you sell
34- Natural path from tool to product
35- Educates on problem you solve
36
37### 3. Simple and Focused
38- Does one thing well
39- Low friction to use
40- Immediate value
41
42### 4. Worth the Investment
43- Lead value × expected leads > build cost + maintenance
44
45---
46
47## Tool Types Overview
48
49| Type | Examples | Best For |
50|------|----------|----------|
51| Calculators | ROI, savings, pricing estimators | Decisions involving numbers |
52| Generators | Templates, policies, names | Creating something quickly |
53| Analyzers | Website graders, SEO auditors | Evaluating existing work |
54| Testers | Meta tag preview, speed tests | Checking if something works |
55| Libraries | Icon sets, templates, snippets | Reference material |
56| Interactive | Tutorials, playgrounds, quizzes | Learning/understanding |
57
58**For detailed tool types and examples**: See [references/tool-types.md](references/tool-types.md)
59
60---
61
62## Ideation Framework
63
64### Start with Pain Points
65
661. **What problems does your audience Google?** - Search query research, common questions
67
682. **What manual processes are tedious?** - Spreadsheet tasks, repetitive calculations
69
703. **What do they need before buying your product?** - Assessments, planning, comparisons
71
724. **What information do they wish they had?** - Data they can't easily access, benchmarks
73
74### Validate the Idea
75
76- **Search demand**: Is there search volume? How competitive?
77- **Uniqueness**: What exists? How can you be 10x better?
78- **Lead quality**: Does this audience match buyers?
79- **Build feasibility**: How complex? Can you scope an MVP?
80
81---
82
83## Lead Capture Strategy
84
85### Gating Options
86
87| Approach | Pros | Cons |
88|----------|------|------|
89| Fully gated | Maximum capture | Lower usage |
90| Partially gated | Balance of both | Common pattern |
91| Ungated + optional | Maximum reach | Lower capture |
92| Ungated entirely | Pure SEO/brand | No direct leads |
93
94### Lead Capture Best Practices
95- Value exchange clear: "Get your full report"
96- Minimal friction: Email only
97- Show preview of what they'll get
98- Optional: Segment by asking one qualifying question
99
100---
101
102## SEO Considerations
103
104### Keyword Strategy
105**Tool landing page**: "[thing] calculator", "[thing] generator", "free [tool type]"
106
107**Supporting content**: "How to [use case]", "What is [concept]"
108
109### Link Building
110Free tools attract links because:
111- Genuinely useful (people reference them)
112- Unique (can't link to just any page)
113- Shareable (social amplification)
114
115---
116
117## Build vs. Buy
118
119### Build Custom
120When: Unique concept, core to brand, high strategic value, have dev capacity
121
122### Use No-Code Tools
123Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow
124When: Speed to market, limited dev resources, testing concept
125
126### Embed Existing
127When: Something good exists, white-label available, not core differentiator
128
129---
130
131## MVP Scope
132
133### Minimum Viable Tool
1341. Core functionality only—does the one thing, works reliably
1352. Essential UX—clear input, obvious output, mobile works
1363. Basic lead capture—email collection, leads go somewhere useful
137
138### What to Skip Initially
139Account creation, saving results, advanced features, perfect design, every edge case
140
141---
142
143## Evaluation Scorecard
144
145Rate each factor 1-5:
146
147| Factor | Score |
148|--------|-------|
149| Search demand exists | ___ |
150| Audience match to buyers | ___ |
151| Uniqueness vs. existing | ___ |
152| Natural path to product | ___ |
153| Build feasibility | ___ |
154| Maintenance burden (inverse) | ___ |
155| Link-building potential | ___ |
156| Share-worthiness | ___ |
157
158**25+**: Strong candidate | **15-24**: Promising | **<15**: Reconsider
159
160---
161
162## Task-Specific Questions
163
1641. What existing tools does your audience use for workarounds?
1652. How do you currently generate leads?
1663. What technical resources are available?
1674. What's the timeline and budget?
168
169---
170
171## Boundaries
172
173- Do not claim search demand, lead volume, link potential, or build feasibility without evidence and dated assumptions.
174- Do not build, deploy, publish, collect leads, or connect production data unless the user authorizes implementation.
175- Do not invent tool outputs or use a calculator as disguised professional, legal, medical, or financial advice.
176- Do not decide pricing, data-retention, or consent policy for the user.
177
178## Routing
179
180- Use `suede-lead-magnets` for downloadable assets and `suede-site-alchemy` for the public conversion surface.
181- Use `suede-seo-audit` for search validation and `suede-analytics` for usage measurement.
182- Use `suede-emails` for the post-capture lifecycle sequence.
majiayu000