AGENT SKILL

free-tool-strategy

Use when planning, evaluating or building a free tool as engineering-as-marketing for lead generation, SEO traffic or brand awareness.

适用职业市场营销
使用场景营销推广
License 许可
MIT
所属仓库
monoes/monomind
最近更新
2026-11-10
Stars
★ 23
Forks
2

01 前言 Front Matter

name
free-tool-strategy
tags
[ "marketing", "product", "growth", "seo" ]
tools
[]
source
https://github.com/coreyhaines31/marketingskills
license
MIT
description
Use when planning, evaluating or building a free tool as engineering-as-marketing for lead generation, SEO traffic or brand awareness.
source_path
skills/free-tools
source_commit
5b2c0007766c6a1cf1d53fd8fc73e979e0821022

02 资源文件 3

03 SKILL.md 正文

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:

  1. Business Context - What's the core product? Who is the target audience? What problems do they have?

  2. Goals - Lead generation? SEO/traffic? Brand awareness? Product education?

  3. Resources - Technical capacity to build? Ongoing maintenance bandwidth? Budget for promotion?


Core Principles

"Your product is my marketing opportunity." Bezos said "your margin is my opportunity." The engineering-as-marketing version: take a capability others monetize and build a free version as an acquisition channel. Unsplash gave away the stock photos Getty sold — and Getty acquired it. See references/tool-benchmarks.md for named cases and conversion numbers.

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

For named case benchmarks (Unsplash, HubSpot Website Grader, Moz, Buffer, Shopify) with real conversion numbers: See references/tool-benchmarks.md


Ideation Framework

Start with Pain Points

  1. What problems does your audience Google? - Search query research, common questions

  2. What manual processes are tedious? - Spreadsheet tasks, repetitive calculations

  3. What do they need before buying your product? - Assessments, planning, comparisons

  4. 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

  1. Core functionality only—does the one thing, works reliably
  2. Essential UX—clear input, obvious output, mobile works
  3. 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

  1. What existing tools does your audience use for workarounds?
  2. How do you currently generate leads?
  3. What technical resources are available?
  4. What's the timeline and budget?

Common Pitfalls

  • Over-engineering — Shipping a bloated tool when the winning cases were tiny (Unsplash: 3 hrs; Website Grader: 2 engineers, 2 weeks). Scope to the one job.
  • Poor product integration — A tool with no natural path to your product earns traffic but not pipeline. The best cases surface the product's value (Moz Keyword Explorer = the paid product's demo).
  • Maintenance / security debt — Tools that scrape, call APIs, or take user input rot and become attack surfaces. Budget for upkeep before you build.
  • Vanity metrics — Visitors and usage feel good but don't pay. Track leads, qualification rate, and trial/signup conversion — the numbers the case library reports.

Related Skills

  • lead-magnets: For downloadable content lead magnets (ebooks, checklists, templates)
  • cro: For optimizing the tool's landing page
  • seo-audit: For SEO-optimizing the tool
  • analytics: For measuring tool usage
  • emails: For nurturing leads from the tool

04 同仓库更多 Skills

monoes
monoes/monomind

zk-steward

Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.

★ 23
monoes
monoes/monomind

writing-plans

Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.

内容创作者写作与文案
★ 23
monoes
monoes/monomind

write-spec

Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

产品经理
★ 23
monoes
monoes/monomind

write-query

Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.

数据分析师
★ 23
monoes
monoes/monomind

workflow-automation

Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.

运维与部署Skill与智能体开发
★ 23
monoes
monoes/monomind

workflow-architect

Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.

Skill与智能体开发
★ 23