Reccie for transformation sponsors
A plan your CEO will fund and your teams will support.
The board wants progress on AI, and your teams want to know what it means for them. Reccie gives you the whole picture, prioritised: what goes first across the business, and why.
Close the gap between what you learn and what you build.
Every build traces to a finding
And every finding to where it came from: a role, or a document.
Disputed findings are kept
Not averaged away. A split between leadership and the floor is itself a finding.
A build needs more than one voice
It’s only proposed when at least two other people confirm the problem, or it shows up in more than one part of the process.
A specification to build from
Not a report: the steps, the systems, the rules and the evidence behind each build.
How you run it
Four stages. A blueprint at the end.
- Explore. We agree the scope with you, read what you already have, and plan who to hear from in each function.
- Map. Scout talks with everyone who does the work, on their own time, and Lens maps every answer onto the blueprint as it arrives.
- Define. Arc proposes builds only where the findings hold, and ranks them on impact and effort.
- Demonstrate. You get the blueprint, the proposed builds and your read-only site. For a proposed build, we can generate a proof of concept and a product brief.
46 people · 6 functions
- Transport planning9
- Warehouse operations14
- Customer service8
- Commercial and pricing6
- Compliance and safety5
- Systems and data4
What your teams experience
Nothing to book, and nothing to prepare.
- They answer when it suits them, on the channel they already use: Teams, a browser, voice, text, phone or email.
- One or two questions at a time, following their lead.
- They can skip a topic, or come back to it later.
- Scout is always clearly AI.
Walk me through the last late booking change.
I changed it in the TMS, rang the depot, then updated the carrier portal.
Roughly how long does that take, end to end?
What you hold
The specification, and the evidence behind it.
- The blueprint, layer by layer, with who does each step and the time it takes.
- Ranked builds, with dependencies and the problem each one solves.
- The evidence behind each build, linked to its source.
- Your read-only site, where Pulse answers questions and cites its sources.
- Summary
- Themes
- Findings
- Builds
- Ask
What we heard
46
people
4
builds
38 h
a week
Ask the evidence…
Telling your people
How your people hear about it.
- Nominate who should be heard: everyone who does the work in the area you choose.
- Managers let their teams know it’s coming, and why.
- Each person then gets an invitation from Reccie, by email or in Teams.
- Scout explains the purpose at the start of every conversation, and what happens to what people say.
Hi Priya, Scout would like to hear how the work really gets done in Warehouse operations.
Answer when it suits you. Skip any topic. No one at Kestrel sees who said what.
It fits how your organisation already works.
Read-only
By default, Reccie doesn’t write back to your systems.
Microsoft Teams
Works in Teams, including organisations with more than one tenant.
Nothing metered
One fixed fee. One more person, or another conversation, doesn’t change the invoice.
Frequently asked questions
How much effort from my team?
As much or as little as each person likes. Five minutes is useful; twenty is great. People can have one longer conversation or several short ones over days or weeks, in Teams, in a browser, by voice, phone or email. Scout picks up where they left off, so no one has to repeat themselves. The more detail people share, the sharper the blueprint.
Do you need access to our systems?
Not to your operational systems. Reccie reads and analyses, and has no write access, so discovery can’t change anything it is studying. If you run it in Microsoft Teams, it connects to your Microsoft 365 tenant, and organisations with more than one tenant are covered.
How do we announce it?
Managers let their teams know it’s coming, and why. Then each person gets an invitation from Reccie, by email or in Teams, and Scout explains the purpose at the start of every conversation.
What is the smallest discovery that makes sense?
Roughly twenty or more people who do the work, in one function or across several. Below that, a few conversations of your own may serve you better, and we will say so.
Start with a reccie.
See it on your problem.
Thirty minutes, a demonstration discovery on screen, and a plain answer on whether discovery fits.
- 1Thirty minutes with the team. No preparation needed from your side.
- 2We walk through a demonstration discovery, and the blueprint behind it.
- 3We tell you plainly whether discovery fits, and what it would cover.