Scoped proposals; terms agreed in writing.
Ways to work together
Focused evaluation
A team assessing one recurring decision or review workflow.
- A written evaluation question
- Agreed inputs and success criteria
- A joint review of the result
Scope and responsibilities are confirmed before the evaluation begins.
Software engagement
A team planning ongoing use across an agreed project and user scope.
- Defined access and workflows
- An agreed onboarding sequence
- Documented support arrangements
The quote sets out access, onboarding, support and any agreed configuration.
Advisory engagement
A team that needs practitioner support for a defined piece of work.
- A defined professional deliverable
- Named responsibilities and inputs
- An agreed review and acceptance process
Advisory work is scoped explicitly, including any software used in the engagement.
What the scope should settle
Starting point
- Focused evaluation
- One question and a representative workflow
- Software engagement
- Recurring workflows, projects and user roles
- Advisory engagement
- A specific deliverable or controls need
Data and access
- Focused evaluation
- Demonstration data or permitted project material
- Software engagement
- Access and handling requirements agreed before rollout
- Advisory engagement
- Inputs and working access defined in the scope
Onboarding and support
- Focused evaluation
- The people and assistance needed for the evaluation
- Software engagement
- Onboarding, configuration and support described in the quote
- Advisory engagement
- Practitioner responsibilities and review points stated explicitly
Software and advisory
- Focused evaluation
- The tools and practitioner involvement agreed for the first cycle
- Software engagement
- Any advisory services scoped separately and explicitly
- Advisory engagement
- Any software use stated in the advisory engagement
Commercial agreement
- Focused evaluation
- Charges, duration and evaluation boundaries in writing
- Software engagement
- Access scope, charges, term and renewal arrangements in writing
- Advisory engagement
- Deliverables, charges, assumptions and acceptance in writing
Bring the context. Define the fit.
The work
Projects, portfolios, recurring reviews and the decisions you need to support.
The people
User roles, reviewers, decision makers and external collaborators who need access.
The information
Schedule formats, document needs, data restrictions and any requested connections.
The support
Onboarding, configuration, training and any practitioner involvement you want included.
Before you decide
Why is there no fixed price on this page?
Project scope, user roles, workflows and support needs vary. Kairos prepares a scoped proposal so you can review the charges, inclusions and terms together. No price or access entitlement is implied by these engagement options.
Is a focused evaluation free?
Any evaluation charges, access period, deliverables and responsibilities are agreed in writing before it starts. A product walkthrough can use demonstration data without sharing confidential project material.
Can we combine software and advisory?
Yes, they can be scoped together. The proposal should make clear what the software provides, what practitioners will deliver and who retains each review and approval responsibility.
What should procurement or IT review?
Bring your supplier, data-handling, access, records and support requirements. The Trust center and Working with Kairos pages are starting points; specific contractual requirements are reviewed during scoping.
Does an evaluation automatically become a subscription?
Expansion is a separate decision. Agree what happens to access, project information and any retained outputs when the evaluation ends. Ongoing software use requires its own agreed commercial terms.