Define
A fixed set of context files — product intent, domain rules, architecture, constraints, definition of done. The thinking happens here, once.
Ten years learning how real systems break — banking platforms, healthcare networks, lending engines. Then I built my own orchestration engine: a spec goes in, a finished product comes out. I don't use AI. I architect it. And I'm building at a scale this region hasn't seen yet.
Available for select engagements
I started where everyone starts — writing features. Then backend architecture, distributed systems, cloud. Then leading engineers, and the uncomfortable discovery that even excellent developers can't rescue a product when requirements, architecture and business goals are disconnected. That's when my attention moved from code to systems, and from systems to the organisations that build them.
Today I consult at GlobalTech — Center of Excellence, alongside independent engagements. My depth is in domains where being wrong is expensive: banking, lending, underwriting, healthcare, payroll. And I've turned that same architectural instinct on AI — not calling an API, but designing systems of agents that plan, retrieve, verify and ship.
I built my own agentic development engine. It ships with the scaffolding every product needs — the roadmap, the stories, the architecture and context files. Fill those in, start the run, and the orchestra conducts Claude and Codex through the build until the product is standing.
A fixed set of context files — product intent, domain rules, architecture, constraints, definition of done. The thinking happens here, once.
The engine expands the spec into a roadmap and story graph, with dependencies, acceptance criteria and the order of attack already resolved.
Work is routed to the right model for the job. Agents implement, review each other, run the tests and correct their own output.
A working product with a coherent architecture, not a pile of generated files — because the structure was decided before a line was written.
Most teams use AI to write functions faster. That's a small win. The leverage is in encoding your architecture, standards and delivery process into the system itself — so quality stops depending on who is at the keyboard, and speed stops costing you maintainability. That's the difference between using AI and architecting with it.
Systems I've designed and built end to end — each one a proving ground for the architecture behind it.
My agentic build system. Roadmap, stories and context scaffolding, plus a conductor that drives Claude and Codex through implementation, review and correction until the product is done.
A clinical reasoning system where a general medical agent takes the first pass and an orchestration layer escalates harder cases to specialist agents — with retrieval, memory, guardrails and a human escalation path built in from the start.
An always-on front desk that handles enquiries, qualifies callers, books appointments and hands off cleanly to a human — the kind of automation that shows up on a payroll line, not a pitch deck.
Model choice is an architecture decision with a price tag attached. Most AI projects don't fail on capability — they fail on the wrong model doing the wrong job at the wrong cost.
Architecture, ambiguous specs, gnarly debugging. Pay for the strongest model here — this is where a bad answer costs weeks.
Classification, extraction, routine transforms. A fast, cheap model with tight prompts and evals wins on every axis that matters.
Whole-repo reasoning and large document sets. Context window and retrieval strategy matter more than raw benchmark scores.
Multi-step execution with real side effects. Pick for instruction-following and tool reliability, then wrap it in guardrails.
Deterministic rules, financial calculations, anything auditable. A model is the wrong tool, and I'll say so early.
Every routing rule earns its place against a real eval set. Vibes are not an architecture.
A rebuild that keeps slipping. A team that's busy but stuck. An AI initiative that demos beautifully and ships nothing. That's the work I want.
Start the conversationFounders and technology leaders bring me in when a decision is about to get expensive to reverse — or already has. I take a small number of clients at a time, so the ones I take get the depth.
Check availabilityAgentic workflows, multi-agent orchestration, RAG and context engineering, model routing, evals, guardrails and observability — designed around a business number that has to move.
Senior technology leadership without the full-time hire. Strategy, architecture, hiring, engineering process, roadmap, and the calls that are painful to unmake.
A structured audit of architecture, code, security, cloud cost, technical debt, DevOps and team structure — with prioritised recommendations and what each one is worth.
For teams missing every deadline, burning infrastructure budget, or scaling on architecture that was never designed for the load it's now carrying.
Put the Orchestra behind your roadmap. Your architecture and standards encoded into the system, then products built at a pace a traditional team can't match.
Money moving, patients treated, payroll running. Domains where approximately right isn't good enough.
Engineering on a financial platform built to onboard banking institutions. Around 22 banks were onboarded on it during 2022.
MERN microservices for healthcare agency workflows, with WebRTC consultations and government reporting. Around 35 agencies onboarded inside two months.
Lending systems that automate application processing and decisioning, and analyse repayment behaviour to sharpen risk decisions.
Principal engineering across three product lines — and I founded and grew two of them, on containerised backend services built to scale.
Consulting on architecture, technical governance, engineering process and delivery standards — alongside independent consulting engagements.
HRMS and payroll systems, telehealth, digital signage and SaaS infrastructure across a decade of product and platform engineering.
Consultant · current
Architecture, technical governance and engineering standards, alongside independent consulting and AI engagements.
Principal engineer / engineering manager
Digital signage, WiFi music and hospitality product lines — founded and grew two of them on containerised AWS infrastructure.
Lending & automation
Automated underwriting, application processing and repayment-behaviour analysis.
Senior engineering, banking platforms
Banking systems on Node.js, Rails, Next.js, AWS, Azure, MySQL and RabbitMQ. Around 22 banks onboarded during 2022.
Healthcare technology
MERN microservices, WebRTC consultations, agency workflows and government vaccination reporting.
Techverx · People · PayPerfect · Emerald Labs · Logicon · Strategic Systems International
Product and platform engineering across HR, payroll, enterprise and SaaS systems.
Software Engineering, 2016
Where it started.
No team reliably delivers something nobody has clearly defined. Most "engineering problems" start here.
Technical debt compounds like financial debt, and the interest is paid in delivery speed forever.
Decisions rest on the code, the metrics and the tests — not on whoever argued hardest in the meeting.
It exists to create predictability and quality. The moment it becomes paperwork, it's failing.
Bolting an LLM onto a product doesn't make it an AI product, and it doesn't make it better.
The strongest ones understand exactly which economic problem the software exists to solve.
The ambition is simple: build technology that reaches millions, from Pakistan, and prove that the engineering coming out of this part of the world competes with anyone's. Consulting funds it. Products compound it. Here's what I'm aiming at.
Help founders dodge the architecture calls that quietly cost a year of runway.
Turn busy-but-stuck engineering groups into ones that deliver predictably.
Automate expensive manual process, and apply AI only where it visibly pays for itself.
Healthcare, lending and business systems where correctness affects someone's real life.
Mentor engineers here into people who own architecture and delivery anywhere in the world.
Move from selling time, to selling expertise, to owning software that scales without me.
Architecture review, a stalled rebuild, an AI initiative that needs a real plan, or a product you want built fast and built right. Send the short version — I'll tell you what I'd look at first.
Opens your mail app. To capture messages directly, point this at a form service — see the comment in the code.