Custom school package
Configured by school size, academic levels, modules, data and deployment.
- Dedicated school deployment
- Onboarding and training
- Selected academic modules
School size, message volume, project scope and provider requirements determine the correct package. Final prices are published or quoted only after approval.
Every option below leads to a focused demo, quotation or technical assessment. No payment is requested through this staging website.
Configured by school size, academic levels, modules, data and deployment.
Configured by message volume, compliance, Sender Name and API needs.
Quoted by pages, content, CMS, integrations, hosting and maintenance.
Quoted after provider, transaction flow, callbacks and reconciliation review.
Need a larger rollout, multi-service engagement or specialised integration? Contact LASET for a custom package.
The following factors are reviewed so the quotation matches the actual work.
Users, schools, branches, academic levels, data volume and access roles.
Modules, pages, messaging volume, integrations and reporting requirements.
Sender Name review, payment-provider requirements, access control and hosting constraints.
Onboarding, training, content preparation, migration, maintenance and response expectations.
A quotation should explain the service, scope, assumptions, responsibilities and next steps clearly.
Ask a Pricing QuestionSchool systems, websites and payment integrations vary significantly by scope. An approved quotation prevents a generic price from hiding important requirements.
No. A demo or enquiry helps define the requirement. Commercial approval happens only after the proposed scope and quotation are reviewed.
Pricing depends on approved traffic, message volume, provider terms, Sender Name requirements and any API or managed-service scope.