Why now?
We look for a real trigger: growth, cost, capacity, customer pressure, compliance or recurring process friction.
Fresh Kiwi · AI consultancy
A complete Efficiency AI Audit at an 80-person organisation, from first conversation to working pilot. Modelled figures, not client results.
Method
Understand and prioritise first. Build only after that.
Overview
| Attribute | At the start |
|---|---|
| Sector | Business services |
| Employees | 80 |
| Departments | Sales, Operations, Finance, HR, Customer Service, IT |
| Current AI | Copilot + disconnected public AI tools |
| Goal | Grow without proportional headcount growth |
Overview
What follows works through the Efficiency AI Audit in detail. That is the first rung on the ladder. Capability AI and Opportunity AI follow the same three lines, but with their own kind of evidence; the scoring method below is specific to the audit.
| Cost line | Capability line | Revenue line |
|---|---|---|
| Efficiency AI Audit: the unit is the task (existing, recurring work) | Capability AI: the unit is the capability gap (demand you're already turning away or rationing) | Opportunity AI: the unit is the opportunity hypothesis (an offer that doesn't exist yet) |
Capabilities
We look for a real trigger: growth, cost, capacity, customer pressure, compliance or recurring process friction.
Someone must be able to organise access, set priorities and make decisions.
A task performed by one person for ten minutes a month is rarely interesting. We look for repetition, volume and impact.
No purchase commitment is required, but there should be willingness to invest if the business case is strong.
We test systems, data, access, security and feasibility at a high level without designing solutions yet.
We agree what should be measurably better within six to twelve months.
Capabilities
Which three goals matter this year and where does operational pressure get in the way?
Which teams are asking for more people and what would those new employees actually spend time doing?
Where do we see waiting, duplicate work, correction loops, copy-paste and recurring reporting?
We inventory Microsoft 365, CRM, ERP, HR, support, storage and existing integrations.
Which tools and pilots already exist and where could Shadow AI be developing?
Which data is sensitive, who may access what and where must approvals remain mandatory?
Method
Not everybody needs a long interview. We combine surveys, workshops and targeted validation.
Efficiency AI Audit
This is how a broad inventory narrows to a manageable roadmap.
Overview
Values are calculated at a fully loaded hourly rate. Time freed is capacity first, not money by itself. Before the pilot we record a baseline and compare it afterwards against time tracking, plus a sample check on quality.
| Opportunity | Before | After | Estimated value |
|---|---|---|---|
| Weekly reporting | 8 hrs/week | <30 min/week | ~€32k/year |
| Lead research | 5 hrs/week | ~1 hr/week | ~€28k/year |
| Invoice processing | Heavy manual work | Automated extraction + review | ~€41k/year |
Perspective
We implement one low-complexity, highly measurable opportunity first. Baseline, KPIs, errors, time and user experience are agreed before implementation so the value review is evidence-based.
Perspective
After value is proven, we move to the next priority in the same portfolio. Existing Fresh Kiwi capabilities are configured where possible instead of being rebuilt.
Perspective
After go-live we monitor usage, cost, quality and risk. We periodically reassess opportunities as processes, data and model capabilities change.
Next step