A property demo checklist helps Kenyan landlords evaluate rental software using real working questions. Instead of judging a system only by its dashboard, ask the presenter to walk through a small, anonymised property example. You can then compare the workflow with the way your team manages units, invoices, payments and owner reporting.
1. Build the property demo checklist around a sample
Prepare an imaginary property with a few units, one vacancy and different payment situations. Avoid sending real tenant identity documents or a full live ledger merely to see a demonstration. A realistic fictional example can test the process without exposing private information.
List the questions that currently consume staff time. Perhaps the team struggles to identify unmatched payments, explain a balance or prepare a statement. Give each question a specific test so that the demonstration produces useful answers.
2. Follow an invoice through to its payment record
Ask how an invoice is created, how a payment is matched and how the resulting balance appears. Include a partial payment and an item that cannot immediately be matched. Ask what requires staff review rather than assuming every payment is allocated automatically.
Use the tenant balances guide to prepare your questions. Confirm the payment channels, configuration and plan requirements that apply to your intended setup.
3. Ask how corrections remain understandable
A useful demonstration should show what happens when an entry needs correction. Ask which roles can make a change, what record remains and how the correction appears in later reports. Confirm the controls actually available in the plan you are considering.
Do not judge a workflow only when every sample entry is perfect. Property teams need a clear way to investigate uncertain items and correct mistakes without creating contradictory records. Make these cases part of the property demo checklist.
4. Review a report that answers an owner’s question
Ask the presenter to produce an example report and explain the period, included transactions and outstanding balances. Check whether a staff member can trace a figure back to its supporting record. A polished layout is useful only if the numbers can be explained.
Read the month-end statement checklist and compare the demonstration with your reporting needs. Ask about exports and limitations before committing to a workflow.
5. Confirm setup responsibilities and ongoing costs
Review the current RentalDesk pricing and ask which services are included, which require configuration and which involve separate charges. Confirm who prepares the initial property data and who checks the opening records.
The software setup guide helps organise this discussion. A successful demonstration should leave you with a practical next step, not just a list of features.
Compare different business tools on their actual purpose
A property business may also use websites such as Zama for business software research or Saseni for a separate writing-service workflow. Evaluate those needs independently and ask for explicit evidence before assuming any connection between platforms.
Do not upload tenant data into an unrelated service simply because both tools are used by the same business. Clarify what information is required, where it will be stored and who can access it.
Turn the demonstration into a decision record
For each test, note whether the workflow was demonstrated, whether further configuration is needed and whether an answer remains outstanding. Record the relevant plan and date so that the team knows which proposal was reviewed.
A property demo checklist does not need a complex scorecard. Five meaningful tests, clear answers and a short list of unresolved questions can be enough to decide whether to continue. Ask for clarification on material gaps before importing live records.
Property demo checklist worksheet
Prepare the property demo checklist before the meeting so that the presenter understands the questions you need answered. List the current operational problems, the tasks you want to see and the people who will assess the results. A landlord, accounts employee and property manager may each notice different details in the same workflow.
Use a small fictional property with clearly named units and an imaginary owner. Include ordinary cases and a few exceptions, such as a partial payment or a vacant unit. This creates a realistic discussion without sending private tenant records merely to explore whether the software suits your needs.
Define what a successful demonstration means
A successful property demo checklist does not require every feature to look impressive. It requires clear answers about the workflows that matter to your team. For each test, decide what you need to understand: the input, the staff action, the resulting record and the report that follows.
Mark each outcome as demonstrated, requires configuration or awaiting clarification. Avoid treating a verbal statement about a future capability as the same thing as a feature shown in the current product. Ask which plan and setup conditions apply so that the decision record reflects the proposal actually being considered.
Property demo checklist test: a normal rent payment
Ask the presenter to begin with the sample unit and its invoice. Follow the payment through the supported workflow and inspect the resulting balance. Confirm which information identifies the correct tenancy and which steps require staff action. The aim is to understand the record from beginning to end.
The property demo checklist should capture how the payment source is represented and how the team can trace the allocation later. Ask what happens when the reference is incomplete or does not match a known record. Do not assume that every incoming transaction can be allocated automatically without review.
Finish by opening the relevant report and checking how the example appears. A successful entry screen is only part of the process. The accounts team needs to understand how the transaction affects later reporting and what evidence remains available when a tenant or owner asks a question.
Property demo checklist test: a partial payment
Use a fictional example in which the payment is less than the invoice amount. Ask the presenter to show the remaining balance and explain how the record distinguishes the amount invoiced from the amount received. Avoid introducing late charges or other adjustments unless their approved treatment is part of the specific test.
The property demo checklist should ask how staff identify the remaining amount and how it appears in the tenant-facing or internal view. If reminders are available, confirm the current configuration and approval process rather than assuming they will behave exactly as your team expects by default.
Then show a later payment for the same sample tenancy and follow the allocation. Ask how staff can review the sequence without creating duplicate entries. This demonstrates whether the team can explain the history, not merely whether the final balance happens to look correct.
Property demo checklist test: an unmatched item
Prepare a payment example that lacks enough information for immediate allocation. Ask where it appears, who can investigate it and how the team records the result. An uncertain item should remain distinguishable from a confirmed payment assigned to a tenancy.
The property demo checklist should include the decision boundary: what evidence is needed before the item is matched, and what happens if the evidence remains incomplete? Confirm the actual workflow in the current plan. Do not treat an unmatched queue as proof that the system has independently resolved the underlying question.
Ask the presenter to complete an authorised match using the sample information and then show the resulting history. The team should be able to understand who took the action and how the record can be reviewed. If a capability is not available, record that limitation and discuss how the organisation would handle it operationally.
Property demo checklist test: a correction
Use a fictional entry that needs correction and ask the presenter to show the supported process. Clarify which role can perform the action and which evidence or explanation can be retained. The goal is to understand how mistakes are handled without leaving contradictory records.
A property demo checklist should distinguish a routine edit from an adjustment that changes financial reporting. Ask how the correction affects the relevant invoice, balance and report. Confirm any limitations rather than assuming that all views update in the same way under every circumstance.
Ask the receiving staff member to explain the result
After the demonstration, ask a colleague who would normally use the system to describe what happened. If they cannot tell which figure was changed or why, the team may need more explanation or training. A workflow can be technically available while still being unclear to the people responsible for daily use.
Record that training need in the property demo checklist. Do not label it as a software failure automatically, but do not ignore it either. Implementation planning should reflect both the product’s capabilities and the team’s ability to use the agreed process consistently.
Property demo checklist test: owner reporting
Ask for a sample report covering a defined period. Identify the transactions included, the outstanding balances and any adjustments used in the example. The report should answer a clear question, such as what happened during the period, rather than simply display a collection of attractive totals.
Use the property demo checklist to trace at least one figure back to its supporting record. Ask how a staff member would investigate an owner’s query. If exports are important, confirm the available formats and what information they contain in the current plan.
Check reporting boundaries
Clarify whether a report is organised by property, owner, tenancy or another grouping. A portfolio with several owners may need different views from a landlord managing one building. Do not assume a report shown for a simple sample will automatically cover every relationship in your actual portfolio.
Record any configuration needed to produce the intended view. The property demo checklist should show whether the requirement was demonstrated directly or whether further setup is needed. This helps prevent a promising demonstration from becoming an unclear implementation commitment.
Questions about roles and access
Ask which users can view, create, edit and approve the relevant records. Use practical roles from your team, such as caretaker, accounts employee and manager. Confirm the permissions available in the plan being discussed rather than assuming that a role name enforces every control you need.
The property demo checklist should identify any operational approval that remains outside the software. If the system cannot enforce a particular rule, decide how the organisation will manage it and whether that approach is acceptable. A clear limitation is more useful than an assumed control that staff later discover does not exist.
Review staff changes
Ask how responsibility is transferred when an employee changes roles or leaves. Confirm the normal process for managing access with the provider and your own administrator. The demonstration should explain the workflow without requiring the use of real employee credentials or live tenant data.
Include the handover of open tasks in the property demo checklist. A new staff member needs to know what remains unresolved, not only how to sign in. Check whether the relevant operational records can be understood without a private conversation with the previous employee.
Setup and data preparation
Ask what information must be prepared before the system can be used. Clarify the format for properties, units, tenancies and opening records. Identify who prepares the source, who checks it and who confirms that the imported result is correct.
A property demo checklist should include a small import or setup example where appropriate. Ask how rejected or incomplete records are handled and how duplicates are avoided. A message saying that an upload succeeded does not establish that every row was associated with the intended unit.
Agree the opening record review
Before going live, the organisation needs a process for checking the starting information. Use the demonstration to understand how staff can compare a sample of records with the approved source. Keep uncertain items visible rather than filling gaps with guesses to finish the setup quickly.
Record the expected responsibilities in the property demo checklist. If the provider offers setup assistance, confirm the scope and any separate charge. If the team must clean its own data, include that work in the implementation plan instead of assuming the software purchase resolves it automatically.
Costs and support questions
Review the current pricing with the provider and identify the plan used in the demonstration. Ask about included features, configuration needs, training and support arrangements. Separate the software subscription from any additional service that has its own scope or cost.
The property demo checklist should record unanswered commercial questions without inventing an estimate. Obtain the relevant written proposal before deciding. A feature demonstrated under one plan should not be assumed to exist under a different plan simply because both use the same product name.
Ask how support requests are handled
Find out which contact method the team should use and what information makes a report useful. Ask how to describe an issue without sending unnecessary private data. A support process should be understandable to the staff who will actually use it, including those who were not present at the demonstration.
Include training questions in the property demo checklist where a workflow is unfamiliar. Confirm whether guidance is available for the specific tasks your team performs. Do not assume that a general product tour replaces the practical preparation needed for everyday use.
Decision worksheet after the demonstration
- List each tested workflow and its observed result.
- Identify the plan and configuration used.
- Record requirements that were not demonstrated.
- Assign an owner to each outstanding question.
- Note the data preparation and training work needed.
- Confirm the current pricing and service proposal.
- Decide what must be resolved before live records are introduced.
Review this worksheet with the people who will own the process. A property demo checklist supports a decision; it should not become a substitute for one. If a material requirement remains unclear, ask for a focused follow-up demonstration rather than relying on a broad assurance that everything can be handled.
Frequently asked questions about a property demo checklist
Do we need to share live tenant information?
A fictional or anonymised example is usually a useful starting point for evaluating workflows. If more detailed information is later needed for implementation, establish the authorised purpose and handling arrangements first. Do not send a complete live ledger merely because the demonstration invitation asks for examples.
Should every available feature be tested?
Prioritise the tasks that matter to your operation. A focused property demo checklist can produce clearer answers than a long tour of features the team may never use. Add specialised tests where they affect your decision, and record them as specific requirements.
What if a workflow needs configuration?
Ask what must be configured, who will do it and how the result will be checked. Record any cost or dependency in the written proposal. A configuration requirement may be manageable, but it should not disappear from the decision record simply because the core feature was shown.
Turn the property demo checklist into an implementation plan
After choosing the next step, carry the unresolved questions, data preparation and training tasks into a practical plan. Give each item an owner and a review date. Keep the tested examples available so that the team can confirm the intended workflow after setup.
A well-used property demo checklist helps RentalDesk discussions stay focused on real work: accurate records, understandable balances and reports the team can explain. It gives the business a clear account of what was demonstrated and what still needs attention before the system becomes part of daily operations.
Talk to RentalDesk
Discuss your requirements and the next practical step. Call 0725345345 or message us on WhatsApp.