Case study 01 · SaaS · Sales operations
LeadPylot CRM
A CRM workspace for sales teams handling lead pipelines, detailed records, and live operational workflows.
- Next.js
- TypeScript
- TanStack Query
- Zustand
- Socket.io
01 / Context
The problem
Sales teams needed to process leads across several pipeline views while keeping records, tasks, email workflows, and status changes in one place.
02 / Contribution
What I owned
I led the Next.js admin interface: realtime lead boards, authentication flows, data-heavy screens, and integrations with the platform APIs. Backend services and infrastructure were part of the wider team’s platform.
Delivered workflows
- Multiple lead pipeline views with live updates and detailed lead records.
- Configurable data tables for sorting, filtering, grouping, columns, and bulk actions.
- Role-aware admin workflows, tasks, calendar, documents, and reporting interfaces.
03 / Engineering
How the system fits together
- 01
Lead enters
- 02
Pipeline view
- 03
Team action
- 04
Live update
Client and server state
The frontend uses Zustand for interface state and TanStack Query for server data, keeping table controls and fetched records separate.
Realtime operations
Socket.io updates feed notifications and live pipeline changes into the admin experience.
Platform integration
The Next.js interface connects to Node.js services backed by MongoDB and Redis, with tenant roles and configurable pipeline stages.
04 / Evidence
What this case demonstrates
The delivered work includes the admin interface and its operational workflows. Usage and business impact figures have not been independently verified for this showcase.
Private product. A permitted walkthrough can be discussed during an interview; source code is not public.