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," or "free resource." This skill bridges engineering and marketing — useful for founders and technical marketers.
What this skill does
# Free Tool Strategy (Engineering as Marketing)
## Overview
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. You guide users through tool ideation, validation, lead capture strategy, build-vs-buy decisions, and MVP scoping.
**Check for product marketing context first:**
If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
## Instructions
### Initial Assessment
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 the problem you solve.
3. **Simple and Focused** - Does one thing well. Low friction to use. Immediate value.
4. **Worth the Investment** - Lead value x expected leads > build cost + maintenance.
### Tool Types
| 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 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
| 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 |
**Best Practices:** Clear value exchange ("Get your full report"), minimal friction (email only), show preview of gated content, optionally segment with one qualifying question.
### SEO Considerations
**Tool landing page keywords**: "[thing] calculator", "[thing] generator", "free [tool type]"
**Supporting content**: "How to [use case]", "What is [concept]"
Free tools attract backlinks because they're genuinely useful, unique, and shareable.
### Build vs Buy
- **Build Custom**: Unique concept, core to brand, high strategic value, have dev capacity.
- **Use No-Code Tools** (Outgrow, Involve.me, Typeform, Tally, Bubble, Webflow): Speed to market, limited dev resources, testing concept.
- **Embed Existing**: 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
**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
## Examples
### Example 1: SaaS ROI Calculator
**User prompt:** "We sell Warehousr, a warehouse management system for e-commerce brands doing 500-5000 orders/day. We want to build a free tool that generates leads. Our buyers are operations managers who need to justify the software cost to their CFO."
The agent will:
- Identify the pain point: ops managers struggle to quantify the cost of manual warehouse processes when building a business case.
- Propose a "Warehouse Efficiency ROI Calculator" that takes inputs (daily orders, current pick time, error rate, labor cost, number of warehouse staff) and outputs annual savings from automation, payback period, and error reduction.
- Score it on the evaluation scorecard: high search demand ("warehouse ROI calculator"), strong audience-buyer match, natural product path (calculator shows savings → Warehousr delivers them), moderate build complexity.
- Recommend partially gated: show headline savings number ungated, gate the full PDF report with detailed breakdown behind email capture.
- Suggest building with a no-code tool (Outgrow or custom React component) for MVP, with supporting blog content targeting "how to calculate warehouse automation ROI."
### Example 2: Agency Lead Generation Tool
**User prompt:** "We're a branding agency called Markcraft. Our clients are funded startups (Series A-B) that need brand identity work. We charge $25k-75k per project. We want a free tool to attract founders who are thinking about rebranding or building their first brand."
The agent will:
- Propose a "Brand Audit Scorecard" — a 10-question interactive assessment that evaluates a startup's current brand across consistency, differentiation, audience clarity, and visual cohesion, outputting a score with specific improvement recommendations.
- Score the idea: moderate search demand ("brand audit tool"), excellent audience-buyer match (founders evaluating their brand = pre-qualified leads), high uniqueness (most brand tools focus on visual assets, not strategic evaluation), clear product path (low score → "we can help").
- Recommend ungated for the score + top-level recommendations, gated for the detailed brand audit report with specific action items.
- Suggest building with Typeform for the assessment + a custom results page, with content marketing around "startup brand checklist" and "when to rebrand your startup."
- Calculate expected ROI: if 200 founders/month complete the audit, 30% gate (60 leads), 5% convert to calls (3 calls), 15% close rate at $40k average = $18k/month potential.
## Guidelines
- **Always validate search demand first** — a brilliant tool nobody searches for requires expensive promotion. Check Google Trends and keyword tools before committing to build.
- **Keep the MVP ruthlessly simple** — the tool should do one thing in under 2 minutes. Feature creep kills free tools before they launch. Ship the calculator, not the dashboard.
- **Make the lead capture feel like a value exchange, not a gate** — "Enter your email to get your personalized 12-page report" works. "Enter your email to see your results" feels like extortion.
- **Plan for maintenance from day one** — tools with external data dependencies (API calls, competitor pricing, benchmarks) require ongoing updates. Budget for this or choose static tool types.
- **Connect the tool output to your product naturally** — the tool should make the problem visible and your product the obviouRelated 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".