Illustrative scenario: a multigenerational London, Ontario family firm modernising its book
A multigenerational family firm in London, Ontario holds decades of client history in the founding partner's memory and paper files. The modernising problem is not scanning documents — it is turning who-knows-what into records: which clients the firm acts for, what services each one buys, when everything is due, and who handles a file when the founder steps back.
The firm in this scenario
An archetype, not a client. The figures below describe the shape of the practice being modelled — they are inputs to the scenario, never results.
| Attribute | Detail |
|---|---|
| Archetype | Multigenerational family firm modernising a founder-held client book |
| Location | London, Ontario |
| Firm size | Founding partner, one second-generation partner and two staff |
| Client profile | Long-tenured personal and corporate clients built over decades, including farm corporations and insurance-commission personal files typical of southwestern Ontario |
- Client CRM
- Custom fields
- Services catalogue
- Internal Team
- Reminders
The problem
The client list exists in three places that do not agree: the tax software, the billing ledger and the founder's memory. Nobody else can answer the basic operational question — which clients do we act for, and what do we do for each — without asking. Farm corporations with off-calendar year-ends and spring commission-income files each run on rhythms only one person fully carries, which makes every vacation a risk and succession a cliff.
Delegation fails for the same reason. The context that makes a file manageable — this client answers in February and November between field seasons, that one's HST should go early because they travel in March — was never written anywhere, so handing a file to the second generation hands over the paperwork but not the knowledge. The younger partner ends up re-learning by making the mistakes the founder stopped making twenty years ago.
The workflow, step by step
- 1
Consolidate the client list into one record
The book is exported from the tax software and billing ledger and imported by CSV, then reconciled once: every client the firm acts for exists as a single record with legal name, fiscal year-end, status and contacts.
Client CRM with CSV/XLSX import
- 2
Write down what each client actually buys
Every engagement becomes a typed service on the client record — T1, T2, HST, bookkeeping — with its frequency and price. The founder's per-client mental catalogue becomes a real one anyone can read.
Services catalogue
- 3
Capture the margin notes as structured fields
The details the founder kept in his head — preferred contact months, farm field seasons, family relationships between client entities — become admin-defined custom fields and internal notes that travel with the record.
Client CRM custom fields
- 4
Reassign files with workload in view
Clients and open tasks move to the second-generation partner and staff with each person's live workload visible, so the transition is deliberate rather than a pile shifted in one weekend.
Internal Team workload
- 5
Let deadlines come from cadences, not memory
With services and fiscal year-ends recorded, the deadline feed generates itself: personal tax each January, HST on each client's cadence, year-end reminders a month before each fiscal year-end. The calendar stops living in one person's head.
Reminders
What this changes
Firms in this position typically find that succession stops being an event and becomes a process: the next generation can answer what the firm does for any client and when it is due without asking, the founder's judgement is preserved as notes rather than lost as memory, and stepping back no longer means the book steps back too.
About this scenario
Related reading
Where this applies
Start running a tidier, deadline-proof practice.
Set up your firm in minutes. No credit card to start.