How firms run their work in SpidNums
Twenty-five jobs Canadian firms run in SpidNums — each one a step-by-step workflow built from live product mechanics, not promises.
A use case here is a real job — onboarding a client, running T1 season, tracking GST/HST cadences, sending engagement letters — described as the steps a firm takes inside SpidNums: which module does the work, what gets recorded, and what the team sees when a deadline approaches. Every step names a live capability.
Onboard a new client
Record, services, engagement letter and portal invite in one pass
Migrate your client list out of spreadsheets
CSV/XLSX template in, same shape out — a reversible migration
Capture the client data your firm actually tracks
Admin-defined custom fields put firm-specific data on the client record
Find any client contact mid-file
Multiple contacts with designations end the mid-file phone-number hunt
Set up recurring services and cadences
Service frequency plus next-due dates put recurring work on rails
Run T1 season on one board
Projects, SLA colours and January reminders run T1 season on one board
Track every corporate year-end
Fiscal-year-end-driven reminders keep staggered corporate deadlines current
Manage GST/HST filings across cadences
Per-client GST/HST cadences in one grouped deadline feed
Track payroll remittance work
Remitter-type cadences keep the quiet payroll cycle visible
Triage deadlines with SLA colours
One SLA colour rule — green, orange, red — replaces the status meeting
Run firm work on a Kanban board
Table and Kanban are one dataset with a toggle, tied to client records
Balance workload across your team
Live-computed workload numbers replace asking people how busy they are
Hand off work between staff cleanly
Reassign the manager and the tasks; the record keeps the history
Send e-signed engagement letters
E-signed engagement letters sent to a no-login page clients actually sign
Reprice annual engagements from history
Renew and reprice annual engagement letters from last year's letter, not a blank page
Roll out a branded client portal
A client portal in the firm's brand, on the firm's domain, invited by magic link
Collect client documents in one place
Client documents on the client's file, with the chase run as SLA-coloured tasks
Keep proof of client contact
Notes, a send log, and e-signed letters — client contact you can show, not just recall
Send deadline digests to the team
A deliberately sent email digest of every deadline the reminder feed is tracking
Put personal-tax reminders on rails
Annual personal-tax services that surface every January without a rebuilt spreadsheet
Start year-end prep a month early
A one-month early warning before every fiscal year-end, read from the client record
Monitor firm health from one dashboard
KPI cards, Needs attention, live workload, and recurring revenue on one screen
Rebrand SpidNums as your own platform
Your name, logo, colours, and domain on the whole platform — included, not a tier
Run a white-label reseller practice
Tenant-per-firm white-label reselling with audited support and fail-closed isolation
Onboard seasonal staff before the rush
Roster, assign, and go — seasonal hires with no per-seat licence maths
Your workflows, with your clients in them.
A tailored demo walks any of these jobs with your services, cadences and deadlines.