I build full-stack AI systems for founders and operators who've outgrown patched-together tools. Multi-tenant SaaS, CRMs, mobile apps, and automation layers — engineered to handle real load, real money, and real consequences.
Also working with healthcare practice managers and ops leads whose billing, coding, and credentialing workflows are held together by spreadsheets and staff memory — and building the systems that replace that.
Systems that don't quit at 3am. — trustworthy, automated, and scalable under pressure. The unfun parts: tenant boundaries, payments, queue-backed fulfillment, and AI layers you can actually operate.
I help founders and operators fix the messy middle — when the idea works but the product, ops stack, or AI layer can't keep up. Usually 1–3 month engagements with clear outcomes, not open-ended body-shop hours.
You want AI in the product — not a demo that impresses in a meeting but breaks in week two. I add assistants, automation, and classification your team can monitor, roll back, and trust when things get weird.
What you get
You've validated the idea. Now you need infrastructure to sell to a second customer, a tenth, a hundredth — without it breaking. I build the multi-tenant foundation so you can scale without a rewrite: auth, billing, async fulfillment, engineered right the first time.
What you get
Your team is drowning in spreadsheets and three tools that don't talk to each other. I build the workspace they actually open every morning — clients, projects, invoices, and a portal your customers can use without calling you.
What you get
Your technicians are on the road; dispatch is in the office — and jobs still get lost between WhatsApp, spreadsheets, and a clunky admin panel. I build dispatch, admin, and mobile on one ticket lifecycle so work gets done and billed.
What you get
Your users need something in their pocket that works on a bad connection — not a responsive site pretending to be an app. I ship iOS, Android, and web from one codebase, store-ready, with the native bits that matter (push, share, payments).
What you get
Your product works but the surface looks like it was built in a hurry — because it was. I redesign and rebuild so you can sell with confidence: one person owns UX, visual design, and engineering. No three-month handoff between designer and dev.
What you get
Your billing team is chasing denials manually. Credentialing is tracked in a shared spreadsheet that's one resignation away from chaos. AR is aging past 45 days and nobody can pinpoint the leak. These aren't people problems — they're systems problems.
I build the automation layer that connects your billing, coding, credentialing, and collections workflows so your team manages exceptions, not volume.
What you get
Right for you if
A multi-tenant B2B2C ticketing business needed to sell real events in regulated markets — not a prototype that breaks when carts fill, seats lock, or compliance APIs change mid-checkout.
I owned and extended core ticketing modules across a production monorepo: order management with cart locking and reserved-seat holds, PDF + QR ticket generation, multi-currency pricing, and regulatory checkout flows for Dubai (DTCM) and Abu Dhabi (DCT). Fulfillment runs async so spikes don’t take the site down.
Multi-tenant ticketing platform now processing live events across Dubai and Abu Dhabi, including regulatory-compliant checkout for DTCM and DCT. The async fulfillment layer handles order spikes without downtime.
Regulatory payment flows, seat inventory under concurrency, and fulfillment that must stay correct when Kafka queues back up — there’s no “fix it in the morning” when money and tickets are on the line.
Agencies were running client work across spreadsheets, a separate CRM, invoicing tools, and email — nothing stayed in sync and clients kept asking for “one place” to see their projects.
I built the full-stack workspace end to end: CRM and pipeline, projects, branded client portals, tokenised invoice links, org-level branding, and AI assistants on leads and activity — one product surface instead of four subscriptions.
Full-stack agency workspace — CRM, invoicing, client portals, AI-powered lead assistants — used by teams who replaced 4 separate tools with one platform.
Two tenant layers (platform + org), public invoice links that must stay secure, and AI features that had to feel native to the CRM — not a chatbot stapled onto the side nav.
Plumbing, HVAC, and electrical businesses were dispatching jobs over phone and paper. Technicians needed maps, signatures, and estimates in the field — owners needed one system, not three apps that don’t talk.
I shipped core ticket, technician, and estimate modules on a single cross-platform codebase: GPS and job maps, on-site photos and signatures, scheduling, analytics, and in-app subscriptions — iOS, Android, and PWA from one build.
Cross-platform field-service CRM deployed to iOS, Android, and PWA. Technicians manage tickets, GPS routing, estimates, and subscriptions from one app — no laptop required.
Offline-tolerant field flows, role-heavy permissions (owner / sub-agent / technician), and store-ready mobile with real money subscriptions — every bug shows up in a van with bad signal.
An energy and HVAC operator needed partners, dispatch, and technicians on different surfaces — but one ticket lifecycle from start to approval. Spreadsheets couldn’t enforce status or billing rules.
Three-tier product: admin console for partners and dispatch, API with a real ticket state machine (start → block → close → approval), and a technician mobile app with push and field plugins. Payments and notifications wired into the same flow.
Dispatch, partner admin, and technician apps sharing one live ticket lifecycle — jobs tracked, approved, and closed without WhatsApp handoffs.
Three apps, one source of truth, and field users on unreliable networks. State transitions had to be strict enough for billing and loose enough for real-world delays on site.
Pilgrims needed step-by-step guidance through Umrah and Hajj rituals in high-stress, crowded environments — often with poor connectivity and no room for a confusing app.
Solo-built mobile companion: structured day-by-day flows, location-specific content, offline-friendly guides, push reminders, and native share/haptics — shipped to both app stores.
Pilgrimage companion used by people with 1L downloads — rituals, duas, and paths that work when it matters, not just on hotel Wi‑Fi.
Content-heavy UX that must stay calm and trustworthy, offline behaviour for sacred sites, and app-store quality as a one-person team.
Outcomes from shipped work — paraphrased from real engagements. Named references available on request; replace with signed quotes as you collect them.
"Our agency was juggling spreadsheets and three tools. The workspace he shipped is what the team opens every morning — clients, projects, invoices, and AI assist on leads in one place."
"Technicians needed maps, signatures, and offline-tolerant flows in the field — not another admin dashboard. The mobile CRM shipped to both stores and became how the business runs jobs day to day."
From teaching assistant at Coding Ninjas to enterprise ticketing at Ticmint — five chapters across edtech, agency product design, field-ops CRMs, and platforms that still run in production.
Teaching assistant
Started here as a TA — reviewing code, running sessions, and helping students ship their first real projects. Where I learned to explain systems clearly and debug under pressure.
Associate software engineer
Built production systems end-to-end — Ticketinry (field-service CRM for trades), Energy TMS (admin + API + technician mobile), and companion apps. Three-tier products, payments, push, and field workflows.
Software engineer
Shipped features inside a high-traffic learning platform — performance, reliability, and navigating large codebases with fast release cycles.
Full-stack engineer
Designed and built service-based products for clients — from UX and visual surfaces through APIs and deploy. WorkOS and similar CRM/workspace tools lived here.
Backend engineer · ticketing
The best stretch yet on a multi-tenant B2B2C ticketing platform — orders, regulatory checkout (DTCM/DCT), Seats.io, BullMQ + Kafka fulfillment across a NestJS monorepo. Still shipping core modules today.
I’m an AI systems builder and full-stack engineer who builds the unfun parts — multi-tenant data models, payment + webhook flows, automation layers, queue-backed fulfillment, and mobile apps that survive a bad connection. The stuff that decides whether your product is trusted on day 90.
What I believe. Most products fail quietly — not in launch week, but on day 90 when the data model cracks, webhooks double-charge, or "we'll fix permissions later" becomes a support ticket fire. I build the foundation first: tenant boundaries, async fulfillment, observable AI layers, and APIs your team can reason about. Speed comes from rigour, not shortcuts.
Five years in, mostly NestJS + Angular + Next.js + PostgreSQL, with Ionic + Capacitor when the work goes mobile. I’ve shipped enterprise ticketing platforms, agency CRMs, field-service systems with technician apps, and pilgrimage companions used during Umrah — each one carrying real money, real schedules, or real obligations.
I work end-to-end: data model, API, jobs, UI, mobile, deploy. Claude for architecture sketches and multi-file refactors, Cursor for inline edits, GPT for SQL and boilerplate — the output ships faster because I'm reviewing the AI, not the other way around.
I'm also building toward healthcare — working with practice managers and ops leads on the back-office systems that determine whether a practice gets paid: billing automation, denial tracking, credentialing systems, and the AI layers that connect them. HIPAA-aware and familiar with the RCM workflow from prior authorization through collections.
Kafka + BullMQ fulfillment, DTCM regulatory checkout, multi-tenant NestJS at scale — the interesting work is in production, not slide decks. I publish build notes on LinkedIn, develop talks from real projects, and ship long-form articles on the topics below. Ask for a draft or booking.
Ongoing · multi-tenant SaaS, AI in production, fulfillment
TalkAvailableTenant boundaries, migrations, and what to get right before scale
TalkAvailableDrawn from enterprise ticketing fulfillment in production
ArticlePublishing soonPayment flows, compliance APIs, and rollback strategy
ArticlePublishing soonEvals, cost controls, and product-shaped LLM features
ArticlePublishing soonThe gap between coding accuracy, denial management, and credentialing delays — and why it compounds silently.
ArticlePublishing soonA systems view of payer enrollment chaos, and what a proper credentialing tracker actually needs to do.
ArticlePublishing soonWhere AI automation earns its keep in revenue cycle operations — and where it still needs a human in the loop.
Currently booking projects · reply within 24h · Pick what feels lowest-friction.