Implementation that proves itself before you commit.
KinetiPlan is introduced through a scoped pilot with a parallel run on your de-identified data, so every result is checked against your current system before anything changes.
A typical first engagement
Week 0: discovery
Your plan mix, current systems, data exports and the workflow to prove first. Output: written pilot scope and acceptance criteria.
Weeks 1 to 2: environment
Customer-hosted environment provisioned (your AWS account or servers), access process agreed, synthetic smoke test.
Weeks 2 to 4: data mapping
De-identified census, payroll and balance exports mapped; validation rules tuned to your plans.
Weeks 4 to 8: parallel run
The same plans processed in KinetiPlan and your current system; differences explained line by line.
Week 8+: decision
Review against the acceptance criteria. Expand, adjust or stop.
Indicative timeline for a 3 to 5 plan pilot. Actual timing depends on data readiness and scope, and is agreed in writing.
Who does what
| Activity | Your team | Software Home |
|---|---|---|
| Scope and acceptance criteria | Owner, operations lead | Product lead |
| Environment | IT: account, network, identity | Install, configure, document |
| Data exports | Plan administrators | Mapping and validation rules |
| Parallel run review | Plan administrators, compliance | Explain every difference, fix defects |
| Sign-off | Owner | Release notes and evidence pack |
- De-identified census and payroll files for 3 to 5 plans with different designs.
- Your current test results for the same plans and year, to compare.
- A named operations lead with a few hours a week.
- An IT contact for the environment and identity provider.
Talk through an implementation plan.
Choose the conversation that fits where you are. Calls run on Google Meet. Nothing on this website asks for participant data.