Multi-tenant CRM SaaS with a kanban pipeline, WhatsApp Cloud API, and an Electron desktop app
01
Trativa is a multi-tenant SaaS built across 4 separate repositories: a React/PWA front end, a Node.js/MongoDB back end, a landing page, and an installable Electron desktop app for Windows. The system has full multi-tenancy per Organization — each company has its own isolated leads, users, and custom fields. The pipeline has 9 real stages (new → in service → contacted → interested → no response → meeting scheduled → proposal sent → converted → lost), with drag-and-drop via dnd-kit and real-time updates through Socket.IO. Reports include the conversion funnel, performance by salesperson, by source, by city, stalled leads, and a conversion time series.
My role
Solo full-stack developer — 4-repository architecture, Node.js/Express/MongoDB back end, React/Vite/PWA front end, WhatsApp Cloud API integration, multi-plan Stripe, Electron desktop app, landing page with Framer Motion.
Category
SaaS
Year
2025
Status
Platforms
Four repositories, one product. The React app talks only to the API; the API is the only one that knows about organization, plan, and WhatsApp. Electron reimplements nothing — it loads the same app, which is already responsive.
Vite · PWA · Railway
Node · Railway
MongoDB + integrations
Electron · Windows
Sync: scopeQuery applies Organization + soft delete on every endpoint: one company's lead never shows up in another's query, even if the id leaks.
02
Brazilian sales teams lose opportunities for lack of structured tracking — leads arrive from different sources (Google Maps, Instagram, referrals, ads), get jotted down in a notebook or WhatsApp, and go without follow-up. Managers have no real-time visibility into the funnel.
03 — The Solution
A web + PWA + desktop CRM with a customizable 9-stage pipeline, WhatsApp Cloud API integration for direct communication, custom fields with 10+ types to fit each company's reality, sales goals per salesperson, and complete funnel reports — with Stripe subscriptions in 4 plans and a 14-day trial.
04
The system in action, recorded from the real application with a demo store — no screen is a mockup.
Pipeline
Nine real sales stages, from first contact to converted. The card leaves one column and enters another with @dnd-kit, each stage's counter adjusts, the status saves instantly, and Socket.IO pushes the change to anyone with the same screen open.
Integration with Meta's WhatsApp Cloud API: the conversation lives in a lead tab, with the 24-hour window notice, the history of sent and received messages with read status, and the choice between a free-form message (inside the window) or an approved template (outside it).
Reports
Stages become proportional bars with the conversion from one to the next. When a transition falls below 30%, it is flagged in red and the system explains what is happening there — the same view can be read by salesperson and by source.
Customization
Eleven field types (text, number, currency, date, yes/no, select, multiple choice, URL, email, phone, long text). The admin chooses where each one appears: on the kanban card, as a table column, or in the search filters — and the change applies to the whole organization instantly.
Lead intake
The spreadsheet is uploaded, the system shows how many rows are valid, how many are duplicates, and how many have errors — and only saves after you confirm. The same route exists as an API with its own key, for those who prefer to send leads straight from automation.
Team
The invitation defines the role and which projects the person can access. Goals are measured against the lead's history — not against a separate counter — so each salesperson's progress reflects exactly the status changes in the period.
Interface
Each user picks the system palette (blue, purple, green, orange, pink, or gray) and it is applied through data-theme on the root, overriding the Tailwind tokens. The brand identity doesn't change with it: the institutional blue stays in the logo and communications.
05
Each video shows a complete task, end to end. Click to watch with controls.
06
Drag-and-drop via @dnd-kit with 9 real sales statuses. Switchable views: kanban, table, and cards. Real-time updates via Socket.IO for the whole team simultaneously.
Native WhatsApp Cloud API integration — send and receive messages right in the lead's timeline, without leaving the CRM.
10+ field types (text, number, currency, date, boolean, select, multiselect, URL, email, phone) created by the admin and displayable on the kanban, in the table, or in filters.
8+ report endpoints: conversion funnel with bottlenecks (<30%), performance by salesperson, leads by source, by city, stalled leads, and a conversion time series.
Goals per salesperson with 4 types (converted, contacted, proposals, meetings), a configurable period, and progress calculated in real time against the LeadHistory.
Installable desktop version for Windows (.exe NSIS) via Electron.js — the same experience as the web app, with native notifications and keyboard shortcuts. Available at trativa.app/download.
07
Real screenshots of the product, organized by module. Click any screen to enlarge it.
08
The salesperson opens the CRM between visits: on mobile the sidebar becomes a drawer, the kanban becomes tabs by stage, and the WhatsApp conversation stays inside the lead's record. The same app is installed as a PWA.
09
Front-end
Back-end
Database
Deployment
Integrations
Libraries
10
A product split into 4 repositories with clear responsibilities: back end (API + business rules), front end (SPA/PWA), landing page (marketing/SEO), and desktop (Electron wrapper). Electron reimplements nothing — it loads the web app, which is already responsive. Custom fields are configured by an admin and propagate to the kanban, table, and filters automatically, with no deploy.
11
Custom fields in filters and CSV export: the customFields field is a Map<Mixed> in Mongoose, but it arrived as a plain object from the JSON. The front end had to handle both formats (getCustomValue accepts Map and object). On export, Papaparse receives dynamic columns computed from the organization's active fields — inactive fields don't appear even if the lead has the value stored.
12
13
Have a similar idea or want to build something different? Let's talk.
Video previewSaaS
A complete point-of-sale system for pet shops, feed stores, grocery stores, and neighborhood shops: POS with barcode scanner, cash register, inventory, customer tabs (fiado), accounts payable, PIX (Brazil's instant payment system), 50+ reports, and Secure Receiving — all working without internet, with cloud sync and a mobile management app.
Video previewWeb system
B2B store for mobile phone accessories: a catalog of 349 products with filtering by device (293 models), progressive pricing by quantity, a cart with color selection, real shipping rates, and a checkout that opens WhatsApp with the order ready to send. Full admin panel for the store owner, Excel/PDF export, and Meta Pixel + Conversions API tracking.
Video previewSaaS
A complete management system for pet shops: a schedule with real-time status via Socket.io, clients, pets, finances, team members, and monthly/annual subscriptions via Stripe — an installable PWA for phone or computer.