Getting Started

This guide covers what to expect between requesting a demo and your first service going live on iCura.

1. Discovery and scoping

Every deployment starts with a conversation about which products you need first. Most providers don't start with all eight — a common starting point is iCura Core for care planning, paired with either WorkOps for rostering or 360 for compliance, depending on which is causing the most immediate pain.

During this stage, our team maps your current systems (care records, rostering, compliance tracking) to confirm what needs to migrate and what can run in parallel during transition.

2. Configuration

iCura is configured, not custom-built, for your organisation. This typically covers:

Setting up services, sites and reporting structures to match your organisation.
Configuring roles and permissions so each user sees exactly what their role requires.
Migrating or importing existing care records, where applicable.
Setting up the Composable Workflow Engine for any forms or approval chains specific to how you operate.

3. Pilot on one service

Rather than switching every site over simultaneously, we recommend piloting on a single service first. This surfaces any configuration adjustments needed before a wider rollout, without disrupting care delivery across the organisation.

4. Group-wide rollout

Once the pilot service is running smoothly, remaining sites are onboarded in planned phases. Throughout rollout, Operational Intelligence dashboards give you a live view of adoption and usage across sites as they come online.

5. Ongoing support

After go-live, your team has direct access to ours — not just a support ticket queue. For technical integration questions, see API & Integrations. For configuration questions, see Platform Overview.