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.

terminalclaudetrending_upRisingcontent_copyUsed 423 timesby Community

API-firstdeveloper-toolsdevrelbottoms-up growthdeveloper adoptiondeveloper communitydeveloper GTM

claude

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

How to Write System Prompts That Actually Work

Article

person Admin•schedule 5 min read

How to Write System Prompts That Actually Work

System prompts set the rules of the game for every AI interaction. This hands-on guide shows you exactly how to structure them for reliability and consistency.

Claude vs GPT-4o: Which Model Fits Your Use Case?

Article

person Admin•schedule 5 min read

Claude vs GPT-4o: Which Model Fits Your Use Case?

Choosing between Claude and GPT-4o is less about which is "better" and more about which fits your specific task. Here is a practical breakdown.

How Our Design Team Cut Brief-Writing Time by 70% with AI

Article

person Admin•schedule 5 min read

How Our Design Team Cut Brief-Writing Time by 70% with AI

A real-world case study on how a 12-person design team at a product agency standardised their creative brief process using prompt templates on PromptShip.

Why AI Hallucinations Happen (and How to Reduce Them)

Article

person Admin•schedule 5 min read

Why AI Hallucinations Happen (and How to Reduce Them)

Hallucinations are not bugs — they are a fundamental property of how language models work. Understanding why they happen is the first step to minimising them.

The State of AI Coding Assistants in 2026

Article

person Admin•schedule 5 min read

The State of AI Coding Assistants in 2026

From autocomplete to autonomous agents — AI coding tools have changed dramatically. Here is where things stand and what to expect next.

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

Article

person Admin•schedule 5 min read

From Idea to Shipped Prompt: A Solo Founder's AI Workflow

One founder. No team. A dozen AI-powered tools and a tight prompt library. Here is the workflow that runs a bootstrapped SaaS doing $15k MRR.

Recommended Prompts

claudeshieldTrusted

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.

Cold Outbound Email Sequence Writer

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

MCP for Code Intelligence Platform

Builds MCP servers providing code intelligence tools covering AST analysis, symbol search, dependency graphs, and code navigation.

Analyst Relations GTM Strategy

Designs an analyst relations program that earns Gartner and Forrester placements, builds category influence, and uses analyst credibility to accelerate enterprise deals.

International Market Entry GTM Plan

Designs a market entry GTM strategy for expanding into a new geography — with market readiness assessment, localization requirements, and a phased entry playbook.

GTM Post-Mortem Template

Conducts a structured GTM post-mortem for a missed target, failed launch, or lost quarter — producing specific root causes and actionable course corrections.

star 0fork_right 312

bolt

pin_invoke