Free tool strategy skill
When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness.
by davila7·MIT license·★ 32,299 Stars on the repo·GitHub ↗
npx degit davila7/claude-code-templates/cli-tool/components/skills/business-marketing/free-tool-strategy#main ~/.claude/skills/free-tool-strategy-davila7Checked ·commit main
Files of Free tool strategy
Show the full text577 lines
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
Before designing a tool strategy, understand:
Business Context
- What's the core product/service?
- Who is the target audience?
- What problems do they have?
Goals
- Lead generation primary goal?
- SEO/traffic acquisition?
- 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
- Consider SEO value
- Consider brand halo effect
Tool Types
Calculators
Best for: Decisions involving numbers, comparisons, estimates
Examples:
- ROI calculator
- Savings calculator
- Cost comparison tool
- Salary calculator
- Tax estimator
Why they work:
- Personalized output
- High perceived value
- Share-worthy results
- Clear problem → solution
Generators
Best for: Creating something useful quickly
Examples:
- Policy generator
- Template generator
- Name/tagline generator
- Email subject line generator
- Resume builder
Why they work:
- Tangible output
- Saves time
- Easily shared
- Repeat usage
Analyzers/Auditors
Best for: Evaluating existing work or assets
Examples:
- Website grader
- SEO analyzer
- Email subject tester
- Headline analyzer
- Security checker
Why they work:
- Curiosity-driven
- Personalized insights
- Creates awareness of problems
- Natural lead to solution
Testers/Validators
Best for: Checking if something works
Examples:
- Meta tag preview
- Email rendering test
- Accessibility checker
- Mobile-friendly test
- Speed test
Why they work:
- Immediate utility
- Bookmark-worthy
- Repeat usage
- Professional necessity
Libraries/Resources
Best for: Reference material
Examples:
- Icon library
- Template library
- Code snippet library
- Example gallery
- Directory
Why they work:
- High SEO value
- Ongoing traffic
- Establishes authority
- Linkable asset
Interactive Educational
Best for: Learning/understanding
Examples:
- Interactive tutorials
- Code playgrounds
- Visual explainers
- Quizzes/assessments
- Simulators
Why they work:
- Engages deeply
- Demonstrates expertise
- Shareable
- Memory-creating
Ideation Framework
Start with Pain Points
What problems does your audience Google?
- Search query research
- Common questions
- "How to" searches
What manual processes are tedious?
- Tasks done in spreadsheets
- Repetitive calculations
- Copy-paste workflows
What do they need before buying your product?
- Assessments of current state
- Planning/scoping
- Comparisons
What information do they wish they had?
- Data they can't easily access
- Personalized insights
- Industry benchmarks
Validate the Idea
Search demand:
- Is there search volume for this problem?
- What keywords would rank?
- How competitive?
Uniqueness:
- What exists already?
- How can you be 10x better or different?
- What's your unique angle?
Lead quality:
- Does this problem-audience match buyers?
- Will users be your target customers?
- Is there a natural path to your product?
Build feasibility:
- How complex to build?
- Can you scope an MVP?
- Ongoing maintenance burden?
SEO Considerations
Keyword Strategy
Tool landing page:
- "[thing] calculator"
- "[thing] generator"
- "free [tool type]"
- "[industry] [tool type]"
Supporting content:
- "How to [use case]"
- "What is [concept tool helps with]"
- Blog posts that link to tool
Link Building
Free tools attract links because:
- Genuinely useful (people reference them)
- Unique (can't link to just any page)
- Shareable (social amplification)
Outreach opportunities:
- Roundup posts ("best free tools for X")
- Resource pages
- Industry publications
- Blogs writing about the problem
Technical SEO
- Fast load time critical
- Mobile-friendly essential
- Crawlable content (not just JS app)
- Proper meta tags
- Schema markup if applicable
Lead Capture Strategy
When to Gate
Fully gated (email required to use):
- High-value, unique tools
- Personalized reports
- Risk: Lower usage
Partially gated (email for full results):
- Show preview, gate details
- Better balance
- Most common pattern
Ungated with optional capture:
- Tool is free to use
- Email to save/share results
- Highest usage, lower capture
Ungated entirely:
- Pure SEO/brand play
- No direct leads
- Maximum reach
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
Post-Capture
- Immediate email with results/link
- Nurture sequence relevant to tool topic
- Clear path to main product
- Don't spam—provide value
Build vs. Buy vs. Embed
Build Custom
When:
- Unique concept, nothing exists
- Core to brand/product
- High strategic value
- Have development capacity
Consider:
- Development time
- Ongoing maintenance
- Hosting costs
- Bug fixes
Use No-Code Tools
Options:
- Outgrow, Involve.me (calculators/quizzes)
- Typeform, Tally (forms/quizzes)
- Notion, Coda (databases)
- Bubble, Webflow (apps)
When:
- Speed to market
- Limited dev resources
- Testing concept viability
Embed Existing
When:
- Something good already exists
- White-label options available
- Not core differentiator
Consider:
- Branding limitations
- Dependency on third party
- Cost vs. build
MVP Scope
Minimum Viable Tool
Core functionality only
- Does the one thing
- No bells and whistles
- Works reliably
Essential UX
- Clear input
- Obvious output
- Mobile works
Basic lead capture
- Email collection works
- Leads go somewhere useful
- Follow-up exists
What to Skip Initially
- Account creation
- Saving results
- Advanced features
- Perfect design
- Every edge case
Iterate Based on Use
- Track where users drop off
- See what questions they have
- Add features that get requested
- Improve based on data
Promotion Strategy
Launch
Owned channels:
- Email list announcement
- Blog post / landing page
- Social media
- Product hunt (if applicable)
Outreach:
- Relevant newsletters
- Industry publications
- Bloggers in space
- Social influencers
Ongoing
SEO:
- Target tool-related keywords
- Supporting content
- Link building
Social:
- Share interesting results (anonymized)
- Use case examples
- Tips for using the tool
Product integration:
- Mention in sales process
- Link from related product features
- Include in email sequences
Measurement
Metrics to Track
Acquisition:
- Traffic to tool
- Traffic sources
- Keyword rankings
- Backlinks acquired
Engagement:
- Tool usage/completions
- Time spent
- Return visitors
- Shares
Conversion:
- Email captures
- Lead quality score
- MQLs generated
- Pipeline influenced
- Customers attributed
Attribution
- UTM parameters for paid promotion
- Separate landing page for organic
- Track lead source through funnel
- Survey new customers
Evaluation Framework
Tool Idea Scorecard
Rate each factor 1-5:
| Factor | Score |
|---|---|
| Search demand exists | ___ |
| Audience match to buyers | ___ |
| Uniqueness vs. existing tools | ___ |
| Natural path to product | ___ |
| Build feasibility | ___ |
| Maintenance burden (inverse) | ___ |
| Link-building potential | ___ |
| Share-worthiness | ___ |
25+: Strong candidate 15-24: Promising, needs refinement <15: Reconsider or scope differently
ROI Projection
Estimated monthly leads: [X]
Lead-to-customer rate: [Y%]
Average customer value: [$Z]
Monthly value: X × Y% × $Z = $___
Build cost: $___
Monthly maintenance: $___
Payback period: Build cost / (Monthly value - Monthly maintenance)
Output Format
Tool Strategy Document
# Free Tool Strategy: [Tool Name]
## Concept
[What it does in one paragraph]
## Target Audience
[Who uses it, what problem it solves]
## Lead Generation Fit
[How this connects to your product/sales]
## SEO Opportunity
- Target keywords: [list]
- Search volume: [estimate]
- Competition: [assessment]
## Build Approach
- Custom / No-code / Embed
- MVP scope: [core features]
- Estimated effort: [time/cost]
## Lead Capture Strategy
- Gating approach: [Full/Partial/Ungated]
- Capture mechanism: [description]
- Follow-up sequence: [outline]
## Success Metrics
- [Metric 1]: [Target]
- [Metric 2]: [Target]
## Promotion Plan
- Launch: [channels]
- Ongoing: [strategy]
## Timeline
- Phase 1: [scope] - [timeframe]
- Phase 2: [scope] - [timeframe]
Implementation Spec
If moving forward with build
Promotion Plan
Detailed launch and ongoing strategy
Example Tool Concepts by Business Type
SaaS Product
- Product ROI calculator
- Competitor comparison tool
- Readiness assessment quiz
- Template library for use case
Agency/Services
- Industry benchmark tool
- Project scoping calculator
- Portfolio review tool
- Cost estimator
E-commerce
- Product finder quiz
- Comparison tool
- Size/fit calculator
- Savings calculator
Developer Tools
- Code snippet library
- Testing/preview tool
- Documentation generator
- Interactive tutorials
Finance
- Financial calculators
- Investment comparison
- Budget planner
- Tax estimator
Questions to Ask
If you need more context:
- What's your core product/service?
- What problems does your audience commonly face?
- What existing tools do they use for workarounds?
- How do you currently generate leads?
- What technical resources are available?
- What's the timeline and budget?
Related Skills
- page-cro: For optimizing the tool's landing page
- seo-audit: For SEO-optimizing the tool
- analytics-tracking: For measuring tool usage
- email-sequence: For nurturing leads from the tool
- programmatic-seo: For building tool-based pages at scale
| 1 | |
| 2 | name free-tool-strategy |
| 3 | description When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers. |
| 4 | |
| 5 | |
| 6 | # Free Tool Strategy (Engineering as Marketing) |
| 7 | |
| 8 | 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. |
| 9 | |
| 10 | ## Initial Assessment |
| 11 | |
| 12 | Before designing a tool strategy, understand: |
| 13 | |
| 14 | **Business Context** |
| 15 | What's the core product/service? |
| 16 | Who is the target audience? |
| 17 | What problems do they have? |
| 18 | |
| 19 | **Goals** |
| 20 | Lead generation primary goal? |
| 21 | SEO/traffic acquisition? |
| 22 | Brand awareness? |
| 23 | Product education? |
| 24 | |
| 25 | **Resources** |
| 26 | Technical capacity to build? |
| 27 | Ongoing maintenance bandwidth? |
| 28 | Budget for promotion? |
| 29 | |
| 30 | |
| 31 | |
| 32 | ## Core Principles |
| 33 | |
| 34 | ### 1. Solve a Real Problem |
| 35 | Tool must provide genuine value |
| 36 | Solves a problem your audience actually has |
| 37 | Useful even without your main product |
| 38 | |
| 39 | ### 2. Adjacent to Core Product |
| 40 | Related to what you sell |
| 41 | Natural path from tool to product |
| 42 | Educates on problem you solve |
| 43 | |
| 44 | ### 3. Simple and Focused |
| 45 | Does one thing well |
| 46 | Low friction to use |
| 47 | Immediate value |
| 48 | |
| 49 | ### 4. Worth the Investment |
| 50 | Lead value × expected leads > build cost + maintenance |
| 51 | Consider SEO value |
| 52 | Consider brand halo effect |
| 53 | |
| 54 | |
| 55 | |
| 56 | ## Tool Types |
| 57 | |
| 58 | ### Calculators |
| 59 | |
| 60 | **Best for**: Decisions involving numbers, comparisons, estimates |
| 61 | |
| 62 | **Examples**: |
| 63 | ROI calculator |
| 64 | Savings calculator |
| 65 | Cost comparison tool |
| 66 | Salary calculator |
| 67 | Tax estimator |
| 68 | |
| 69 | **Why they work**: |
| 70 | Personalized output |
| 71 | High perceived value |
| 72 | Share-worthy results |
| 73 | Clear problem → solution |
| 74 | |
| 75 | ### Generators |
| 76 | |
| 77 | **Best for**: Creating something useful quickly |
| 78 | |
| 79 | **Examples**: |
| 80 | Policy generator |
| 81 | Template generator |
| 82 | Name/tagline generator |
| 83 | Email subject line generator |
| 84 | Resume builder |
| 85 | |
| 86 | **Why they work**: |
| 87 | Tangible output |
| 88 | Saves time |
| 89 | Easily shared |
| 90 | Repeat usage |
| 91 | |
| 92 | ### Analyzers/Auditors |
| 93 | |
| 94 | **Best for**: Evaluating existing work or assets |
| 95 | |
| 96 | **Examples**: |
| 97 | Website grader |
| 98 | SEO analyzer |
| 99 | Email subject tester |
| 100 | Headline analyzer |
| 101 | Security checker |
| 102 | |
| 103 | **Why they work**: |
| 104 | Curiosity-driven |
| 105 | Personalized insights |
| 106 | Creates awareness of problems |
| 107 | Natural lead to solution |
| 108 | |
| 109 | ### Testers/Validators |
| 110 | |
| 111 | **Best for**: Checking if something works |
| 112 | |
| 113 | **Examples**: |
| 114 | Meta tag preview |
| 115 | Email rendering test |
| 116 | Accessibility checker |
| 117 | Mobile-friendly test |
| 118 | Speed test |
| 119 | |
| 120 | **Why they work**: |
| 121 | Immediate utility |
| 122 | Bookmark-worthy |
| 123 | Repeat usage |
| 124 | Professional necessity |
| 125 | |
| 126 | ### Libraries/Resources |
| 127 | |
| 128 | **Best for**: Reference material |
| 129 | |
| 130 | **Examples**: |
| 131 | Icon library |
| 132 | Template library |
| 133 | Code snippet library |
| 134 | Example gallery |
| 135 | Directory |
| 136 | |
| 137 | **Why they work**: |
| 138 | High SEO value |
| 139 | Ongoing traffic |
| 140 | Establishes authority |
| 141 | Linkable asset |
| 142 | |
| 143 | ### Interactive Educational |
| 144 | |
| 145 | **Best for**: Learning/understanding |
| 146 | |
| 147 | **Examples**: |
| 148 | Interactive tutorials |
| 149 | Code playgrounds |
| 150 | Visual explainers |
| 151 | Quizzes/assessments |
| 152 | Simulators |
| 153 | |
| 154 | **Why they work**: |
| 155 | Engages deeply |
| 156 | Demonstrates expertise |
| 157 | Shareable |
| 158 | Memory-creating |
| 159 | |
| 160 | |
| 161 | |
| 162 | ## Ideation Framework |
| 163 | |
| 164 | ### Start with Pain Points |
| 165 | |
| 166 | **What problems does your audience Google?** |
| 167 | Search query research |
| 168 | Common questions |
| 169 | "How to" searches |
| 170 | |
| 171 | **What manual processes are tedious?** |
| 172 | Tasks done in spreadsheets |
| 173 | Repetitive calculations |
| 174 | Copy-paste workflows |
| 175 | |
| 176 | **What do they need before buying your product?** |
| 177 | Assessments of current state |
| 178 | Planning/scoping |
| 179 | Comparisons |
| 180 | |
| 181 | **What information do they wish they had?** |
| 182 | Data they can't easily access |
| 183 | Personalized insights |
| 184 | Industry benchmarks |
| 185 | |
| 186 | ### Validate the Idea |
| 187 | |
| 188 | **Search demand:** |
| 189 | Is there search volume for this problem? |
| 190 | What keywords would rank? |
| 191 | How competitive? |
| 192 | |
| 193 | **Uniqueness:** |
| 194 | What exists already? |
| 195 | How can you be 10x better or different? |
| 196 | What's your unique angle? |
| 197 | |
| 198 | **Lead quality:** |
| 199 | Does this problem-audience match buyers? |
| 200 | Will users be your target customers? |
| 201 | Is there a natural path to your product? |
| 202 | |
| 203 | **Build feasibility:** |
| 204 | How complex to build? |
| 205 | Can you scope an MVP? |
| 206 | Ongoing maintenance burden? |
| 207 | |
| 208 | |
| 209 | |
| 210 | ## SEO Considerations |
| 211 | |
| 212 | ### Keyword Strategy |
| 213 | |
| 214 | **Tool landing page:** |
| 215 | "[thing] calculator" |
| 216 | "[thing] generator" |
| 217 | "free [tool type]" |
| 218 | "[industry] [tool type]" |
| 219 | |
| 220 | **Supporting content:** |
| 221 | "How to [use case]" |
| 222 | "What is [concept tool helps with]" |
| 223 | Blog posts that link to tool |
| 224 | |
| 225 | ### Link Building |
| 226 | |
| 227 | Free tools attract links because: |
| 228 | Genuinely useful (people reference them) |
| 229 | Unique (can't link to just any page) |
| 230 | Shareable (social amplification) |
| 231 | |
| 232 | **Outreach opportunities:** |
| 233 | Roundup posts ("best free tools for X") |
| 234 | Resource pages |
| 235 | Industry publications |
| 236 | Blogs writing about the problem |
| 237 | |
| 238 | ### Technical SEO |
| 239 | |
| 240 | Fast load time critical |
| 241 | Mobile-friendly essential |
| 242 | Crawlable content (not just JS app) |
| 243 | Proper meta tags |
| 244 | Schema markup if applicable |
| 245 | |
| 246 | |
| 247 | |
| 248 | ## Lead Capture Strategy |
| 249 | |
| 250 | ### When to Gate |
| 251 | |
| 252 | **Fully gated (email required to use):** |
| 253 | High-value, unique tools |
| 254 | Personalized reports |
| 255 | Risk: Lower usage |
| 256 | |
| 257 | **Partially gated (email for full results):** |
| 258 | Show preview, gate details |
| 259 | Better balance |
| 260 | Most common pattern |
| 261 | |
| 262 | **Ungated with optional capture:** |
| 263 | Tool is free to use |
| 264 | Email to save/share results |
| 265 | Highest usage, lower capture |
| 266 | |
| 267 | **Ungated entirely:** |
| 268 | Pure SEO/brand play |
| 269 | No direct leads |
| 270 | Maximum reach |
| 271 | |
| 272 | ### Lead Capture Best Practices |
| 273 | |
| 274 | Value exchange clear: "Get your full report" |
| 275 | Minimal friction: Email only |
| 276 | Show preview of what they'll get |
| 277 | Optional: Segment by asking one qualifying question |
| 278 | |
| 279 | ### Post-Capture |
| 280 | |
| 281 | Immediate email with results/link |
| 282 | Nurture sequence relevant to tool topic |
| 283 | Clear path to main product |
| 284 | Don't spam—provide value |
| 285 | |
| 286 | |
| 287 | |
| 288 | ## Build vs. Buy vs. Embed |
| 289 | |
| 290 | ### Build Custom |
| 291 | |
| 292 | **When:** |
| 293 | Unique concept, nothing exists |
| 294 | Core to brand/product |
| 295 | High strategic value |
| 296 | Have development capacity |
| 297 | |
| 298 | **Consider:** |
| 299 | Development time |
| 300 | Ongoing maintenance |
| 301 | Hosting costs |
| 302 | Bug fixes |
| 303 | |
| 304 | ### Use No-Code Tools |
| 305 | |
| 306 | **Options:** |
| 307 | Outgrow, Involve.me (calculators/quizzes) |
| 308 | Typeform, Tally (forms/quizzes) |
| 309 | Notion, Coda (databases) |
| 310 | Bubble, Webflow (apps) |
| 311 | |
| 312 | **When:** |
| 313 | Speed to market |
| 314 | Limited dev resources |
| 315 | Testing concept viability |
| 316 | |
| 317 | ### Embed Existing |
| 318 | |
| 319 | **When:** |
| 320 | Something good already exists |
| 321 | White-label options available |
| 322 | Not core differentiator |
| 323 | |
| 324 | **Consider:** |
| 325 | Branding limitations |
| 326 | Dependency on third party |
| 327 | Cost vs. build |
| 328 | |
| 329 | |
| 330 | |
| 331 | ## MVP Scope |
| 332 | |
| 333 | ### Minimum Viable Tool |
| 334 | |
| 335 | **Core functionality only** |
| 336 | Does the one thing |
| 337 | No bells and whistles |
| 338 | Works reliably |
| 339 | |
| 340 | **Essential UX** |
| 341 | Clear input |
| 342 | Obvious output |
| 343 | Mobile works |
| 344 | |
| 345 | **Basic lead capture** |
| 346 | Email collection works |
| 347 | Leads go somewhere useful |
| 348 | Follow-up exists |
| 349 | |
| 350 | ### What to Skip Initially |
| 351 | |
| 352 | Account creation |
| 353 | Saving results |
| 354 | Advanced features |
| 355 | Perfect design |
| 356 | Every edge case |
| 357 | |
| 358 | ### Iterate Based on Use |
| 359 | |
| 360 | Track where users drop off |
| 361 | See what questions they have |
| 362 | Add features that get requested |
| 363 | Improve based on data |
| 364 | |
| 365 | |
| 366 | |
| 367 | ## Promotion Strategy |
| 368 | |
| 369 | ### Launch |
| 370 | |
| 371 | **Owned channels:** |
| 372 | Email list announcement |
| 373 | Blog post / landing page |
| 374 | Social media |
| 375 | Product hunt (if applicable) |
| 376 | |
| 377 | **Outreach:** |
| 378 | Relevant newsletters |
| 379 | Industry publications |
| 380 | Bloggers in space |
| 381 | Social influencers |
| 382 | |
| 383 | ### Ongoing |
| 384 | |
| 385 | **SEO:** |
| 386 | Target tool-related keywords |
| 387 | Supporting content |
| 388 | Link building |
| 389 | |
| 390 | **Social:** |
| 391 | Share interesting results (anonymized) |
| 392 | Use case examples |
| 393 | Tips for using the tool |
| 394 | |
| 395 | **Product integration:** |
| 396 | Mention in sales process |
| 397 | Link from related product features |
| 398 | Include in email sequences |
| 399 | |
| 400 | |
| 401 | |
| 402 | ## Measurement |
| 403 | |
| 404 | ### Metrics to Track |
| 405 | |
| 406 | **Acquisition:** |
| 407 | Traffic to tool |
| 408 | Traffic sources |
| 409 | Keyword rankings |
| 410 | Backlinks acquired |
| 411 | |
| 412 | **Engagement:** |
| 413 | Tool usage/completions |
| 414 | Time spent |
| 415 | Return visitors |
| 416 | Shares |
| 417 | |
| 418 | **Conversion:** |
| 419 | Email captures |
| 420 | Lead quality score |
| 421 | MQLs generated |
| 422 | Pipeline influenced |
| 423 | Customers attributed |
| 424 | |
| 425 | ### Attribution |
| 426 | |
| 427 | UTM parameters for paid promotion |
| 428 | Separate landing page for organic |
| 429 | Track lead source through funnel |
| 430 | Survey new customers |
| 431 | |
| 432 | |
| 433 | |
| 434 | ## Evaluation Framework |
| 435 | |
| 436 | ### Tool Idea Scorecard |
| 437 | |
| 438 | Rate each factor 1-5: |
| 439 | |
| 440 | | Factor | Score | |
| 441 | |--------|-------| |
| 442 | | Search demand exists | ___ | |
| 443 | | Audience match to buyers | ___ | |
| 444 | | Uniqueness vs. existing tools | ___ | |
| 445 | | Natural path to product | ___ | |
| 446 | | Build feasibility | ___ | |
| 447 | | Maintenance burden (inverse) | ___ | |
| 448 | | Link-building potential | ___ | |
| 449 | | Share-worthiness | ___ | |
| 450 | |
| 451 | **25+**: Strong candidate |
| 452 | **15-24**: Promising, needs refinement |
| 453 | **<15**: Reconsider or scope differently |
| 454 | |
| 455 | ### ROI Projection |
| 456 | |
| 457 | |
| 458 | Estimated monthly leads: [X] |
| 459 | Lead-to-customer rate: [Y%] |
| 460 | Average customer value: [$Z] |
| 461 | |
| 462 | Monthly value: X × Y% × $Z = $___ |
| 463 | |
| 464 | Build cost: $___ |
| 465 | Monthly maintenance: $___ |
| 466 | |
| 467 | Payback period: Build cost / (Monthly value - Monthly maintenance) |
| 468 | |
| 469 | |
| 470 | |
| 471 | |
| 472 | ## Output Format |
| 473 | |
| 474 | ### Tool Strategy Document |
| 475 | |
| 476 | |
| 477 | # Free Tool Strategy: [Tool Name] |
| 478 | |
| 479 | ## Concept |
| 480 | [What it does in one paragraph] |
| 481 | |
| 482 | ## Target Audience |
| 483 | [Who uses it, what problem it solves] |
| 484 | |
| 485 | ## Lead Generation Fit |
| 486 | [How this connects to your product/sales] |
| 487 | |
| 488 | ## SEO Opportunity |
| 489 | - Target keywords: [list] |
| 490 | - Search volume: [estimate] |
| 491 | - Competition: [assessment] |
| 492 | |
| 493 | ## Build Approach |
| 494 | - Custom / No-code / Embed |
| 495 | - MVP scope: [core features] |
| 496 | - Estimated effort: [time/cost] |
| 497 | |
| 498 | ## Lead Capture Strategy |
| 499 | - Gating approach: [Full/Partial/Ungated] |
| 500 | - Capture mechanism: [description] |
| 501 | - Follow-up sequence: [outline] |
| 502 | |
| 503 | ## Success Metrics |
| 504 | - [Metric 1]: [Target] |
| 505 | - [Metric 2]: [Target] |
| 506 | |
| 507 | ## Promotion Plan |
| 508 | - Launch: [channels] |
| 509 | - Ongoing: [strategy] |
| 510 | |
| 511 | ## Timeline |
| 512 | - Phase 1: [scope] - [timeframe] |
| 513 | - Phase 2: [scope] - [timeframe] |
| 514 | |
| 515 | |
| 516 | ### Implementation Spec |
| 517 | If moving forward with build |
| 518 | |
| 519 | ### Promotion Plan |
| 520 | Detailed launch and ongoing strategy |
| 521 | |
| 522 | |
| 523 | |
| 524 | ## Example Tool Concepts by Business Type |
| 525 | |
| 526 | ### SaaS Product |
| 527 | Product ROI calculator |
| 528 | Competitor comparison tool |
| 529 | Readiness assessment quiz |
| 530 | Template library for use case |
| 531 | |
| 532 | ### Agency/Services |
| 533 | Industry benchmark tool |
| 534 | Project scoping calculator |
| 535 | Portfolio review tool |
| 536 | Cost estimator |
| 537 | |
| 538 | ### E-commerce |
| 539 | Product finder quiz |
| 540 | Comparison tool |
| 541 | Size/fit calculator |
| 542 | Savings calculator |
| 543 | |
| 544 | ### Developer Tools |
| 545 | Code snippet library |
| 546 | Testing/preview tool |
| 547 | Documentation generator |
| 548 | Interactive tutorials |
| 549 | |
| 550 | ### Finance |
| 551 | Financial calculators |
| 552 | Investment comparison |
| 553 | Budget planner |
| 554 | Tax estimator |
| 555 | |
| 556 | |
| 557 | |
| 558 | ## Questions to Ask |
| 559 | |
| 560 | If you need more context: |
| 561 | What's your core product/service? |
| 562 | What problems does your audience commonly face? |
| 563 | What existing tools do they use for workarounds? |
| 564 | How do you currently generate leads? |
| 565 | What technical resources are available? |
| 566 | What's the timeline and budget? |
| 567 | |
| 568 | |
| 569 | |
| 570 | ## Related Skills |
| 571 | |
| 572 | **page-cro**: For optimizing the tool's landing page |
| 573 | **seo-audit**: For SEO-optimizing the tool |
| 574 | **analytics-tracking**: For measuring tool usage |
| 575 | **email-sequence**: For nurturing leads from the tool |
| 576 | **programmatic-seo**: For building tool-based pages at scale |
| 577 |
Discussion
Alternatives
Browse more free Claude skills or everything in Product.