If you have
People re-key data between tools that do not talk to each other.
You get
I connect the systems and make the handoff a job with retries and an audit trail.
Problems I solve · Lahore, open to remote roles
Problems I solve
Workflows that span systems that do not talk to each other. I make them reliable, and add AI where it helps.
If you have one of these
Each one is backed by a case study.
If you have
We want AI, but our data lives in an ERP or a scheduling system.
You get
I build the AI layer on top of the system of record, not a second copy of it.
If you have
The AI demo works. Production does not.
You get
I find what breaks between the demo and real traffic, and fix it at the root.
Proof: A production AWS backend →
If you have
Signals arrive from everywhere and nobody sees the important ones.
You get
I build ingestion, search and alerting that says why it fired.
If you have
The system runs, and nobody trusts what it shows.
You get
I trace the numbers back to their source until they add up.
Proof: An operations console for a healthcare integration engine →
When nothing is defined yet
From an unclear ask to something shipped.
-
1A vague ask
Write down what the client means, not just what they said.
-
2Pin down what is known
Turn it into numbered requirements. Mark what is still open.
-
3Design around the open parts
Keep the architecture stable while decisions are still pending.
-
4Show it early
A working demo the client can react to, traced to the requirements.
-
5Ship and hand over
Production, documentation, and a codebase someone else can own.
When something is broken
The same four steps, every time.
-
1Notice
Something looks plausible but wrong.
-
2Trace
Follow the number back to its source.
-
3Fix the cause
Fix the root, not the symptom, then prove it.
-
4Keep the rule
Write down what to check next time.
Open to select engagements
Tell me what the system is doing. Tell me what it should be doing.
Lahore, Pakistan · PKT (UTC+5)
Describe the problem