ONBOARDING
Go live without turning implementation into a second job.
Most software transitions take months because the implementation becomes its own project. We are after a live system your district uses with confidence — not a binder.
WHAT WE NEED FROM YOU
Five things. That is the whole list.
We are not going to ask your team to document their entire process before we start. We need enough to stand the system up, and we get the rest as we go.
Your prior-year balances come across too. Years of history in an old platform or a filing cabinet is usually what stalls the decision to switch.
THE IMPLEMENTATION PACKET
Your school list
Funds and activities
Who does what - user roles
Opening Balances
A training window that suits your calendar
KICKOFF TO LAUNCH
Structured, but not overbuilt.
01
Kickoff
We walk your current process, confirm what good looks like for your district, and agree the rollout order.
Your time: one meeting
02
We import
Schools, funds, users and balances go in. You send files. We do the mapping.
Your time: send the files
03
Train by role
Advisors learn to submit. Approvers learn to approve. Nobody sits through a feature tour of a screen they will never open.
Your time: one hour per role
04
Go live
Real requests start flowing, with us on hand while people settle into it.
Your time: normal work
WHY IT DOES NOT DRAG ON
Training should be short enough that people actually absorb it.
Role-based, not feature-based
People learn the four things their job requires, not every administrative screen in the system.
Setup covers what you operate
Schools, funds, balances, users, approvals. We are not designing a perfect chart of accounts before you can use anything.
Built to be picked up
If a coach needs a manual to submit a request, that is our design failure, not their training gap.