Ready · Aim · Fire
Most companies aim and fire. Few get ready first.
Before you pick an AI project, an automation, or a headcount number: can you answer these about your own team?
- How many hours a week does your team spend emailing each other — not customers?
- How long does a trouble ticket really take to resolve — not how long the ticketing system says it took?
- When someone answers a customer email, how much of that time is hunting across systems for the answer?
- How much of the day goes to copying and pasting between systems that don't talk to each other?
- Why does the same task take one person minutes and another most of an hour?
- Does the work arrive when your people are actually online?
- Why is overtime constant when half the day looks quiet?
- Where do people get stuck — and what do they do while they're stuck?
- Which of your AI ideas would save real hours, and which would just add a tool?
- Who is already pasting company data into a public AI chatbot?
- If you hired one more person tomorrow, which backlog would it actually clear?
- Could you prove your team's productivity to a client, a board, or a buyer — with data, not anecdotes?
If the answer comes from gut feel, a survey, or what the ticket system logged, you’re aiming before you’re ready.
From $4,950 · 2–4 weeks of continuous desktop measurement · fee credited toward deployment
OLi answers those questions. It measures how the work is actually performed — and notices the moments where help, a skill, or an automation would pay off.
Quote to SparkCo opened 4× with no reply
Suggested
Draft a nudge citing the slide they re-read most
1 · The assessment
Ready. Measure how the work is performed.
Two to four weeks of continuous desktop measurement across the whole team: where the hours actually go.
2 · The report & readout
Aim. Pick the project the data points to.
AI use cases, automations, staffing or training — ranked by measured hours, not by the loudest request.
3 · Deployment
Fire. Execute, then prove it.
OLi implements the changes, then measures the result — one instrument for the baseline, the fix and the proof.
Try it on your own team
Estimate · not a measurement
The rest is back office, where recoverable time usually sits higher — in customer-facing work the handling time is the service.
3,938
desktop hours a month we would measure
300–470
hours a month in the planning range
1.9–3people’s worth of capacity
Not headcount to cut — capacity to absorb growth, or to stop paying for in overtime.
Five questions, and it accounts for your channels, systems and how the work is paid for. Assumes half to three quarters of the day at a computer until you tell us otherwise.
What you get
This is what an assessment hands you — run it for your own team.
Illustrative — synthetic data
Illustrative · synthetic data
40%team occupancy. No agent reaches 80%; 12 of 24 are below 40%.
Illustrative · synthetic data
2,250–3,100 hsavable a month across eight use cases, from 21,584 measured hours.
- Ticketing ↔ industry-specific platform lookups2,420 h · 485–725
- Bank reconciliation1,450 h · 290–430
- Ticket reply drafting1,380 h · 415–550
- Call wrap-up & notes1,370 h · 340–480
- General-ledger transaction entry1,090 h · 380–545
Invented organizations, synthetic numbers — the shape of the findings, not a real customer’s. Answer five questions and we run the same charts against your team’s size and mix. Run the simulation for your team →
Illustrative · one person, one day
- Ticketing / case system2.1 h
- Email1.6 h
- CRM1.2 h
- Spreadsheets0.9 h
- Between systems1.1 h
- Everything else0.6 h
A paid day is one number.
Seven and a half hours a person. That is what the schedule says and what payroll pays for, and as far as most reporting goes, that is where it ends.
Measured, it is a dozen applications.
The same day, split by where the time actually went. No single system holds this picture, because the work crosses all of them.
This is the part nobody schedules.
Copying between systems, re-keying, hunting for the answer. It is on no ticket and in nobody's job description, and it is usually the largest single pattern we measure.
That seam is what an assessment sizes.
Measured per person, for weeks, across the whole team — until the range becomes a number you can plan a project around.
Pricing
Fixed fee. Stated up front.
| Assessment | Scope | Measurement period | Price |
|---|---|---|---|
| Single-Team Snapshot The fastest way to see what measuring actually gives you. | One team, up to 15 seats | 2 weeks | $4,950 |
| Workforce Assessment How many people does this work actually need — and when? | One team, up to 40 seats, 1–2 sites | 3 weeks | $12,500 |
| AI & Automation Assessment Which AI use cases and automations should you pick — ranked by measured hours? | Up to 75 seats, 1–2 sites | 4 weeks | $15,000 |
| Workforce + AI & Automation Assessment Both answers from one measurement period. | Up to 75 seats, 1–2 sites | 4 weeks | $22,500 |
| Enterprise program Multiple teams, sites, or functions — one staffing picture across all of them. | 76+ seats or 3+ sites | Scoped | From $25,000 |
| Portfolio Program For private equity: a measured value-creation baseline across recently acquired companies, converted to an EBITDA range for each 100-day plan. | Up to 3 companies, 75 seats each | 4 weeks | $55,000 |
Single-Team Snapshot
$4,950
The fastest way to see what measuring actually gives you.
One team, up to 15 seats · 2 weeks
Workforce Assessment
$12,500
How many people does this work actually need — and when?
One team, up to 40 seats, 1–2 sites · 3 weeks
AI & Automation Assessment
$15,000
Which AI use cases and automations should you pick — ranked by measured hours?
Up to 75 seats, 1–2 sites · 4 weeks
Workforce + AI & Automation Assessment
$22,500
Both answers from one measurement period.
Up to 75 seats, 1–2 sites · 4 weeks
Enterprise program
From $25,000
Multiple teams, sites, or functions — one staffing picture across all of them.
76+ seats or 3+ sites · Scoped
Portfolio Program
$55,000
For private equity: a measured value-creation baseline across recently acquired companies, converted to an EBITDA range for each 100-day plan.
Up to 3 companies, 75 seats each · 4 weeks
60-day fee credit. 100% of the assessment fee is credited toward your first-year OLi deployment and implementation if you sign within 60 days of the readout. Fixed fee, no free trials.
The instrument
OLi is how we measure the work.
A desktop agent for Windows and macOS. It measures the work, then implements the changes and measures those too — one instrument for the baseline, the fix and the proof. Anonymized at capture, inside your tenant.
Step 3 · Deployment
Then OLi implements it.
After the readout, OLi delivers what the report ranked: automations, help at the point of work, schedule changes. Your assessment fee is credited if you sign within 60 days of the readout.
Or skip the assessment
Deploy OLi directly: 10% more productive time in 30 days, guaranteed.
Measured against a baseline agreed at kickoff. Choose one path: the assessment earns the fee credit; direct deployment carries the guarantee.
In production since 2020
10B+
activity graph records
5+
years of continuous operation
1M
activity records per day
Real results from real deployments.
Production deployments, running for years.
“We needed AI that actually understood how our people work — not another chatbot waiting to be prompted. OLi shows up in the moment with the right action, and the activity graph gives us visibility we never had before.”
Randy Steinle
CEO, Cyber Trust Alliance
“What convinced me was the specificity. OLi does not give generic advice — it sees what you are doing right now and responds to that. The difference is night and day.”
Brian Chace
Find out what the work actually needs.
In 30 minutes we agree on the team, the question and the number of seats — and start your security review.
You leave the 30-minute call with
- Which assessment fits — or whether you need one at all
- The fixed fee, or an indicative fee for enterprise and portfolio programs
- What could slow the install in your environment — Citrix or VDI, mainframe screens, unmanaged devices, security review, client or portfolio approvals — and how we handle each
- A measurement plan and a realistic start date, followed by a written scoping summary and draft proposal
Five minutes before it: the pre-assessment
- What the team does, how many people, how many sites
- Which activities are directly tied to revenue, and which are back office
- How the work is paid for — if clients pay for your people’s hours, efficiency can cut revenue, and we scope around that from the start
- The systems the team works in, and whether any of it runs through Citrix or VDI