You implement the system their whole business runs on
An ERP or CRM implementation touches sales, finance and operations at once, so when something goes wrong, whether it's a go-live that fails, a migration that corrupts customer records, or a customisation that breaks on the next platform release, the exposure is bigger than the fee. Professional indemnity and cyber cover, built for implementation work.
Where an ERP or CRM consultant actually gets exposed
Your risk scales with what the system touches. If a rollout, migration or customisation you delivered stops a core business process, that's a professional indemnity claim, and standard business cover won't answer it.
The go-live that broke order-to-cash
You lead a cutover to a new ERP system for a client. A configuration issue in the new environment means invoices stop generating and orders stop flowing for weeks after go-live.
The client's cash flow is disrupted, and they argue a properly tested cutover would have caught it.
The migration that duplicated the customer base
You migrate the client's customer and financial records into the new CRM. A logic error in the migration duplicates and mismatches thousands of records.
Sales and finance teams can't trust the data, and the client seeks the cost of the clean-up and the disruption.
The customisation that broke on the next release
A custom integration or field you built into the client's system conflicts with a platform update, breaking a core process the business relies on daily.
The client says the customisation should have been built to survive routine platform updates.
Who's going to ask you for it
It's a condition of being an implementation partner
For ERP and CRM consultants, cover is frequently a gate to doing the work at all:
- Partner programs. Certified implementation partner status with Salesforce, SAP and similar platforms often requires proof of professional indemnity.
- Enterprise implementation contracts set minimum PI and cyber limits given the scale of business processes touched.
- Prime-subcontractor arrangements on government projects flow their own insurance requirements down.
The exclusion ERP and CRM consultants assume is covered
If Salesforce or SAP itself goes down, that's a platform outage and it isn't your problem. But a claim that your configuration or customisation caused the process failure is squarely on you, and it's usually what the client actually alleges.
Liquidated damages in fixed-price contracts for a late go-live are also typically excluded beyond your actual legal liability.
Common questions
If the platform itself goes down, is that on me?
No. The platform vendor's own infrastructure outages sit with them. But how you configured and customised the system is on you, and that's usually what a client's claim actually targets.
Isn't this just professional indemnity?
PI is the core, but implementations typically involve migrating full customer and financial datasets, so cyber exposure is significant. ICT cover combines professional indemnity with cyber so there isn't a gap between policies.
What limit should I get?
Match it to your partner program requirements or the client's contract. Enterprise implementations often name $5M or more. If you're unsure, we'll read it with you before you buy.
A partner program needs a certificate of currency, how fast can I get one?
Once you're bound, a certificate is quick to issue. If your partner status is waiting on it, tell us and we'll prioritise it.
Does it cover an implementation I delivered before I was insured?
Professional indemnity is claims-made and usually responds to claims first made while you're insured, provided the issue wasn't already known to you. It's best to have cover in place before a dispute surfaces.