This is taking longer than expected.

Try againBrowse the library
AI Blocks

All AI specialists

Hire an AI paid idea test launch planner

Give it the idea, in a few lines. You get a three-buyer test plan: who to ask, in what order, what counts as a yes.

What you give

  • The idea, in a few lines
  • Who it is for and how you can reach ten of them this week
  • What you could deliver in thirty days with what you have

What you get

  • A three-buyer test plan: who to ask, in what order, what counts as a yes
  • A two-day paid ask script and how to take the money
  • A thirty-day launch plan with the smallest version that works
  • A trial log that records every attempt and what it taught

An example

You have an idea and have been thinking about it for months.

You ask: “Give it the idea, in a few lines. Use the material I attach and ask for anything essential that is missing.”

You get back:

  • Step 1: Three-buyer test. Who to ask first, in what order, the one-line pitch, and what counts as a real yes.
  • Step 2: Paid ask. The two-day message, price, how to take the money, what you promise and when, and what to say to a no.
  • Step 3: Thirty-day launch or the change. If three paid, the smallest version that works with a ship date. If not, what to change and whether to retry.

An example, not your task.

Hire this specialist

It is free and needs no account. Download the pack, give it to your AI and tell it the job. Your AI asks for anything it is missing, then does the work and checks it.

Download the specialist

Related specialists

Skills and workflows for this job: Test an idea before you build it

Details

Everything it can hand back

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

  • A three-buyer test plan: who to ask, in what order, what counts as a yes
  • A two-day paid ask script and how to take the money
  • A thirty-day launch plan with the smallest version that works
  • A trial log that records every attempt and what it taught

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 have an idea and have been thinking about it for months.

  • Step 1: Three-buyer test. Who to ask first, in what order, the one-line pitch, and what counts as a real yes.
  • Step 2: Paid ask. The two-day message, price, how to take the money, what you promise and when, and what to say to a no.
  • Step 3: Thirty-day launch or the change. If three paid, the smallest version that works with a ship date. If not, what to change and whether to retry.
  • Step 4: Trial log. One entry per attempt: what you expected, what happened and what it taught.
  • Hand-back summary. Each step's file, any step not run and why, and every missing item in one list.

How the work is checked

  • The test counts money, not kind words.
  • The ask says how to pay today, what the buyer gets by when, that the product is not built yet and what happens if you miss the date (a refund).
  • Fewer than three paid buyers means no launch plan: step 3 writes the change instead.
  • The log has a line for every attempt, including the nos.
  • 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 Noah Kagan and Pieter Levels would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

  • Plan the three-buyer test. Plans who to ask, in what order, and what counts as a real yes, in Noah Kagan's manner.
  • Script the paid ask. Scripts the two-day ask with the message, the price, how to take the money and what to say to a no.
  • Run the ask. A pause. Run the ask for two days. Record who said yes, who said no and why, and the money taken.
  • Plan the thirty-day launch. If three paid, plans the smallest version that works, shipped in thirty days, in the manner of Levels and Blakely. If not, says what to change.
  • Set up the trial log. Sets up a log that records each attempt, what you expected, what happened and what it taught.

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 pre-sell-your-idea-to-three-buyers-then-launch-in-thirty-days 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/pre-sell-your-idea-to-three-buyers-then-launch-in-thirty-days/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

  • The idea, in a few lines
  • Who it is for and how you can reach ten of them this week
  • What you could deliver in thirty days with what you have
  • What you have tried before (optional)

Helpful context (optional)

  • Names of ten people you can message this week
  • A payment link you already have
  • Past polite yeses and who gave them

Tools and access

  • Any good chat AI: Every step is a plan or a piece of writing.
  • A payment link: The real yes is a payment. Have the link ready before day one.
  • A spreadsheet: The trial log lives here.
  • Any good chat AI: The math and the message writing are text work that any strong chat AI does with this skill.
  • A payment link or invoice tool: Lets a buyer pay in a click when you ask.
  • Any good chat AI: One message is enough, so any strong chat AI works.
  • Any good chat AI: Fitting a plan to your hours and tools is text work that any strong chat AI does with this skill.
  • A payment link tool: Lets you take a card payment before the product is finished. It may need an account, a plan or a fee.
  • Any good chat AI: Listing options and designing a log is text work that any strong chat AI does with this skill.
  • A spreadsheet: Holds the trial log with one row per trial.

Functions and deliverables

  • Paid idea test launch planner: Share your idea and delivery limits. Get a three-buyer test, payment-request script, conditional launch plan and trial log.
    • A three-buyer test plan: who to ask, in what order, what counts as a yes
    • A two-day paid ask script and how to take the money
    • A thirty-day launch plan with the smallest version that works
    • A trial log that records every attempt and what it taught
  • Business idea payment test planner: Test a business idea in a weekend. Get the math on buyers needed, ten people to ask, and a plan to see if they will pay.
    • The one-minute math, with the number of buyers needed
    • A list of ten people you can reach within 48 hours
    • A direct ask for payment, and a plan for day two and day three
    • Go and change rules, written before the test
  • Paid idea test planner: Share an idea, buyer, price and profit goal. Get buyer-count maths, a two-day outreach plan and decision rules set before testing.
    • The buyer count your goal needs
    • Ten people to ask and how to reach each
    • The exact ask and a two-day schedule
    • Go, change and one-more-round rules
  • 30-day launch planner: Plan a 30-day launch with a fixed deadline, an early payment step, a spending cap and a keep, kill or change rule. Give it your idea and tools.
    • A fixed 30-day plan, day by day or week by week
    • A split of the work into what you do and the one part to pay for
    • A payment step placed before launch
    • A spending cap and a written decision rule
  • Trial and learning log planner: Name the result and buyer. Get a rough first trial, a checked measure, cheap next tests and a log of what failures rule out.
    • A check that the result is worth getting
    • A list of every option to try, and the roughest first version
    • A trial log with a row for each trial
    • A "what it ruled out" line for each failed trial, and what else the whole system needs
  • 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.
  • Noah Kagan: Plan a small paid business test using Noah Kagan’s recorded approach. Check profit math, draft a direct offer and set a short learning deadline.
    • Your problem worked on the way Noah Kagan would: their questions, their method, their push-back
    • The answer or the work, in Noah Kagan's voice, using their ideas by name
    • Anything that goes beyond their public record, marked
    • One suggested next step
  • Pieter Levels: Plan a small product launch using Pieter Levels’s recorded approach. Solve a real problem, cut the first version and use tools you already know.
    • Your problem worked on the way Pieter Levels would: their questions, their method, their push-back
    • The answer or the work, in Pieter Levels'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 have an idea and have been thinking about it for months.
  • Friends say it is great and none of them has paid.
  • You want to ship something this month instead of planning something this year.

Limits to check before starting

  • You can't deliver by the date you promise buyers, or the product is in a regulated category: run the Customer discovery interview planner instead, since it tests the idea without taking any money.
  • You don't yet know who your buyers are: use the Best customer finder first, then come back with ten names.
  • You only want to know what buyers worry about: use the Buyer problem list builder.

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 handoff pack. It's a zip with HANDOFF.md and every skill file this workflow uses.
  • Give the folder to Claude (in Claude Code, or as files in a Claude Project) and say "Follow HANDOFF.md".
  • Paste the idea and who it is for. It plans the three-buyer test and the paid ask.
  • Run the ask over two days. Record every answer in the trial log.
  • If three pay, follow the thirty-day plan. If not, read the log and decide what to change.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/pre-sell-your-idea-to-three-buyers-then-launch-in-thirty-days 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.