School and user scope
The school workspace, user roles, expected usage and any agreed multi-campus requirements.
PRICING APPROACH
Clear scope before
commercial commitment.
DASHIFY is in development, so public subscription prices have not been set. We intend to understand each school’s requirements and agree what is included before discussing commercial terms.
Illustrative product concept · DASHIFY by BRIZNOVA01WHY NO PRICE TABLE YET
No surprise promises.
Price should follow
a clear scope.
School size, users, modules, data migration needs, support expectations and integrations can all affect the effort involved in an implementation.
Publishing a premature price would create the wrong expectation. We will validate workflows, define the pilot scope and confirm service responsibilities first. Any commercial proposal will be shared in writing for review.
02WHAT A FUTURE PROPOSAL MAY COVER
Understand what
you are paying for.
When commercial plans are ready, proposals should make service boundaries and support clear.
Included modules
The exact modules, workflows and limits included in the agreed subscription or pilot.
Setup and migration
Any configuration, training, data preparation or migration activities, listed separately.
Support arrangements
Support channels, operating hours, response expectations and escalation process.
Optional integrations
Payment, messaging, biometric or third-party integrations and related provider charges.
Renewal and exit terms
Billing cycle, renewal, data export, retention and termination arrangements.
LET'S EXPLORE THE FIT
Request a discussion ↗Tell us what your school needs.
We can begin with a no-obligation discovery conversation and determine whether the proposed pilot scope is relevant.