CALL 30-45 MIN· BOOTCAMP 5 DAYS· PILOT 8 WKS
PRICINGclient process
From the qualifying call to expansion.
We work in stages. We start with five days on your data, then a pilot on a slice of the business, a rollout and ongoing care. Every stage ends with a decision we make together, and scope and terms are agreed on the first call.
PROCESS
Every stage, step by step
Open a stage to see who runs each step, where it happens, how long it takes and what comes out of it. Between the steps sit decisions we make together.
- On site
- Remote
- Decision
Before the bootcamp
approx. 1-2 wksWe check that there is a problem worth solving and data to measure it on. Without that, we do not start.E0.1
Qualifying call
We know whether there is a problem and data
Decision D0
Is there a big problem, with data in a system or in spreadsheets?
YesWe book the bootcamp
E0.2
Bootcamp agreement
Dates and scope reserved
E0.3
You send three months of data and your client contracts
Complete data set
Decision D0b
Has the data arrived before day one?
YesWe load it into your instance
E0.4
We load the data into your instance
First numbers before the kickoff
Bootcamp
5 daysFive days of work on your data. At the end: a working prototype, a one-page report and a pilot proposal.B1
Kickoff: we pick 2-3 problems and talk to your coordinators
Protocol: problems, acceptance criteria, baseline
B2
Configuration for your data
Rules and mapping
B3
Build and review with a coordinator
Prototype ready for testing
B4
Parallel test and demo rehearsal
Evidence on your data, a rehearsed demo
Decision D1
Does the prototype meet the acceptance criteria in the protocol?
YesWe present it on day five
B5
Demo, one-page report and pilot proposal
Pilot decision
Decision D2
Do you sign the pilot right after the demo?
YesWe start the pilot and credit the bootcamp towards it
Pilot
8 wksThe system runs on a slice of the business, on live traffic. Every Friday you get a report on what it delivers.P1
Permanent integration, configuration and training
The system runs on a slice of the business
P2
Production work and a Friday savings report
Weekly evidence measured in money
P3
KPI measurement against the bootcamp baseline
Final report
P4
Results presentation and rollout proposal
Rollout decision
Decision D3
Are the pilot KPIs met?
YesYou get a rollout proposal and fourteen days to decide
Decision D4
Do you sign the rollout within fourteen days?
YesThe pilot is credited in full towards the rollout
Rollout
4-8 wksFrom a slice to the whole business. Expansion and hardening run in parallel and end with sign-off at your site.W1
Expansion: every branch, every coordinator and further problems
The whole business in the system
W2
Hardening: integrations, roles, GDPR, procedures and training
System ready for production
W3
Sign-off
Subscription starts
Subscription
12 mthsMaintenance, support and development. Every quarter we sit down with results measured in money.S1
Maintenance: infrastructure, care, support and updates
The system runs and keeps improving
S2
Switching on the predictive layer
Forecasts from your data
S3
Quarterly business review
Return on investment and next steps
Decision D5
Do we renew after twelve months?
YesAnother year and further expansion
Expansion
from month 6Once the core is running, we add further areas of work and further locations.X1
Further areas: documents, accommodation, quotes, client acquisition, voice calls
More processes in one system
X2
New branches, companies and clients
The system grows with the business
PRINCIPLES
Risk spread across stages
Every stage has its own agreement. The detailed terms come with the proposal; the rules are open from day one and the same for everyone.
BOOTCAMP
The bootcamp is not lost
A quick pilot decision credits the bootcamp towards the pilot. The sooner you decide, the more carries over.
PILOT
Fixed scope plus a results-based part
The pilot combines a fixed scope with a part tied to savings measured against the bootcamp baseline. That part is capped, and the cap is known before the start.
PILOT
A partial result extends the pilot
If the KPIs are only partly met, we extend the pilot at no extra cost and measure again.
PILOT
Results risk sits with us
If the system misses the KPIs it is responsible for, we refund part of the pilot cost.
ROLLOUT
Pilot credited towards the rollout
A rollout decision within fourteen days of the results presentation credits the pilot in full towards it.
ROLLOUT
Sign-off closes the account
The final part of the rollout is settled at sign-off, when the whole business works in the system.
SUBSCRIPTION
One subscription
Infrastructure, care, support and updates in one monthly subscription, on a twelve-month agreement.
ALWAYS
Your data stays yours
If you do not continue after the pilot or after a year of subscription, you get a data export. We do not lock anyone in.
CHANGES
What happens to your request
Every request, at every stage, goes through the same four questions. That keeps the system one product rather than a pile of customisations, and you know upfront what goes in now and what comes later.
Is it part of the core?
YesWe build it. The improvement ships to every client, not just you.
No
Is it configuration: data, rules, thresholds, rates, views?
YesWe set it in the panel. If we set something by hand a second time, it becomes a new setting you can change yourselves.
No
Is it an area we already have?
YesWe add it after the rollout, never during the pilot.
No
Is it something entirely new?
YesIt goes on the roadmap and into the code once three clients need the same thing. Otherwise it is a separate engagement or an honest "no".
Every "no" moves the request on to the next question.
QUESTIONS
Before you ask
What people ask most often before we book a bootcamp.
Every stage has its own agreement and scope: bootcamp, pilot, rollout and subscription. We present the terms after the first call, once we know what problem we are solving and on what data. The rules are the same for everyone and are set out above on this page.
Because five days on your data says more than a month of proposals. At the end you have a working prototype, a one-page report and a pilot proposal, and a quick pilot decision credits the bootcamp towards it.
The last three months of data, from a system or from spreadsheets, and your client contracts. We load them into your instance before day one, so the kickoff starts with numbers, not with collecting files.
Only in the pilot, and only on savings measured against the baseline set during the bootcamp. That part is capped, and the cap is known before the start. The rollout and the subscription have a fixed scope and fixed terms.
With a partial result we extend the pilot at no extra cost and measure again. If the system misses the KPIs it is responsible for, we refund part of the pilot cost.
For the bootcamp, a decision-maker on the first and last day and coordinators for short conversations in between. In the pilot your coordinators work in the system and we handle the configuration.
No. Omnira does not replace your stack; it reads context from it and writes decisions back. Replacing a system is a separate project and it is not one we sell.
We need no access to any system for the first call. Bootcamp data goes into your own instance, and the scope of processing is set out in the data processing agreement and the privacy policy.
FIRST STEP
It starts with thirty minutes with the founder
This is the qualifying call from the first step of the process. We check that there is a problem worth a bootcamp and data to measure it on. If there is not, we say so straight away.
- ANSWER
- < 8 h
- PHONE
- 732 304 554
- hello@omniralab.com
On the first call I do not ask about budget. I ask which process costs you the most and how you know. The quote comes out of the answer, not the other way round.
