Khalid Rizvi, pencil portrait

Hello, and welcome in. I’m

Khalid Rizvi.

I design systems, build them myself, and lead the teams that ship them.

I came into software from mechanical engineering, so I think about a system the way you would think about a machine, with real parts, real limits, and a habit of surprising you the moment you look away. For about thirty years I’ve built the consequential kind, for hospitals, banks, utilities, and federal agencies. The sort that has to keep running long after everyone has gone home. And the whole time, I never split the architect from the engineer. I draw the design, and I write the code that carries the weight.

These last few years I’ve pointed all of that at AI: taking generative and agentic systems from a promising demo to something you can actually trust in production, where a wrong answer has consequences. That is the work I care about now, making AI real rather than just impressive. And after all this time, I still write code most days. I expect I always will.

Right now I’m building generative and agentic AI on top of real enterprise systems.

A bit about me

Every system I’ve shipped had one requirement in common: it had to keep running.

The last few years tell it best. I’ve been taking generative and agentic AI from a promising demo to something large companies can trust in production, the retrieval, the workflows, and the testing that keeps it honest. I can do that because of everything that came before it: three decades of building the quiet, consequential kind of software for hospitals, utilities, federal agencies, and banks, the sort that has to keep running long after launch.

What I’ve learned, over and over, is that the hard part is rarely the technology. It’s turning uncertain business requirements into software people can depend on. That takes a team, and I lead the way I like to be led: in the work, alongside everyone else, sharing the accountability through delivery.

More about me →

Things I've built

Four systems, owned end to end.

Different projects, but the way I build stays the same. Keep the important logic dependable, keep a clear record of what happened, and let AI help rather than make the final call. Each one has a short “Behind the Build” if you want to see how it came together.

Live · multi-tenant SaaS

ClinSupplyCompass

Closed-loop clinical-supply planning, proven against the 130-sheet workbook it replaced.

  • Python
  • FastAPI
  • PostgreSQL · RLS
  • HTMX
  • Anthropic Claude
  • Supabase

Live · free pilot

HeyLayla

A private, verified matrimonial platform: a public site, a member PWA, and an operator console over one API.

  • TypeScript
  • React 19 PWA
  • Astro
  • Hono
  • Postgres · Supabase
  • Fly.io

Pre-launch

Care Partners at Home

A multi-tenant operating platform for a home-care agency: operator, caregiver, and family, over one auditable workflow.

  • Next.js
  • PostgreSQL · RLS
  • State machines
  • Append-only audit
  • SMS-first comms
  • AI workflows

For sale · in negotiation

Hunt Planner Pro

A productized planning-and-booking experience for guided hunts, built as a transferable commercial asset.

  • React
  • TypeScript
  • Vite
  • Typed content model
  • Supabase (integration seam)

Away from the desk

The person behind the work.

I’m a family man and a man of faith, and that’s the center everything else turns around. It keeps me patient, grateful, and honest about what matters.

When I can, I’m outdoors. I hunt, though not really for the trophy. It’s the discipline of it: the early mornings, the long stalk, the respect you owe the animal and the land, and the quiet that’s hard to find anywhere else.

A trip to the bushveld →

Currently reading

What is on the desk this quarter. Some of it will end up in the writing; some will quietly fail to be useful.

  • Paper

    Mamba: Linear-Time Sequence Modeling with Selective State Spaces

    Gu & Dao

    Re-reading to keep the alternatives to the transformer architecture honest in my head.

  • Paper

    Lost in the Middle: How Language Models Use Long Contexts

    Liu et al.

    Useful reminder when designing retrieval contexts: the position of the answer matters as much as its presence.

  • Book

    A Philosophy of Software Design

    John Ousterhout

    On modules as deep abstractions. I return to it about once a year and find something I missed.

  • Essay

    Notes on AI Engineering

    Various, around the web

    Reading widely on how teams are actually putting LLMs into production. The good ones are specific; the rest are theatre.

Something to listen to while you read.

The listening room searches the world’s public radio, by genre, artist, or song, and plays it live, right here. Good for working, reading, resting, or a long train ride. Worth a bookmark.

Enter the listening room →

Let’s talk.

Maybe you’re hiring for a principal-level role, or weighing an architecture or an AI initiative, or you want an engineer who’ll own it from design all the way through to production. Whatever it is, I’d be glad to hear from you. A short paragraph about the problem is the best place to start.

Based in
Vienna, Virginia

No forms, no calendar links. Just a note.