<React and TypeScript at enterprise scale, tested and measured.>

NCX is Nextiva's contact center platform: shared inbox, tickets, video calls and an AI assist panel for support and sales teams, used daily by thousands of agents at companies of every size.

I designed the architecture of the entitlements system, which is what let Nextiva move its whole pricing to subscription packages. What each customer sees depends on what they pay for, not on hardcoded checks. Under the hood it's a reusable React Query hook plus feature flags, used across nearly every module.

I also built the single sign-on integrations (Azure AD, Google, Okta), so enterprise teams sign in without creating a new password. With product and design, I built the onboarding for new customers: one guided flow, made from reused components, that replaced 12 separate configuration pages.

NextivaONE centralizes calls, messages, email and team chat into one inbox, so a business never loses the thread of a customer conversation, no matter which channel it came in on.

Real-time messaging is the core of NextivaONE, so when it broke, agents lost the thread of a live conversation with a customer. I found and fixed the reliability issues in that module, and along the way rebuilt state management with Redux across several parts of the product.

I also built the mini, compact and large view modes for the inbox, so an agent who needs to scan dozens of conversations and one who needs full context on a single one can each set up their workspace the way that works for them. I also added Statsig events so the team could see where they were missing data on how people used the product.

More than 300 products, no online ordering channel, and pricing and stock tracked outside any real system. Every quote went through one person. I never set foot there: the whole assessment ran over calls and screen shares.

They had no control over their parts. Every question about a measurement or stock sent someone walking to the warehouse. The information existed, but only on the physical part.

In stages. First the storefront for their customers, with per-user pricing and permissions. Then the internal system: catalog, orders and online payments.

An auto repair shop already at its limit with 100 cars a month. Customer files lived in boxes in a back room, and every new car made searching for all the previous ones slower.

I sat down separately with the appraiser, the service advisor and both owners. Each described a different process. The map ended up as sheets of paper taped to a wall, and that is where it became clear their growth ceiling was not the shop floor: it was the filing system.

Phased, starting where it hurt most: internal processes first, then customer communication, then positioning. Status updates now go out on their own, customers look their car up with their work order number, and the weekly meeting runs off live KPIs.

With the operation in order, they went on to secure 7+ insurance company partnerships, which is where the extra volume came from.