Salesforce Org Health for Software Companies

Symptom: Fast headcount growth means onboarding a new AE, SDR, or CS rep usually meant cloning whatever permission set the person next to them had, rather than assigning a role-based baseline. Years and a few reorgs later, dozens of overlapping sets exist with no clear owner and no record of why any one of them diverged from the others.

What it costs: Some reps end up with more data access than their role needs — comp data, forecast visibility into territories they don't own, records from a business unit that was sold off. Admins can't safely revoke access without knowing what quietly depends on it, so the sprawl just keeps growing.

Symptom: Growth-stage software companies swap GTM tools often — comp planning, CPQ, marketing automation, conversation intelligence, RevOps analytics — and each one gets its own dedicated integration or API user at connection time. When a tool gets replaced, the integration user that authenticated it is rarely deactivated along with it.

What it costs: A stale integration user keeps standing API access, and sometimes broad object permissions, to a system nobody is monitoring anymore. It also counts against active-user totals the next time someone reconciles licensing.

Symptom: As the sales org restructures around new segments, territories, or an expansion motion, assignment rules and routing flows get added on top of the old ones instead of replacing them — because nobody wants to be the one who breaks live lead routing testing the removal.

What it costs: Leads land with the wrong rep, especially at territory or segment boundaries, or sit unassigned entirely. Reps end up chasing down misrouted leads by hand instead of the system catching it, and pipeline reporting reflects wherever the lead actually landed rather than where it should have.

Symptom: Fields and objects built for a pricing model the company has since changed, an ABM push that wrapped up, or a partner motion that got deprioritized stay on page layouts and reports long after the initiative ended.

What it costs: Reps scroll past dead fields on every record, new hires learn 'how we do things' from a layout that's years out of date, and reports mix data from the current motion with leftovers from the old one — making the numbers harder to trust than they should be.

Symptom: Flows, triggers, and webhooks get added one integration at a time — a CDP or data-warehouse sync here, a comp platform there, a marketing automation tool on top — without anyone tracking the cumulative daily API call volume all of them draw from the same pool.

What it costs: The org creeps toward its daily API limit, save performance degrades during peak hours, and integration sync jobs start failing intermittently in ways that get blamed on the vendor rather than the shared limit everything is competing for.

Symptom: Every SaaS tool connected to Salesforce — comp platforms, RevOps tools, data enrichment, forecasting — requested OAuth scopes at connection time. When the company swaps one out, which happens often while a software company is still iterating on its own stack, the old Connected App registration is rarely revoked along with the subscription.

What it costs: An unused Connected App with an active OAuth grant is exactly the kind of thing a SOC 2 review or security questionnaire flags, and each one left standing is a credential surface nobody is actively watching.