A software implementation guarantee is usually discussed as a commercial term: money back if the work is not delivered. For the IT lead, it also has a technical side that nobody mentions in the sales meeting. If you ever need to use it, you will have to show what was delivered, stop using it, and return or delete it as the agreement sets out. That is far easier if the project was set up cleanly from day one.
This guide covers that technical side, using the terms of the SARVO Verified guarantee as the example.
What the software implementation guarantee actually says
On SARVO, the guarantee applies only when you hire a SARVO Verified partner through SARVO, and the clause is in your contract. Under it:
- the partner refunds 100% of the initial project fees if the agreed work is not delivered,
- you can also cancel in writing within the first 14 days, with no reason needed,
- the partner pays the refund within 14 days,
- if a refund is not honoured, SARVO reviews both sides and mediates. SARVO is not a party to the contract and does not hold payments; you pay the partner directly.
Not covered: work or licences already delivered and used, third-party software costs such as vendor subscriptions, requests made after the window, and partners who are not SARVO Verified. The full terms are on the SARVO Verified guarantee page. Confirm the clause is in your agreement before you sign.
The claim steps are all in writing: tell the partner, stop using the work and return or delete anything delivered as the agreement sets out, then receive the refund.
Why handover hygiene matters for a guarantee
"Stop using the work" is simple when the work is a document. It is harder when the work is configuration inside your production tenant, scripts running on a schedule, or integrations moving data every hour. If delivered work is tangled into live systems, it becomes hard to show what was delivered, hard to stop using it, and hard to agree what "used" means. Clean setup avoids that argument.
1. Keep accounts and ownership in your name
- Create the software tenant, subscriptions and admin accounts under your company's email domain.
- Give the partner named user accounts with the roles they need, not shared logins.
- Turn on audit logs where the product supports them.
If the partner leaves, you remove their accounts. Nothing else has to move.
2. Separate sandbox from production
- Ask for all build work to happen in a sandbox or test environment first.
- Promote to production only after you accept a deliverable in writing.
- Keep a simple change log: what was promoted, when and by whom.
This gives you a clear line between "delivered and accepted" and "in progress". It also makes the 14-day window easier to judge, because you can see what has actually reached you.
3. Write deliverables as checkable items
A guarantee is about whether the agreed work was delivered. Make the agreed work checkable:
- list each deliverable (for example, "lead capture form connected to CRM with duplicate check", not "CRM setup"),
- add a one-line acceptance test for each,
- record acceptance in writing, by email or a shared tracker.
4. Put code and scripts in a repository you own
Custom functions, integration scripts and report definitions should be stored somewhere your company controls, with history. If a claim is ever needed, the repository shows what was delivered. If the project goes well, it is your documentation.
5. Keep data movement reversible
- Run trial migrations into the sandbox, not production.
- Keep exports of source data before each migration.
- Document any integration that writes into another system, and how to switch it off.
6. Know which costs sit outside the guarantee
Vendor subscriptions and other third-party software are not covered. Keep those purchases separate from the partner invoice, ideally bought directly by your company, so it is obvious which payment is initial project fees and which is a licence.
7. Plan the first 14 days deliberately
Use the walk-away window to see how the partner works, not just to wait:
- kickoff with the named delivery team,
- sandbox access granted to you,
- a first written plan and deliverables list,
- one early deliverable you can inspect.
If something feels wrong, you have a written, no-reason exit inside the window.
A quick checklist
- [ ] Tenant and admin accounts in your company's name
- [ ] Named partner accounts, audit logs on
- [ ] Sandbox for all build work
- [ ] Deliverables list with acceptance tests
- [ ] Code and scripts in your repository
- [ ] Source data exported before migration
- [ ] Licences bought separately from project fees
- [ ] Guarantee clause confirmed in the contract
The same hygiene makes any project easier to manage, guarantee or not. For the migration part, SARVO's data migration checklist for ERP and CRM is a good starting template.
If you want a partner who offers these terms, send a free matching request on the guarantee page and filter for SARVO Verified partners.
Disclosure: I work on SARVO.
Top comments (0)