Rocket Lawyer · Co-Branded Partner Sites
Rocket Lawyer · Co-Branded Partner Sites
Case Study · Rocket Lawyer
One integration. Six months. How we launched Rocket Lawyer's first enterprise partnership and built a platform for the next ten.
11.5M+
Partner Customers
16%
EU Traffic Driven
New Channel
Enterprise Revenue
Context & Mission
Rocket Lawyer was entering a new phase: expanding beyond direct-to-consumer and proving an enterprise distribution model across Europe. Covéa, an insurer with 11.5M customers, was the first major test. What we built for this launch would determine whether Rocket Lawyer could scale its legal services through partners, unlock new revenue channels, and support future deals already in the pipeline.
Covéa's scale and complexity meant the work had to support multiple identity flows, distinct brand requirements, and usage tracking at the partner level. A one-off integration wouldn't be enough. We built toward a model that could support future partners, new markets, and more advanced commercial structures.
This work extended Rocket Lawyer's mission, affordable, accessible legal help, to millions of insurance customers who previously had limited access to digital legal services.
Who we were serving
We were building for customers who would enter Rocket Lawyer through Covéa's ecosystem. The experience needed to feel native, secure, trustworthy, and co-branded while still delivering Rocket Lawyer's full value.
Designing for partners, not one-offs
We framed Covéa as the first of many enterprise integrations. Every decision optimized for durability over convenience, knowing future integrations would benefit.
Anchoring on OpenID Connect set us up for long-term partner scalability, but meant absorbing short-term complexity to support Covéa's existing identity system. We built a custom connector to isolate edge-case logic.
Runtime control over branding, pricing, features, and content, no release cycles required. The Partner Config API became the single surface for partner onboarding.
A flexible UI and pricing framework that adapted to partner value propositions while preserving Rocket Lawyer's product integrity. Partner-exclusive content coexisted with the core catalog.
Partner-aware reporting and analytics drove billing accuracy and business insights. The unified integration layer was designed to support additional partners without rearchitecting.
What we actually shipped
These became the reusable building blocks for partner expansion:
Enabled partner customers to access Rocket Lawyer without creating new accounts. Built on OpenID Connect to keep identity ownership with the partner and reduce sign-up friction.
An integration layer that handled partner-system exceptions (like Covéa's non-OIDC setup) without breaking platform principles. It isolated edge‑case logic while keeping future partner integrations predictable.
A single surface for controlling branding, pricing, features, and content at runtime. This removed the need for release cycles, accelerating partner onboarding and iteration.
A flexible UI and pricing framework that adapted to partner value propositions while preserving Rocket Lawyer's product integrity. It set the foundation for differentiated models across partners.
A curated set of partner-specific documents and workflows colocated with Rocket Lawyer's legal tools. This gave customers a single, coherent place to complete partner and legal tasks.
Partner-aware event tracking that powered dashboards, billing, and performance reviews, supporting expansion opportunities and strengthening Rocket Lawyer's enterprise story.
Key moments in the partner journey
The partner experience had to feel familiar, fast, and trustworthy inside a non-Rocket Lawyer environment. Authentication had to work without friction, co-branding had to feel natural, pricing had to adjust in real time, and legal help needed to stay clear and actionable.
How we stayed on track
Launching with a major partner required disciplined sequencing and tight coordination. I focused on unblocking engineering early, resolving dependencies ahead of time, and structuring milestones so each one supported the next.
We cut anything that didn't support the partner launch and built around minimum capabilities: authentication, pricing, onboarding, and partner-specific content. This kept engineering focused and avoided late-stage rework.
Every architectural decision supported Covéa while keeping the path open for future partners. We built the Partner Config API, defined consistent integration patterns, and isolated edge-case logic.
I worked ahead of engineering to resolve open questions with Covéa, align legal and content teams, confirm pricing rules, and prepare the design system for co-branding.
What changed after launch
16% of Rocket Lawyer's EU traffic came from partner channels shortly after launch, proving that enterprise distribution could meaningfully extend reach.
The launch created a net-new enterprise revenue stream and strengthened the case for partner-led growth across Europe.
The reusable architecture, documentation, and integration pattern reduced the cost and time required to onboard the next wave of partners.
The success of this launch validated Rocket Lawyer's partner platform approach, de-risking future deals and giving teams a clear blueprint for expansion.
Where the work was hardest
Every phase forced hard choices. Here's how the project evolved and what we navigated along the way.
April → June
I ramped quickly on Rocket Lawyer's business model and platform architecture so early decisions would hold up through launch. In parallel, we defined the integration model, selected OpenID Connect, and created the Partner Config API.
June → July
Following the June authentication demo, we delivered an early preview of the broader partner experience: co-branding, onboarding designs, and document access. We also built the first version of the Custom Connector for Covéa.
July → August
I front-loaded decisions and closed open questions before Covéa's August vacation. This unblocked engineering to maintain steady progress while partner teams were offline.
August → September
I demoed authentication, co-branding, pricing, Ask-A-Lawyer, and partner-exclusive content as a unified walkthrough. We also stabilized the Custom Connector and Config API.
September → Launch
We prioritized a long-delayed Angular upgrade without disrupting partner deliverables. Moving to ahead-of-time compilation significantly improved load times for customers in France.
How this shaped my approach
Designing Covéa as the first instance of a platform shaped decisions that paid off immediately during later enterprise work.
Balancing launch speed with long-term flexibility meant making crisp, explicit decisions early.
Absorbing churn, communication, and ambiguity enabled engineers to stay in flow, one of the biggest drivers of predictable delivery.
The best co-branded experiences feel native to the partner and trustworthy to their customers. That principle guided every decision.
External and internal validation
Feedback from Covéa and Rocket Lawyer leadership on the strategic and execution impact.
"We are delighted to partner with Rocket Lawyer to provide new legal solutions to our 11.5 million clients."
"We gave Kevin an extremely complex and strategic partner project to tackle and he really knocked it out of the park. He quickly onboarded to the product development challenge, understood the breadth of the deliverables, and started to methodically chip away at them. His team was hyper-focused and motivated, thanks mostly to Kevin and his constant energy and attitude."
