Short answer: give every property-management software vendor the same fictional portfolio and require five workflows live: property setup, a lease or booking change, maintenance from request to proof, owner reporting from source records, and complete data export. Score the result, not the presenter's confidence. Record time, clicks, handoffs, duplicate entry, permissions, exception behavior, required add-ons, and evidence that remains after the task.
Buildium's current buyer guidance recommends needs assessment, weighted criteria, team testing, workflow-based acceptance criteria, trials, and phased implementation. This independent script applies those principles consistently to JHA Solutions and every competitor. It is not a certification, and a 45-minute session cannot replace accounting, security, legal, integration, performance, or migration due diligence.
Prepare a safe fictional portfolio
Create one property, two units, one owner, one resident, one vendor, one cleaner, one lease or booking, one recurring charge, one invoice, one repair photo, and one document. Include an inactive record and one deliberate data error. Never upload real resident, applicant, bank, access, or identity information to a sales sandbox.
Define pass conditions before the meeting
Write the required outcome, evidence, maximum handoffs, permitted workaround, role, and quoted plan for each test. Mark blocking requirements separately from preferences. Use the permissions matrix for allowed and denied actions instead of accepting a verbal statement that roles are configurable.
Download the demo scorecard
Download the editable five-workflow software demo scorecard (CSV). It records scenario, pass condition, role, completion time, clicks, handoffs, duplicate entry, evidence, permissions, mobile result, exception handling, quoted tier, add-on, score, blocker, and follow-up proof.
Workflow 1: Start and understand a property
Add the property, units, ownership, resident, lease or booking, rent or nightly rate, key dates, document, opening balance, and responsible staff. Then ask a second person to identify current status without coaching. Record required configuration, reused fields, imports, validation, audit history, and what appears on mobile.
Workflow 2: Process a real change
For long-term rentals, change a lease date, recurring charge, or partial payment. For short-term rentals, add a booking, owner block, or cleaner turn. Confirm dependent calendars, balances, tasks, communications, and reports update correctly. Reverse the change and check whether the history remains understandable.
Workflow 3: Resolve maintenance end to end
Submit a leak with a photo, classify urgency, apply an owner approval threshold, assign a vendor, communicate with the resident, record access, add an estimate and invoice, verify completion, and reopen the issue. Use the maintenance workflow guide to test request, dispatch, proof, cost, and closure rather than only the ticket form.
Workflow 4: Produce and explain an owner report
Generate a concise report showing money, open work, completed work, upcoming lease or booking dates, and pending owner decisions. Trace one amount back to the transaction and one maintenance result back to its evidence. Test property and owner filters, corrections, approval, delivery, and what the owner sees.
Workflow 5: Export and reconstruct the record
Export properties, people, leases, bookings, transactions, work orders, messages, documents, custom fields, and audit records. Open the files without vendor assistance, verify attachments and relationships, and ask what changes after cancellation. The data export checklist defines the deeper portability test.
Force one exception and one denied action
Use the wrong role to attempt a restricted export or approval. Enter a duplicate record, missing required field, failed payment, delayed calendar feed, unavailable vendor, or amount above an approval threshold. Record whether the system blocks, warns, logs, routes, retries, or silently accepts the condition.
Measure the complete commercial requirement
For every demonstrated capability, record the plan, user limit, unit threshold, implementation dependency, integration, usage charge, support requirement, and contract assumption. Connect the quote to the three-year cost method. A feature shown in a demo is not necessarily included in the proposed configuration.
Score evidence and usability separately
Give each workflow 0-2 points for completion, connected context, role control, exception handling, evidence, usability, mobile fit, and export. Weight the highest-volume and highest-consequence work more heavily. Keep blockers outside the average; a failed trust-account, access-isolation, or export requirement should not disappear inside a strong visual score.
Frequently asked questions
Should vendors receive the script before the demo?
Yes. The goal is a fair workflow test, not a surprise. Require the actual proposed product and plan, and preserve unanswered items for written follow-up.
Can a free trial replace the guided demo?
Use both when available. The demo answers configuration questions; the trial reveals whether staff can complete the same work without the presenter.
Research and vendor references
- Buildium: weighted criteria, team trials, cost, support, and onboarding evaluation
- Buildium: workflow-based software acceptance criteria
- AppFolio: onboarding preparation, data, roles, and phased transition
Use the concise question-center version or compare JHA Solutions and Buildium with the same scorecard.