Viedoc: from first contact to signature in 39 days, after a partner left.
A big partner launched Salesforce for 52 users and left. We took it over as a Run engagement: full review and fixes in the first week.
What was there
A clinical-trials software company in Sweden. A large partner had launched Salesforce for 52 users and left: nobody used forecasting, changes went straight to production, there was no documentation, and purchased AI features had never been switched on.
What we did
Took the org over as a Run engagement: a full system review and the obvious fixes in the first week, then a queue with a release process. The client's legal and security teams reviewed and signed off before go-live; a documented extension layer around the purchased package keeps the org readable by any partner after us.
What came out
From first contact to signature in 39 days. A $31,680 engagement with a team of five, two of them non-billable. The org has an owner, a release process and documentation.
What we say out loud
There was an expectation gap at the start: the client bought a team and expected a managed service. We levelled it within a month, and that is how Run became the model for this account. Our best-documented example of the "previous partner did not finish" trigger.
What the client needed from a partner.
A large partner had left after launching 52 users. Legal and security had to sign off before anyone touched the org, and the client wanted a full review in the first week, not a discovery phase. The whole engagement had to fit a $31,680 budget with a named team.
What happened next
Run became the model for the account: a monthly queue with a release process, documentation any partner after us can read, and a verified review from the Global Head of Sales Operations in September 2026.
How the weeks went.
First contact
The previous partner has left; forecasting unused, changes going straight to production.
Signature
Legal and security review passed with documents; a team of five, two non-billable.
Full review
The whole org read, the obvious fixes shipped, a queue written down.
Run
A release process where there was none; unused hours roll over one month.
Who did the work.
Named in the proposal, the same people from kickoff to release.
Roles on the project
- Lead engineer
- Salesforce developer
- QA engineer
- Project manager
- Account lead
Stack
Sales Cloud, forecasting, Flow, a purchased package with a documented extension layer; a release process where there was none.
For a small team, having a partner who tidies up as they go rather than adding to the pile is worth a great deal.
Other clients, other numbers.
Plus $53,000 a year of manual work removed. Payback in 2.7 months.
Read the case GoodLeapLending · mortgage0 incidentsin 13 changes to a live lending system, each one tested and reversibleWork that used to take 6–12 months now ships in weeks.
Read the case 49 FinancialWealth management · custodian & reporting−40%client onboarding time, with every custodian's data in one placeAdvisers 60% more productive with one client view. No lock-in to the package.
Read the case Keep Texas BeautifulNon-profit · Texas−95%data errors across 100,000+ recordsValidation rules and cleanup. For a non-profit, a bad record is a donor relationship, not cosmetics.
Read the caseMake your Salesforce earn.
Thirty minutes, one hypothesis about your business, no pitch. We reply within one business day.
One reply from a person, within one business day.