Developer and API motion

Use this when the user names developers, API adoption, docs, SDKs, or a bottom-up motion. Start from the API or dev product, the time-to-first-call path today, the docs and SDKs on hand, and the funnel numbers if any — Amplitude where connected.

Map the developer funnel

Discover, first call, first success, production, expand. Each stage gets its conversion point and the one number that proves it. Instrument before you opine.

Time the golden path

Minutes from landing to first successful call. Every step that is not needed is a conversion tax — name each one with the fix.

Write the content spine

The reference architectures, guides, and samples each funnel stage needs, each mapped to the question the developer is asking at that point. Docs stay with product; you spec what the motion needs.

Design the community and reach layer

The watering holes where your developers already gather, the event or build-week shape that earns attention, and the champion path from user to advocate.

Set the dev-motion scorecard

First-call conversion, activation rate, time-to-production, and expansion per account, each with a guardrail so growth never trades against experience.

What you hand back

The developer motion plan with funnel, content spine, and conversion points, saved dated. Review it when first-call conversion drops or a launch adds a new surface.

Fallbacks

No funnel numbers means you define the instrumentation spec before any read. No docs access means you draft from the public surface and flag the gaps. Never invent adoption numbers, community sizes, or benchmark rates. Anything published to developers ships only on the owner's explicit yes.