Can Evari integrate with custom or in-house systems?
Yes. Evari can integrate with custom and in-house systems, provided there is a mechanism to exchange data. This is one of the more common questions we get from brokers and MGAs who have built proprietary tools over the years.
What we need to integrate
If your system exposes an API (REST, SOAP, GraphQL), we can connect to it. During the Week 1 discovery phase, we will review your API documentation or work with your development team to understand the available endpoints.
If your system does not have an API, there are other options:
- File-based exchange — the assistant can read from and write to a shared folder, network drive, or SFTP location
- Email-based exchange — the assistant can parse structured emails or attachments that your system generates
- Database access — for internal systems, we can connect directly to the database with read or read/write permissions (requires your IT team's involvement)
What this costs
Custom integrations are included in the sprint cost. There is no separate integration fee. If a custom integration is unusually complex or requires significant back-and-forth with your development team, we will flag this during discovery and discuss whether it affects the sprint scope.
Long-term maintenance
Once the integration is live, it is maintained under your platform subscription. If your internal system changes and breaks the integration, we will work with you to update the connector. Depending on the change, this may be covered under standard support or may require a small follow-on engagement.
What if we are building a new system?
If your organisation is mid-way through building or migrating to a new system, let us know during discovery. We can design the integration with the new system as the target rather than the current one, or build a temporary bridge to the current system that can be replaced when the new one goes live.