Use when the user names developers, API adoption, docs, SDKs, or a bottom-up motion: the developer motion plan with funnel, content spine, and conversion points.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
Discover, first call, first success, production, expand. Each stage gets its conversion point and the one number that proves it. Instrument before you opine.
Minutes from landing to first successful call. Every step that is not needed is a conversion tax — name each one with the fix.
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.
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.
First-call conversion, activation rate, time-to-production, and expansion per account, each with a guardrail so growth never trades against experience.
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.
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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.