Safe evidence
Redacted workflow proof
Bring rough counts, tool names, owner roles, and two to five redacted examples that show the workflow pattern.
First audit readiness packet
Bring the safe starting packet before the 72-hour Payback Map audit begins.
Use this page as the buyer-safe checklist for the first $299 audit. It consolidates the evidence to gather, what to leave out, how privacy requests are handled, when payment is confirmed, and exactly when the delivery clock starts.
This page does not collect payment, book a call, submit customer records, or request production access. Use redacted workflow notes only.
Payment timing
After scope is clear
The $299 audit should be paid only after one workflow, safe starting materials, and the report boundary are confirmed.
72-hour clock
After the packet is complete
The delivery window starts only after scope, payment or approval to proceed, and safe evidence receipt are complete.
Safe evidence
Send proof of the workflow pattern, not private records.
The first audit needs enough real context to separate facts from assumptions. It does not need passwords, account access, or a full customer export.
| Packet item | Safe version to share | Leave this out | Why it matters |
|---|---|---|---|
| Chosen workflow | One repeated handoff such as missed-call recovery, estimate follow-up, booking, intake routing, reporting, support, or invoicing. | A whole-business AI wish list or request to change live systems during the intro audit. | Keeps the report narrow enough to produce a useful first pilot ticket. |
| Volume and stakes | Approximate weekly or monthly counts, time spent, response delay, rework, missed follow-up, or owner interruption. | Unsupported revenue guarantees, exact private invoices, payment data, or sensitive notes. | Gives payback estimates a basis while keeping assumptions labeled. |
| Current tools and owners | Tool names, channels, handoff owners, status labels, and approval roles. | Passwords, API keys, admin links, workspace IDs, broad drive links, or one-time codes. | Shows whether the workflow can be made agent-ready without production access. |
| Redacted examples | Two to five cropped screenshots, emails, call notes, templates, tickets, or status lists with private details removed. | Names, phones, emails, addresses, payment information, private customer lists, exact records, or regulated details. | Lets the audit inspect real patterns without exposing customers. |
| Human review rule | Who approves customer-visible messages, price changes, refunds, complaints, schedule promises, opt-outs, and exceptions. | Requests for AI to send unreviewed customer messages or make sensitive decisions. | Keeps early AI assistance under human oversight. |
Support and privacy
If something sensitive was submitted, ask for review without repeating it.
Payback Map support includes a privacy request topic for access, correction, deletion, or accidental sensitive-data review. Include only safe locating context so the request can be checked without resending private details.
Safe locating context
- The email address used for the intake or support request.
- Company name if relevant.
- The page or form used and the approximate date.
- Whether you are asking for access, correction, deletion, or review of accidental sensitive data.
Do not repeat sensitive details
- Do not paste the sensitive note again.
- Do not send passwords, billing credentials, customer lists, or private records.
- A sent request is a receipt for manual review; it does not mean the requested action is already complete.
Start-record checklist
Confirm the start record before payment, private storage, or the 72-hour clock.
The public intake and support paths help with scoping. They do not automatically create a purchase, choose a private delivery location, book a call, start delivery, or authorize implementation. A person should confirm the start record first.
Scoped workflow
One repeated workflow is named, the report boundary is clear, and any missing evidence questions are known.
Safe evidence received
Starting materials are redacted, no production access is requested, and human-review boundaries are explicit.
Payment / start condition
Payment or approval to proceed is confirmed manually after scope and safe materials are clear, not from an instant public checkout.
Private delivery location
The buyer and reviewer agree where the finished report will be delivered privately before any customer materials are stored there.
Support and refund owner
A human owner is named for support questions, privacy requests, refund exceptions, and sensitive-data concerns before the audit starts.
72-hour clock trigger
The delivery window begins only after scope, payment or approval, safe evidence receipt, private delivery location, and exception owner are all confirmed.
Next step
Prepare the packet, then use the intake result as the scoping note.
If evidence is thin
Gather rough volume, tool names, a redacted example, and the approval rule before asking for paid audit work.
If the packet is ready
Use the AI intake to summarize one workflow, then confirm scope and payment through the separately approved path.
If a privacy question comes up
Use support with safe locating context only. Do not resubmit the sensitive material you want reviewed.