Complex reporting  ·  done right, built to run itself

The report is only the tip. The logic is where the work is.

I build, modernize, and fix complex reporting — accurate, automated, and correct where it counts. Ten years of building and migrating report logic across Excel, WebI, SAS, and Databricks, with the diagnostic depth to find what's actually going wrong when the numbers don't add up.

the tip
the logic below it
The short version

I build reporting that's accurate, modern, and automated. When something breaks and the cause won't surface, finding it is what I do best.

Complex reporting hides its hardest problems in plain sight — a subtle logic error, a total that won't reconcile, a report the team has been staring at for weeks. The numbers are right there; the reason they're wrong isn't. Finding it is a specific skill, and after ten years across four reporting stacks, it's mine.

What I do

Four ways I get called in

Different starting points, one throughline: complex reporting that has to be right — and provably so.

01

Build complex reports

Dense, audit-grade reporting — complex logic, numbers that have to hold up to scrutiny — built on whatever modern stack fits.

02

Modernize & automate

Rebuild reporting in Databricks or Power BI and make it run itself — ingestion pipelines into clean medallion schemas, scheduled runs, and automated data-quality checks that catch problems before anyone downstream does.

03

Migrate off legacy BI

Moving reports off WebI safely depends on reading the old logic correctly. A decade inside SAP BusinessObjects means critical reports come across intact and validated — not rebuilt blind and quietly broken.

04

Fix what won't reconcile

When a total won't tie out and the team is stuck, I trace the variance to its real cause — context, grain, filters, joins, definitions — instead of patching the symptom.

A decade translating report logic across stacks Excel → WebI → SAS → Databricks  ·  Power BI  ·  Tableau
How it goes

Correct isn't a promise. It's a process.

Every engagement is built so you can prove the result to whoever needs to trust it — an auditor, a funder, your own leadership.

01 — Surface

Establish the baseline

Inventory every report, universe, and dependency, and lock the exact figures the new system has to reproduce. You can't prove a match without first defining truth.

02 — Rebuild

Modernize the logic

Reconstruct the reporting on the new platform — automated, scheduled, checked — reading the original logic closely enough to carry it over faithfully or fix what was subtly wrong all along.

03 — Prove

Reconcile and validate

Check the rebuilt output against the baseline until it ties out, with a record you can hand to anyone who needs to trust the numbers.

Who's behind it

Methodology, not just tooling.

Most report-builders know a tool. Fewer understand data integrity at the level of research design — what makes a number defensible, not just present. That combination, plus ten years of hands-on reporting work, is what I bring.

Sarah Taylor · Principal

10 YRS

Deep SAP BusinessObjects / WebI expertise

Built and maintained complex, logic-heavy reports for a decade — the fluency that makes migrating off WebI safe instead of risky.

MA

Research methods & statistics

Graduate training centered on rigorous methodology — data integrity and statistical validity as a discipline, not an afterthought.

CS

Computer science background

SQL, modern data platforms, medallion pipelines — I build and automate the solution, not just diagram it.

Get in touch

Reporting you need to modernize — but can't afford to get wrong?

That's the conversation to have. Tell me what you're on now, where you're trying to go, and what has to keep tying out. I'll tell you honestly whether I'm the right fit.

hello@ninetenthsdata.com