How to rescue a failed Salesforce implementation
How to tell whether a Salesforce project can be saved, what to do in the first two weeks, and how to decide what to keep, fix or rebuild.
Read the full post →Salesforce implementations usually fail for a handful of reasons: requirements that were never agreed, a design built around the tool instead of the process, poor data migration, too much custom code, no owner on the client side and too little training. Most failed projects can be recovered without starting over once those causes are identified.
A review of the build, data and original scope to separate what works from what does not.
Urgent fixes so the business can operate while the plan is agreed.
A clear decision for each component, avoiding a full restart where possible.
Delivery of the remaining scope with documentation your team can maintain.
Training and adoption support so users give the system a second chance.
Written by the consultants delivering the work.

How to tell whether a Salesforce project can be saved, what to do in the first two weeks, and how to decide what to keep, fix or rebuild.
Read the full post →Yes. An industrial-services firm had paid a previous partner over $100,000 for a Field Service build it could not use. Within a 20-hour engagement we fixed the multi-day scheduling errors and eliminated per-worker licensing for 75–100 laborers.
Rarely. Most failed implementations have usable parts. The assessment decides what to keep, what to fix and what to rebuild.
We begin with a short assessment so we understand the build before promising a plan. Stabilization fixes can often start while the full recovery plan is being agreed.
Yes. We recovered a broken Pardot instance for a medical-device company, removing 970+ invalid records, and salvaged a failed two-year Tableau investment for an advocacy agency.
Headquartered in St. Louis, working with companies across the U.S.
Get Salesforce help →