SpidNums vs Firm360: an honest comparison for Canadian firms

What Firm360 does well

This section comes first deliberately. Firm360 is a serious product with real customers, and a comparison that pretends otherwise is not worth reading.

• Genuinely all-in-one for small firms — document management, workflow, billing and portal in a single system.
• Consolidating several point tools into one platform is a real reduction in administrative overhead.
• Positioned squarely at small firms rather than scaled down from an enterprise product.

Where the fit differs

These are differences in model rather than claims about missing features. Where a capability is not listed for Firm360, that means we did not verify it — not that it is absent.

• Jurisdiction: Firm360 is built for the US market. SpidNums is built around CRA, Revenu Québec and Alberta TRA obligations.
• Pricing model: per user versus a flat firm fee.
• White-label: SpidNums presents the firm's brand across the app, client emails and engagement letterhead on every plan.
• Data residency: SpidNums hosts in Canada (ca-central-1). We make no claim about competitor hosting.

Pricing

Firm360 does not publish pricing we could verify, so this page does not state a number for it — ask the vendor for a current quote. SpidNums is a flat USD $1,200 per firm per year with every feature included, including white-label branding.

What SpidNums is, plainly

SpidNums is practice management for Canadian accounting firms: the client list, the services each client buys, the deadlines those services generate, the person who owns each one, and the engagement letter that defined the scope. It is not a general ledger, it does not prepare or transmit returns, and it does not calculate payroll — those stay in the tools your firm already files with.

The list below is the complete set of claims this site makes about the product. If a capability is not on it, we do not claim it.

• Multi-tenant white-label branding per firm — name, logo, colours, emails and letterhead
• Colour-coded SLA deadline dashboard ranked by proximity
• Aggregated reminders across tasks, service cadences and fiscal year-ends
• E-signed engagement letters with a public, no-login client portal
• Per-tenant Google Workspace integration
• Client portal
• Staff roles with confidential-client gating
• Canadian-hosted data (Supabase ca-central-1)
• Flat USD $1,200 per firm per year, all inclusive
• CSV/XLSX client import and export

Questions worth asking both vendors

Comparison grids converge because feature names converge. These six questions separate products that look identical on paper, and they are worth asking of Firm360 and of SpidNums alike.

• How is a deadline generated — from a rule tied to the client's fiscal year-end and reporting period, or from a recurring task somebody configured by hand?
• When a client's filing cadence changes, is that one field or a rewrite of every future date?
• Whose brand does the client see on emails, on the portal and on a signed engagement letter — and on which plan does that become true?
• Where is client data hosted, and is tenant isolation enforced in the database or only in the application? Get the answer in writing.
• What is the total annual cost at three seats and at ten? Ask for the total, not the per-user figure.
• What comes across on migration, and what does not? Clients usually move; documents, notes and completed work usually do not.

Who should choose Firm360

A US-based firm, or a firm whose priority is consolidating document management and time-and-billing into one system, will get more from Firm360 than from a Canada-specific platform. Breadth in one product is a legitimate reason to choose it.

If that describes your firm, take the other product seriously. If it does not, the practice management overview covers what SpidNums does in full.

Switching

Client lists move by CSV or XLSX import. Documents and billing history should be exported and retained separately — there is no direct connector.

SpidNums imports and exports clients as CSV or XLSX. There is no direct migration connector, so historical documents, notes and completed work do not come across automatically — plan the cutover around a period boundary rather than mid-season.