Services / Data & reporting

Data tooling, dashboards, and reporting you can trust

Most small teams don't have a data problem. They have a where is the data, why are there three versions of it, and which one is right problem. I build the plumbing and the dashboards that turn that mess into numbers you and your team can actually use to make decisions.

Custom dashboardsData pipelinesReporting automationAudit trailsQA & compliance tooling

When this work pays off

Data projects can be a black hole. I take them on when there's a specific decision or workflow that's broken, not because someone wants "a dashboard." Patterns I've seen pay off:

You can’t see your real numbers
Revenue, margin, utilisation, conversion, but each lives in a different tool. A weekly export gets emailed around. Decisions feel like guessing.
Manual reporting is eating hours
Someone spends a half-day every week (or month) copy-pasting between spreadsheets to produce the same report. Time to automate.
Your audit / compliance is shaky
You need traceable, audit-friendly records. ALCOA+, GxP, GDPR, SOX. Whatever your regime, the data has to hold up under scrutiny.
You’re hitting the SaaS ceiling
Your BI tool is per-seat and getting expensive. Or the data warehouse needs a real engineer to maintain. A custom layer can be simpler and cheaper.

Recent projects

Audit trail reviews, data-flow risk assessments, and digital QA tooling in a heavily regulated environment. ALCOA+ data integrity, end to end.

Data integrityQA & ComplianceReporting

Consolidated fragmented Access databases into a single on-premise CRM with proper reporting and pipeline visibility.

Data consolidationCRMInternal tool

How I work on data projects

Start with one decision
Pick the single most painful report or unanswered question. Build the pipeline and dashboard for that. Ship in 2–4 weeks. Prove value before scope grows.
One source of truth
Pull from whatever you use today (accounting, CRM, spreadsheets, payment platforms) into a single store. Postgres in most cases. No giant warehouse you can’t afford.
Audit by default
Every transformation is versioned and reproducible. If a number on the dashboard looks wrong, you can trace it back to the row in the source.
Handoff & documentation
Your team gets clear docs on where the data comes from, how it’s transformed, and how to extend the dashboard themselves.

Stack & approach

I keep the stack boring and the maintenance burden low. The point is decisions made with confidence, not impressing other engineers.

Pipelines

Python + dbt-style SQL transformations. Or n8n / Airflow when orchestration matters. Whatever fits the size of the problem.

Storage

Postgres for most things, BigQuery or DuckDB when scale demands it. Small data is fine. Most SMBs don't need a warehouse.

Dashboards

Custom Next.js dashboards when you want polish, Metabase or Power BI when you want fast iteration. I'll recommend whichever fits.

Let's talk

What number do you wish you could trust?

Tell me the decision you're trying to make and where the data lives today. I can usually tell within a call whether this is a 2-week fix or something bigger.