Ways to work together

Choose an engagement that matches the decision in front of you

The right starting model depends on how well the problem, data, systems, ownership, and target state are understood. Scope and commercial terms are agreed only after the relevant unknowns are visible.

Discuss your operation Explore solutions

Context

Engagement comparison

Model	Best when	Typical outputs	Decision at the end
Operational assessment	The problem is important but causes and options are unclear	Process map, baseline, constraints, prioritized next step	Whether and where to invest
Focused pilot	A bounded workflow and owner exist, but feasibility or adoption needs proof	Tested workflow, evidence, exception design, rollout decision	Stop, revise, or expand
Implementation project	Requirements and dependencies are sufficiently known	Configured solution, integrations, testing, cutover, training, handover	Accept and operate the agreed scope
Ongoing support	A live supported service needs defined monitoring and change ownership	Triage, changes, runbooks, reviews, optimization backlog	Continue, adapt, or transition support

Action

What changes effort and cost

Number and condition of systems and interfaces

Process variation, sites, languages, and user groups

Data cleanup and migration

Security, regulated, validation, and retention requirements

Availability of client owners and test environments

Cutover, parallel running, training, and support coverage

Action

Commercial clarity

A proposal should name deliverables, assumptions, client responsibilities, exclusions, acceptance, change control, expenses, third-party costs, intellectual property, data handling, and support boundaries. No price list is published until the actual offering and market are configured.

Buying questions

Questions to resolve before work starts

These answers establish a practical default. Actual scope follows the systems, process, data, risks, and responsibilities in view.

01How are scope, timeline, and price determined?

They depend on process variation, systems and interfaces, data condition, security requirements, testing effort, number of sites, training, and support boundaries. Discovery produces an evidence-based scope rather than an unsupported fixed promise.

02Who owns the data and operating documentation?

The client remains responsible for its data and operational decisions. Project terms should identify ownership of configuration, custom code, credentials, runbooks, architecture records, and vendor accounts before implementation begins.

03What support can be included after launch?

Handover can include training, runbooks, monitoring, incident triage, change requests, and periodic optimization. Response targets, hours, exclusions, access, and escalation routes must be agreed in the support scope.

Start with one process

Which workflow currently costs your team the most time?

Bring one normal example and one exception. Use them to frame the systems, decisions, controls, and evidence a sensible next step needs.

Discuss your operation