Start with one decision. Build from there.

Build your internal business case

Give your sponsor, delivery team and procurement reviewer a shared starting point.

Examples use fictional data. Effort targets are assumptions to test; confirm scope, pricing and terms in a proposal.

Choose the decision

Start with one recurring question: whether a schedule update is credible, what changed across the portfolio, or which submission needs attention. Name the people who prepare, review and act on that information.

Agree the boundaries

Use demonstration data first. Before sharing project material, agree the project scope, authorized participants, permitted data, handling arrangements and evaluation terms. Identify the baseline, reporting period and source of each record.

Work through one cycle

Bring a representative input through the selected workflow. Compare the result with the team’s existing review or reporting process. Record gaps, configuration needs and questions while the people doing the work are present.

Review the evidence together

Assess the agreed criteria: preparation effort, clarity of findings, traceability and ease of follow-up. Decide whether to expand, adjust the scope or finish the evaluation. Rollout and support arrangements are agreed separately.

Bring the essentials

One project or a small, representative portfolio. A baseline and update, or an example reporting package. The reviewer, project lead and intended decision maker. Your current review checklist and reporting expectations. Data restrictions and any IT or procurement requirements.

Focused evaluation

Agree a bounded workflow, demonstration or permitted project data, success criteria and a review point. Scope and responsibilities are confirmed before the evaluation begins.

Software engagement

Discuss the projects, user roles, reporting needs and operating support required for ongoing use. The quote sets out access, onboarding, support and any agreed configuration.

Advisory engagement

Scope scheduling, review, risk or project-controls support around a defined deliverable and team responsibility. Advisory work is scoped explicitly, including any software used in the engagement.

Do we need to replace our scheduling process?

Begin with a representative file and your existing review process. The evaluation should establish how Kairos fits the work, what information transfers, and any changes your team would need to make.

How long does implementation take?

Timing depends on the selected workflow, data quality, access requirements and organizational review. We agree the sequence and responsibilities after understanding that scope.

Can we start without uploading confidential data?

Yes. A product walkthrough can use demonstration data. Project information should be shared only after the appropriate data arrangements and permissions are agreed.

How is pricing determined?

Bring your project and user scope, desired workflows, support expectations and advisory requirements. We use those inputs to prepare a scoped proposal. Commercial terms and any evaluation charges are agreed in writing.