Cathund Digital uses institution-centred commercial models. Pricing can reflect the software selected, institutional size, deployment requirements, configuration, support and future integrations.
These packages describe service levels rather than fixed public prices. A formal quotation can be prepared after the institution’s requirements are confirmed.
For institutions beginning with a focused academic workflow or controlled deployment.
For institutions requiring broader adoption, multiple academic structures and stronger administrative controls.
For larger or more complex institutions requiring wider deployment, integrations or tailored implementation.
Instead of forcing every institution into the same package, the commercial scope can be shaped by practical deployment requirements.
CAPMS now, or additional Cathund Digital products as the software ecosystem expands.
The size and complexity of the institution, programmes and intended deployment.
Institution-specific structures, branding, permissions and academic workflow requirements.
Deployment assistance, onboarding, migration requirements and administrator preparation.
The operational support and service level required after implementation.
Future payment, identity, learning, communication or other institutional integrations where required.
The commercial architecture is being designed to remain flexible as Cathund Digital adds more software and serves different types of institutions.
A structured licence can support institution-wide use based on the agreed deployment scope.
Recurring commercial arrangements can support continued platform access, services and future product models.
Implementation requirements can be quoted according to institutional structure and the level of customisation required.
Institutions can begin with a focused deployment and expand as programmes, users or software requirements grow.
We recommend discussing requirements before a commercial proposal is issued.
Institutions differ significantly in size, structure, configuration, implementation and support needs. A requirements-based quotation prevents an institution from paying for an unsuitable package.
Yes. CAPMS can be deployed as a focused solution while Cathund Digital’s wider software ecosystem continues to expand.
Yes. The platform strategy is designed for growth, allowing additional institutional structures, users and future software capabilities to be considered as needs evolve.
Yes. Institution-centred configuration and branding are part of the deployment approach, with the exact scope agreed during requirements review.
Request a demonstration or contact Cathund Digital. After the requirements are understood, a commercial proposal can be prepared for the agreed scope.
Not necessarily. Each software product may have its own commercial model, while bundled or institution-wide arrangements may also be considered as the portfolio grows.
Tell us about your institution, the academic workflow you want to improve and the software you are interested in. We can then discuss the most appropriate deployment approach.
