Guides
Toronto Business Software Planning Guide
A sequence for Toronto companies choosing software, including the Ontario electronic monitoring policy and HST questions that change the decision.
Quick answer: measure before you shop. Put a stopwatch on the report that takes longest, trace one transaction through every system that touches it, and list the five workflows people complain about. Then settle three Ontario-specific questions that eliminate options quickly, because discovering them after signing is expensive.
Step One: Two Measurements
Time your slowest recurring report. Month end, a client profitability question, a compliance return, a security questionnaire. Include the chasing. That number is your business case.
Count the re-entries. Follow one transaction end to end and count every system it passes through and every re-typing. That count predicts total cost better than licence pricing, because integration and duplicate entry are where the money goes.
Step Two: Define the Workflows
Write down the five workflows that matter most, in enough detail that a stranger could follow them, including the workaround everybody uses. Scope built on documented workflows can be priced. Scope built on a wish list expands.
Step Three: Settle the Ontario Questions
Electronic monitoring policy. Ontario employers with 25 or more employees must maintain a written policy disclosing whether and how they electronically monitor employees, a description of the circumstances, how the resulting information is used, and the date the policy was prepared or changed. Employees must be given a copy. The threshold is assessed on January 1 each year with the policy required before March 1.
| What Ontario requires | |
|---|---|
| Who | Employers with 25 or more employees in Ontario, counted across all Ontario locations |
| When counted | January 1 each year |
| Deadline | Before March 1 of that year |
| Must state | Whether monitoring occurs, how and in what circumstances, how the information is used, and the date prepared or changed |
| Employee copy | Provided to each employee, within 30 days of the policy being required |
| Nature of the duty | Disclosure only. It creates no new restriction on how the data may be used |
This matters at purchase time because so much ordinary software monitors: time tracking with automated capture, endpoint management, GPS on vehicles, call recording, document access logging, and productivity analytics. If a purchase changes what you monitor, the policy has to change with it. Guidance is at ontario.ca, and this is general guidance instead of legal advice.
HST at 13 percent. Ontario applies 13 percent HST where Alberta applies 5 percent GST. For a registrant recovering input tax credits the true cost is comparable, and the cash and working capital difference is real, particularly on annual prepaid subscriptions. Vendors quoting in USD add a second variable.
Privacy and breach obligations. Under PIPEDA, breaches of security safeguards must be reported to the Privacy Commissioner of Canada and affected individuals notified where there is a real risk of significant harm, with records kept of all breaches. Any system holding personal information sits inside that, so ask where data is stored, who at the vendor can reach it, and what the contract says about breach notification.
Step Four: Know Which Problem You Have
- Professional services technology covers utilisation, realisation, and work in progress
- Managed IT vs internal IT covers who operates the systems
- Cybersecurity software covers the tool categories and buying order
- Cybersecurity readiness checklist covers the control set buyers will ask you about
- Vendor access covers the permissions you are about to grant an implementer
Step Five: Demo Your Own Hard Cases
Give each vendor a scenario from your business and watch it run live. A client with three matters and two rate structures. A retainer partly consumed. A month end with unbilled work in progress. A security questionnaire from a prospective client.
Vendors demo their strengths. You need to see the edges.
Where Projects Go Wrong
No internal owner. Someone must own the data model after go-live, or the system decays within a year.
Customizing in month one. Run standard first, then customize what genuinely does not fit.
Underestimating data cleanup. Duplicate clients, dead matters, and inconsistent naming are their own workstream.
Choosing on licence price. The gap between platforms is usually small. The gap between implementations is large.
Compliance as an afterthought. The monitoring policy, the privacy terms, and the questionnaire evidence all belong in the scope document.
Recommended Next Step
Do step one this week. Then check whether you have an electronic monitoring policy, because if you have 25 or more employees in Ontario and you do not, that is a same-week fix worth more than most of an implementation.
If the shortlist has narrowed to open-source platforms, our Calgary edition compares them side by side in ERPNext vs Odoo vs Zoho.
Frequently Asked Questions
- What is the Ontario-specific thing most software buyers miss?
- The written electronic monitoring policy. Ontario employers with 25 or more employees must have a policy disclosing whether and how they electronically monitor employees, how the information is used, and when the policy was prepared. A great deal of ordinary business software monitors, so buying it can trigger the obligation.
- Does HST change the software cost comparison?
- It changes the cash cost. Ontario applies 13% HST where Alberta applies 5% GST, so an identical subscription costs more in Ontario before input tax credits. For a registrant recovering the tax the real cost is comparable, and the working capital difference is still worth modelling.
- How long does an implementation take?
- For a Toronto SMB, accounting and CRM usually runs 4 to 8 weeks. Add inventory, purchasing, or project accounting and it becomes 8 to 16 weeks. Add manufacturing or multi-entity consolidation and 12 to 24 weeks is realistic. Data cleanup slips most often, so give it a named owner.