Zaigham Naveedbuilds productspeople trust.

The challenge

Alfa needed one product to serve very different people — retail users onboarding for the first time, and businesses running transfers, scheduled payments, and day-to-day operations. In fintech, a confusing screen isn't a UX bug; it's a support ticket or a lost customer.

Approach 1 / 3

Roles first, screens second

Mapped every role to the actions it actually needs, then built role-based dashboards so each user sees only their world — nothing to ignore, nothing to misclick.

Approach 2 / 3

Predictable state for money

Redux Toolkit and RTK Query own every server interaction, so balances, transfers, and schedules stay consistent across the app with caching and refetching handled in one place.

Approach 3 / 3

A component system that scales

Tailwind and shadcn/ui gave a consistent, accessible base; lazy loading and code splitting keep heavy flows out of the first load.

What shipped

• Guided onboarding flows
• Transfers & payment scheduling
• Business operations management
• Role-based dashboards
• API-ready architecture against a FastAPI backend

Stack

Next.js · TypeScript · FastAPI · Redux · RTK Query · Tailwind · shadcn/ui

The challenge

Hiring involves three parties — recruiters, companies, and candidates — usually working in separate tools and email threads. Contario set out to put all three in one real-time workspace, with AI doing the matching.

Approach 1 / 3

One workspace, three perspectives

Designed the flows so recruiters, companies, and candidates each get a focused view while collaborating on the same live data.

Approach 2 / 3

Matching that earns trust

Built candidate profile management and intelligent matching so recommendations come from structured profiles rather than keyword guesswork.

Approach 3 / 3

Real-time by default

Supabase and real-time APIs keep every party in sync instantly — no refresh, no stale pipeline.

What shipped

• AI-powered candidate matching
• Candidate profile management
• Real-time collaboration across three user types
• Secure, scalable APIs

Stack

Next.js · Supabase · AI · Real-time APIs

The challenge

Most AI chat interfaces look identical no matter what's being said. MAI Chat's idea: characters with real emotional range — happy, sad, angry — and an interface that feels those emotions too.

Approach 1 / 3

Personas with feelings

Built multiple AI characters on the OpenAI API, each able to express distinct emotions throughout a conversation.

Approach 2 / 3

UI as an emotional mirror

The interface reads each message's emotional context and shifts colors and backgrounds to match, so mood is felt before it's read.

Approach 3 / 3

Solid plumbing underneath

Supabase handles persistence and auth; Redux Toolkit keeps conversation and theme state predictable as moods change mid-chat.

What shipped

• Multi-character AI personas
• Emotion-reactive theming
• Persistent conversations

Stack

Next.js · Supabase · OpenAI API · Redux

The challenge

Getting a legal document drafted or a case filed usually means expensive back-and-forth before anything happens. Golega puts the whole journey — documents, lawyers, filing, sharing — in one place.

Approach 1 / 3

Questionnaires instead of jargon

AI-driven questionnaires gather plain-language answers and generate the legal document, so users never face a blank template.

Approach 2 / 3

Humans when it matters

Users can hire a lawyer for case filing directly in the platform, with secure document sharing between parties.

Approach 3 / 3

A business model built in

Integrated payments and subscription plans so access to services is clear, simple, and sustainable.

What shipped

• AI document generation
• Lawyer hiring & case filing
• Secure document sharing
• Payments & subscriptions

Stack

Next.js · Node.js · Express · MongoDB · AI

The challenge

In a busy hospital, appointments, doctor availability, and patient records live in different places — so the front desk, doctors, and patients are constantly out of sync. Every mismatch means a longer wait or a missed consultation.

Approach 1 / 3

Appointments, end to end

Built the full appointment workflow so patients can book, track, and manage consultations themselves instead of calling the front desk.

Approach 2 / 3

APIs as the single source of truth

Designed RESTful APIs for patient data, doctor availability, and appointment processing, so every screen reads from the same live data.

Approach 3 / 3

Dashboards for every role

Centralized dashboards with real-time updates give the front desk, doctors, and patients the same picture at the same moment.

What shipped

• Patient self-service booking & tracking
• Doctor availability management
• Patient record management
• Real-time role-based dashboards
• RESTful API layer

Stack

MongoDB · Express · React · Node.js · REST APIs