Reporting in Salesforce: what good looks like

Most Salesforce orgs have reports. Log into almost any CRM that has been in use for more than a few months and you will find a library of them, often dozens, sometimes hundreds. The problem is that having reports is not the same as having reporting that anyone actually uses or trusts.

In our experience, reporting is one of the most common areas of frustration for small businesses on Salesforce. Managers are not confident in the numbers, sales reps run different reports and get different answers, and the dashboards on the home page stopped being updated months ago. The data is there, somewhere, but nobody is quite sure they are looking at it correctly.

This article looks at what good Salesforce reporting actually looks like, the most common reasons it breaks down, and what it takes to get it right.

Why Salesforce reporting breaks down

Good reporting does not just require the right reports. It requires clean data, consistent processes, and a clear understanding of what the business actually needs to measure. When any of those three things are missing, reporting falls apart regardless of how sophisticated the tool is.

The most common root causes we see are:

• Inconsistent data entry. If different people are logging activities, updating stages, or recording close dates in different ways, no report will give a reliable picture. Garbage in, garbage out.
• No agreed definitions. What counts as a qualified lead? What does it mean for an opportunity to be at the proposal stage? If the team does not agree on definitions, the same pipeline can look very different depending on who is reporting on it.
• Too many reports, not enough clarity. Salesforce makes it easy to create reports, which means orgs accumulate them quickly. When there is no clear set of agreed reports that the team uses, everyone defaults to building their own version and trust in the numbers erodes.
• Reports built on the wrong object or filters. A report that looks right can still be wrong if it is filtering out records it should include, or including records it should not. Many reports in older orgs were built by someone who has since left, and nobody is entirely sure what they are actually showing.
• Dashboards that are not refreshed or maintained. A dashboard that was set up during implementation and never updated quickly becomes irrelevant, and managers stop looking at it.

What good Salesforce reporting looks like

Good reporting is not about having the most reports. It is about having the right ones, used consistently, based on data everyone trusts.

Here is what we look for when assessing whether a Salesforce org has good reporting in place:

The reports most small businesses actually need

For a small business using Sales Cloud, a relatively small set of reports covers the vast majority of what a sales manager needs to run their team effectively. These tend to include:

• Pipeline by stage and owner: a clear view of where all open opportunities sit, broken down by who owns them.
• Forecast by close date: opportunities expected to close this month and next, with their values and stages.
• Win and loss analysis: what proportion of opportunities are being won and where in the pipeline losses are happening.
• Sales activity by rep: calls logged, emails sent, tasks completed, so managers can see engagement levels and not just outcomes.
• Stale and at-risk opportunities: deals that have not been updated recently or have close dates that have passed without being maintained.
• Lead source conversion: where leads are coming from and which sources are converting to closed business.
• New business versus renewal split: understanding whether growth is coming from new customers or existing ones.

These reports, combined into a single sales leadership dashboard, give a manager everything they need for a weekly pipeline review without digging through multiple tabs or building one-off queries.

Getting reporting right: where to start

If your Salesforce reporting is not where you want it to be, the starting point is almost never the reports themselves. It is the data behind them.

Before building or fixing reports, it is worth asking a few questions:

• Are opportunity stages clearly defined and being used consistently by the team?
• Are close dates being kept up to date, or are there large numbers of overdue opportunities sitting in the pipeline?
• Are key fields like lead source, record type, and owner being populated reliably?
• Does the team understand why the data matters and what happens to the reports when it is not filled in correctly?

Once the data foundation is solid, building good reports becomes straightforward. Without it, even well-built reports will produce numbers the team does not trust, and the cycle of workarounds and spreadsheets continues.

When to get help with Salesforce reporting

Some reporting problems are easy to fix with a bit of time and knowledge of the platform. Others are symptoms of deeper issues with how the org has been configured or how the team is using it.

It is worth getting outside help if:

• You are not confident that your current reports are showing you the right data.
• Your team runs their own version of every report because nobody trusts the shared ones.
• You have a large backlog of reports that nobody maintains and nobody uses.
• You are preparing for a pipeline review or board presentation and are not sure whether the numbers are accurate.
• Your close rates, conversion figures, or pipeline values look implausible but you are not sure why.

A Salesforce Health Check is a good starting point if you are not sure whether your reporting issues are a symptom of a broader org problem. It gives you an independent view of what is working and what is not, without any obligation to take further action.