NextPilot
Chat
WhatsApp-first multi-tenant CRM with shared inbox, pipeline, broadcasts, flows, AI, voice, and billing — built for teams that sell and support on messaging channels.

About the Product
NextPilot is a WhatsApp-first multi-tenant CRM with shared inbox, pipeline, broadcasts, flows, AI, voice, and billing. Organizations run sales and support on Meta channels from one product — WhatsApp, Messenger, Instagram, and webchat in the same conversation model.
The product is strong on messaging UX. A focused P0 SaaS pass (Aug 2026) moved plan limits from UI-only banners to real entitlements: org RPC gates, WhatsApp daily caps, org-scoped phone validation, and seeded limits so Growth accounts cannot send until checkout completes.

SaaS without soft limits
Entitlements lived in UI only
Trial banners were not enough to gate WhatsApp sends, broadcasts, or Growth payment_required states.
Multi-tenant send risk
Org IDs were passed without validating that the WhatsApp phone number belonged to that organization.
Plan limits missing on orgs
Many organizations lacked seeded limits, so caps and usage tracking could not be enforced consistently.
Ops depth beyond inbox
Agent reports, campaign ROI, tasks / follow-ups, and multi-channel dispatch were required for real CRM loops.
Product surface + SaaS control plane
We shipped the messaging CRM operators expect — then hardened it with entitlements, org phone validation, seeded plan limits, and deeper CRM workflows.

WhatsApp-first shared inbox
Multi-tenant conversation workspace for agents — WhatsApp-first with Messenger, Instagram, and webchat in one model so teams reply where customers already are.
Unified conversations
WhatsApp 582 · Messenger · Instagram · webchat threads
Team collaboration
Shared inbox for multi-agent orgs
Org-scoped data
Multi-tenant isolation across organizations

Pipeline & lead lifecycle
Move leads through stages with follow-ups, tasks, and a lead-won loop that clears work and logs activity when deals close.
Pipeline stages
Structured CRM flow for messaging-led sales
Tasks / follow-ups
Dedicated follow-ups surface with assignee support
Lead → won loop
closeLeadAsWon clears follow-up, completes tasks, logs activity

Campaign broadcasts
Outbound campaigns gated by entitlements — Growth orgs cannot send until checkout completes, and WhatsApp daily caps are enforced on send APIs.
Entitlement-gated sends
API routes require WhatsApp entitlement before delivery
WA daily caps
Enforced via get_org_entitlement + api_usage
Campaign ROI
Reports → Campaign ROI with campaign analytics API

Flow builder
Automation flows for onboarding, replies, and operational journeys — part of the messaging product surface that teams run every day.
Visual flows
Build messaging journeys without leaving the CRM
Operational handoffs
Connect inbox actions to structured follow-up work
Scale-ready paths
Same multi-tenant model as inbox and broadcasts

AI-assisted messaging
AI agent surfaces help teams answer faster while human agents stay in control of the shared inbox and pipeline.
AI in the workflow
Assist agents without replacing CRM ownership
Inbox-native
Designed for the same conversation model as WhatsApp threads
Team scale
Supports multi-member orgs (27 members across 7 orgs in live snapshot)

Agent reports & campaign ROI
P1 product depth: agent performance stats, campaign ROI reporting, and ops visibility so messaging volume turns into managed revenue work.
Agent reports
Reports → Agents tab + org agent report stats RPC
Campaign ROI
Reports → Campaign ROI + /api/reports/campaigns
Live snapshot
7,221 contacts · 598 conversations · 4 subscriptions
From UI banners to real gates
Aug 2026 P0 pass: get_org_entitlement and validate_org_wa_phone RPCs, seeded plan limits, and gateway checks so WhatsApp sends are blocked for pending payment, expired trials, and daily caps.
Entitlements
Before: Trial banner only
After: RPC + API/gateway gates
WA daily cap
Before: within_wa_limit unused
After: Enforced via RPC + api_usage
Multi-tenant send
Before: org_id with no phone check
After: validate_org_wa_phone on CRM + droplet
Plan limits
Before: Often missing on orgs
After: Seeded on signup, trial, checkout
Growth billing
Before: Soft client checks
After: payment_required until checkout
Legacy fallback
Before: Always used PHONE_NUMBER_ID
After: Gated behind ALLOW_LEGACY_WA_FALLBACK
Signup → WhatsApp E2E
Signup → create-org → Starter trial or Growth pending_payment → Onboarding → Connect WhatsApp → first-message API → entitlement check → droplet send → contact + conversation created. Growth orgs cannot send until checkout completes.
Product surfaces that ship
Mobile-ready CRM

Messaging workflows designed for teams that live in WhatsApp — with a path to App Store–ready auth and push (P3).
Integrations

Meta channels, catalog order status transitions, and a multi-channel send dispatcher for WA / Messenger / IG.
Why NextPilot

One product for inbox, pipeline, broadcasts, flows, AI, and billing — with real SaaS enforcement.
Pricing model

Starter ৳3,990 · Growth ৳12,990 · Scale custom — limits seeded per tier on signup and checkout.
Built for multi-tenant messaging SaaS
NextPilot runs on Next.js with Supabase for multi-tenant data and RPCs. WhatsApp delivery goes through Cloud API paths with org phone validation and a Python gateway on the droplet. Entitlements use SECURITY DEFINER RPCs (get_org_entitlement, validate_org_wa_phone) called from API routes and the webhook layer.
Documented platform metrics
Live snapshot from Supabase (Aug 2026) — real org, contact, and channel volume behind the product.
Contacts
Conversations
Orgs / members
WhatsApp threads
Subscriptions
4 active · 1 billing checkout
Other channels
Messenger 7 · webchat 5 · Instagram 4
Plans
Starter ৳3,990 · Growth ৳12,990 · Scale custom
From inbox to enforceable SaaS
For SaaS operators
- Plan limits and WA caps enforced server-side
- Growth orgs gated until checkout completes
- Seeded limits on signup, trial, and billing
For messaging teams
- Safer multi-tenant WhatsApp send paths
- Agent reports, campaign ROI, and follow-ups
- WhatsApp-first with Messenger, IG, and webchat
Key Achievements
Contacts managed
SaaS gates shipped
CRM + channels depth

Need a WhatsApp CRM or messaging SaaS?
We design and ship multi-tenant messaging products with real entitlements, billing, and channel depth — not soft UI limits.
Ready to discuss your
next digital product?
Share your project idea, timeline, and budget. We'll review the scope and respond with a practical plan.
What Happens Next
We review your requirements and map initial technical direction.
We schedule a discovery call to align business goals and product scope.
You receive a clear proposal, timeline, and launch roadmap.
RedoNext Limited
Product & Engineering Studio
Response within 24 hours · Free consultation · NDA available on request