Free worksheets
Three worksheets. One pen.
Read them here or download each as a PDF. There is no sign-up and nothing is collected. They help you scope a conversation; they do not certify readiness or predict income.
Worksheet 01
Business systems readiness
Start with one business and one workflow.
- 01What do you sell, to whom, and who owns the business decisions?
- 02Trace one real inquiry through booking, delivery, payment and follow-up. Where does information get copied or lost?
- 03List your current tools, who owns each account, and what each costs. Which tool is the record of truth for bookings, customers and payments?
- 04Choose three manual bottlenecks. Estimate minutes per week from what you actually observe. Pick one to improve first.
- 05Which computer will you use? Do you control administrator access, backups, and your own vendor accounts and two-step verification? Never write passwords on this worksheet.
- 06Which actions need your approval: customer messages, bookings, purchases, refunds, publishing or access changes?
- 07What data should stay private? Can a new workflow be rehearsed with made-up records first?
- 08Define a successful handover: you can run, pause, diagnose, export and recover the workflow yourself.
- 09Who teaches your industry craft, if that is needed? Who can assess it? No partner is assumed.
- 10What time can you protect for preparation, practice and support? What would that displace?
Bring this to a scoped conversation. A proposal should state supported tools, deliverables, dates, exclusions, account ownership, price and support limits before any payment.
Worksheet 02
One workflow audit
Pick one workflow. Write its name, your business, and who owns it. Then answer each row.
- Trigger
- What event starts it?
- Input
- What is the minimum information needed?
- Record of truth
- Where does the authoritative version live?
- Responsible person
- Who checks the exceptions?
- Action
- What changes, and who approves it?
- Receipt
- How do you prove the action happened where it was meant to?
- Failure
- What happens if a tool times out or creates a duplicate?
- Stop
- How do you pause it without losing the record?
- Recovery
- How do you restore or export, and carry on safely?
Example: a booking inquiry enters your customer list. Availability comes from the actual booking system, and a confirmation is sent only after the booking is accepted there. A made-up customer is used to test a duplicate and a failed booking. Measure handling time and failed or duplicate actions before and after. Do not project sales from one test.
Checklist 03
Your AI setup should stay yours
- You hold the vendor accounts, subscriptions and two-step verification. Any setup access is explicit and can be revoked.
- Your business knowledge is organized and backed up. Private payroll and client records stay out of demonstration data.
- Supported tools and included workflows are named. Extra custom integrations are scoped separately.
- Customer messages, payments, bookings and publishing have clear approval boundaries.
- Tests show a clean start on your computer, your data kept separate from anyone else’s, safe failures, duplicate handling, and proof that actions reached their destination.
- You can run, pause, diagnose, export and recover the workflow yourself.
- Support hours, duration, ongoing vendor costs, exclusions and ownership are written down.
- Industry craft instruction comes from a qualified instructor where it is needed.
No setup connects to every app, and none guarantees sales. No accreditation is implied.