Selected work by our team during its LuckyTruck engineering tenure, 2021–2024. The case describes that contribution; LuckyTruck’s current product has continued to evolve.
The CRM was part of the product
A customer-facing application is only one part of insurance delivery. Operations teams also need the account, drivers, vehicles, application details and resulting quotes in the tools they use to serve customers. A disconnected form leaves agents reconciling records between systems.
Our contribution spanned platform services, Salesforce code and Zoho widgets. The integration surface included quote creation, quote status updates, related fleet records and document workflows. This was product engineering across systems, rather than a standalone marketing website.
What we connected
| System | Our contribution | Why it mattered |
|---|---|---|
| Salesforce | Apex services, platform synchronization and quote/policy integration using Node.js and jsforce. | Keep CRM operations connected to the customer’s insurance journey. |
| Zoho CRM | Embedded quote and certificate widgets, related-record lookup and platform integrations. | Let agents begin work from the account and fleet information already in their CRM. |
| CoverWhale | Quote workflows connecting application information with carrier quoting steps. | Carry insurance information through the carrier journey and return usable quote information. |
| Progressive | Application and quote workflow automation with fleet and driver information. | Connect carrier-specific steps to the wider platform and operations process. |
From CRM record to quote workflow
- Load the account and its related drivers, vehicles and insurance information.
- Prepare the application information required by the selected carrier workflow.
- Run the appropriate integration and expose progress to the user.
- Connect quote information and subsequent status changes back to the platform and CRM.
- Keep certificates, documents and follow-up work connected to the customer record.
Different integration surfaces needed different tools
The archived implementation includes Salesforce Apex and Aura components, jsforce, Zoho’s embedded-app APIs, REST endpoints, GraphQL services and browser automation using Playwright. These served different parts of the system. Carrier integrations included both service calls and automated application journeys; we do not describe every carrier connection as a direct API partnership.
The important boundary is the business operation: requesting a quote, receiving a result, updating a record or preparing a document. Each has different inputs and failure states. A new implementation should define the system of record, duplicate handling and recovery before allowing automation to write business-critical data.
This experience is relevant to teams extending an existing CRM. A focused service or embedded tool can connect the missing workflow while letting staff keep their familiar workspace. A full CRM replacement is a separate decision.
A connected operating workflow
The delivered scope brought carrier quoting and internal insurance work into the same product ecosystem. Customer-facing software, CRM users and backend services could participate in the insurance journey instead of treating each integration as an isolated tool.
This is a qualitative account of delivered capability. Carrier names identify systems we worked with, not certifications, endorsements or a claim of an ongoing partnership.
Continue exploring
- Documents, signing and SAFER data
- How the AWS platform was delivered
- Extend existing tools or build custom software?
