Data-Roo

Data-Roo LLC · Independent analytics consultancy · Wisconsin

Analytics you can audit.

Data-Roo is Ren Rooney. I build the platform, the model, and the application that sits on top, for organizations whose numbers have to hold up in front of a payer, a board, or a regulator. One senior practitioner, start to finish. No junior hand-offs, no agency overhead.

How I work Terms

Engagement
Time and materials, against a written not-to-exceed.
Basis
Signed statement of work. NDA and BAA where PHI is in scope.
Based
Milwaukee area, Wisconsin. Remote, US clients.
01 Engagements 4 shapes

Four shapes of engagement.

Scope is written down before anything starts, and you keep everything that gets built.

  1. 01 Make the numbers defensible.

    Reimbursement and benchmark models, price-transparency data, payer-facing analysis, outcomes and effect-size work. Sourcing you can hand to a skeptic without bracing for it. Where a figure has no anchor in a primary source, it gets listed as a gap rather than estimated into place.

  2. 02 Build the platform underneath them.

    Microsoft Fabric: medallion lakehouse, PySpark notebooks, OneLake shortcuts, capacity sizing, workspace and gateway governance, refresh orchestration. Power BI: semantic models, DAX, Power Query M, row-level security. Fix the model once and everything downstream gets easier.

  3. 03 Ship the tool people use.

    Next.js and Postgres on Vercel: auth-gated internal applications, importers, export packs, CRMs. Built by the same person who modeled the data, so the model and the interface never drift apart.

  4. 04 Sit in the room for the decision.

    Fractional analytics leadership. Roadmap, governance, vendor evaluation, and the translation between data, operations, and leadership that most teams are actually short of. Most organizations do not need another report.

You get the code, the models, and the documentation. Not just a slide deck.

02 Terms As signed

The terms, before you ask.

These are the terms on the signed statement of work, not a posture written for this page.

Basis
Time and materials, billed against a written estimate.
Cap
A written not-to-exceed on every engagement. The invoice cannot surprise you.
The 80% call
When billed hours reach 80 percent of the estimate, I tell you in writing before continuing. That is a clause, not a courtesy.
Invoicing
Itemized by workstream with the hours attached, not a lump sum. Net 15.
Ledger
A running hours ledger you can read start to finish, with every hour tagged to the invoice it was billed on.
IP
Assigns to you on full payment. All of it.
Exit
Either of us can end the engagement on seven days' written notice.
Changes
Scope changes by written change order only.

The budget position is printed on the face of every invoice I send — hours worked against the estimate, dollars billed against the cap — so you never have to ask where you stand. Including on the invoices where the position is uncomfortable.

03 Audit Fixed scope

Fixed scope · Fixed price · Written deliverable

Start with the audit.

Before anyone commits to a build, a short engagement on what you already have. You get a written finding you can act on with or without me, and you own it either way.

  • A map of the current stack: sources, pipelines, models, reports, and who actually depends on what.
  • An inventory of every report and dashboard in use, with the ones nobody opens marked as such.
  • The root cause of the specific thing that is broken — model, pipeline, definitions, or governance — named, not hedged.
  • A sequenced remediation plan with effort estimates, in the order that unblocks the most downstream work first.
  • A 90-minute working session to walk through it with your team.

Priced per engagement.Fixed quote, in writing, before any work starts

There is no list price because the honest range is wide — one warehouse and four reports is not the same job as five source systems and a governance problem. Tell me what you have and what is going wrong, and you get a fixed number and a scope in writing. If you do not like the number, you have lost a phone call.

Book the audit

If the finding is that you do not need the build, that is in the document too, and the audit ends there.

04 Ren 10+ years

Ren Rooney.

Ten-plus years building data products in healthcare and consulting. Most recently, Director of Analytics at a multi-site behavioral health provider, where I architected and administered the Microsoft Fabric environment — medallion lakehouse, PySpark notebooks, OneLake shortcuts, capacity sizing, workspace and gateway governance, refresh orchestration — and owned the Power BI semantic layer above it.

Before that, four years in management consulting in Chicago: staffing and spend analysis across managed IT services engagements, technology scorecards benchmarking client operations against their peers, and the BI layer behind an annual industry technology benchmark. I started in healthcare revenue-cycle analytics at an academic medical center, building recurring dashboards across several revenue-cycle systems and presenting fiscal-year trend findings at quarterly reviews.

Data-Roo is the independent practice. It runs on my own accounts and my own infrastructure and has never touched an employer's.

Published
Co-author, a peer-reviewed study on the effectiveness of brief partial hospitalization for depression and anxiety. the Behavior Therapist, Vol. 49 No. 1, January 2026.
Spoke
Four Becker's Healthcare panels across 2025 and 2026: behavioral health data strategy, EHR data silos and integration, and health IT tooling.
Degree
B.B.A., Business Analytics and Information Systems, University of Iowa.

Microsoft Fabric · Power BI · DAX · PySpark · T-SQL / Spark SQL · Python · Next.js · Postgres · Vercel

05 Contact Milwaukee · Remote

Tell me what is broken.

The report nobody trusts, the platform decision you are stuck on, the number two systems disagree about. Send the problem, who else is involved, and what "done" would look like.

This goes to one inbox and is used only to reply. It is not tracked, sold, or added to a list. Please do not put PHI in this form.

Based
Milwaukee area, Wisconsin. Remote, US clients.
Entity
Data-Roo LLC, Wisconsin.