Nyra Command Center — Nyra AI

The sales team was running on spreadsheets and memory. Leads lived in one file, sprint results in another, and nobody could answer what the pipeline actually looked like without rebuilding it by hand every Monday.

It also had to work on a phone. Reps are on the road, not at a desk, and a CRM they cannot update between meetings is a CRM that goes stale.

Next.js 14 with the App Router, Supabase for Postgres and auth, Tailwind for the interface layer. Roles are enforced at the database level rather than hidden in the UI, so an Ops login genuinely cannot read what an Admin can.

The pipeline is a drag-and-drop Kanban across nine stages, with activity history on every lead. Sprint tracking runs on fifteen-day trial cycles and rolls confirmations, calls, and feedback into one view.

Mobile-first was a constraint, not a breakpoint. The layouts were designed at 390px and then allowed to expand, which is why the desk view has no wasted space.

Subscription management covers four plan tiers with contract types and MRR rolled up automatically, so revenue is a query rather than a monthly reconciliation.

Rep performance became a daily War Room view — visits, meetings, pitches, sprints, subscriptions — plus a leaderboard, which turned out to do more for adoption than any amount of training.