Hire an AI customer progress strategy reviewer

Everything it can hand back

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

• Your growth engine, the one rate that drives it and a sum showing where you stand
• A chain of hoped-for rates, starting rates to measure and dated milestones with predictions
• Per-group rates in place of totals, and which changes were proven or unproven
• A keep going or change course call with facts for and against, the kind of change and a dated review

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 run a first test or launched, and your totals are rising but you cannot say why.

• Step 1 file: the engine. Your growth engine, the one rate that drives it, and a sum with your figures showing where you stand.
• Step 2 file: milestones. Hoped-for rates, starting rates to measure, and three dated milestones with predictions.
• Step 3 file: rates, not totals. Which numbers are vanity totals, and the per-group rates to use instead.
• Step 4 file: reading the groups. A table by customer group showing which changes moved which rates, and how far each rate is from target.
• Step 5 file: the call. Stuck signs, test cycles left, a persevere or pivot call, the kind of pivot, and a dated review.
• HAND-BACK SUMMARY. Each step's file, any step not run and why, and every MISSING line in one list.

How the work is checked

• Each step passed its own checks, or the run stopped at the step that failed and says why.
• The steps ran in order, and each one used the result of the one before.
• Nothing was invented to fill a gap. Every gap is a MISSING: line.
• Nothing was sent, published or paid for without a clear yes.
• 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 Eric Ries and Jeff Bezos would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Picks the growth engine. Decides whether growth comes from keeping, referral or paid customers, does the sum with your figures and names the one rate to watch.
• Sets milestones. Writes the hoped-for rates, the test that gives true starting figures, one target rate per change and three dated milestones with predictions.
• Turns totals into rates. Marks the numbers that only grow and swaps them for per-customer rates split by group and release.
• Reads the groups. Puts each customer group in its own row, checks which changes moved which rates and tests whether the report can be trusted.
• Makes the call. Counts the signs of being stuck, works out how many test cycles are left and says pivot or persevere, with the kind of change and a review date.

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 pivot-or-persevere 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/pivot-or-persevere/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

• Your plan, with the figures you hope for
• After a test, results by join week or month for each step of the customer path, for at least two join periods, with what each count means
• Dates of each change you released (optional)
• Notes from customers, including those who left (optional)
• Money and time left (optional)

Tools and access

• Any good chat AI: Choosing an engine and doing the sums is text and arithmetic.
• A spreadsheet: Keeps monthly rates and shows the trend.
• Any good chat AI: Writing the rate chain and the milestone plan is text work.
• A spreadsheet: Holds the rate chain, predictions and later results side by side.
• Any good chat AI: Reading a sheet and writing formulas is text work.
• A spreadsheet or analytics tool: Builds the per-group tables and charts from your export.
• Any good chat AI: Reading a table and writing the verdict is text work.
• A spreadsheet or analytics tool: Builds the group table from an export.
• Any good chat AI: Weighing evidence and writing a call is text work.
• A shared document: Keeps the evidence, the call and the review date where the team can see them.

Functions and deliverables

• Customer progress strategy reviewer: Share the plan, goals and dated results by customer group. Get progress checks, gaps and a reasoned choice to change or continue.
  • Your growth engine, the one rate that drives it and a sum showing where you stand
  • A chain of hoped-for rates, starting rates to measure and dated milestones with predictions
  • Per-group rates in place of totals, and which changes were proven or unproven
  • A keep going or change course call with facts for and against, the kind of change and a dated review
• Customer growth model finder: Describe how customers arrive and stay. Compare repeat use, referrals and paid growth, with clear sums and the missing facts to check.
  • A supported main model, or the evidence still needed to choose one
  • A calculation with units, assumptions and missing figures
  • A primary metric with its owner and review date
  • A simpler weekly view that retains necessary cost, customer-flow and cash evidence
• Learning milestone planner: New product, little revenue? Paste your plan. Get starting rates, dated checkpoints and predictions written before the data.
  • Your hoped-for business as a chain of rates
  • The test that gives your true starting rates
  • Each change tied to one rate
  • Three dated milestones with predictions
• Business metric quality reviewer: Find the vanity metrics in your weekly report and swap them for per-customer rates you can act on, plus one main number to track.
  • A table showing which numbers are vanity
  • Replacement rates with formulas
  • Results split by group and release
  • One goal, one main number and a data check
• Cohort funnel analyst: Read your results by join week or month. See which changes moved which rates, and whether the report can be trusted.
  • A table of each group's path
  • Which changes moved which rates, and which are unproven
  • Signs that you are stuck
  • A pass or fail on whether the report can be trusted
• Product pivot decision reviewer: Decide whether to keep going or change course. Get a one-line call with facts for and against, the kind of pivot that fits and a review date.
  • A keep-going or change-course call in one line, with facts for and against
  • A count of six stuck signs, each with its evidence
  • How many more test cycles you can afford
  • If changing course, the kind of change that fits, what you keep and a new guess to test
  • A date for the next review and who should be there
• 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.
• Eric Ries: Turn a product plan into testable guesses using Eric Ries’s public approach. Start with the riskiest assumption and measure what customers actually do.
  • Your problem worked on the way Eric Ries would: their questions, their method, their push-back
  • The answer or the work, in Eric Ries's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Jeff Bezos: Review a product or stuck decision through Jeff Bezos’s recorded approach. Start with the customer, test what can be undone and write the reasoning.
  • Your problem worked on the way Jeff Bezos would: their questions, their method, their push-back
  • The answer or the work, in Jeff Bezos'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 run a first test or launched, and your totals are rising but you cannot say why.
• You made many changes and no rate moved.
• Your team is split between one more try and a change of direction.

Limits to check before starting

• You have one quiet period and have run no test yet: keep a simple spreadsheet of your totals until you have something to compare.
• You only want to know why sales dropped in a set of ads: use the Ad sales drop analyst.
• You want to check a test is big enough to trust: use the A/B test traffic checker.

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".
• Start with the plan. It sets the milestones first, then tells you when to run the test and bring back results.
• Hold the review on the date it gives, with the people it lists.
• The pack holds the five skills it runs, in order: Customer growth model finder, Learning milestone planner, Business metric quality reviewer, Cohort funnel analyst and Product pivot decision reviewer. Each step needs its skill file.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/pivot-or-persevere 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.