All work

Prospect Engine CRM

Sales funnel, data and campaigns in one platform

NestJSTypeScriptPrismaPostgreSQLNext.jsKafkaRedisDocker
Role
Software Engineer
Company
Prospect Engine LLC
Period
February 2024 – Present
Location
Dhaka, Bangladesh
Domain
CRM

Overview

Prospect Engine CRM is a comprehensive sales management platform, designed around the reality that modern outbound sales does not happen in one channel. A rep talks to prospects on WhatsApp, LinkedIn, Telegram, and email — often the same prospect across several of them — and a CRM that only models email loses most of the conversation.

Three pillars carry the product. Sales funnel management moves a deal from first touch to close and makes the state of the pipeline legible. Data management is what everything else stands on — a lead nobody enriched, deduplicated or scored is not an asset. Campaign management is how a team acts on that data at scale rather than one message at a time.

The platform is TypeScript end to end: a NestJS API over PostgreSQL through Prisma, a Next.js front end, and Apache Kafka as the event backbone that carries inbound messages and lead events between services. Redis handles caching, queues and sessions; the whole thing runs in Docker.

I designed and implemented the platform: the funnel and pipeline, the data layer with its enrichment and scoring pipeline, the campaign engine, the real-time multi-channel communication hub, the collaboration and permissions layer, and a browser extension that captures leads directly from the pages reps already work in.

What I built

  • Designed and implemented a comprehensive CRM solution for sales teams with multi-channel communication capabilities.
  • Built sales funnel management with explicit, event-driven stages and Kanban-style deal tracking.
  • Built the data management layer: ingestion, enrichment, deduplication, segmentation and custom fields.
  • Built campaign management: segment-driven, multi-channel campaigns with scheduling, pacing and performance tracking feeding back into lead scoring.
  • Built an advanced lead management system with automated data enrichment and scoring algorithms.
  • Developed a real-time communication hub integrating WhatsApp Business, LinkedIn, Telegram, and email platforms.
  • Created visual pipeline management with a Kanban-style interface for intuitive deal tracking.
  • Redis-backed caching, queues, session management, and real-time event coordination for high-performance operations.
  • Implemented team collaboration features with role-based permissions and workspace management.
  • Built a browser extension for seamless lead capture from LinkedIn and company websites.

In depth

  1. 01

    Sales funnel management

    The funnel is the spine of the product: every prospect occupies a stage, and the whole team can see where the pipeline is thick, where it is stalling and what is about to close. Stages are modelled explicitly rather than left as a status field, so movement between them is an event the system can act on — triggering follow-ups, updating scores and feeding forecasts. A Kanban interface makes it tangible, because dragging a deal between stages is the interaction sales teams already have a mental model for.

  2. 02

    Data management

    Everything else rests on this. A CRM is only as good as the records inside it, and lead data arrives dirty — duplicated across sources, half-complete, and stale within weeks. The data layer handles ingestion, enrichment, deduplication, segmentation and custom fields, so a lead becomes a usable record rather than a row someone has to clean by hand before working it.

  3. 03

    Campaign management

    Campaigns are how a team acts on the database at scale instead of one message at a time: build a segment, run a multi-channel sequence against it, schedule and pace the sends, and measure what came back. Campaign performance loops straight back into scoring, so the funnel reflects who actually engaged.

  4. 04

    Lead management with enrichment and scoring

    Leads are enriched automatically rather than typed in by hand, and scored algorithmically so reps work the most promising prospects first instead of working the list top to bottom.

  5. 05

    Real-time multi-channel communication hub

    WhatsApp Business, LinkedIn, Telegram, and email are integrated into a single real-time hub, so a conversation with a prospect reads as one thread rather than four disconnected inboxes. Real-time event coordination keeps the hub live across a team.

  6. 06

    Team collaboration and permissions

    Role-based permissions and workspace management, so teams can share a pipeline while keeping access to data scoped to the people who should have it.

  7. 07

    Browser extension for lead capture

    A browser extension that captures leads straight from LinkedIn and company websites, removing the copy-paste step between finding a prospect and having them in the CRM.

  8. 08

    Kafka event backbone

    Inbound messages, lead events and enrichment jobs move through Apache Kafka rather than direct service calls. Producing an event decouples the channel adapters from everything downstream — scoring, notifications, pipeline updates — so a slow or failing consumer never blocks message ingestion, and events can be replayed rather than lost.

  9. 09

    Type-safe data layer with Prisma

    PostgreSQL through Prisma, so the schema is the single source of truth and the generated client makes the database types flow into application code. Migrations are versioned and reviewable, which matters on a schema that models leads, threads, campaigns and permissions all at once.

  10. 10

    NestJS module architecture

    The API is a NestJS application, using its module and dependency-injection structure to keep each channel integration, the scoring pipeline and the permissions layer isolated behind explicit boundaries — the same discipline that makes an integration testable in isolation.

  11. 11

    Performance layer

    Redis-backed caching, queues and session management carry the load: expensive work moves to background queues, hot reads come from cache, and real-time coordination runs on the same infrastructure.

Core modules

  • Sales Funnel Management
  • Data Management
  • Campaign Management
  • Lead Management
  • Communication Hub
  • Pipeline (Kanban)
  • Enrichment & Scoring
  • Analytics & Reporting
  • Team & Workspaces
  • Roles & Permissions
  • Browser Extension

Stack

Backend

  • NestJS
  • Node.js
  • TypeScript
  • REST APIs

Frontend

  • Next.js
  • React
  • TypeScript

Data

  • PostgreSQL
  • Prisma ORM
  • Redis

Messaging & events

  • Apache Kafka
  • WebSockets
  • Webhooks
  • Queues

Integrations

  • WhatsApp Business
  • LinkedIn
  • Telegram
  • Email

Infrastructure

  • Docker
  • CI/CD

Other

  • Browser extension
  • Role-based access control