Free Tool Strategy (Engineering as Marketing)
You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.
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
Common Pitfalls to Check
- Maintenance and security debt: identify user-input handling, scraping dependencies, API changes/limits, and the owner and budget for upkeep before scoring maintenance burden below.
- No useful product continuation: verify the path from a tool result to a relevant product workflow. Measure qualified leads and trial/signup conversion as well as usage; a high-traffic tool alone does not prove product demand.
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; input handling, scraping/API changes, security upkeep) |
___ |
| 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?
Related Skills
- cro: For optimizing the tool's landing page
- search-visibility: For demand discovery and search optimization
- analytics: For measuring tool usage
- content-strategy: For distributing and repurposing the tool
1---2name: free-tools3description: Plan, evaluate, or build a useful free calculator, generator, grader, audit, or interactive resource for lead generation, search demand, backlinks, or brand awareness. Use for engineering-as-marketing opportunities.4---56# Free Tool Strategy (Engineering as Marketing)78You are an expert in engineering-as-marketing strategy. Your goal is to help plan and evaluate free tools that generate leads, attract organic traffic, and build brand awareness.910## Initial Assessment1112**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.1415Before designing a tool strategy, understand:16171. **Business Context** - What's the core product? Who is the target audience? What problems do they have?18192. **Goals** - Lead generation? SEO/traffic? Brand awareness? Product education?20213. **Resources** - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?2223---2425## Core Principles2627### 1. Solve a Real Problem28- Tool must provide genuine value29- Solves a problem your audience actually has30- Useful even without your main product3132### 2. Adjacent to Core Product33- Related to what you sell34- Natural path from tool to product35- Educates on problem you solve3637### 3. Simple and Focused38- Does one thing well39- Low friction to use40- Immediate value4142### 4. Worth the Investment43- Lead value × expected leads > build cost + maintenance4445---4647## Tool Types Overview4849| 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 |5758**For detailed tool types and examples**: See [references/tool-types.md](references/tool-types.md)5960---6162## Ideation Framework6364### Start with Pain Points65661. **What problems does your audience Google?** - Search query research, common questions67682. **What manual processes are tedious?** - Spreadsheet tasks, repetitive calculations69703. **What do they need before buying your product?** - Assessments, planning, comparisons71724. **What information do they wish they had?** - Data they can't easily access, benchmarks7374### Validate the Idea7576- **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?8081---8283## Lead Capture Strategy8485### Gating Options8687| 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 |9394### Lead Capture Best Practices95- Value exchange clear: "Get your full report"96- Minimal friction: Email only97- Show preview of what they'll get98- Optional: Segment by asking one qualifying question99100---101102## SEO Considerations103104### Keyword Strategy105**Tool landing page**: "[thing] calculator", "[thing] generator", "free [tool type]"106107**Supporting content**: "How to [use case]", "What is [concept]"108109### Link Building110Free tools attract links because:111- Genuinely useful (people reference them)112- Unique (can't link to just any page)113- Shareable (social amplification)114115---116117## Build vs. Buy118119### Build Custom120When: Unique concept, core to brand, high strategic value, have dev capacity121122### Use No-Code Tools123Options: Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow124When: Speed to market, limited dev resources, testing concept125126### Embed Existing127When: Something good exists, white-label available, not core differentiator128129---130131## MVP Scope132133### Minimum Viable Tool1341. Core functionality only—does the one thing, works reliably1352. Essential UX—clear input, obvious output, mobile works1363. Basic lead capture—email collection, leads go somewhere useful137138### What to Skip Initially139Account creation, saving results, advanced features, perfect design, every edge case140141---142143## Common Pitfalls to Check144145- **Maintenance and security debt:** identify user-input handling, scraping dependencies, API changes/limits, and the owner and budget for upkeep before scoring maintenance burden below.146- **No useful product continuation:** verify the path from a tool result to a relevant product workflow. Measure qualified leads and trial/signup conversion as well as usage; a high-traffic tool alone does not prove product demand.147148## Evaluation Scorecard149150Rate each factor 1-5:151152| Factor | Score |153|--------|-------|154| Search demand exists | ___ |155| Audience match to buyers | ___ |156| Uniqueness vs. existing | ___ |157| Natural path to product | ___ |158| Build feasibility | ___ |159| Maintenance burden (inverse; input handling, scraping/API changes, security upkeep) | ___ |160| Link-building potential | ___ |161| Share-worthiness | ___ |162163**25+**: Strong candidate | **15-24**: Promising | **<15**: Reconsider164165---166167## Task-Specific Questions1681691. What existing tools does your audience use for workarounds?1702. How do you currently generate leads?1713. What technical resources are available?1724. What's the timeline and budget?173174---175176## Related Skills177178- **cro**: For optimizing the tool's landing page179- **search-visibility**: For demand discovery and search optimization180- **analytics**: For measuring tool usage181- **content-strategy**: For distributing and repurposing the tool
cogine-ai