Assess · Implementation rescue
Salesforce and HubSpot implementation rescue
For a stalled or failed CRM rollout. A senior consultant finds the root cause, sorts every component into keep, fix, rebuild or retire, and prices the recovery as fixed sprints, so you know what can be saved before you spend more.
Short answer
Vantage Point rescues stalled or failed Salesforce and HubSpot implementations. A two-week diagnosis finds the root cause, classifies every finding as a people, process or technology problem, and puts each component on a keep, fix, rebuild or retire register. Recovery is then priced as fixed sprints that you approve one at a time. You can start with a Free 45-minute Expert Review with a senior consultant.
Why CRM implementations fail
Most failed rollouts we're asked to look at still run on a working platform. The usual causes are people and process: nobody inside the firm owns the system, requirements were never agreed in writing, or training stopped at go-live. Technology problems are real too, mostly custom code nobody can explain and integrations that fail without anyone noticing.
That's why our diagnosis classifies every finding as a people, process or technology problem. You see why the project went wrong as well as which parts are broken, and the recovery plan includes the ownership and training work that keeps it from happening again.
Signs you need a rescue
People
- The previous partner or your admin has left, and nobody can say how the system was built.
- Advisors, loan officers or reps have gone back to spreadsheets and email.
- Leadership has stopped trusting the dashboards and asks for numbers by hand.
- Training ended at go-live, and new hires learn from whoever sits next to them.
Process
- Go-live has slipped twice, or there's no date anyone believes.
- Requirements were never written down or signed off, so every meeting reopens scope.
- Each team defines a lead, a stage or a client differently.
- Compliance approvals and supervision still happen outside the system.
Technology
- Custom code, flows or HubSpot workflows break when anyone changes a field.
- Integrations fail quietly, such as a custodian feed, a loan origination sync or the HubSpot and Salesforce connector.
- Duplicate records and missing data make reports unreliable.
- You pay for licenses, hubs or seats nobody uses.
Inherited systems
- You inherited an org or portal through an acquisition and don't know what's in it.
- For wealth firms this is often a Financial Services Cloud org built by an acquired advisory practice.
If three or more of these sound familiar, start with the Free 45-minute Expert Review. A senior consultant goes through your self-assessment results with you and follows up with three written recommendations, including whether you need a full rescue or a smaller fix.
The keep, fix, rebuild or retire register
The main output of the diagnosis is a register with one line for every component we review: objects and data model, automation, integrations, security and permissions, reports and dashboards, and installed apps. Each line gets one of four verdicts.
| Verdict | What it means | Typical example |
|---|---|---|
| Keep | Works as designed and is used. Leave it alone. | Page layouts reps fill in without complaint |
| Fix | Right idea, wrong setup. A targeted change fixes it. | Lead routing that sends leads to the wrong territory |
| Rebuild | Can't be fixed in place without more risk than starting that part again. | Person Accounts never configured in a B2C lending org |
| Retire | Not needed, or replaced by something better. Remove it and archive the data as agreed. | An unused app still charging license fees |
Each line also shows the reason, the people, process or technology root cause, the effort, and who on your side owns the decision. You approve the register before any recovery work is priced, so nothing gets rebuilt that could have been kept.
How a rescue runs: four phases
1. Diagnose (two weeks)
This phase is the Implementation Rescue package. The package page is the scope sheet, with what's included and what isn't.
What you get
- A root-cause review, with every finding classified as people, process or technology
- An inventory of what works, what's broken and what's missing
- The keep, fix, rebuild or retire register
- A recovery plan priced as fixed sprints, presented in a decision meeting with your leadership
What your team provides
- A project owner with decision authority, available 2 to 4 hours a week
- Admin access to the org or portal, and a sandbox or test environment where the platform supports one
- The original statement of work, requirements and design documents, and whatever the previous partner handed over
- Short interviews with a few users from each role that uses the system
2. Stabilize
What you get
- Fixes for anything that stops daily work or creates compliance risk, such as failed syncs, broken automation, permission gaps or opt-outs not carrying over
- A change freeze on everything else until the recovery plan is approved
- A weekly written status
What your team provides
- Approval of each fix within 3 business days
- One place for users to report problems, so issues aren't lost in email
3. Rebuild
What you get
- Fix and rebuild items delivered in fixed sprints, each built in a sandbox, tested and deployed to production
- Retired components removed, with their data archived the way you agreed
- One supported user acceptance testing cycle per sprint
What your team provides
- Subject-matter experts for each process in scope, available for design sessions
- Source data exported in the agreed format by the dates in the plan
- User acceptance testing sign-off within 3 business days of each request
4. Hand over
What you get
- Recorded, role-based training and a training guide for each audience
- Admin documentation: a configuration log, a runbook and a field or property dictionary for what we built
- 30 days of hypercare after go-live
- An adoption check at the end of hypercare against the goals agreed in the diagnosis
What your team provides
- A named internal owner for the system after we leave
- Users' time for training sessions
- A decision on ongoing support: none, a block of hours, a retainer or managed services
What drives the effort
| Keeps effort down | Raises effort |
|---|---|
| The original requirements and design documents still exist | Nothing was written down and the previous partner is gone |
| One production org or portal | Several orgs or portals to merge, often after an acquisition |
| Mostly configuration | Large amounts of custom code with no tests |
| A decision maker who answers within days | Approvals that need a committee every time |
| Data in one exportable system | Data spread across spreadsheets, old CRMs and inboxes |
What we've rescued
National mortgage lender, 33 branches. A failed Financial Services Cloud rollout from another vendor, rescued and rebuilt. Read the case study.
Regional insurance brokerage. 100% login at go-live after three failed CRMs. Read the case study.
Vantage Point has delivered 700+ engagements for 175+ clients since 2018 with senior consultants, and holds a 4.7/5 AppExchange rating from 19 reviews. See mortgage lending and insurance.
Smaller problems, smaller packages
Not every stalled system needs a rescue. If the Expert Review points to a narrower problem, these fixed-price options cover it:
- Salesforce Org Assessment, $5,000
- HubSpot Portal Audit, $3,500
- Block of Hours: 40 hours, $8,000 per block for Salesforce work or $7,000 for HubSpot
See every assessment and add-on on Assess & add-ons, or read how a CRM health check works.
Implementation rescue questions
How do I know if our implementation can be saved?
The two-week diagnosis tells you. In the failed rollouts we review, the platform usually works and the problems sit in ownership, requirements and a few broken components. Every component goes on a keep, fix, rebuild or retire register, so you see how much is salvageable before you commit to recovery work.
How long does a Salesforce or HubSpot rescue take?
The diagnosis takes two weeks. Recovery then runs as fixed sprints, and the number of sprints depends on the register: an org or portal with mostly fix items needs fewer sprints than one with several rebuilds. You see the sprint plan at the end of the diagnosis.
How much does an implementation rescue cost?
The diagnosis is quoted in writing after a short scoping call, because the effort depends on your systems and data. Recovery is priced as fixed sprints, and you approve each one before it starts. For narrower problems, the Salesforce Org Assessment is $5,000 and the HubSpot Portal Audit is $3,500.
Will you deal with our previous implementation partner?
We'll review anything they handed over and can ask them factual questions with your permission. Disputes and contract conversations with a previous partner stay between you and them, and they're outside the package.
Do you rescue HubSpot implementations as well as Salesforce?
Yes. The same diagnosis and register apply to HubSpot portals, including broken workflows, lifecycle stages that don't match how sales works, and a HubSpot and Salesforce connector that overwrites data.
Should we switch platforms instead of fixing the one we have?
Sometimes, but rarely as the first answer. We'll tell you if the register shows that a move would cost less than recovery, for example a small team on Salesforce that would run more easily on HubSpot. See Salesforce to HubSpot migration.
What does compliance need during a rescue?
Records your firm must keep stay intact and in place until they're archived the way your retention rules require. We configure supervision, approval and archiving controls, and your compliance team approves them.
Scope, inclusions and exclusions for the diagnosis are on the Implementation Rescue package page. Updated October 6, 2026.