Why us

From signed contract to go-live in 8 to 12 weeks.

Six-phase methodology, with named owners and acceptance criteria at every step. Not the four-month 'we'll figure it out' you've heard before.

Request a demo
🚀
8–12 weeks typicalNamed owners every phaseAcceptance gates between phasesData import we own
Methodology

Six phases. Six acceptance gates.

Every phase has a written deliverable and a sign-off before the next phase starts. No drift, no scope creep, no 'phase complete in our head'.

Phase 1 · Weeks 1–2

Discovery

Your team and ours sit together (in person or remote) for 8–12 hours of structured conversations. We come out with a written configuration brief and a data-import checklist.

  • Class structure · grading scale · report-card template
  • Modules in scope · modules deferred to Phase 2 onwards
  • Existing data: what we'll import, what we won't
  • Integrations: payment · biometric · GPS · SMS · WhatsApp
  • Acceptance: signed configuration brief
Owned by — Solutions architectSign-off — School principal + IT head
Phase 2 · Weeks 2–4

Data import

We do the data work, not you. You hand us the spreadsheets / database exports / vendor extracts; we import and reconcile.

  • Students · staff · classes · fee structures imported
  • Reconciliation report — what came in, what didn't
  • Edge cases: duplicate students, missing parent contacts
  • Re-import dry run on a test environment before production
  • Acceptance: signed reconciliation report
Owned by — Data engineerSign-off — Accounts head + Academics head
Phase 3 · Weeks 3–6

Configuration

Based on the discovery brief, we configure your account: classes, sessions, fee heads, report-card template, communication channels, integrations.

  • Account-specific masters: schools · sessions · classes
  • Fee structure with discount and concession rules
  • Report-card layout in your template
  • Communication channel selection per event
  • Acceptance: walk-through demo to your team
Owned by — Implementation specialistSign-off — Module-by-module owners on your side
Phase 4 · Weeks 5–8

UAT (User Acceptance Testing)

Your team uses the live account for 2-3 weeks alongside the existing system. We pair on bug triage daily.

  • Parallel run with current system
  • Daily 30-min triage call with our team
  • Documented issue log with status
  • Configuration tweaks based on real usage
  • Acceptance: ≥ 95% of test scenarios pass
Owned by — Your IT headSign-off — School principal
Phase 5 · Weeks 8–10

Training

Role-based training tracks — admin, teacher, accounts, transport, security. Train-the-trainer model: we train your key users, who then train the rest.

  • 4-hour admin track · 2-hour teacher track · 1-hour parent track
  • Recorded sessions + cheat-sheets
  • Train-the-trainer for scale
  • Q&A drop-in sessions weekly for 4 weeks
  • Acceptance: each role has ≥ 1 certified trainer on your side
Owned by — Training leadSee also — /why-us/training
Phase 6 · Weeks 10–12

Go-live + handover

Cutover weekend. Production goes live. CSM handover happens. We stay daily-present for the first month.

  • Cutover scheduled at a low-traffic moment
  • First parent communications go through your live account
  • Daily check-in for the first 4 weeks
  • Weekly check-in for weeks 5–12 post-go-live
  • Acceptance: 30-day stable operation with no Sev-1 incidents
Owned by — Implementation lead → CSM transitionSign-off — Director (your side) + Director (ours)

Want a sample implementation timeline?

We'll share an anonymised plan from an institution similar to yours — student count, board, modules.

Request a demo