Illustrative scenario: a Charlottetown generalist practice that does everything for everyone
A small-market generalist practice in Charlottetown takes the work its clients need — T1s, T2s, bookkeeping, payroll and HST returns in whatever combination each client buys. The breadth is the business model; the risk is that no two files follow the same path, so nothing is standard and every deadline type lands on the same short-staffed calendar.
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 | Small-market generalist practice serving every client type |
| Location | Charlottetown, Prince Edward Island |
| Firm size | One partner and two staff |
| Client profile | Tourism operators, farms, seafood processors, trades and professionals — each buying a different mix of T1, T2, bookkeeping, payroll and HST work |
- Services catalogue
- Reminders
- Engagement Letters
- Task Master
- SLA dashboard
The problem
The firm's mental model is per-client, not per-service. Each file is remembered as a whole — what this operator needs, roughly when — so there is no single view of every HST filer due this month or every payroll year-end approaching. That works until the busy months stack: personal tax in spring, slip season in February, HST cadences all year, and tourism clients who go quiet from June to September just when their paperwork is needed. In a market as small as Prince Edward Island's, a missed deadline is a reputational event, not a statistic.
The other cost of breadth is unpriced growth. Engagements that started as a handshake gained payroll here, a second corporation there, and were never re-papered — so the service list per client exists nowhere, year-over-year pricing is a guess, and the partner cannot say which bundles carry the firm and which quietly lose money.
The workflow, step by step
- 1
Write down each client's actual bundle
Every client's real mix of work becomes typed services on their record — T1, T2, bookkeeping, payroll slips, HST — each with a code, frequency and price. The bundle stops being folklore.
Services catalogue
- 2
Let every cadence run its own clock
Each service's frequency and next-due date feed the reminder feed on its own schedule: HST on the client's reporting period, personal tax each January, year-end reminders a month before each fiscal year-end.
Reminders
- 3
Paper every bundle with an engagement letter
Letters price from the client's assigned services plus custom line items, and next year's letter loads from history — so re-pricing a grown bundle is an edit, not archaeology.
Engagement Letters
- 4
Run all the work on one board
Bookkeeping months, returns and slip runs all live as projects and ordered tasks with a table and Kanban view, so the mixed workload is visible as one queue instead of five mental lists.
Task Master
- 5
Triage by colour across every deadline type
One SLA rule covers everything: green beyond seven days, orange within seven, red when due or overdue. The partner scans a single board instead of reconciling deadline types in their head.
SLA dashboard
What this changes
Firms in this position typically find the generalist book becomes manageable by service rather than by memory: every cadence runs its own visible clock, seasonal clients get chased before they disappear for the summer, and each bundle is papered and priced from a real service list instead of a handshake nobody wrote down.
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.