Buyer time
20–30 minutes
Gather notes, rough numbers, tool names, and redacted examples before any paid audit work starts.
Audit readiness checklist
First-customer pre-start checklist for a 72-hour Payback Map.
Use this checklist before payment or scope approval. It shows the required inputs, what to redact, when the 72-hour clock starts, and what happens after the audit is approved.
This page does not collect payment, book a call, or submit private customer data. Start with safe notes only.
Payment timing
After scope is clear
The $299 audit should be paid only after the workflow and safe starting materials are confirmed.
Clock trigger
Confirmed start packet
The 72-hour window starts after workflow, scope, payment, and safe inputs are all ready.
Preparation
The minimum useful prep packet.
Payback Map does not need account access to produce a first audit. It needs enough workflow evidence to distinguish facts, assumptions, risks, and the first safe pilot.
Bring these items
- One repeated workflow to inspect first, not a whole-business AI wish list.
- Rough weekly or monthly volume: leads, estimates, bookings, tickets, invoices, reports, or updates.
- Current tools involved: inbox, phone, forms, CRM, calendar, spreadsheet, scheduling, invoicing, or project-management system.
- Two to five redacted examples of the workflow, with private customer details removed.
- Where delay, rework, missed follow-up, owner interruption, or staff confusion appears.
- The human approval rule for customer-visible messages, pricing, refunds, complaints, or sensitive cases.
Do not share these
- Passwords, API keys, billing credentials, or admin access.
- Private customer lists, payment data, medical/legal/sensitive details, or unredacted screenshots.
- Requests for unreviewed AI sends, pricing decisions, refunds, legal promises, or safety-sensitive actions.
- A requirement that the $299 audit include implementation, CRM administration, live automation, or guaranteed ROI.
Required inputs
What to collect before the audit can start.
Rough information is enough. The point is to make one workflow inspectable without exposing private accounts, customer lists, or production systems.
| Input | Safe version to share | Why it matters |
|---|---|---|
| Chosen workflow | One repeated handoff such as missed-call recovery, estimate follow-up, booking, intake routing, reporting, support, or invoicing. | Keeps the $299 audit focused enough to produce a useful pilot starter kit. |
| Volume and friction | Approximate weekly or monthly volume, time spent, delays, rework, missed follow-up, or owner interruptions. | Gives the payback estimate a basis without claiming guaranteed ROI. |
| Current tools | Names of tools and channels involved: email, phone, CRM, forms, calendar, spreadsheet, scheduling, invoicing, project management, or AI assistants. | Shows whether the workflow is agent-ready inside the tools already used. |
| Redacted examples | Two to five screenshots, emails, templates, call notes, status lists, or tickets with names, contact details, addresses, payment data, and sensitive facts removed. | Lets the report separate real patterns from guesses while protecting customers. |
| Human-review boundary | Who must approve customer-visible messages, pricing, refunds, complaints, schedule promises, opt-outs, and exceptions. | Keeps the first AI-assisted workflow under human oversight instead of unsafe autopilot. |
Readiness questions
Five questions make the audit safer and more useful.
Use these questions to prepare a focused workflow review instead of a vague AI wish list.
What workflow repeats every week?
Name the exact handoff: estimate follow-up, missed-call recovery, job completion update, invoice reminder, intake routing, reporting, review request, or another recurring process.
What makes it expensive today?
Estimate owner time, staff time, response delay, rework, missed follow-up risk, avoidable tool work, or implementation waste. Ranges are acceptable; hidden math is not.
What evidence can be safely redacted?
Confirm you can provide examples, fields, screenshots, or templates with names, contact info, addresses, payment details, and sensitive notes removed.
What must stay human-reviewed?
Define review owners for customer messages, pricing, schedule promises, refunds, complaints, disputes, opt-outs, and any situation that should not receive an AI-generated draft.
What would make the report useful?
Clarify the desired handoff: first pilot ticket, prompt pack, SOP, tool-stack cleanup list, measurement dashboard, training agenda, or implementation decision.
What is out of scope?
The intro audit does not include live billing changes, production access, live automation, customer sends, implementation, or ongoing support unless separately scoped.
72-hour delivery path
What happens after scope and payment are approved.
The delivery window starts only after the workflow, scope, $299 payment, and safe starting materials are confirmed. It does not start when someone reads this page, clicks the AI intake, or sends incomplete notes.
Confirm the workflow, volume range, tools, pain points, redaction rules, human-review boundary, payment, and what would count as a useful report.
Map current steps, owners, handoffs, bottlenecks, risks, AI assistance candidates, payback assumptions, confidence, and missing verification questions.
Draft the ranked payback map, assistance mode map, oversight map, prompt examples, SOP starter, tool-stack cleanup notes, and first pilot ticket.
Review for generic advice, invented data, unsupported ROI, unsafe auto-send recommendations, unclear assumptions, and missing next steps before delivery.
After approval
What changes once the audit starts.
After scope and payment are approved, the work shifts from readiness checking to a concrete workflow map. The audit still stays within the intro scope.
You can expect
- A ranked Payback Map for one workflow, not a whole-business transformation plan.
- Clear assumptions, missing questions, safe AI assistance modes, and human-review rules.
- Prompts, SOP starter notes, tool-stack observations, a first pilot ticket, and a 30-day review cadence.
- A final handoff that your owner, operations lead, VA, consultant, or builder can review without needing live account access.
Still not included
- Live implementation, CRM administration, data migration, or managed automation.
- Unreviewed AI messages to customers, pricing decisions, refunds, legal promises, or support sends.
- Guaranteed revenue, guaranteed labor savings, model performance promises, or ongoing support unless separately scoped later.
- Requests for passwords, API keys, billing credentials, private customer lists, or production system access.
Handoff standard
The report should leave you ready to decide, not wondering what to do next.
A mature Payback Map is useful even if implementation is not purchased. It gives the owner, operations lead, VA, or builder a clear first pilot and safety boundary.
The report names the recommended workflow, why it ranks first, which assumptions need proof, and which lower-ranked ideas should wait.
The first ticket includes trigger, inputs, output, owner, review rule, failure cases, and the metric that decides whether to expand or pause.
Customer-visible messages, pricing, refunds, disputes, sensitive cases, opt-outs, and schedule promises remain human-reviewed unless separately scoped and proven.
Before you start
How to tell whether you have enough to begin.
Ready to start
You can name one repeated workflow, provide redacted examples, estimate volume or time, define the approval owner, and want a pilot starter kit before implementation.
Gather more first
The pain is real but examples, volume, tools, or approval rules are unclear. Gather a few more examples before relying on the report timeline.
Choose a different path
You need guaranteed ROI, immediate live automation, unreviewed customer sends, secret access, a whole-business transformation, or implementation without diagnosis.