Route-efficient planning and routing for care
ContactInvest

Choose language

English
Request access

Pilot and pricing

Start with a focused pilot

Together we choose one concrete planning question. You then receive a proposal covering scope, timing and cost. A pilot is normally paid and only starts once the agreements are clear.

Discuss a pilot See how a pilot works

Test first

From a broad question to one workable trial

Routeez is introduced step by step. We do not try to change your entire organisation at once, but first bound what we can honestly test and evaluate.

After discovery, you decide based on a written proposal. Nothing starts without agreement on work, timing and cost.

  1. Discovery

    We discuss the current process, the first problem you want to solve and who decides.

  2. Proposal

    You receive a written proposal covering scope, timing, cost, data and review criteria.

  3. Trial

    Planners compare proposals with their current method and control publication.

  4. Review

    Together we decide whether to stop, adjust or expand deliberately.

Always included

Every pilot has the same clear foundation

  • Discovery of one concrete planning problem
  • A written proposal covering scope, timing and cost
  • Planners retain control over every proposal
  • A joint review: stop, adjust or expand

Examples

Which situation looks like yours?

These are recognisable starting situations, not fixed packages. We define the final pilot together.

  • One team

    One team, one area

    For a practice or care team that wants visits and routes in one shared view.

    What we test firstTest one working day or route with the people who plan it every day.
    • Scheduling, routes and availability
    • One area and fixed core rules
    • Simple import of starting data
    Discuss this situation

  • Several teams or rounds

    Several rounds or teams

    For a care organisation coordinating several teams, or a lab with recurring sample rounds.

    What we test firstPlan one recurring round or several teams together and make exceptions visible.
    • Rules by route, team or area
    • Central view of demand and capacity
    • Recurring rounds and exceptions
    Discuss this situation

  • Collaboration and integrations

    Collaboration and integration

    For a group sharing capacity or an organisation connecting intake and planning to existing systems.

    What we test firstBound one collaboration or data flow before integrating or rolling out more broadly.
    • Collaboration across teams or organisations
    • Discovery of imports, APIs and ownership
    • Integrations within an agreed scope
    Discuss this situation

How pricing is shaped

What affects the price

We price what is needed to run the agreed trial carefully. Scope, rules, data and guidance make the main difference.

  • Teams and routes

    More teams, roles and areas require more setup and alignment.

  • Planning rules

    Time windows, skills, continuity and exceptions determine how much planning logic must be tested.

  • Data and integrations

    Starting-data quality and any integrations determine much of the technical work.

  • Guidance

    A self-directed team needs less guidance than a rollout involving several teams or organisations.

Differences by situation

What becomes more complex as the scope grows?

We group only the differences that genuinely affect an initial conversation. Technical detail follows when it becomes relevant.

Teams and areas

How many people and areas are included in the first trial?

What we test first One teamSeveral teams or roundsOne collaboration or data flow
Who decides The plannerPlanner and team leadEvery involved organisation

Planning and routes

Which rules, recurring patterns and exceptions must demonstrably work?

Planning rules Fixed core rulesBy team, round or areaWith agreements between parties
Exceptions Planner adjustsVisible by team or roundConfirmed by involved parties

Data and integrations

How do we get reliable starting data into Routeez without integrating everything immediately?

Starting data Calendar, addresses and availabilityAdds teams, rounds and exceptionsAdds roles, processes and sources
Integrations Not needed for the first trialAfter technical discoveryWithin an explicitly agreed scope

Guidance and next steps

Who do we guide during the pilot and what happens after the review?

Guidance Pilot start and reviewAdds planners and team leadsAdds governance and integration
After the pilot Stop, adjust or expandContinue gradually by teamPhase by partner and integration
Teams and areas

How many people and areas are included in the first trial?

One team

What we test first
One team
Who decides
The planner

Several teams or rounds

What we test first
Several teams or rounds
Who decides
Planner and team lead

Collaboration and integrations

What we test first
One collaboration or data flow
Who decides
Every involved organisation
Planning and routes

Which rules, recurring patterns and exceptions must demonstrably work?

One team

Planning rules
Fixed core rules
Exceptions
Planner adjusts

Several teams or rounds

Planning rules
By team, round or area
Exceptions
Visible by team or round

Collaboration and integrations

Planning rules
With agreements between parties
Exceptions
Confirmed by involved parties
Data and integrations

How do we get reliable starting data into Routeez without integrating everything immediately?

One team

Starting data
Calendar, addresses and availability
Integrations
Not needed for the first trial

Several teams or rounds

Starting data
Adds teams, rounds and exceptions
Integrations
After technical discovery

Collaboration and integrations

Starting data
Adds roles, processes and sources
Integrations
Within an explicitly agreed scope
Guidance and next steps

Who do we guide during the pilot and what happens after the review?

One team

Guidance
Pilot start and review
After the pilot
Stop, adjust or expand

Several teams or rounds

Guidance
Adds planners and team leads
After the pilot
Continue gradually by team

Collaboration and integrations

Guidance
Adds governance and integration
After the pilot
Phase by partner and integration

Clear expectations

What your proposal does and does not establish

The proposal gives

  • A clear initial pilot scope
  • Timing, cost and responsibilities
  • Which data and people are needed

The proposal does not promise

  • An automatic commitment to a broad rollout
  • A guaranteed outcome before the pilot
  • Unlimited integrations outside the agreed scope

Frequently asked questions

Why is there no fixed price?
We price a bounded pilot first. Team count, planning rules, data quality and integrations vary too much for one honest catalogue price.
Is a pilot free?
A pilot is normally paid. After discovery, we document work, duration, cost and responsibilities before anyone starts.
What information is needed for an estimate?
A description of teams or routes, recurring rules, current data sources and the first problem you want to test.
Are integrations included?
Only when explicitly scoped. We first investigate source, ownership, data quality and maintenance.

Discuss your first pilot

Tell us which planning problem you want to test first. We bring scope, timing and cost together in a clear proposal.

Discuss a pilot