Starter
One inbox, no minimum. For teams answering a few hundred messages a week.
$0.65
per resolved conversation
- One inbox
- Help centre sync
- Weekly gap report
- Month to month, cancel any time
SIMBA platform
SIMBA is not a one-price SaaS template. We size the engagement around the member journey, partner network, service flow and governance needs of the operating model.
One inbox, no minimum. For teams answering a few hundred messages a week.
$0.65
per resolved conversation
MOST TEAMS
From 2,000 resolved a month. Everything the agent can do, with a person always one click away.
$0.55
per resolved conversation
From 20,000 resolved a month, with the paperwork your security team will ask for.
Custom
talk to us
Commercial model
What it includes
Pilot
Scale
Ecosystem
Access and onboarding
Member registration and identity flow
Eligibility and verification checks
Referral and routing logic
Custom
Service discovery and API integration
Custom
Operational coordination
Stakeholder mapping and operating model
Payment and data exchange support
Custom
Workflow and audit tracking
AI-assisted service support
Custom
Delivery and governance
Discovery and design workshops
Implementation support
Governance and operating rules
Custom
Longer-term ecosystem partnership rollout
Pilot: Custom scope
Commercial structure
Pricing basis
Project-based
Service and usage-based
Strategic partnership model
Contract type
Pilot engagement
Extension agreement
Ecosystem partnership agreement
Support model
Dedicated onboarding
Shared program support
Named platform lead
The final commercial structure depends on stakeholder count, service complexity, data exchange needs and the scale of the rollout.
FAQ
We can map the right scope for your stakeholders, integration needs and rollout plan.
No. SIMBA is priced around the stakeholder ecosystem, operating model, service depth, integration needs and governance structure of each deployment.
Yes. In many cases the first stage is a pilot to validate onboarding, service flow, verification rules and stakeholder coordination before broader rollout.
The main changes are in ecosystem scope, partner integration, data exchange, governance and operational support. The architecture remains the same, but the rollout becomes more complex and deeply integrated.
Yes. SIMBA is designed to support connected service models that span healthcare, payments, identity, funders and community access pathways.
Yes. Discovery is usually the first step and covers stakeholder mapping, service flow analysis, verification checks and the implementation pathway for the network.
Yes. The operating model is built to coordinate multiple institutions and stakeholder groups without losing trust, accountability or service clarity.
A digital platform for registration, identity verification, service discovery, referrals, payments and secure data exchange.
Request a demo