Hire an AI first-customer manual delivery planner

Everything it can hand back

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

• A delivery procedure with an owner, customer inputs and a done check for each step
• A who-does-what table
• A capacity check: hours needed against hours you have, with options if there is a gap
• A list of open handoff checks, each with a person who must confirm it
• A hand-back summary with one next step

How it does the job well

• Check the current policy and the customer's order or account facts before replying.
• Answer the actual question in the first two lines, then explain.
• Match the customer's tone. Acknowledge the problem once, without grovelling.
• Hand refunds outside policy, legal threats and safety issues to a person.

Mistakes it avoids

• Describing a tool or automation that does not exist yet as available.
• Promising anything beyond the accepted scope.
• Giving a person hours they do not have.
• Guessing effort when the user did not give it.
• Promising refunds, dates or fixes the policy does not allow.
• Copy-paste replies that ignore what the customer said.

What a good result looks like

An example, not your task: A first customer has said yes and you now have to deliver, with no process yet.

• Scope promised. What the customer accepted and the document it comes from, so nothing extra is promised.
• Delivery procedure. Each manual step with an owner, the customer's input, a done check and what to do when it fails.
• Who does what. A table of who does each step, who approves it and who is told.
• Capacity check. Hours the procedure needs against the hours your people have, with gaps shown.
• Options. Ways to close a gap, each with its trade-off.
• Handoff checks. Open items, who must confirm each and by when.

How the work is checked

• Only the accepted scope is promised. Manual work, dependencies and unbuilt tools are all visible.
• Each step has an owner, a done check and a place to go when it fails.
• Hours needed and hours available are shown side by side for every role.
• Every fact, figure and date traces to a source or is labeled as an assumption.
• 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 Alex Hormozi would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Process and SOP writer. Writes the manual delivery path: each step with its owner, what the customer must send, the done check, exceptions and who to tell when something goes wrong. Hands step 2 the list of steps with effort per step. Check before moving on: every step is something your team can do today.
• Team capacity planner. Compares the effort in the procedure with the hours of the people you named and what else they already do. Returns options and the estimates still missing. Check before moving on: nobody is given hours they do not have.

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 plan-a-manual-first-customer-delivery 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/plan-a-manual-first-customer-delivery/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 the first customer accepted, in writing (from the order, contract or an agreed email)
• The real steps you will do by hand, even if rough
• The people who will deliver, with the hours each can give per week
• The tools you have today, such as email, a spreadsheet or a shared folder
• Service limits and promises to the customer, such as response times and dates (optional)

Helpful context (optional)

• The customer's own words about what they expect and by when.
• A time log from any earlier similar job.

Tools and access

• A chat AI that reads files: It can read the order or contract and quote the promise from it, instead of from memory.
• A shared folder or doc: Keep the procedure where the delivery team can open it, so it is used and not just written.
• Any good chat AI: It needs your numbers pasted in. A tracker or calendar connection saves typing.

Functions and deliverables

• First-customer manual delivery planner: Share accepted scope, real steps, people and available hours. Get a delivery guide, workload check and unresolved handoffs.
  • A delivery procedure with an owner, customer inputs and a done check for each step
  • A who-does-what table
  • A capacity check: hours needed against hours you have, with options if there is a gap
  • A list of open handoff checks, each with a person who must confirm it
  • A hand-back summary with one next step
• Process and SOP writer: Turn how your team works into a clear SOP. Give it a process name or old notes. You get a RACI table, a flow, steps and exceptions.
  • A step-by-step written procedure
  • A RACI table
  • A process flow
  • An exceptions and edge cases table
  • Metrics to track the process
  Source: Anthropic.
• Team capacity planner: Give it your team and projects. Get workload against people, who is overloaded, and whether you can take on more.
  • A table of hours available, hours used and percent full for each person
  • A list of who is over or under their target
  • Which coming projects fit and which leave a gap
  • Three to five options with the hours each one frees up
  • One recommendation, and what would change it
  • A list of assumptions and missing facts
  Source: Anthropic.
• Offer delivery options planner: Share the promises in your offer. Compare one-to-one, group and reusable ways to deliver them, with estimated cost and buyer value.
  • Five to ten delivery options for each promise, in three groups by audience size
  • Stretch options you may never use, labelled as stretch
  • A rating for each option: build hours, hours per buyer, cash cost and what it does for the buyer
  • The best two or three options per promise marked as candidates
  • One shortlist table of every candidate
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Alex Hormozi: Improve an offer, price or lead plan using Alex Hormozi’s recorded frameworks. Check buyer needs, costs and honest promises before adding more leads.
  • Your problem worked on the way Alex Hormozi would: their questions, their method, their push-back
  • The answer or the work, in Alex Hormozi'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

• A first customer has said yes and you now have to deliver, with no process yet.
• You are about to hand delivery to a teammate and nothing is written down.
• A pilot customer expects a service level your small team has never tested.
• You are launching and doing each step by hand until the system is ready.

Limits to check before starting

• No customer has accepted anything yet, so there is no scope to promise. Write the scope first with the Project kickoff brief writer.
• You deliver this work every week and only want it written down. Use the Process and SOP writer.
• You need to set a date for a new request. Use the Team capacity and delivery-date planner workflow.
• You want to design the automated version. This plans the manual one and will not describe a tool you have not built.

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.

• Open Claude, ChatGPT or Gemini. Pick one that can read files if you will attach the order or contract.
• Add the workflow pack. Paste what the customer accepted, your manual steps, your team's weekly hours and your tools.
• After step 1, read the procedure step by step. Does each step match what you will really do? Delete any step that relies on a tool you do not have.
• After step 2, check the hours against your team's real week. If there is a gap, pick an option or change the promise.
• Send the procedure to whoever leads delivery for sign-off. Fill every MISSING line before you book the customer's start.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/plan-a-manual-first-customer-delivery 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.