AREA 1
Process
Value stream mapping with operations leadership and frontline staff. Steps, handoffs, wait times, rework loops. Cycle efficiency comes out as a percentage, and in contact operations it usually starts between 30 and 40.
Before we build anything, we map what you already have. Process, tools and experience, scored 1 to 5, turned into an ROI case and a small number of REVEAL agents running on your own data.
[01 / THE PROBLEM]
The platform lands on a process nobody wrote down, next to four tools that do not speak to each other, and the pilot is judged on whether people liked it. That is not a technology outcome, and no amount of model quality rescues it.
HOW IT USUALLY GOES
HOW A DESIGN ENGAGEMENT GOES
A Solution Design engagement is a diagnostic, not a report. The output includes REVEAL agents tuned to your operation and running while we are still in the room.
[02 / THE AREAS]
Three are measured directly. The fourth is where they meet, and it is the only one the board reads.
AREA 1
Value stream mapping with operations leadership and frontline staff. Steps, handoffs, wait times, rework loops. Cycle efficiency comes out as a percentage, and in contact operations it usually starts between 30 and 40.
AREA 2
What is in use, what actually integrates, and what is being rekeyed by hand. Scored against an AI readiness canvas so automation feasibility is a finding rather than an opinion.
AREA 3
Journey maps and friction analysis, from both sides of the conversation. Where the customer gives up, and where the agent has to work around the system to help them.
AREA 4
The synthesis. Findings from the first three areas become a ranked opportunity list with an ROI model built on your volumes, configurable, with the sensitivity shown rather than hidden.
Each area connects to REVEAL modules that keep measuring it after we leave. Root cause and top call drivers sit under process, the knowledge base under tools, the experience modules under experience. The diagnostic does not end when the document is signed off.
[03 / READINESS]
Process, tools and experience each get a score from 1 to 5, current state against target. The gap between the two is the scope of the engagement, which is why we show the scale before we show your result.
Nothing structured. Manual, ad hoc, undocumented. Firefighting is the normal working day.
Some structure, applied inconsistently. Systems are siloed and the fires are frequent.
Processes are documented and tools are in use. Improvement is planned, and slow.
Measured and tracked. Tools are integrated and used. Decisions are made from data.
Automated and AI-augmented, with improvement built into how the operation runs.
A composite around 2.3 means there is real room and a clear first move. A composite above 4 usually means you do not need a consulting engagement, and we will say so. That client is better served by a retainer, or by nothing at all.
[04 / THE PIPELINE]
Every engagement runs the same pipeline, with a review gate between each stage. The gates exist so that work stops early when the fit is wrong, rather than late when the invoice is written.
01 · QUALIFY
An hour, internally, before anything is proposed. We decide the tier, the areas and which REVEAL agents would earn their place. If the answer is no, the answer is no.
02 · DISCOVER
A structured session, live rather than sent ahead. You see the framework applied to your operation in the meeting, and we leave with the questions the assessment has to answer.
03 · ASSESS
Interviews, mapping sessions, tool review, and REVEAL agents run against your data for real. The findings come from what the operation does, not from what the org chart says it does.
04 · PROPOSE
A current-state assessment, process maps, the readiness score, a ranked opportunity list, an ROI model you can open and change, and a 30 · 90 · 12-month roadmap. Then a session to walk it, with the agents already running.
[05 / PRICING]
Three tiers, priced by depth and by how many agents are deployed. Every tier ends with REVEAL running on your data rather than with a recommendation to buy it.
SMALL
ONE TIME · PRICED ON THE CALL
MEDIUM
ONE TIME · PRICED ON THE CALL
LARGE
ONE TIME · PRICED ON THE CALL
A rapid diagnostic runs 2 to 3 days, and is free when we are still working out whether there is a fit. Afterwards, a technology partner retainer keeps the agents running and improving, sized by the number of agents and the depth of advisory. Platform licences are separate · take the exercise to see which model your operation lands on, then arrange the call with your own numbers.
[06 / CONSOLE]
Book a diagnostic.A rapid diagnostic scopes the fit on your own data. Prefer to walk the agents first? Open the console, then we will tell you which tier fits — or that none of them does.