LEM CRM.
A CRM and browser-extension ecosystem designed around customer and lead management workflows.
Context
Sales work does not happen inside a CRM. It happens in an inbox, on a profile page, in a browser tab — and the CRM is where it gets recorded afterwards, if at all.
LEM pairs a web application with a Chrome extension so lead and communication management can happen in the place the work is already happening.
My role
- Frontend development with React
- Chrome extension development
- CRM interfaces and lead management views
- Translating client requirements into product changes
- Responsive implementation across the web experience
The Problem
A CRM only works if people actually update it. Every context switch between the browser and the product is a chance for a lead to go unrecorded.
The product needed to meet users where they already were, without becoming a second, disconnected application.
The Approach
Extend the product into the browser. The extension handles capture and quick actions in context; the web app remains the place for depth.
Both surfaces share the same concepts and language so moving between them does not feel like changing tools.
The Build
A React frontend for the CRM alongside a Chrome extension, built against the same product APIs.
- React
- Chrome extension
- CRM interfaces
- Responsive experiences
The Challenge
Extension development has constraints a normal web app does not — limited space, isolated contexts, permission boundaries and a host page you do not control.
Keeping the two surfaces consistent while respecting those constraints was the ongoing work.
Project technology
What I built
In-context capture
The extension puts lead capture and quick actions next to the work, so recording something costs a click instead of a tab switch.
CRM interfaces
Lead and communication views built for scanning first — the list has to be useful before any detail screen matters.
Shared product language
Extension and web app use the same terminology, states and patterns, so the extension reads as part of the product rather than a companion to it.
Requirement-driven iteration
Client requirements were translated into scoped product changes and shipped incrementally rather than in large, risky batches.
Outcome
A connected web and browser-extension experience for CRM and lead-management workflows.
The work evolved through practical client requirements and incremental product improvements.
Key takeaways
- Building outside the page teaches you how many assumptions a normal web app quietly makes.
- Consistency between surfaces is a product decision, not a styling one.
- Shipping small changes often is the only sane way to work against evolving requirements.