Rollout
Live in about
4 weeks
Live in about
4 weeks
ERP projects fail in the migration, not the demo. This is the sequence we run, what we need from you at each point, and the things that will not surprise you later.
The sequence
Four weeks, in order.
- 01
Week one — scoping
We sit with the people who do the work, not only the people who sign. Which modules you switch on, who holds which role, how your fee structure is actually built, and what your certificates and receipts have to look like when printed. Everything after this follows from getting that right.
- 02
Week two — your workspace
Your institution gets its own address, its own branding, and its own database. Your medium of instruction is configured. Students, staff, classes, and fee heads come across from your existing spreadsheets or system — we do the import, you check the totals.
- 03
Week three — parallel run
You run a real fortnight of work in both places at once: attendance marked, fees receipted, a notice issued. Every printed output is put side by side with what you issue today until they match. Staff are trained on the screens they will actually use, by role.
- 04
Week 4 — live
Students and parents get their access, on web and on the mobile apps. The old system is retired rather than left running quietly. We stay close for the first fee cycle and the first exam, because those are where a bad migration shows up.
Your side
What we need from you.
Your current data
Student and staff lists in whatever shape they are in — a spreadsheet is fine, several inconsistent spreadsheets are normal. We clean and map them; you confirm the result before anything is committed.
Your printed formats
One sample of each document you issue: fee receipt, bonafide, leaving certificate, report card, ID card. We match the layout rather than asking your office to accept ours.
One decision-maker per area
Someone who can settle how fees are structured and how attendance is counted. Rollouts slow down over unanswered policy questions far more often than over software.
A fortnight of patience
The parallel run feels like double work because it is. It is also the only reliable way to find the gap between how a process is documented and how it is really done.
No surprises
What does not happen.
No per-module invoice later
The licence covers every module that exists. Switching one on during the rollout because you realise you need it does not produce a new quote.
No implementation partner
The people who configure your workspace are the people who wrote the system. Nothing is passed to a reseller who then asks us questions on your behalf.
Your data stays yours
Every list in the system exports. If you ever leave, you leave with your records in a readable format — not as a bargaining position.
Larger institutions and multi-campus groups take longer, and we say so in the written quote rather than discovering it in week three. Custom software for companies follows a different sequence — the documents your business runs on today are the starting point.
Start with the scoping call
An hour with the people who do the work is enough for us to tell you what your rollout actually looks like.