Which source produced which customer, cohort reporting, and the weekly number everyone quotes. Built so it still works after the team changes and the channels move.
The common failure is not a missing dashboard. It is three dashboards that disagree, so every meeting starts with an argument about whose number is right and ends before anyone decides anything. This module produces one set of figures that everybody quotes, and makes the disagreements visible rather than hidden.
Why attribution is usually wrong. Not the model. The data underneath it. If source is set by whichever integration touched the record last, no attribution model will save you. Fix the field before arguing about first touch versus last touch.
The dashboards, the definitions in writing, and the status map showing which numbers are verified and which are not. That last part is the one clients keep referring back to, because it tells them which figures they can take into a board meeting.
If the underlying data is not being captured yet, reporting on it produces confident nonsense. Lead sources and pipeline come first. Reporting is the last module for a reason, and anyone selling it as the first is selling you a dashboard rather than an answer.
The first two weeks produce a status map of your own stack. Every piece named, colour coded by how proven it is, gaps included. You keep it whether or not we work together.