Find out what’s actually failing before you spend more money fixing the wrong thing.
When Salesforce isn’t trusted, the business feels it before anyone can explain it. I help companies investigate Salesforce data, automation, reporting, adoption, and org complexity so leadership can decide on evidence ...not guesses.
Most Salesforce problems don’t start as clean tickets. They start as complaints.
Messy as they sound, they usually point to real business risk. The diagnostic turns vague frustration into specific findings.
- “The dashboard is wrong.”
- “This field keeps changing.”
- “Nobody knows what automation is firing.”
- “We can’t trust the data.”
- “Our admin is afraid to touch anything.”
- What’s happening ..and what’s likely causing it
- What evidence supports that conclusion
- What risk it creates, and what to fix first
- What should not be touched yet
- What needs business validation
- What leadership needs to decide
A field that keeps changing, records reassigned overnight, a report showing unexpected numbers, a Flow firing when it shouldn’t. Built for speed and focus: one issue, one focused investigation, one practical next-step plan.
The object & fields, relevant Flows, Workflow Rules, Process Builder, Apex, validation & assignment rules, scheduled jobs, integration users, field history, reports, layouts.
- A plain-English summary of the issue
- Likely root causes, ranked by likelihood
- Evidence to collect or validate
- Immediate risks
- A clear next-step plan
Once people stop trusting the data, the real work moves into spreadsheets and private reporting. This audit finds out why trust is breaking down, for teams where the data is being challenged by users, Finance, Sales, Operations, or leadership.
Critical fields & objects, field history, automation touching those fields, integration users, scheduled jobs, duplicate/merge behavior, formula & roll-up fields, reports, ownership, source-of-truth decisions, auditability gaps.
- Executive summary
- Ranked root-cause hypotheses
- Metadata evidence
- Data-trust risk findings + auditability assessment
- Recommended monitoring & fixes
- A remediation roadmap
Old Flows, Workflow Rules, Process Builders, Apex, scheduled jobs, rules built for a process that changed two years ago - automation becomes invisible infrastructure, and that creates risk. This audit maps it and identifies what’s creating that risk.
Record-triggered, scheduled, autolaunched & screen Flows, Process Builder, Workflow Rules, Apex triggers & scheduled Apex, approval & assignment rules, managed-package automation, field updates, and their dependencies.
- Automation inventory + execution map
- Field-update matrix
- Conflict analysis
- High-risk & retirement candidates
- A sandbox test plan
- Recommended future-state direction
Some orgs carry years of decisions - objects, fields, record types, packages, automations built by people who’ve left. Not anyone’s fault, but still risk. The baseline gives leadership and the team a clear view of the current state before any major change.
Objects, fields, Flows, reports, dashboards, record types, layouts, profiles, permission sets, roles & sharing, installed packages, legacy automation, metadata complexity, inactive-user ownership risk.
- Executive summary
- Metadata risk heatmap
- Top findings + highest-risk areas
- Complexity & automation concentration
- Installed-package footprint
- Recommended next projects + priority roadmap
Cleanup sounds simple - it isn’t. Deleting fields, retiring record types, or consolidating automation creates real risk if nobody knows what depends on what. For teams that already know the org is cluttered and need a disciplined path to simplify it safely.
Field, record-type, page-layout & picklist rationalization, report cleanup, automation & integration impact, source-of-truth decisions, business-validation questions, retirement & migration planning.
- A cleanup backlog
- Source-of-truth recommendations
- Duplicate/overlap & retirement candidates
- A “do not touch yet” list
- A sandbox test plan
- Rollout recommendations
Find the situation that sounds like you.
Each path points to the right first engagement - tap one and we’ll take you straight to it. Not sure? The opening call sorts it in minutes, even if the answer isn’t us.
You have one urgent, specific issue; a field keeps changing, a report’s wrong, records are being reassigned.
The real problem is trust in the data; teams don’t believe the reports, Finance and Sales disagree, people work from spreadsheets.
It’s about automation; Flows, Process Builder, Apex or scheduled jobs fire unexpectedly and overwrite fields nobody touched.
You need the big picture before changing anything; a new team inherited the org, docs are weak, a migration or release is coming.
You already know it needs simplifying; and want to clean it up without breaking reports, automation, or integrations.
Still not sure which path is yours? Book a quick call and we’ll identify the right first step together.
Clear scope. Clear output. Clear next step.
Start with the complaint
What are users saying, what are managers challenging, what is leadership worried about? Clear complaints create clear diagnostic paths.
Define the scope
One object and a few fields for a quick triage; a broader process or whole-org baseline for a deeper audit. No vague consulting sprawl.
Inspect the evidence
Metadata, automation, fields, reports, permissions, integrations, audit trails. The goal isn’t to document every corner. It’s to find what matters.
Separate symptoms from causes
A reporting problem may really be a data-definition problem; an adoption problem may really be a workflow problem. Both matter, they’re not the same thing.
Deliver findings & next steps
Written for both business and technical audiences: evidence, priority, next steps. No panic, no blame theater, no generic recommendations.
Who this is for
Business and technology leaders who need clarity before expensive Salesforce decisions.
- CEOs, COOs, CFOs, CIOs, CROs
- RevOps, Sales Ops & IT leaders
- Salesforce platform owners, admins & analysts
- Teams prepping for cleanup, migration, or remediation
Who this is not for
Probably not the right fit if you want…
- Generic Salesforce training
- Someone to blindly defend Salesforce
- To justify a replacement you’ve already decided
- A quick opinion without evidence
Before we talk.
Do we need to know the root cause before contacting you?
No — that’s the point of the diagnostic. You need a clear complaint, business impact, and access to people who can explain what they’re seeing.
Can you work with our internal admin or IT team?
Yes - usually the best path. Your team knows the history and politics; I bring structure, diagnostic discipline, and an outside perspective.
Will this turn into a huge open-ended project?
Not by default. The first engagement is contained. If deeper remediation is needed, it can be scoped separately.
Do you only recommend staying on Salesforce?
No. Sometimes it should be fixed, sometimes rebuilt, sometimes the operating model changes - and sometimes replacement is reasonable. The mistake is deciding before diagnosis.
What access do you need?
It depends. Triage may need screenshots, examples, and a guided screen-share; deeper audits may need Salesforce access or structured metadata review. Discussed during scoping.
Can you use AI-assisted tools during the diagnostic?
Yes, where useful - AI-assisted metadata review can speed up the investigation. But AI isn’t the diagnosis. The tool surfaces suspects; the work is deciding what the evidence means.
What a diagnostic actually changed.
Start with diagnosis.
If your team is arguing about whether Salesforce is broken, prove what’s actually failing first.