Scintia

Scintia had a working AI voice backend but no production frontend operators could use. Business teams, sales reps, developers, and QA each needed different workflows — agent configuration, call monitoring, subscription management, support tickets — but everything lived in fragmented tools and ad-hoc dashboards. Without a unified product surface, the company could not onboard customers, bill subscriptions, or give operators day-to-day visibility into call operations.

Scintia Callflow is a B2B SaaS company building intelligent voice agents for business operations. When I joined as Frontend Team Lead, the backend and AI models were progressing, but there was no cohesive product experience — each stakeholder group was effectively waiting on a different interface. I led a team of four over 16 months of ongoing product development to ship four role-specific portals on a shared architecture, with Stripe billing, Twilio/Vapi telephony, and bilingual (EN/FR) support.

Before: Scintia had AI voice capability but no unified product surface — operators, sales, and developers each lacked dedicated tools to configure agents, monitor calls, or manage subscriptions.

After: Four role-specific portals on a shared architecture, with live Stripe billing, Twilio telephony, call analytics, and support workflows — enabling Scintia to onboard and bill customers through a single SaaS product.

Rather than building one monolithic dashboard that tried to serve everyone, I separated the experience by role — business operators, sales teams, developers, and testing staff each get a portal built for their workflow, while all four connect to a single backend API. Shared patterns for auth (including OTP flows), billing, analytics, support tickets, and knowledge management keep the product feeling like one platform, not four disconnected apps. This let Scintia onboard different user types in parallel without blocking launches on a single UI.

Four user types, one product — Business operators, sales reps, developers, and QA teams had fundamentally different workflows. Building four separate products that felt like one was the design problem, not just the engineering problem.

Billing and telephony in production — Subscription management (Stripe) and live call infrastructure (Twilio, Vapi) had to work reliably in customer-facing portals, not just in demos.

Bilingual operations — EN and FR locales across legal notices, operational copy, and user-facing flows added scope beyond a single-language MVP.

Sustained delivery over 16 months — Ongoing product development meant balancing new features, regression risk across four panels, and evolving backend API contracts without breaking live users.

Frontend ecosystem — Four React + TypeScript + Vite SPAs (developer, business, sales, test), each using Redux Toolkit + RTK Query for state/API, React Router for navigation, shared UI patterns with Tailwind/Radix, and environment-driven API base URLs.

Delivered capabilities

• Role-based authentication (including OTP flows)
• Dashboard analytics
• AI agent configuration
• Call-log workflows
• Product/knowledge modules
• Support ticketing
• Notification systems
• Plan/payment management

A modular multi-panel SaaS frontend — four React SPAs sharing Redux Toolkit patterns, RTK Query for API state, and environment-driven configuration. Each portal covers role-specific workflows (agent setup, call analytics, developer tools, test operations) while Stripe billing, support ticketing, and knowledge modules work consistently across all four.

• Zero to four production portals in 16 months — Scintia went from no working frontend to business, sales, developer, and testing portals serving live operators.
• Integrated billing and telephony — Stripe subscription management and Twilio/Vapi call infrastructure embedded in customer-facing workflows, not bolted on later.
• Unified support and knowledge — Ticketing and document management accessible across panels, reducing context-switching for operations staff.
• Team of 4, sustained engagement — Delivered as Frontend Team Lead across 16 months of ongoing product development, not a one-off build handoff.
• Live product at scintia.ai — Production SaaS with role-based auth, call analytics, and agent configuration used by Scintia's customers.

Scintia's product team could focus on AI model quality and go-to-market instead of fighting frontend fragmentation. Every operator type had a portal built for their workflow — and the CEO could point prospects at a polished, scalable product, not a backend demo.