Salesforce optimization consulting in St. Louis.

Rarely. Low use is usually a design problem inside the org, not a platform problem. Record pages ask for too much, reports do not match what reps see and nobody retrained people after the last change. We interview a few users in each role, often at your site, and fix the steps that cost them the most time. A rebuild only makes sense if the underlying data model is wrong for how the business works.

Yes, and it is one of the most common tasks in an optimization project. We list every automation on each object, identify overlaps and conflicts, then rebuild the logic in a smaller number of well-documented Flows. Testing happens in a sandbox with realistic records before anything moves to production, and the old automation is deactivated only after the new version has run cleanly.

We weigh each issue by how many people it affects and how much it distorts the numbers leadership uses. Duplicate accounts and broken stage definitions usually come first because they undermine every report. Layout and usability fixes follow, then automation cleanup. You approve the order, and each batch of changes is released and explained to users before the next one begins.