01
Initial Interview
With you: the sponsor, founder or executive owner. Establishes context: your business, your stage, your risk profile. Also identifies who else needs to be in the room.
Delivery Advisory
The Delivery
Diagnosis.
Your systems, your data, your transformation programme. You're told they're fine, or on track, or value for money. You have no independent way to tell whether any of that is true.
Your team or your vendor is throwing tools, timelines and acronyms at you. Some of what they're doing is right. Some is overkill. Some is missing entirely. You have no way to tell which is which.
A structured, independent assessment of your systems, data and delivery setup. No vendor agenda. No framework handed to a junior analyst. I work directly with you, deliver a plain-language report your board can read, and give you the questions to ask your team and your vendors, and what good answers look like. So you can own the answer.
Independent systems and data review · Fixed price · Plain-language report
Book the DiagnosisReport within 5 business days. If you don't leave with clarity, you don't pay.
What You Walk Away With
A position you
can defend.
The Risk Profile
Your organisation's stage, sector, and the delivery and data risks that are actually relevant to you. Not a generic framework. Not a template. Specific to what you are.
An Honest Audit
What your current systems, data and delivery setup really look like: what's working, what isn't, and who owns what.
A Scope Reality Check
What you're genuinely required to do, what's optional, and what's irrelevant for your stage. In plain language.
Prioritised Actions
Options for each gap with pros, cons and rough cost. No jargon. No open questions. A plan you can act on.
A Readout Session
I walk your leadership team through every finding, with time for questions. Everyone in the room leaves with the same picture.
The Right Questions
The framework to evaluate your systems and data yourself: what to ask your vendor, your data lead, your delivery team, and what a good answer looks like in each case.
How It Works
1,2 days · On-site or remote
From first call
to clear answer.
02
Follow-on Interviews
With the relevant people: your system vendor, internal data or systems lead, delivery lead, or whoever owns the decisions. I ask the questions you don't know to ask.
03
Ad-hoc Follow-ups
Where specific detail isn't available during interviews, I request what I need directly, without creating noise for your team.
04
Written Report
A full assessment covering every area in scope. Delivered within 5 business days.
05
Readout
I walk your leadership team through every finding, in plain language, with time for questions.
Scope
What's in.
What's out.
In Scope
- +Organisation profiling: maturity, growth phase, operational complexity
- +The delivery and data risks relevant to your organisation specifically
- +Inventory of current systems, data and processes: what exists, who owns it
- +Evaluation of current vendors and your internal team
- +What's missing, what's overkill, what's misaligned for your stage
- +An independent verdict on a system, vendor or tool you're considering
- +Prioritised recommendations in business language
Out of Scope
- ,Hands-on implementation, migration or build (a separate engagement, delivered by Ahonsi & Co)
- ,Formal certification or accreditation
- ,Fixing or rebuilding the systems themselves
Design Principle
Comprehensive enough for what you are, not for what you are not. A 30-person operation doesn't need enterprise-grade architecture. A regulated, data-heavy organisation does. I tell you what's appropriate for your stage, your sector and your actual exposure. Nothing more. Nothing less.
When to Book This
The right moment
to get the read.
Before a Board Review or Fundraise
People will ask whether your systems and data can scale. If you can't answer, it creates doubt. Get the independent read before they ask.
Before a Big System Decision
You're about to choose or replace a core system. Get an independent verdict before you commit the budget.
Your Board Is Asking
You shouldn't be dependent on your vendor to speak for you in that room.
Team or Vendor in Place, No Way to Evaluate Them
Having someone in place is not the same as knowing whether what they do is right for you.
A Programme Is Stalling or Running Over Budget
Before you react and spend, understand what actually needs to change.
Onboarding a New Lead or Provider
Before you hand over the keys, know what the baseline is and what you should expect from them.
After an Incident, Outage or Failed Go-Live
Understand what actually went wrong, independently.
Entering a New Market, Scale or Operating Model
The requirements just changed. Understand what that means before the bills land.
Why Barbara
Both sides
of the table.
I have operated at both ends of this. I've built and owned the systems, data and operations functions, and I've come in from outside to evaluate them. That combination is rare.
I know what good looks like. I also know what it costs to build, what's genuinely worth it at your stage, and what isn't.
Most advice in this space comes from people who have only seen one side: either the vendor selling the solution, or the team deploying it. I've been inside both.
I have no product to sell. No vendor agreement. No referral fee. When I recommend something, it's because it fits, not because it pays.
Final Call to Action
Know where
you stand.
The questions to ask your team and your vendors. What good answers look like. A clear, written position you can defend to your board, your investors and yourself.
Fixed price · No jargon · No vendor agenda · No open questions
Common Questions
What people
ask first.
- What is a systems and data diagnosis?
- A structured review of your current systems, data and delivery setup: what you have, who owns it, what's working, and where you're exposed. It tells you exactly where the gaps are before your board or your customers find them. A plain-language report in 5 business days, with no vendor agenda and no product to sell you.
- Do we actually need a new system or platform yet?
- Not necessarily, but you need to be able to answer the question. The diagnosis tells you which path makes sense for your stage and what to prioritise first, so you don't spend ahead of need or behind it.
- What do investors and boards actually check on systems and data in due diligence?
- Typically: whether your data is accurate and accessible, whether your systems can scale, how dependent you are on key people or spreadsheets, and whether you have a credible plan. The bar rises sharply with stage. Most leaders prepare for the wrong things. The diagnosis tells you what actually gets asked.
- Should we replace our system or fix it?
- It depends on the gap. Sometimes the system is fine and the operating model is broken; sometimes it's the other way round. The diagnosis tells you which, before you spend on the wrong fix.
- What does an organisation at our stage actually need?
- The baseline is usually: accurate, accessible data; systems that match how you actually operate; clear ownership; and a plan that survives your next phase of growth. Most organisations aren't fully there. That's what scrutiny exposes.
- We already have a data or systems lead, or a vendor.
- That's exactly why this is useful. The question isn't whether you have someone. It's whether what they're doing is right for your stage and your risk. This gives you the independent read.
- We're not in a regulated industry.
- Regulation is one risk vector, not the only one. Data loss, key-person dependency, systems that can't scale, runaway cost: these aren't compliance problems, they're business problems.
- We'll handle it after the raise, or next quarter.
- The questions get asked in due diligence and board reviews. If you can't answer, it creates doubt. This gives you a clear, defensible answer before the question is asked.
- This sounds expensive.
- Most organisations at your stage are either overpaying for capability they don't need, or missing what actually matters. Knowing the difference saves you far more than the cost of finding out.