Hire an AI developer partner program planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A developer adoption plan: open or curated, the developer path, docs to write first and numbers to track
• Partner types and tiers, with what each side gives and gets
• Incentives for each tier
• Small tests with a go or no-go number for each stage
• Missing facts and one next action

How it does the job well

• Start from the user problem and the evidence for it, then the solution.
• Write decisions down with the reason and the options you rejected.
• Keep scope small enough to ship and learn. Name what is out of scope.
• Define how success will be measured before building.

Mistakes it avoids

• Treating opinions or one loud request as proven demand.
• Specs that skip edge cases, error states or dependencies.
• Roadmaps with dates but no owners or confidence levels.

What a good result looks like

An example, not your task: You run an API or platform and almost nobody outside your team builds on it.

• Developer adoption plan. Open or curated, the developer path, docs to write first, support rules and numbers to track.
• Partner types and tiers. Each tier with what each side gives and gets, and the reason a partner needs you.
• Incentives. What each tier earns, sized to the work it takes on.
• Small tests and measures. Crawl, walk and run stages, each with a go or no-go number and a time limit.
• Source coverage, gaps and next action. What each part rests on, every MISSING line and one first step.

How the work is checked

• Every requirement can be tested.
• Assumptions and risks are listed with how each will be checked.
• Dependencies and owners are named.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Al Ries and Charlie Munger would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Developer adoption program planner. Decides open or curated for your size and risk. Maps the developer path from awareness to a live app and sharing. Picks which docs to write first, when community help is enough and when support steps in, and which numbers to watch. Hands step 2 the developer path and numbers.
• Revenue partnership program planner. Asks what each side loses if the deal fails. Finds why a partner needs you. Sets partner tiers, incentives and a build-or-partner call. Plans crawl, walk and run tests, each with a go or no-go number, and a written charter for both sides.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id build-a-developer-partner-program only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/build-a-developer-partner-program/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• What your platform or API does, and who builds on it today
• Your partner goal: more developers, more revenue, or both
• Companies you could partner with (optional)
• Your docs, support setup and developer numbers, such as sign-ups and API calls (optional)
• Your limits: team size, budget and deadline

Helpful context (optional)

• Developer numbers: sign-ups, first API calls and live apps
• Your docs and any support questions developers ask most
• A short list of partners you already talk to

Tools and access

• Claude, ChatGPT or Gemini: Any of them can read the pack's files and keep step 1's findings for step 2.
• Your product analytics: Sign-ups, API calls and time to first call show which stage of the developer path is weak.
• Any good chat AI: It plans from your notes. Paste in your docs outline if you have one.
• Claude, ChatGPT or Gemini: Any chat AI can run this. It only reasons over the facts you paste.

Functions and deliverables

• Developer partner program planner: Plan how developers use your platform and how partners benefit. Get small tests, incentives and measures for the program.
  • A developer adoption plan: open or curated, the developer path, docs to write first and numbers to track
  • Partner types and tiers, with what each side gives and gets
  • Incentives for each tier
  • Small tests with a go or no-go number for each stage
  • Missing facts and one next action
• Developer adoption program planner: Plan how outside developers build on your product. Get an open or curated choice, a developer path, docs order, support routes and metrics.
  • A readiness check with fixes to make first
  • An open or curated choice, with reasons
  • The developer path with a metric for each stage
  • A docs order and a support route
  • Partner tiers, and a student program if it fits
  • A 30, 60 and 90 day plan
  Source: GitHub Copilot community.
• Revenue partnership program planner: Plan a partner program that earns revenue. Test if a deal is real, sort partners into tiers and pilot each one in three phases.
  • A real-or-not check on each partner deal
  • A build-or-partner call, with the reason
  • A tier plan that says who gets what help
  • A three-phase pilot with go or no-go lines
  • A one-page partner charter and a launch checklist
  Source: GitHub Copilot community.
• Nonprofit program measurement planner: Build a nonprofit program measurement plan: pick measures, set targets and dates, and report results with clear limits. Give it your goals and records.
  • An indicator table with baselines, targets, sources and timing.
  • A named evaluation design that fits your budget.
  • A data collection calendar with an owner for each task.
  • A one-page board scorecard.
  • A funder-ready results section that shows sample size, response rate and limits.
  Source: Nonprofit Skills.
• Product context file writer: Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.
  • A product marketing context file
  • A summary of what the file already holds
  • A change log of updates
  • Gaps you still need to fill
  Source: Corey Haines.
• Al Ries: Clarify what a brand should stand for using Al Ries’s recorded approach. Examine its category, focus, name and launch story.
  • Your problem worked on the way Al Ries would: their questions, their method, their push-back
  • The answer or the work, in Al Ries's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Charlie Munger: Stress-test a plan using Charlie Munger’s recorded approach. Turn it upside down, examine incentives and ask where your knowledge ends.
  • Your problem worked on the way Charlie Munger would: their questions, their method, their push-back
  • The answer or the work, in Charlie Munger's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You run an API or platform and almost nobody outside your team builds on it.
• A company has offered to partner and you need to know what to ask for and what to give.
• You want to set partner tiers before partners start asking for special deals.
• You want to test a partnership with one or two customers before you invest in it.

Limits to check before starting

• You are selling to one large customer. Use Enterprise sales and onboarding planner.
• You need the terms and profit sums for one partner deal. Use Partner deal profit planner.
• You are ready to announce a partnership. Use Partner launch announcement and approval planner.
• Your product is not working yet, or nobody uses it. Fix that first, because a program built too early stalls.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the workflow pack and give it to an AI that can read files, such as Claude, ChatGPT or Gemini.
• Paste what your platform does, who uses it and your partner goal. Attach docs or numbers if you have them.
• Check step 1 before step 2 starts. It should say open or curated and why, name what a developer does first, and list the numbers it will watch. Step 2 reuses all of it.
• Check step 2. Each partner tier should show what each side gives and gets, and each test should have a pass or fail number.
• Nothing is sent or signed. Review the plan before you contact any partner.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/build-a-developer-partner-program for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.