BI Readiness Scorecard

What you'll get

A scored, plain-English read on your reporting risk.

An overall score (0–60) and a band: Mature, Developing, At risk, Critical.
Sub-scores across Reporting fragility, Governance, Process risk, and Data & systems.
Three specific risks pulled from your highest-scoring answers.
Three quick wins you can action this week without us.

Buyer-to-buyer. No marketing list, no drip sequence. Your email is used to deliver the PDF and (if your score warrants it) to offer a 30-minute fit call. Privacy policy.

Contact details

Where should we send the PDF?

Your name

Work email

Company

Your role

Section A · Reporting fragility

How much your business runs on spreadsheets, who maintains them, how often they break.

A1. Where do your most important weekly or monthly reports live?

Power BI or Tableau with a governed data model Mix of BI tool and manual Excel files Mostly Excel workbooks maintained by named people One or two Excel workbooks that everyone depends on

A2. If the person who maintains your most critical reporting file left tomorrow, how long before someone else could reliably update it?

Same day, documented process Within a week Several weeks with significant disruption No one else could

A3. How often does a critical report break, freeze, or produce a number someone disputes?

Rarely, numbers are trusted Occasionally Monthly Weekly or more

Section B · Governance

Access control, audit trail, data lineage, row-level security.

B1. Can you say, today, who has access to which numbers and why?

Yes, with documented access rules Broadly yes, informally Not really No, and it worries us

B2. If audit or due diligence asked to see how a reported number was calculated, could you produce the full lineage within a day?

Yes, with automated lineage Yes, with some digging Only if the right person is available No

B3. How are permissions on reports controlled today?

Row-level security in place Folder or workspace permissions Files sent by email to the people who need them Mix of all of the above, inconsistent

Section C · Process risk

Which revenue-critical or compliance-critical processes depend on manual reporting.

C1. Which of the following processes currently depend on a spreadsheet or manual workflow?

Select all that apply. Each adds 1 point, capped at 5. If none apply, pick the last option.

Sales commissions Purchase orders or approvals ARR, MRR or revenue reporting Weekly trading or management pack Board-level KPIs Budget vs actuals None of these apply

C2. Has a finance, sales or ops process ever been delayed, disputed or paid incorrectly because of a reporting or data error?

No Once or twice Regularly Recently and it caused reputational or financial damage

C3. How are commissions, POs, or management accounts signed off today?

Automated workflow with audit trail Email or Slack approvals with documentation Email threads, informal A named person manually checks spreadsheets

Section D · Data and systems

Warehouse, pipelines, time to answer a new question.

D1. How is data moved from source systems (NetSuite, Salesforce, HubSpot, SQL, HRIS) into reporting?

Automated pipeline into a warehouse Scheduled exports, mostly automated Someone downloads CSVs each week Mix of exports and copy-paste

D2. Do you have a data warehouse or lakehouse (Snowflake, Fabric, BigQuery, Synapse, Redshift)?

Yes, in active use Yes, partially No, planning to No

D3. How long does it take to answer a new senior question (e.g. "what's gross margin by product line last quarter?") that isn't already in a dashboard?

Same day Within a week Several weeks We rarely answer these questions confidently

Working…

Scoring your answers and preparing your PDF.

This usually takes a few seconds.

Your result

Score: — / 60 · —

The full one-page diagnostic — including the three specific risks and three quick wins — is on its way to your inbox now.

If your score warrants a conversation, you'll see the next step in the email itself.

Book a 30-minute fit call

Hmm

Something went wrong submitting that.

Please try again. If it keeps failing, email [email protected] directly.