Multi-product enterprise suite
Zallo
Gateway-led suite—production multi-tenant AI receptionist (zallo.ai) plus NestJS/Next ERP-style SKUs (CRM, POS, finance, HRM, inventory, CMS) with shared portal UI.
Background & Context
Zallo is a multi-product business software suite evolved from a .NET ERP (ERP.Domain.*) into per-product NestJS APIs and Next.js portals. Flagship sellable SKU is the AI Receptionist (REC) at zallo.ai: Twilio + Vapi voice that books against real availability, FAQ answers, human transfer, SMS recovery, tenant/admin portals, Stripe billing. Platform gateway handles identity, entitlements, service links, federated suite home, and product handoff. Sibling modules (CRM, POS, Finance, HRM, Inventory, Procurement, Manufacturing, Projects, Reports, AI CMS, Medical Billing) ship as independently runnable Nest + Next + contracts; ERP-style APIs use file-backed .data stores locally with Supabase schema ownership prefixes ready for Postgres promotion. Receptionist is production-depth; siblings share patterns.
The Challenge
Appointment businesses lose bookings when phones go unanswered; operators also need modular back-office SKUs instead of a single legacy monolith release train. Without a coherent multi-product enterprise suite foundation, Zallo stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The Solution
Zallo: Gateway-led suite—production multi-tenant AI receptionist (zallo.ai) plus NestJS/Next ERP-style SKUs (CRM, POS, finance, HRM, inventory, CMS) with shared portal UI. End-to-end receptionist loop: answer → book → SMS follow-up. Tekvers delivered a maintainable multi-product enterprise suite system for Zallo using NestJS, Next.js, TypeScript, Supabase Postgres + RLS (REC), with phased rollout, operator workflows, and documentation suited to long-term ownership.
Our Approach
Wedge then suite
Ship receptionist as the revenue wedge; expand via entitled sibling SKUs rather than a forced monolith rewrite.
Gateway first
Identity, entitlements, and handoff live in Platform so products stay domain-focused.
Maturity honesty
Case study distinguishes production REC depth from ERP scaffolds on local JSON stores.
What We Delivered
- AI receptionist product surface (voice, portals, APIs, SMS, Stripe hooks, marketing)
- Platform gateway for auth, entitlements, and suite home
- Modular product APIs/portals across CRM, POS, finance, HRM, inventory, manufacturing, projects, reports, CMS
- Shared TypeScript contracts and `@zallo/portal-ui`
- Docker Compose / Caddy-oriented deploy path for REC
- Vertical presets path for med spa → adjacent appointment verticals
Outcomes & Impact
- End-to-end receptionist loop: answer → book → SMS follow-up
- Independent module delivery with shared identity patterns
- Clearer commercial packaging per Zallo product SKU
- Modern Nest/Next path off a legacy .NET ERP domain split
Zallo behaves like a product family—clinics get a production AI front desk; operators entitle ERP siblings as needed; identity and entitlements stay centralized without forcing one release train.
Technology Stack
Services Delivered
Related Case Studies
Planning a similar platform? Share your scope and we will map architecture, delivery phases, and a realistic timeline.