A delayed or underperforming Salesforce programme does not always need to be abandoned. A structured review can reveal whether the blockage sits in governance, processes, data, technology, capacity or a combination of all five.
A Salesforce transformation rarely stalls because of one dramatic failure. More often, progress slows through a series of smaller problems. Decisions take too long, ownership becomes unclear, data work expands, employees lose confidence and the original outcome becomes buried beneath technical tasks.
By the time leaders recognise the programme is in difficulty, the organisation may already have invested substantial time and money. That can create pressure either to keep moving without resolving the underlying issues or to replace the system and start again.
Neither response should be automatic. The more useful first step is an independent, outcome-led review of what is happening and why.
What does a stalled Salesforce project look like
Not every delay means a project is failing. Transformation programmes need to adapt as teams learn more about their requirements. However, several warning signs suggest the organisation needs to pause and reassess.
- The launch date keeps moving without a clear explanation.
- Different departments have conflicting expectations of the platform.
- Nobody has authority to resolve scope or process decisions.
- Data migration is larger or less reliable than expected.
- The solution depends on manual workarounds that were meant to disappear.
- Employees are disengaged or continuing to use spreadsheets and legacy systems.
- Reports do not answer the questions leaders expected them to answer.
- New integrations or applications are being added without a coherent architecture.
- The implementation partner is delivering tasks, but the organisational outcome remains unclear.
Do not begin by buying more technology
When a programme is under pressure, a new application or product can feel like a route around the problem. Sometimes an additional technology is genuinely required, but it should follow diagnosis rather than replace it.
The charity needs to understand whether the blockage is caused by the platform, the way it has been configured, the quality of the data, the operating model or the decisions surrounding the programme. Adding more technology before answering that question can increase cost and complexity without improving the outcome.
A practical recovery review
A recovery review should be proportionate to the project and focused on decisions. It is not an exercise in producing a long report that repeats what the organisation already knows.
Return to the intended outcome
The review should establish what the programme was meant to improve. Was the objective better fundraising insight, more reliable service information, reduced administration, improved supporter engagement or a connected view across teams? The answer provides a test for every subsequent recommendation.
Clarify governance and ownership
The charity should identify who sponsors the programme, who owns the key processes and who can approve changes to scope, cost and design. Delayed decisions are often a symptom of unclear accountability rather than a lack of effort.
Review the operating processes
A system cannot compensate for unresolved ways of working. The review should examine how teams currently operate, where information changes hands and where different departments follow different rules for the same activity.
Assess the data honestly
Duplicate records, inconsistent fields, missing consent information and disconnected data sources can hold back implementation and undermine reporting. The charity needs an evidence-based understanding of the work required rather than an assumption that all available data can simply be imported.
Examine the technical design
The review should consider configuration, custom development, security, integrations, reporting and the wider technology landscape. This is where an experienced partner can determine whether Salesforce remains the right foundation and whether an integration platform or different architecture would simplify delivery.
Understand readiness and capacity
Even the right design can fail if the organisation does not have enough time, skills or confidence to adopt it. The recovery plan should therefore include realistic responsibilities for testing, training, decision-making and ongoing ownership.
How an end-to-end partner helps
A conventional systems integrator may be asked to configure the agreed technical requirement. A transformation partner needs to go further: challenging whether the requirement solves the real problem, identifying what must change around the system and remaining accountable for how the pieces fit together.
Sweet Potato Tec combines strategic advisory, Change Enablement for Non-Profits, Salesforce delivery, data engineering, integration and managed services. This allows the recovery plan to move from diagnosis into implementation without losing the reasoning behind the recommendations.
In one animal-welfare programme, for example, the challenge involved far more than moving data into Salesforce. Operational consultancy helped identify the people, process and training issues. Sweet Potato Tec then recommended an integration-led approach using Boomi, implemented the solution and created a scalable foundation for fundraising information. The value came from joining the operational and technical thinking rather than treating either in isolation.
Bringing commercial innovation into the nonprofit sector
Sweet Potato Tec works across nonprofit and commercial organisations. That provides visibility of technology and operating approaches that may develop more quickly in commercially competitive environments.
The aim is not to import commercial practice without considering the charity’s mission, governance or resources. It is to identify proven ideas that can be adapted responsibly: better automation, faster testing, clearer data models, more useful analytics and structured approaches to continuous improvement.
For charities, this can reduce the time spent solving problems that other sectors have already addressed while ensuring the eventual design reflects nonprofit realities such as Gift Aid, restricted income, safeguarding, volunteer management and sensitive supporter data.
What a useful recovery roadmap should contain
- A clear statement of the outcome and the reasons progress has stalled.
- Immediate actions needed to protect data, service delivery or fundraising.
- Decisions required from leadership and named owners for each one.
- A prioritised plan covering people, processes, data and technology.
- Work that should stop, continue or be redesigned.
- Realistic phases, costs, dependencies and success measures.
- A plan for adoption, training and support after release.
The objective is not simply to get the project moving again. It is to make sure it is moving towards an outcome the charity still needs.
A stalled project can still become a strong foundation
A pause can be uncomfortable, particularly when leaders are under pressure to demonstrate progress. However, continuing with an unclear design or unresolved operating model can create a much more expensive problem later.
A focused review gives the charity a chance to recover the useful work already completed, correct what is holding the programme back and rebuild confidence around a practical plan.
Sweet Potato Tec helps charities assess Salesforce programmes that are delayed, underperforming or no longer aligned with organisational priorities. The starting point is not a predetermined product. It is understanding what outcome has become stuck and what needs to change to unlock it.