# Developer lead gen Human Guide

## What This Is For
Traditional lead generation tactics fail with developers. It gives the agent a clearer input/output frame for paid media: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Developer lead gen agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for developer lead gen.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Developer lead gen guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- PDFs that could be blog posts
- "Ebooks" that are product pitches
- Whitepapers with no original research
- Webinar recordings hidden behind forms
- Chatbots that appear immediately
- Required email for documentation
- Forced account creation for trials
- "Free" tools that require signup to use
- Calculators that email results
- Generic content disguised as resources
- **Developers talk**: One bad experience gets shared in Slack channels, Twitter, and Hacker News
- **Temporary emails**: Developers use disposable addresses for forms

## Decision Points And Nuance
The original skill emphasizes: Overview, Why Traditional Lead Gen Fails with Developers, What Developers Reject, Why It Fails, Building Free Tools That Generate Leads, Tool Ideas That Attract Developers, Characteristics of Successful Tools, Build vs Buy Decisions, Ungated vs Gated Strategy, What to Never Gate.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Required email for documentation
- No signup required to use
- What Can Be Gated (Carefully)
- If you must gate something, ensure value clearly exceeds effort:
- Value must be obvious before the gate
- **Plausible/Fathom**: Privacy-respecting analytics (developers don't block as often)
- Build a simple, instantly-useful tool (no signup required)

## Copy-And-Paste Prompt
```text
Use the Developer lead gen human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the jonathimer/devmarketing-skills skill entry for `developer-lead-gen`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Developer Lead Generation

## Overview

Traditional lead generation tactics fail with developers. Gating content behind forms generates resentment, not qualified leads. Developers have finely-tuned spam detectors and share warnings about pushy tools in their communities.

Effective developer lead gen focuses on providing genuine value upfront—free tools, useful utilities, and ungated resources that solve real problems. Conversion happens when developers recognize the value and choose to engage, not when they're forced through a funnel.

## Why Traditional Lead Gen Fails with Developers

### What Developers Reject

**Form-gated content:**
- PDFs that could be blog posts
- "Ebooks" that are product pitches
- Whitepapers with no original research
- Webinar recordings hidden behind forms

**Aggressive tactics:**
- Chatbots that appear immediately
- Exit-intent popups
- Required email for documentation
- Forced account creation for trials

**Fake value:**
- "Free" tools that require signup to use
- Calculators that email results
- Generic content disguised as resources

### Why It Fails

1. **Developers talk**: One bad experience gets shared in Slack channels, Twitter, and Hacker News
2. **Temporary emails**: Developers use disposable addresses for forms
3. **Ad blockers**: Many developers block tracking and popups
4. **Time protection**: Developers guard their attention fiercely
5. **Trust loss**: Pushy tactics damage brand perception permanently

## Building Free Tools That Generate Leads

### Tool Ideas That Attract Developers

Effective developer tools solve specific, frequent problems:

**Format converters:**
- JSON to YAML (and vice versa)
- Timestamp converters
- Base64 encode/decode
- Markdown to HTML

**Generators:**
- UUID generators
- Password/secret generators
- Regex builders and testers
- Cron expression builders
- .gitignore generators

**Validators/linters:**
- JSON validators
- YAML validators
- SQL formatters
- Code formatters

**Calculators:**
- Unix timestamp calculators
- Color converters (hex to RGB)
- Byte size converters
- Rate limit calculators

**Reference tools:**
- Cheat sheets (keyboard shortcuts, syntax)
- Status code references
- Comparison tables

### Characteristics of Successful Tools

**Instantly useful:**
- No signup required to use
- Works immediately on visit
- Solves problem in seconds