Rebuilding weekly reporting for a growing startup

Situation

Weekly reporting lived across Slack, Sheets and multiple SaaS tools. The founder was rebuilding the same picture every week before the team could discuss what to do next.

What they thought was wrong

The initial request sounded like a dashboard project. The real question was which numbers deserved attention, and who owned each number before the review started.

What I found

This was a data ownership problem before it was a visualisation problem. The team had useful information, but no shared operating view or clear handoff between collection, checking and action.

What was worth fixing

I prioritised the recurring reporting loop: source mapping, a smaller set of trusted signals, and a weekly review that connected each signal to a decision. The unknown result fields stay visible until the client confirms the evidence.

What I changed

I mapped the current workflow, consolidated the key data sources and designed a reporting room around the founder's weekly decisions. The system leaves room for the team to update ownership as the company evolves.

What I built

• A single weekly operating view
• Data consolidation across existing tools
• A repeatable reporting workflow
• Automation points for recurring collection

Result

The result should be measured against the cost of the old loop. Add the confirmed time saved, manual steps removed and reporting adoption in the fields above rather than guessing.

Reflection

The next improvement would be connecting the operating view to the team's planning rhythm so reporting creates a decision, not another document to maintain.