free-tool-strategy
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," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
What this skill does
# 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-context.md` exists (or `.claude/product-marketing-context.md` 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 ### 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](references/tool-types.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? --- ## Related Skills - **lead-magnets**: For downloadable content lead magnets (ebooks, checklists, templates) - **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
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".