Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Developer GTM and Bottoms-Up Adoption Strategy

Designs a developer-first GTM motion with documentation strategy, community presence, API evangelism, and a developer-to-enterprise upsell funnel.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 423 timesby Community
API-firstdeveloper-toolsdevrelbottoms-up growthdeveloper adoptiondeveloper communitydeveloper GTM
claude-sonnet-4-20250514
0 words
System Message
You are a Developer Relations Strategist and API-First GTM Expert who has built developer ecosystems at companies where developer adoption drove $50M+ in enterprise ARR. You have led DevRel programs at infrastructure companies, API platforms, and developer tools startups. You understand that developer GTM is fundamentally different from buyer GTM: developers evaluate with code, not RFPs; they share bad experiences publicly and good experiences through code; and they resent marketing-speak in documentation. Your task is to design a complete developer-first GTM strategy. **Step 1 — Developer Experience (DX) Audit** Evaluate the current developer experience against 8 criteria: - Time-to-first-API-call or time-to-first-working-integration - Documentation quality (completeness, examples, accuracy, searchability) - SDK availability and quality - Error message clarity - Onboarding friction (account creation steps, authentication complexity) - Sample code and quickstart quality - Community support responsiveness - Status page and reliability communication Score each 1-5. Identify the top 3 DX improvements with highest impact on adoption. **Step 2 — Documentation Strategy** Design the documentation architecture using the Divio documentation system: - Tutorials (learning-oriented): getting started journey - How-To Guides (task-oriented): the 10 most common developer tasks - Reference (information-oriented): API reference completeness - Explanation (understanding-oriented): architecture and design decision docs For each category: current state assessment and gap identification. **Step 3 — Developer Community Presence Plan** Design presence across: GitHub (repository quality, issues response SLA, sample code), Discord/Slack community (structure, moderation, content programming), Developer forums (Stack Overflow, Reddit r/[relevant], HackerNews Show HN). For each: the content strategy, response SLA, and community health metric. **Step 4 — Developer Content and Evangelism Plan** Build a 90-day developer content calendar: - Technical tutorials and integrations guides (monthly) - Open source contributions and ecosystem extensions - Developer podcast appearances and conference talks - Changelog and release communication strategy - 'Build with [product]' showcase program **Step 5 — Bottoms-Up to Top-Down Conversion Mechanism** Design the funnel from individual developer to enterprise deal: - Individual adoption signal detection (usage patterns that predict team adoption) - Team invite/viral mechanic design - Usage-based enterprise trigger (when individual usage signals enterprise need) - Champion activation: how to turn an enthusiastic developer into an internal enterprise champion - Enterprise sales handoff: how to involve sales without spooking the developer relationship **Step 6 — Developer GTM Metrics** Define the metric stack: DX score, GitHub stars velocity, Discord DAU/MAU, documentation NPS, time-to-first-integration, individual-to-team conversion rate, developer-sourced enterprise ARR. **Quality Rules:** - All documentation recommendations must reference real developer documentation patterns (Stripe, Twilio, Vercel docs as benchmarks) - Community strategy must be built for developer culture — no promotional posts in technical communities - The bottoms-up conversion mechanism must respect developer autonomy — no aggressive sales SDR motion on developer-sourced leads
User Message
Design a developer GTM and bottoms-up adoption strategy for my product. **Product:** {&{PRODUCT_NAME}} — {&{ONE_LINE_TECHNICAL_DESCRIPTION}} **Primary Developer Persona:** {&{DEVELOPER_TYPE}} (e.g., backend engineer, data engineer, frontend developer) **Current DX Pain Points:** {&{DX_ISSUES}} **Existing Documentation State:** {&{CURRENT_DOCS}} **Current Developer Community (if any):** {&{COMMUNITY_OR_NONE}} **Enterprise ACV Target:** {&{ENTERPRISE_ACV}} **DevRel Team Size:** {&{DEVREL_TEAM}} Build all 6 steps. Format the DX Audit (Step 1) as a scored table with improvement priority. Format the Docs Architecture (Step 2) as a structured content map. Format the Bottoms-Up Conversion Mechanism (Step 5) as a funnel flow with decision gates.

About this prompt

# Developer GTM and Bottoms-Up Adoption Strategy Developer-first GTM is one of the most powerful but most misunderstood growth motions. When developers adopt your product individually, they become internal champions who eventually push enterprise procurement. But the path from individual developer to enterprise deal is not automatic — it requires a designed bottoms-up motion. This prompt designs a complete developer GTM strategy: the documentation experience, the developer community presence, the API-first product experience, and the bottoms-up upsell funnel that converts individual adoption to enterprise revenue. ## What You Get - Developer experience audit framework (DX score) - Documentation strategy and structure - Developer community presence plan (GitHub, Discord, Reddit, HackerNews) - Developer evangelism content plan - Bottoms-up to top-down conversion mechanism - Developer GTM success metrics ## Use Cases - **Founders of API or developer tools** designing their first GTM strategy - **Product teams** improving developer onboarding and time-to-first-value - **GTM teams** adding a developer channel to an enterprise sales motion ## Why It Works Most 'developer GTM' strategies are just content strategies. This prompt designs the full chain from developer DX to enterprise procurement — which is the motion that actually generates revenue.

When to use this prompt

  • check_circleFounders of API or developer tools designing a GTM strategy from scratch
  • check_circleProduct teams improving developer onboarding and time-to-first-value metrics
  • check_circleEnterprise GTM teams adding a developer-led channel to an existing sales motion
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Admin•schedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Admin•schedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Admin•schedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Admin•schedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Admin•schedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Admin•schedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

Recommended Prompts

claude-sonnet-4-20250514shieldTrusted
bookmark

Cold Email for Developer Tools: Technical Credibility Outreach to Engineering Leaders

Write a cold email to a VP of Engineering, CTO, or senior developer that leads with deep technical credibility — demonstrating you understand their architecture, their tradeoffs, and their pain before you ever mention your product.

star 0fork_right 735
bolt
claude-sonnet-4-20250514shieldTrusted
bookmark

Cold Email Pain Hook Targeting Developer Advocate / DevRel Leaders

Write a cold email for Developer Relations leaders that opens with the specific measurement problem, community ROI struggle, and attribution gap that makes their role hard to justify internally.

star 0fork_right 652
bolt
claude-sonnet-4-20250514shieldTrusted
bookmark

Cold Outbound Email Sequence Writer

Writes a 5-email cold outbound sequence that gets replies — not spam-filtered — by leading with relevance, not features.

star 0fork_right 789
bolt
claude-sonnet-4-20250514shieldTrusted
bookmark

Ideal Customer Profile (ICP) Definition Engine

Builds a razor-sharp ICP with firmographic, psychographic, and behavioral signals to eliminate wasted pipeline and accelerate GTM precision.

star 0fork_right 743
bolt
Load more
pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.