ENTERPRISE PILOT · 6–12 MONTH EXAMPLES

One workflow. Clear milestones. Measurable value.

Choose an example timeline. Open a milestone for its scope and acceptance criteria.

Choose your example

Illustrative startMonth 1

Examples start next month. Your actual kickoff and scope are agreed together.

Prove one process, then decide.

One organization, one credential workflow and a limited pilot group.

First cost-reduction windowMonth 4

After release approval, as digital use replaces eligible card and manual tasks.

Scale decisionMonth 6

Review measured benefit, adoption and total costs before committing further.

  1. 01
    Month 1

    Agree the problem and baseline

    Scope and acceptance criteria

    Map your current process, card events and handling time. Agree users, data access, success metrics and the full pilot budget.

    Milestone: a scoped plan and an agreed cost baseline.

  2. 02
    Month 2–3

    Integrate and test

    Scope and acceptance criteria

    Connect the agreed data source. Test issuance, changes, revocation and verification with your team, including device support and offline status rules.

    Decision gate: approve real-user operation only when acceptance and security criteria are met.

  3. 03
    Month 4–5

    Go live and measure avoided work

    Scope and acceptance criteria

    Introduce the approved workflow to the pilot group. Track actual use, avoided card events and handling time against the baseline. Count only work that is truly replaced.

    Value milestone: first measured cost reductions can begin here, subject to adoption and replacement of the old process.

  4. 04
    Month 6

    Evaluate and agree the next step

    Scope and acceptance criteria

    Review usage, reliability and net operating savings. Compare the full investment with the business case, then decide whether to renew, expand, adjust or stop.

    Milestone: an evidence-based rollout decision and a costed next phase.

Validate first. Expand in stages.

Validate one workflow, then expand across teams in stages.

First cost-reduction windowMonth 7

After release approval, as digital use replaces eligible card and manual tasks.

Scale decisionMonth 12

Review measured benefit, adoption and total costs before committing further.

  1. 01
    Month 1–2

    Agree the problem and baseline

    Scope and acceptance criteria

    Map your current process, card events and handling time. Agree users, data access, success metrics and the full pilot budget.

    Milestone: a scoped plan and an agreed cost baseline.

  2. 02
    Month 3–5

    Integrate and test

    Scope and acceptance criteria

    Connect the agreed data source. Test issuance, changes, revocation and verification with your team, including device support and offline status rules.

    Decision gate: approve real-user operation only when acceptance and security criteria are met.

  3. 03
    Month 6

    Validate readiness with your team

    Scope and acceptance criteria

    Run acceptance tests, train the operating team and confirm support, trust and status-refresh procedures before introducing the workflow to users.

    Decision gate: proceed, adjust the scope or pause before live operation.

  4. 04
    Month 7–9

    Go live and measure avoided work

    Scope and acceptance criteria

    Introduce the approved workflow to the pilot group. Track actual use, avoided card events and handling time against the baseline. Count only work that is truly replaced.

    Value milestone: first measured cost reductions can begin here, subject to adoption and replacement of the old process.

  5. 05
    Month 10–12

    Expand where the numbers work

    Scope and acceptance criteria

    Review pilot results before each additional team or site. Measure adoption and total operating costs as volume grows, then agree the next contract and rollout scope.

    Milestone: validated expansion economics and an agreed continuation plan.

When do your costs start to fall?

Savings can start after approved go-live, when digital use replaces existing tasks. Released time creates capacity; cash savings require costs you can actually remove.

Track net benefit

Subtract SaaS, usage and additional operating costs from avoided costs. Include parallel operation.

Check full payback separately

Recover the full pilot and setup investment through cumulative net savings. Go-live alone does not establish payback.

Estimate your savings →

Build your plan with us.

Agree scope, milestones and a separate pilot quote for your workflow.

Request a pilot offer →

Illustrative schedules, not a delivery or savings guarantee. Scope, procurement, data access and acceptance determine the actual timeline.