Pricing
Pricing starts with scope, not package theatre.
A healthcare platform quote depends on modules, departments, users, locations, migration, integrations, training, and support.
Pricing
Pricing inputs
- Facility footprint
- Module mix
- User roles
- Migration needs
- Support model
Scope
What shapes the quote.
Pricing becomes useful when it is connected to facility complexity.
Facility footprint
Locations, departments, users, service lines, and access roles define the implementation shape.
Module mix
EMR, OPD, IPD, lab, pharmacy, billing, payroll, telemedicine, AI voice, and dashboards can be phased.
Implementation support
Training, migration, integrations, and post-launch tuning shape the delivery plan.
Comparison
Transparent scope vs generic packages.
This keeps the pricing page honest while still helping visitors understand the buying path.
Area
Traditional
With Odoo Afya
Starting point
A generic package grid asks visitors to guess fit.
A discovery call maps facility type, departments, and module needs.
Rollout
Everything is sold as one fixed bundle.
The first release can focus on the highest-value workflows.
Support
Support assumptions are hidden.
Training, migration, and support are visible in scope.
FAQ
Pricing questions
Starter FAQs for the pricing page.
Why are there no public prices?
The right quote depends on module mix, user roles, facility complexity, implementation support, and integrations.
Can we start with a few modules?
Yes. The implementation can begin with the most urgent workflows and expand later.
Do hospitals and clinics cost the same?
Usually no. Departments, users, reporting, and workflows affect the implementation scope.
Can support and training be included?
Yes. Support, training, and migration needs should be visible in the scope.
How do we get a quote?
Book a pricing call and bring facility context: departments, users, current tools, and first-release priorities.