Pricing and scope
Pricing shaped by facility scope
Proposals separate platform, hardware, setup, and support costs. The final scope depends on layout, site requirements, device mix, rollout, support, and optional capabilities.
Facility scenarios
Start with the shape of the evaluation
These non-priced scenarios help a buyer identify a likely starting point before a facility assessment and written proposal.
Scenario 01
Small validation area
One wing or limited assessment area.
A potential scope can include workflow mapping, device placement, staff training, and review against the facility's current process.
Scenario 02
Single-site facility
A full senior-care home with defined rooms, wings, roles, and escalation paths.
A potential scope can include coverage planning, installation, training, support, and a facility-specific proposal.
Scenario 03
Complex facility
Multi-building sites, an optional voice bridge, integrations, or expanded reporting.
Requires deeper IT planning, rollout sequencing, support ownership, and validation scope review.
Quote factors
What changes the proposal
Pricing follows the operational scope: where alerts travel, what the site requires, how devices are placed, who needs training, and which optional capabilities are approved.
Facility size
Number of rooms, wings, buildings, and coverage zones.
Device mix
Wearables, wall devices, staff devices, gateways, and badges.
Rollout scope
Assessment area, phased rollout, onboarding, and setup.
Optional capabilities
Optional voice bridge, integrations, and expanded reporting needs.
Potential scope
What a proposal can include
The written proposal identifies which capabilities, services, and responsibilities are actually in scope.
Configured alert routing and staged escalation
Incident documentation support
Smart device monitoring
Health-sector-grade safeguards
Staff badge verification
Natural language queries
Dedicated hands-on support
Staff training included
Regular system updates
Local-operation design reviewed by configuration
Proposal path
What happens before a quote
A proposal follows facility context, not a generic package selector.
01
Facility assessment
Review room count, buildings, coverage areas, staff roles, current process, and IT constraints.
02
Scope and options
Define device mix, setup support, training needs, optional voice bridge, and reporting requirements.
03
Written proposal
Separate platform, hardware, setup, and support costs so the facility can evaluate the full commitment.
04
Validation plan
Where appropriate, define a limited validation that runs in parallel with the current process.
No per-seat alert licensing
OshriKa does not charge each staff member to receive alerts. Staffing changes do not turn every roster update into a licensing conversation.
Clear quote factors
Quotes are based on coverage area, device count, setup support, and optional capabilities.
Documentation starts from the record
Report drafts use alert timelines so staff review a recorded workflow instead of reconstructing events from scattered notes.
No per-seat alert licensing
Facility proposals separate platform, hardware, setup, and support costs so procurement can review the full commitment.