A feature name such as “maintenance management” does not show who follows up when a repair stalls. A walkthrough should let you test that.
Before comparing property management software, write down three tasks you repeat and one task that is difficult today. Use those same examples in every demonstration.
Start with the work you need to complete
Choose examples that reflect your portfolio. An independent landlord and a management team may need different levels of coordination, even when both manage leases and maintenance.
- Find a tenant’s current agreement and the next relevant lease date.
- Take a maintenance request from its first report to a completed work record.
- Review income and expenses for a selected property and period.
Ask the presenter to follow each example through the product. Note where you would still need another spreadsheet, message thread or manual step.
Test three connected workflows
Use examples you recognize. For maintenance, a leaking tap is enough to test the process. You do not need a complicated scenario to find out where the next action lives.
| Workflow | Ask to see | Record any gap |
|---|---|---|
| Lease records | Find the property, unit, tenant and current agreement. Review the relevant terms and dates. | Missing information, duplicate entry or documents stored elsewhere. |
| Maintenance | Record an issue, identify the next action and follow the work to completion. | Unclear responsibility, updates outside the system or incomplete history. |
| Reporting | Select a property and period, inspect the underlying records and review the available output. | A missing report, an unclear calculation or an export you still need. |
Check Ontario fit through specific questions
An Ontario label alone does not establish that every part of your operation is supported.
Ask which parts of the product apply to your type of rental and which require separate documents or processes. If you need a particular agreement, notice, reporting treatment or integration, name it and ask to see the current capability.
Confirm the currency used in prices and financial records, and how dates and time zones appear. Check any requirement you depend on directly rather than assuming it follows from the product’s location or marketing.
For tenancy, legal or tax requirements, use the relevant official guidance and professional advice. Software can organize records; a product demonstration does not establish legal compliance.
Check who can access and change records
List the people who would use the system: you, a colleague, a contractor or an external adviser.
Ask what each person can see and change, how access is removed and whether you can review important changes. Confirm how you would retrieve your records if you stopped using the service.
Verify these points against the plan you would buy. A capability shown in a demonstration may have a different entitlement or setup requirement.
Work out the price for your actual portfolio
Ask for a written price using your current unit count and the features you need.
Check the base subscription, per-unit charges, optional features, setup charges and any separate services. Confirm currency, applicable taxes, billing frequency and cancellation terms.
If a trial is available, check what it includes and what happens when it ends. Put any unresolved cost beside the relevant requirement rather than treating the headline price as the total.
Agree on what a successful trial would prove
Choose a small set of records and a few tasks you can check:
- Set up the chosen property and its current records.
- Complete one lease or maintenance task.
- Review one report against records you already trust.
- Have the intended users try the steps they would own.
Mark each requirement “works,” “needs another step” or “not yet verified.” Keep the unresolved items for your next conversation.
Finish with a clear account of which daily tasks the system supports, what remains outside it and what the full setup would involve.