You have a school ERP to offer and a meeting with a school. It is tempting to show every module so the customer can see how much the software does.
But the person across the table may have one immediate problem: fee balances are hard to check, attendance takes too long, or parents keep calling the office for information.
A useful demo starts there. Show how the software could fit the school's working day, then agree what needs to happen next.
Ask a few questions before the meeting
Speak to the person who arranged the demo. Find out who will attend and what they want to review. A principal, accountant, and teacher may each have a different priority.
These questions are a good starting point:
- Which task is causing the most trouble today?
- How do staff handle it now?
- Who will use the software every day?
- Which report or document do they need to see?
- Who needs to approve a purchase and a rollout?
Use the answers to choose two or three workflows. If the school asks about something unfamiliar, note it for review rather than promising a feature you have not checked.
Prepare sample data that makes sense
Use fictional students, classes, fee entries, and staff accounts. Keep the example small enough that everyone can follow it. Do not use another school's live records to make your demo look realistic.
Check the accounts and permissions before the meeting. Open the screens you will need and make sure the selected edition supports the workflow you plan to show.
If you are evaluating InstiKit for your business, book a guided demonstration and share your intended reseller or partner use case beforehand.
Show a complete task
Suppose the school says its office struggles to answer questions about outstanding fees. You could demonstrate a simple sequence:
- Open a sample student's fee details.
- Review the applicable charges and existing payments.
- Record a sample payment using a supported method.
- Check the updated balance and receipt.
- Show the relevant staff report or parent view, if included.
Pause between steps. Ask whether the example matches how the school works. If they use different fee rules, write those down and check the configuration later.
The goal is to let them judge one useful task, not to rush through a row of menus.
Let the future user try it
After your walkthrough, ask the accountant or teacher to repeat part of the task in the demo environment. Watch where they need help.
Perhaps they cannot find the class selector or do not understand a label. That tells you what training or configuration to plan. It also gives the school a more honest view of the learning involved.
You can explore other InstiKit features after you have covered the school's main concern. Keep a separate follow-up list for requirements that need technical confirmation.
Explain what your company will deliver
Schools need to understand your role as well as the product. Explain who will prepare the data, configure the account, train staff, and handle support.
Be clear about the package you are quoting. Mobile apps, messaging services, payment integrations, customization, and extra training may have separate terms or costs. Check availability and scope before adding them to the proposal.
Confirm your own resale and service rights with the vendor too. The reseller edition page is the appropriate starting point for those discussions with InstiKit.
Finish with a small, clear next step
A next step could be a technical review, a written proposal, or a limited pilot. Agree who will do what and when you will speak again.
For a pilot, list the users and workflows to test. Choose observable checks, such as staff being able to mark attendance or the accountant confirming a sample balance. Avoid promising a fixed improvement before you have a baseline.
Send a short recap after the meeting. Include the problem discussed, the workflows shown, open questions, and the proposed next step.
Build confidence one conversation at a time
Your first client does not need to see every possibility in one meeting. They need enough information to decide whether your offer fits their school and whether your team can deliver it.
Still comparing platforms? The white-label ERP selection guide covers the checks to make before you build your offer.
If you are still preparing your offering, discuss an InstiKit partnership. Share your target schools and the kind of implementation and support service you plan to provide.