Case study

Exonec is a WhatsApp automation SaaS that turns bot infrastructure into a client-manageable, subscription-backed product.

The project starts from a simple FAQ auto-reply idea, but the repo shows a much more complete platform: multi-tenant bot logic, billing automation, onboarding, dashboard management, and admin oversight for businesses running customer support through WhatsApp.

Visit live project

Category: WhatsApp SaaS platform

Project snapshot

coordinated surfaces: bot and API backend plus separate web onboarding and dashboard frontend

backend source files across bot logic, API server, models, auth, payment, cache, monitoring, and subscriptions

frontend app files covering landing, onboarding, login, dashboard, FAQs, settings, admin, and payment flows

subscription tiers modeled across trial, starter, professional, and enterprise

What NEXGEN built

A customer-support automation platform with real product operations around it.

Multi-tenant WhatsApp bot engine that routes customer messages per client, loads business-specific FAQ data, and applies subscription-aware response behavior.

Client self-service dashboard for profile management, FAQ editing, settings, subscription visibility, and usage stats without needing developer intervention for every content change.

Admin platform for viewing clients, filtering by status and tier, checking system metrics, and managing subscription-level operations from one control surface.

Payment and subscription automation built around trials, paid tiers, Paystack payment links, webhook-driven activation, and automatic service halt on expiry.

Onboarding and acquisition flow through a dedicated web app with marketing pages, lead capture, contact routes, and admin email notifications.

Product framing

The real value is not the bot alone, but the repeatable service model around it.

Exonec becomes much more compelling when you read it as infrastructure for many businesses, with clear controls for acquisition, billing, support, and account lifecycle management.

A SaaS layer on top of messaging automation

Exonec is not just a WhatsApp bot script. The repo clearly evolves it into a commercial platform with onboarding, subscriptions, auth, dashboards, admin tooling, and billing operations.

Multi-tenant by design

The backend is built around serving multiple businesses from one bot infrastructure, with client-specific FAQs, limits, statuses, and configuration loaded dynamically per tenant.

Operations and monetization are first-class

Trials, payment links, webhook verification, expiry checks, rate limits, and support for account states make the product feel like a managed service rather than a one-off deployment.

Non-technical clients can control their system

The dashboard pages for FAQs, settings, stats, and account management matter because they shift Exonec from custom implementation work toward repeatable product delivery.

Architecture

One product across bot runtime, API operations, and a separate web control layer.

WhatsApp bot and Express API backend deployed together, handling message routing, client lookup, subscription enforcement, auth, payment events, and monitoring

Next.js web frontend deployed separately for marketing, onboarding, login, client dashboard, admin dashboard, and payment callback flows

MongoDB-backed client and message storage with cache and monitoring services to reduce repeated lookups and keep the free-tier-friendly deployment practical

Platform ops layer spanning JWT authentication, password hashing, payment verification, admin approval flows, and email notifications via Resend

Technology stack

Node.js

Express

MongoDB Atlas

Baileys

JWT

bcrypt

Paystack

Next.js 15

React

TypeScript

Resend

Railway

Vercel

Why it stands out

Exonec stands out because it productizes what is often delivered as bespoke client work. The repo shows a clear move from custom WhatsApp setup into a reusable SaaS workflow with customer autonomy and platform controls.

System breakdown

The product gets stronger the more you look at lifecycle and platform operations.

Bot and FAQ matching layer

The backend includes bot runtime logic, WhatsApp client integration, FAQ matching, social-media helpers, and client-loading services, showing that responses are generated from structured business configuration rather than hardcoded replies.

Subscription and limit enforcement

The system models trials, active and expired states, message limits by tier, and automatic service halt behavior. That is a strong product signal because platform rules are enforced in code, not manually tracked by the team.

Client and admin dashboards

The web app includes login, dashboard, FAQ management, settings, upgrade flow, admin login, admin client views, and admin analytics routes, which turns the service into a manageable product for both customers and operators.

Onboarding and conversion flow

Lead capture, contact pages, onboarding forms, payment link creation, callback verification, and admin email notifications create a complete path from prospect to activated customer.

Repo evidence

The implementation supports the SaaS framing directly.

The progress docs explicitly describe a multi-tenant bot, subscription management, Paystack payment links, webhook activation, caching, monitoring, and a production-ready MVP deployed on Railway and Vercel.

The backend source tree includes dedicated services for clients, admins, subscriptions, payments, rate limiting, caching, and monitoring rather than a single combined bot file.

The frontend app structure includes customer-facing routes for onboarding, login, FAQs, settings, upgrades, and admin surfaces for client management and system stats.

The project docs repeatedly frame Exonec as a business platform with lifecycle automation, pricing tiers, onboarding approvals, and support workflows, not just a technical bot integration.