How I can help

When leadership can’t trust the numbers, decisions stall.
I turn manual reporting, forecasts and approvals into systems you can rely on.

A paid diagnostic scopes the work, a fixed-scope build ships it on your live data, and an optional retainer keeps it running. Senior delivery, fixed scope, no lock-in.

The Diagnostic

A paid, one-week audit that pinpoints where manual reporting or a fragile forecast is costing you, and exactly what to build.

Best for: a COO, operations or finance leader who suspects a manual report, a fragile forecast or a hand-run workflow is leaking time, money or trust, but hasn’t quantified it.

from1,500
credited in full against a build · ~1 week
Request a diagnostic
Includes
A written diagnosis of the two or three highest-cost blind spots in your data and process
The cost of inaction quantified in your numbers: hours, rework and revenue at risk
One working sample built on a slice of your own live data
A data-readiness assessment and written acceptance criteria for the build
A scoped, fixed-price roadmap, so you decide the build with real numbers

Not included: the production build, live deployment or ongoing support. Those are the build and the retainer.

The Retainer

Your systems kept live, monitored and evolving, senior capacity without a full-time hire.

Best for: an organisation that wants its dashboards, forecasts and automations kept reliable and improving, without hiring a €55k+ salaried analyst.

from2,000
per month · minimum 3 months
Discuss ongoing support
Includes
Pipelines and dashboards kept live, with monitoring and alerting
A monthly decision report: three to five prioritised insights with recommendations
A capped monthly build block for changes and small new work
A scheduled review call and a defined response window
Priced as a fraction of a loaded senior-analyst salary, so we’re not counting hours

Not included: large new builds beyond the capped block, which are scoped as fresh projects.

Not sure which fits? Book a discovery call and I’ll tell you honestly whether I can help. Engagements start with a paid diagnostic and run into four and five figures for a build.Indicative “from” prices; each build is scoped and quoted from your diagnostic.

The cost of untrusted numbers

You rarely lose money on the reports you know are wrong. You lose it on the ones you trust, and shouldn’t.

When reporting is held together by hand and approvals run on memory, leadership ends up deciding on numbers no one fully trusts. Here’s how most teams cope:

Stay manual

Hours re-keyed every week, a month-end that breaks when one person is off, and numbers leadership never fully trusts.

The cost: Hours lost every week

Hire a full-time analyst

A €55k+ salary, plus payroll and the effort of managing someone, when the work that actually needs a senior analyst only comes up a few days a month.

The cost: €55k+ a year

Do nothing

Decisions keep getting made on shaky numbers, risk compounds, and the manual work quietly scales with the business.

The cost: Compounding risk
Proof

Proven at enterprise scale.

The job is always the same: take reporting that lives in someone’s head or a fragile spreadsheet and turn it into a system people can trust.

Enterprise sales analytics · Apple (CEMEA)

Browser-based automation with Playwright plus interactive Tableau dashboards and predictive models — turning large-scale, cross-regional sales data into trusted reporting for the CEMEA Sales BPR & Systems team, and building automation that removes hours of manual work for freelance clients.

−80% manual effort, via Python & RPA
Terabytes of data engineered into BigQuery
CEMEA cross-regional sales visibility
Compare

Which build do you need?

What’s included
A live dashboard leadership relies on
A fragile forecast or manual report rebuilt and made auditable
A repetitive manual workflow automated with human oversight
Governance layer: human-in-the-loop, audit trail, rollback
Built and validated on your live data
Scoped from a paid diagnostic, with written acceptance criteria
A UAT-and-hardening phase before handover
Runbooks, monitoring and alerting
Source in your own repository, no lock-in
A defined post-handover support window
How it works

From manual and fragile to reliable, in three phases.

Modular by design. Start with whichever phase fits, there’s no obligation to take all three.

Start here
Diagnostic

Phase 1

Find the real problems.

Discovery call Data audit Live sample dashboard Fixed-price roadmap
  • Blind spots found
  • Cost of inaction quantified
  • A working sample built
  • Data-readiness check
  • No production build or support
Optional
Retainer

Phase 3

Keep it improving with ongoing support.

Monitoring Monthly report Priority support
  • Monitoring and alerts
  • Monthly decision report
  • Review call
  • Senior capacity, no full-time hire
Step by step

From first message to a system you own.

Every stage of working together, so you know what to expect before you commit.

01 Phase 1 · Diagnostic

The discovery call

We start with a call to go through your objectives, where your data actually lives, and the numbers you want to track: revenue, deals, pipeline stages, team performance. Everything lines up before I build anything.

Discovery agenda
  • Objectives and success metrics
  • Where your data lives
  • The KPIs you want to track
Analytics Project Brief: a spreadsheet template with sections for company info, goals and data sources to fill in before the build.
02 Phase 1 · Diagnostic

A spec and a fixed price

You leave with a written spec and a fixed price, and the diagnostic fee comes off the build. It’s a scoped roadmap, so you decide with real numbers in front of you rather than a guess.

03 Phase 2 · Build

Designed to your spec

I design to that spec: layout and wireframes for a dashboard, backend work for a reporting rebuild, or learning your business rules so agentic AI can run an automation safely.

Wireframe board for a sales analysis dashboard: greyscale layout frames for the Overview and Top Performers tabs, mapped out before any build.
Wireframes come first, mapped to your spec before a line is built.
04 Phase 2 · Build

First draft, plus a walkthrough

You get a first working version and a short walkthrough video covering the design, the KPIs, and how to explore it yourself. You see it working long before the end.

05 Phase 2 · Build

Your feedback, my revisions

You review and tell me what’s off. I make the revisions that are part of your build and tune it to match how your business actually runs.

06 Phase 2 · Build

Final delivery, on your data

Polished, running on your live data, with insights and recommended actions where they help. You own the source and the workbooks, with no lock-in.

07 Phase 3 · RetainerOptional

Kept live

Want it kept live? A rolling retainer keeps your systems reliable and gives you senior capacity without a full-time hire. Each month covers a set number of changes, or new automated workflows and agent skills.

Each month on retainer
  • A set number of changes
  • New automated workflows or agent skills
  • A monthly decision report
  • Priority senior support

The first step is the diagnostic. Book a discovery call

Before we talk

What could this save you?

This is the first sum I run on any reporting or automation brief, so you may as well run it yourself. Put in what the work actually costs you today — the arithmetic is printed underneath, and the numbers stay on your machine.

per week

salary plus overhead

be conservative — I would rather under-promise

a fixed-scope build starts at €8,000

given back per year
returned to the team
to pay back the build
Time spent today
Cost of that time
Saving per month
In working days

The arithmetic

A model, not a quote — the diagnostic replaces these estimates with your real numbers. See what that looked like for other teams in the case studies, or take apart five more working models in the playground.

Questions

Straight answers, before you ask.

I’ve built the reporting and approval systems a large enterprise sales operation ran on, and delivered a paying client a live profit dashboard that lifted gross profit 20%. You don’t have to take that on faith: we start with a low-risk paid diagnostic, so you see how I work and what I find before committing to a build.

You work directly with the person who does the work, with no juniors and no hand-offs. Everything is documented: runbooks, monitoring and the source in your own repository, so your team can run it without me. For continuity, the retainer keeps a named owner on your systems, and I’ll always be honest about capacity before we start.

That’s exactly why automation ships with a governance layer: human-in-the-loop, audit trails, rollback and edge-case handling, validated in a UAT-and-hardening phase before it touches production. For sensitive or regulated-adjacent decisions I lead with dashboards or forecasting first, where the blast radius is lower.

A contractor takes a spec and bills days. A large firm puts juniors behind a partner. You get one senior person who diagnoses the problem, owns the outcome, and hands over a documented system: fixed scope, no layers, no day-rate clock and no RFP.

Because I won’t quote a build blind. The diagnostic quantifies the cost of the problem in your numbers and produces a written spec with acceptance criteria, so the build is fixed-scope and de-risked for both of us. The fee is credited in full against the build.

Builds are value-priced against the outcome and scoped from the diagnostic, not billed by the day. Fixed scope with a change-order clause means the price holds, and my speed is my problem to solve, not your cost to carry.

I’ll sign an NDA on request, work with least-privilege access and on a copy where possible, and delete data on completion. For any automated decisioning I build in the human oversight and audit trail GDPR Article 22 expects.

You own the source, the runbooks and a documented, monitored system, with a defined support window. Keep it in-house, or take the retainer and I’ll maintain and evolve it: capacity without a full-time hire.

Let’s see if I can help.

Tell me what’s breaking, roughly what it’s costing, and what you’ve tried. If it’s a fit, we start with a paid diagnostic; if it isn’t, I’ll say so and point you somewhere better.

Book a discovery call

Engagements start with a paid diagnostic (from €1,500, credited to your build). If you need a few hours of ad-hoc analysis, I’m probably not the right fit, and I’ll happily point you to someone who is.

Prefer to scope it out first? Grab the project brief, or see how working together works.

Ask the AI Advisor