A sample AI roadmap: what you get after a consultation
What you will take away
- How one workflow is written up: where the hours go today, three ranked changes, what not to do yet
- How each change shows its benefit, effort and risk
- What a concrete first step looks like
See the format before you pay. The sample AI roadmap was made for a fictional cleaning company of 32 people and is labelled as a sample; it shows how I describe each task, what it saves, what it needs and what it risks.
Company A: from client request to paid invoice
In short
How it works today
| Role | Where the time goes | Hours a week |
|---|---|---|
| Coordinators two people, 40 h each | Reading requests and writing replies | about 10 each |
| Retyping requests into the scheduling tool | about 6 each | |
| Quotes for one-off jobs, written from scratch | about 3 each | |
| Visit changes and sick calls, phoned one by one | about 8 each | |
| 27 of 40 each, about 54 for both | 54 | |
| Bookkeeper | Invoices made by hand | about 4 |
| Phoning late payers | about 10 | |
| 14 of 40 | 14 | |
| Senior or manager | Checking that visits happened, phoning cleaners, collecting reports | 8 |
| Total | Almost two of the eight office roles | about 76 |
Hours are your estimates from the call. Two weeks of simple time tracking will confirm or correct them. Quotes stay as they are for now; they get easier once the inbox drafts replies.
Three improvements, ranked
Ranked by benefit against effort, best first.
1Invoices and paymentEffort: low · bookkeeper
2Request inboxEffort: medium · coordinators
Risk, wrong answers: automatic answers only for questions with one fixed answer. Everything else waits for a coordinator.
3Client, office and cleaners in one loopEffort: medium · coordinators and senior
What not to do yet
- A new scheduling platform. Moving 24 people on client sites to a new app costs more than it returns.
- A third coordinator. The three changes free more hours than a new hire would add. Measure office hours for four weeks after improvement 1 goes live, then decide.
First step
Improvement 1, in two stages
List last quarter's invoices with the days each took to be paid. Then switch on invoices on completion and email reminders.
Estimated effort: about 4 to 6 hours of setup. Cost is these hours at the rate of whoever builds it: your team, a freelancer or me. No running cost: it is part of your current plan.
Stage two, a month later: messenger reminders and AI calls to clients who still have not paid. They add a small running cost per message and call, estimated before you decide.
Implementation is quoted separately. You decide who builds it: your team, a developer or me.
When this works, next steps
- Time from the "done" button goes straight into timesheets for payroll.
- A photo after cleaning goes with the "done" button, and the client rates the visit in one click; a low rating alerts the manager.
- A cleaner reports sick by button or in the call, and the system suggests a replacement from those who are free.
- A weekly dashboard for you: visits, late arrivals, complaints, unpaid invoices, margin per client.
Start here: free call or consultation
Was this useful?