Skip to content

Services

Power BI work, from diagnosis to verified delivery.

Bring the report you have — or the reporting problem you haven’t solved yet. We start with the decision, inspect the model and measures underneath it, and change only what the evidence supports.

Three ways in

Start where the problem is.

Most engagements begin with a review. Some need the whole report rescued. A few need the reporting itself rebuilt. Each one starts with the same question: what decision is this for?

01

Report review

Method: xReview

Find the problem before redesigning the page.

A review establishes what the report is for before judging how it looks. It reads the definitions, the report and, where it is available, the model underneath, and comes back with findings you can check rather than opinions you have to take on trust.

The work

  • Establish the decision, the audience and the mandate the report serves
  • Inspect the definitions, the report and the model, where available
  • Findings backed by evidence: the measure, the relationship, the row
  • A priority order, so the first fix is the one that matters most
  • A recommended next move, including when the answer is to change nothing

Deliverable

The decision context, the findings with their evidence, and a recommended next step.

02

Report rescue

Method: xReviewxDesignxBuildxVerify

Fix the report without losing what the numbers mean.

For a report that matters but is not working: too slow to read, doubted in meetings, or quietly worked around in a spreadsheet. The rescue follows the evidence from the review into a redesign and an implementation, then ties the rebuilt report back to the previous version and the source, so intended changes are explicit and unexpected differences are surfaced.

The work

  • Review: the decision, the definitions and what does not hold
  • Redesign: what the page must communicate first, before it is styled
  • Implementation: the measures, the model and the report, changed where the findings point
  • Tie-out and verification: every difference traced to a change that was meant
  • Handover: the files, the notes and the reasons behind each change
03

Reporting transformation

Rebuild the reporting product end to end.

When the problem is not one report but the reporting itself: definitions that differ by team, a model that grew by accident, pages nobody owns. The transformation starts from the decisions the business has to make and rebuilds the product underneath them.

The work

  • Requirements written as a decision contract: who decides what, from which numbers
  • The semantic model, designed for those decisions
  • The measures, one definition per number
  • The report architecture: which pages exist, and why
  • The reporting UX, page by page
  • Implementation
  • Verification against the sources and the previous numbers
  • Handover and documentation your team can maintain

How engagements work today

Founder-led, by request.

Who does the work
The services are founder-led. Mihai Lăpușneanu does the work, and reads every request himself.
Scope and price
Agreed per engagement, after the first conversation about the report and the decision behind it. There is no public price list yet.
Software
The method uses internal tooling. It is not a product, and it is not sold on its own.
Certification
None is sold or issued. Findings and verification are stated with their evidence and their limits, never as a certificate or an automated score.

Start with the question

Request a review.

Name the report, and name the decision it is supposed to support. The rest follows from those two answers.

Start with the question

What should your report help you decide?

Two answers are enough to begin. The brief is written in your browser: email it from your own mail app, or save a copy. This site sends nothing on its own.

The buttons switch on when this page has finished loading. If they stay off, email mihai@playwithdata.io directly.

Goes to mihai@playwithdata.io · No account · No tracking · No network request from this site