Sample documents

What you receive

Every stage ends in documents you can use without us. Four samples show the format. Their figures are illustrative.

Assessment

Sample: issue register

What is wrong, how much it matters, the evidence, and who owns the fix.

Issue registerIllustrative

Rank	Issue	Evidence	Impact	Effort to fix	Suggested owner
1	Orders from email typed into both the CRM and the ERP	A timed sample of 40 orders: 6 minutes on average. Errors in 3% of 500 orders checked	High	Medium	Order desk lead
2	Customer records re-keyed between two CRM systems	A time log kept by the sales team for two weeks: about 10 hours a week	High	Medium	Head of sales
3	Service visits booked by phone after each call	Service desk tickets for three months: 3 days from call to visit (median)	High	Medium	Service manager
4	Warehouse system out of vendor support	The vendor’s published dates and the contract: support ended over a year ago, with no security updates since	High	High	Operations director
5	Monthly report rebuilt by hand from three exports	Calendars and interviews: 4 working days a month	Medium	Low	Finance controller

Ranked by impact, then by the effort to fix. Impact and effort are judged against the company’s goals for the next two years, agreed with the leadership team in week 1.

Technology strategy

Each system with its decision (keep, fix, buy, build or retire), the reason, and the quarter work starts.

Decision registerIllustrative

System	Decision	Reason	Work starts
Order intake	Fix	Orders are typed in twice. One entry point into the ERP, and an AI pilot on reading order emails.	Q1
Warehouse system	Buy	Out of vendor support, with no security updates. The new product is chosen through a selection.	Q1
Second CRM	Retire	Its records move into the main CRM, which ends the re-keying.	Q2
Field service scheduling	Build	The market check found no product that handles multi-day jobs with parts reserved in the warehouse.	Q3
ERP	Keep	Fits the main processes, and vendor support runs beyond the plan.	–

Quarters count from the start of the plan. The full register also records the options considered for each system.

Software selection

Three shortlisted products on one basis: licences, implementation, integration, data migration, training and price increases.

Five-year cost comparisonIllustrative

Cost over five years	Product A	Product B	Product C
Subscription or licence, maintenance and support	420	360	570
Implementation	180	150	210
Integration with the ERP	60	30	90
Data migration	40	40	50
Training	30	20	30
Expected price increases	40	20	20
Total	770	620	970
Fit score from scripted demonstrations, out of 5	3.5	4.0	3.0

Money in thousands, in the client’s currency. Price increases follow each vendor’s stated cap, compounded yearly.
Product B has the best fit and the lowest five-year cost. Before signing: its price cap in writing, data returned within 30 days of leaving, and named implementation staff.

AI strategy

Baseline, success line, stop line, decision date and cost at volume, on one page.

Pilot sheetIllustrative

Item	Agreed before the pilot starts
Task	Order intake from email, about 300 orders a week
Baseline	6 minutes per order, and 3% of orders with errors, from a timed and checked sample of real orders
Success line	At most 2 minutes per order, including the check, and at most 1% with errors
Stop line	Errors above today’s 3%, or an average time per order above today’s 6 minutes
Between the lines	Decided on the decision date, on the readings
Scope	500 real orders over four weeks. A person confirms every order before it reaches the ERP.
Decision date	End of week 4, by the operations director
Cost at volume	About 2,000 a month at the success line, against about 5,200 a month for the work today. To switch it off, the desk goes back to typing orders in.

Money in the client’s currency. People’s time at 45 an hour; the model and software at 0.05 an order; four hours of monitoring a month. A month is 46 working weeks divided by 12.

Each stage ends in documents like these, written about your company.