How to choose a Salesforce consulting partner after a failed project

Why the second project is different

The first time, you bought a vision: a partner's deck, a transformation, a roadmap. The second time you are buying something narrower and more useful: a specific result from specific people, with a way out if it goes wrong. That changes what to ask. Logos and certifications told you nothing the first time; they will tell you nothing now. What you need to know is who, how, and what you keep.

Seven questions, and the answers to watch for

1. Who exactly will do the work?

By name, in the proposal, with the promise that they do not rotate out. The answer to watch for is "our team of certified experts". A team is not a name. If the senior person on the sales call is not on the project, ask who is, and ask to meet them before you sign.

2. What happens to a change before it reaches production?

You want to hear: a development environment, a test environment, user acceptance testing by your people, a release window you choose, a rollback tested beforehand, and a change record. The answer to watch for is "we are agile", which often means changes go straight to production on a Friday.

3. What do we keep if we leave?

Documentation of what was built, an org another partner can read, the data dictionary, the integration mappings, the runbooks. The answer to watch for is "it depends", or a knowledge base that lives in the partner's tools. If you cannot leave, the partner has no reason to stay good.

4. What is the smallest thing we can buy first?

A diagnostic with a document at the end, and a first fix with a named result in a fixed time. The answer to watch for is a free discovery phase. Free discovery is paid for by the project that follows it and sized to make that project large. A paid diagnostic credited against the fix has the opposite incentive: the report has to be useful on its own.

5. What is in your hours that is not in the cheaper quote?

Test environments, user acceptance testing, rollback, documentation, a project manager if the scope needs one. Two quotes for "the same" work usually differ by exactly those hours. The cheaper one often is the expensive one.

6. Which documents can you send our legal and IT today?

Registration documents, an NDA signed by every team member, a liability statement, a data-access scheme, answers to a security questionnaire within a known number of days. The answer to watch for is a delay. A partner who has done this before has the pack ready.

7. What will you say no to?

A good partner has a list: products they have not shipped, industries they do not claim, AI features they will not switch on before the data is ready. The answer to watch for is "we can do anything". At GoodLeap, Service Cloud Voice and Agentforce were discussed and scoped, and not contracted; the case study says so. That sentence is worth more than a logo wall.

How to buy two weeks instead of a year

Structure the second engagement so that every step is small enough to stop after. First, a diagnostic: five days, read-only access, a report you own, a fixed price credited against what follows. Second, one fix with one named result in two weeks, priced before it starts. Third, only if the first two worked, a backlog in two-week streams with the same team. At every step you have a document, a result, and a decision. A year-long contract with a partner you have not watched deliver is how the first project went wrong.

What this looked like at Viedoc

A clinical-trials platform in Sweden, 52 Salesforce users, launched by a large partner who then left. Trust was low and the legal and security review was thorough; from first contact to signature took 39 days. The engagement started with a full review in the first week, not a roadmap. Then fixes, then the HubSpot integration, then the account lifecycle automated. The client's Global Head of Sales Operations later wrote that for a small team, having a partner who tidies up as they go rather than adding to the pile is worth a great deal. That is the review a second project should earn.

A short checklist to take into the call

1. Names, not a team.
2. Environments, testing, rollback, change record.
3. What we keep.
4. Smallest first purchase, with a document.
5. What is in the hours.
6. Documents for legal and IT, by when.
7. What they say no to.

What to put in the contract

1. The named team, and that substitutions need your approval.
2. The release process in one paragraph: environments, testing by your people, a rollback path, a change record per release.
3. Documentation and the org belong to you, delivered at every milestone, not at the end.
4. Fixed prices per package, and what moves them.
5. A way out at every step: the diagnostic stands alone, the first fix stands alone, nothing requires the next step.

A partner who has been burned by clients will negotiate the details. A partner who objects to the principles is telling you something.

Our answers to all seven are on the Health Check, pricing and security and compliance pages. Ask us the questions anyway.