Customer journey
Follow one coherent operating journey through planning, delivery, MEAL, reporting and management intelligence.
Step 01
Establish the organization, project and accountable delivery model before data collection begins. Country and sub-national geography are configured per programme—new countries are added as your programme needs them, not pre-loaded for every country in advance.
Learn this in the Learning Centre →Step 02
Connect goals, outcomes, outputs and indicators so teams share one definition of success.
Learn this in the Learning Centre →Step 03
Translate expected results into activities, owners, dates and delivery progress.
Learn this in the Learning Centre →Step 04
Keep planned and actual resources linked to the project and the work they enable.
Step 05
Keep Direct Implementation distinct from each Implementing Partner while enabling authorized consolidation.
Learn this in the Learning Centre →Step 06
Use Native Forms and supported data sources to capture records in the right project and implementation context.
Learn this in the Learning Centre →Step 07
Apply Data Quality checks, evidence, review and authorization boundaries before a number becomes an institutional claim.
Learn this in the Learning Centre →Step 08
Compare targets and actuals, preserve disaggregation and make insufficient data visible instead of fabricating certainty.
Learn this in the Learning Centre →Step 09
Dashboards bring delivery, results and management attention into a role-aware view.
Learn this in the Learning Centre →Step 10
Build reports that retain the project, period, reviewer and evidence behind the result.
Learn this in the Learning Centre →Step 11
Deterministic Intelligence identifies performance, delivery and financial signals; provider-backed responses require approved configuration, and authorized people remain accountable.
Evidence boundary
Accepted platform foundation.
Distinct governed implementation models.
Core governance remains part of the platform.
Accepted Integration Hub connectors.
Token-authenticated outbound feed, plus a bidirectional connector for any external system reachable over HTTPS.
Accepted connector; customer credentials and provider configuration are required.
Accepted connector; customer credentials and provider configuration are required.
Accepted connector; customer credentials and provider configuration are required.
Country packages and core browser flows are proven; live PostgreSQL and remaining boundary/multi-actor evidence stay pending.
Fifteen starter packs, including the importer, preview and version governance behind creating a new project from one.
Performance, delivery, financial and evidence-aware decision surfaces are implemented; live AI-provider behavior depends on approved configuration.
