Muhammad Asad Tanwir

The Dispatch

An architect who never stopped shipping

A few weeks ago he posted a coffee invitation to an entire city. "Hello Riyadh," it began, and the rest was an open door: anyone working on AI, technology, or stubborn problems was welcome to trade ideas over a cup. No badge, no booth, no pitch deck required. That is the working style of Muhammad Asad Tanwir in one paragraph.

The Riyadh stint is the current chapter. Tanwir has been there on AI-driven projects tied to Azm Development, a Saudi technology firm that builds custom software for fintech, health, education and telecom. When his stay made the rounds on LinkedIn, a colleague did not say he was capable or experienced. They said he was the company's biggest gem. People reach for that word when someone is hard to replace and easy to like.

He is based in the Netherlands, of Pakistani heritage, and his projects routinely cross three regions before lunch. The geography matters less than the habit underneath it: he keeps showing up where the hard problem is, not where the comfortable seat is.

Rewind the tape and the through-line is consistency. Tanwir spent roughly six years at Wiseman Innovations, a long stretch of it as a resident software engineer - the person who lives inside a product long enough to know where the bodies are buried and how to dig them out cleanly. Six years anywhere is a quiet kind of achievement in an industry that prizes the eighteen-month hop. He stayed long enough to be dependable, then left to chase something newer.

What makes him unusual is the span of the job description. Most people pick a lane. Tanwir's CV reads like an entire software organization compressed into one person: ecosystem architecture, cloud transformation, DevOps, pre-sales, program management - and then, underneath all of it, the actual code. Angular on the front, .NET MVC and C# in the middle, MS SQL and Azure holding it up, CI/CD wiring it together. He can sell the vision in the morning meeting and ship the thing that proves it by night.

That combination is rarer than it sounds. The architect who can talk to a customer usually stops writing code. The developer who loves code usually flees the sales call. Tanwir does both, which is why the word "pre-sales" sits comfortably next to "lead developer" on the same line of his profile. He is the translator in the room - turning what a client wants into a system that an engineer can actually build, and back again.

Writing the manual he works from

There is a tell in how engineers spend their spare attention, and Tanwir spends his explaining. In early 2023 he published a pair of technical walk-throughs on building Microsoft Teams applications - one on webhooks and connectors, another on standing up a Teams app from scratch. They are not thought-leadership fluff. They are the kind of step-by-step notes you write when you have done the thing, hit the sharp edges, and decided to leave a map for the next person.

It says something about how he thinks. He does not just want the connector to work; he wants the reasoning behind it to be legible. The article and the implementation come from the same instinct - finish the job, then make it repeatable for everyone who comes after.

From product to platform

The newest turn is the most telling. After years of building enterprise applications - the .NET-and-Azure machinery that keeps companies running - Tanwir has pointed himself at AI. Riyadh is where that bet is currently being placed, against the backdrop of a region pouring money and ambition into technology. He showed up at Money20/20 Middle East too, working the fintech crowd, because that is where the conversations about what to build next are happening.

You can read the move two ways. One: a seasoned architect following the heat. Two: someone who has spent a decade learning how to make systems talk to each other, now applying that to the systems everyone is suddenly obsessed with. Both readings are probably true. Ecosystem architecture - his stated specialty - is exactly the muscle AI products need, because the model is never the hard part. The plumbing around it is.

What he has not done is make noise about it. The Riyadh post is striking precisely because of how low-key it is. No grand claims about disruption, no thread of predictions. Just: I'm here, I'm working on something, come have a coffee. It is the confidence of someone who would rather show you than tell you.

The shape of the next thing

Where this goes is still being written. The AI projects he is on are not public, and Tanwir is not the type to pre-announce. What is clear is the direction of travel: away from being the hands on a single product, toward being the person who designs how many systems fit together. The architect's job, fully realized.

If you want the quick read on him, skip the title and watch the pattern. He stays long enough to matter, leaves when the next problem is more interesting, writes down what he learns, and invites strangers for coffee in cities he has only just landed in. Catch him mid-stride - which is the only way anyone ever seems to catch him - and that is what you find: a builder who is still, after ten years, genuinely curious about what gets made next.

The coffee invitation, it turns out, was never really about coffee.