How AccelOne fixed a broken cart and checkout system that was costing a legal services company sales, and built a scalable foundation for growth.
In brief: A legal services company came to AccelOne with a checkout system that couldn't retain cart state, couldn't connect customers to the right sales associates, and had no way to follow up on incomplete transactions. AccelOne rebuilt the entire cart and checkout process, integrating all sales channels, adding Redis-powered cart persistence, implementing customer-to-associate matching, and deploying a transaction follow-up system. Built with Angular, Node.js, MongoDB, and Redis. The result: increased conversion rates, reduced cart abandonment, and improved sales for independent associates.
The client is a legal services company with a mission to make professional legal help affordable and accessible to everyday people, not just those who can afford traditional law firm fees. Their model relies on a network of independent sales associates who connect customers with the right legal services for their situation.
The business model works when customers can find the right services, complete a purchase, and get matched to the right associate without friction. The checkout system was undermining all three.
The existing system had three distinct problems, each one costing the client sales independently, and compounding when combined.
AccelOne developed a new generic cart and checkout platform designed to address all four problems in a single, integrated solution, architected to work across all of the client's sales channels rather than patching individual sites.
Problem |
AccelOne's solution |
|---|---|
Cart not retained between sessions or sites |
Redis-powered cart persistence with configurable session window, cart state survives across sessions and channels |
No associate matching for new customers |
Automated customer-to-sales-associate matching logic based on location, service type, and routing criteria |
No recovery for incomplete transactions |
Transaction tracking and follow-up system, incomplete checkouts are logged and surfaced for associate outreach |
Outdated, friction-heavy UI |
Full Angular/TypeScript frontend rebuild, streamlined UX designed to reduce drop-off at each checkout step |
Siloed across multiple sales channels |
Single unified checkout integrated across all channels, cart contents exportable to any channel |
Cart abandonment in legal services is not always impulsive, customers often research, pause, return. A cart that expires with the session treats every pause as a lost sale. The fix was architectural, not cosmetic.
AccelOne handled both frontend and backend development, deploying an architecture designed for scalability and strict quality control, critical for a platform that processes legal service transactions and handles customer financial data.
On process and security
The client maintained an unusually rigorous GitFlow-based source control workflow, a reflection of the compliance and security standards expected in legal services technology. AccelOne adopted this workflow in full, integrating with the client's existing procedures rather than imposing a separate process. All deployment orchestration ran through the client's CI/CD pipeline via Codeship.
AccelOne used Agile Scrum methodology throughout, dividing work into sprints with specific goals and tracking progress on a visual Kanban board. This approach gave the client visibility into every sprint cycle and allowed priorities to be adjusted as development revealed edge cases in the existing system's behavior.
The team integrated tightly with the client's engineering organization, adopting their GitFlow procedures, working within their code review standards, and coordinating deployment through their CI/CD infrastructure. The result was a build process that felt like an extension of the client's own team rather than an external vendor working in isolation.
AccelOne's scope spanned the full stack: frontend UI design and development, backend API engineering, Redis and MongoDB integration, cross-channel cart architecture, and deployment orchestration through CI/CD pipelines.
The rebuilt checkout system produced measurable improvements across the metrics that mattered most to the client's business model.
✔ Conversion rates increased
✔ Cart abandonment reduced
✔ All sales channels integrated
✔ Incomplete transactions now tracked and recoverable
✔ Customer-to-associate matching automated
✔ Sales boosted for independent associate network
Beyond the immediate conversion improvements, the new architecture was built for scalable growth, capable of integrating additional sales channels and features without requiring another rebuild. For a company whose mission is making legal services accessible at scale, that architectural foundation matters as much as the immediate results.
What checkout problem did AccelOne solve for the legal services company?
The client's outdated checkout system had three core problems: carts were not persisted across sessions or sites, there was no mechanism to connect customers to the right sales associates, and incomplete transactions had no follow-up capability. The result was high cart abandonment and lost sales. AccelOne replaced the system with a unified cart and checkout platform that retained cart state, matched customers to associates, and enabled transaction recovery across all sales channels.
What does a multi-channel checkout integration involve?
A multi-channel checkout integration means a single cart and checkout experience that works consistently across all of a company's websites and sales channels, preserving cart contents, user data, and transaction state regardless of which channel the customer entered from. For this legal services client, it also meant exporting cart contents to other sales channels and routing customers to the appropriate independent sales associate.
What technology stack was used to rebuild the legal services checkout platform?
AccelOne built the frontend with Angular and TypeScript, the backend API with Node.js and Express, MongoDB for data storage, and Redis for cart state persistence and session management. The team followed the client's GitFlow-based workflow for version control and used Codeship for CI/CD pipelines. Agile Scrum methodology with a visual Kanban board managed sprint execution.
How does cart persistence work in a multi-site platform?
Cart persistence means a user's cart contents are retained across sessions and sites. AccelOne implemented this using Redis, which stores cart state in memory with a configurable expiry window. If a customer returns later or arrives through a different channel, the cart is restored from Redis (not from a browser session) so progress is never lost within the retention window.
How do you reduce cart abandonment in a legal services checkout?
AccelOne addressed legal services cart abandonment through three mechanisms: persistent cart state via Redis so users don't lose progress, a rebuilt UI/UX that removed friction from the checkout journey, and a follow-up system for incomplete transactions allowing sales associates to re-engage customers who did not complete their purchase. The combination of fewer drop-off points and active recovery of incomplete transactions increased overall conversion rates.
How does customer-to-sales-associate matching work in a legal services platform?
The platform routes customers to the right independent sales associate based on their location, the type of legal service they are purchasing, and other matching criteria. When a customer initiates a checkout, the system identifies the most appropriate associate and establishes the connection, ensuring the customer gets relevant guidance and the associate gets a qualified lead, replacing a manual process that was causing leads to fall through.
What results did the rebuilt checkout system produce?
The rebuilt checkout produced increased conversion rates, reduced cart abandonment, and improved user experience across all sales channels. The client gained the ability to track and follow up on incomplete transactions, directly boosting sales for the independent associate network. The new architecture was also built for scalable growth, ready to add features and channels without requiring a full rebuild.