Demo with made-up data
01
Noouter
WhatsApp marketing SaaS built for contingency
- Role
- Co-founder · full-stack engineer
- Stack
- Next.js 16 · NestJS 11 · Prisma 7 · PostgreSQL 16 · Redis + BullMQ · Stripe
- Period
- Apr 2026 —
- Stage
- Pre-launch
- Constraint
- A number gets banned, a group gets lost. The audience has to survive both. Every tenant's data, AI spend and billing must stay its own.
- Built
- Tenant isolation enforced in the data layer, not in services. Entry links that rotate themselves, with one contact channel per rescued lead (SMS, email or the official API) and cost estimated before it sends. An LLM router that never throws, caps concurrency on the webhook path and books every call, failures included, to the tenant's cost ledger.
- Result
- Pre-launch. 213 API endpoints, 82 data models, 127 test files.
- WhatsApp provider orchestration
- Instagram & TikTok acquisition
- AI reply reading
- Storybook design system