Currently building 24on.ai

Most AI never leaves the demo. I build the part that runs in production.

I build systems for the place where things are actually stuck. A messaging stack nobody connected. An ERP that never reaches the sales pipeline. An AI pilot that impressed the room and shipped nothing. I find where the time is going, design the system that removes it, and stay accountable for it long after launch.

Riyadh, Saudi Arabia Architecture through to production
6Years shipping production software, cloud and applied AI
4Systems designed and built end to end
20+Platforms integrated: ERP, messaging, payments, LLM providers
6Agentic AI & LLM certifications, 2026

Selected work

Four systems. Every one of them started as something broken.

Each card below reads the same way: what was going wrong before, the system that replaced it, and the hard facts of the build. Architecture, implementation, deployment and everything after launch, end to end.

Flagship · Live

Aunwan

Live

Describe an event in one sentence. Get a plan, a budget, and vendors who actually exist.

Problem
Organising an event in the GCC means assembling a venue, AV, booths, catering and staffing from five separate vendor networks, mostly over WhatsApp and personal contacts. Nothing is priced until you ask, every timeline has to work around Ramadan, summer heat and permit windows, and an organiser without the right contacts cannot see the market they are buying from. The generic AI tools are worse than useless here: ask one for a vendor and it will confidently invent a company that does not exist.
What I built
A two-sided marketplace with an AI copilot, Dalil, sitting on top of it. An organiser describes the event in plain language and gets back a structured plan across venue, AV, staffing and catering, a budget, and a shortlist of verified vendors. The copilot then drafts the brief and hands it to the posting wizard, so the organiser reviews and posts rather than writing a specification from scratch. Crucially it answers only from real marketplace inventory, so every vendor it names is one you can actually book, and the planning logic carries GCC scheduling rules rather than treating the region as a generic calendar.
  • 5vendor categories, venues through to staffing
  • Groundedanswers come from bookable inventory, never an invented supplier
  • GCC-awareplans around Ramadan, summer and permits
AI copilotTwo-sided marketplaceVendor verificationBrief & order workflow
aunwan.com
aunwan.com

aunwan.comOpen the live site

launchaudit.app

launchaudit.appOpen the live site

LaunchAudit

Live

The check a vibe-coded project skips on its way out the door.

Problem
Anyone can ship a working product in a weekend now. Almost nobody audits it first. Generated code goes live carrying exposed keys, missing security headers, no indexing rules and pages that fall over on a real connection. The tools that catch that properly are priced for enterprise, and the free ones hand back a score with no reasoning, so nobody knows what to fix first.
What I built
A multi-tenant SaaS that runs the full audit as a background job and returns written findings rather than a number. Crawling and analysis sit behind a queue so a slow site never blocks the app, and Claude turns raw results into prioritised, plain-language reasoning you can act on before launch, not after the first incident.
  • 3audit domains: security, SEO, performance
  • 5pricing tiers, self-serve checkout
  • Asyncqueue-backed crawl pipeline
Next.js 15Node.jsPostgreSQLRedisBullMQClerkStripeAnthropic API
launchaudit.app

Agency OS

Under testing

A whole agency runs on one system instead of four tools and a spreadsheet.

Problem
Agencies run people, clients and payroll in separate tools that never talk. Answering a question as basic as what a client actually costs to serve means a manual reconciliation nobody has time for, so nobody does it and the agency prices work on instinct.
What I built
Team, client and payroll management on a single data model, so hours, cost and delivery roll up on their own. One record per person and per client, no re-keying between systems, and the margin on a client is a number the system already knows.
  • 4 → 1tools consolidated
  • 3modules, one data model
  • 0manual reconciliation steps
Full-stack platformMulti-module

24on.ai

In development

The one I'm not talking about yet.

Problem
Every team now has AI that can answer. Almost none have AI that can finish. A model finishes a sentence and hands the work straight back, so the messy middle of a job, the part with the tool access and the judgement calls and the twelve steps nobody wrote down, still lands on a person. That gap is where the real cost sits, and it is not a prompting problem.
What I'm building
An agent platform aimed squarely at that gap. Agents that hold context across a long task, act on real systems rather than describing what they would do, and are accountable for an outcome instead of a reply. It is the largest thing on this page and the one everything else has been practice for. Details when it ships.
  • Agenticbuilt to finish work, not answer questions
  • Long-horizoncontext held across an entire task
  • Quietmore at launch
Agent orchestrationTool use

How I work

The expensive problem is the one nobody has scoped yet.

Teams usually know their tools are slow. What they cannot see is where the cost actually sits, because it hides in the gaps between systems rather than inside any one of them. Finding that gap is the first job, and it is the one that decides whether the rest of the work is worth doing.

01

Find where the time goes

I sit with the process before I touch the architecture. The bottleneck is almost never where the complaint is. It is usually a handoff between two systems that were never introduced, and someone quietly absorbing it by hand every day.

Process mappingSystems auditCost of the gap

02

Build the narrowest thing that fixes it

Not a platform, not another pilot. The smallest system that removes the manual step permanently, designed so it still holds when the volume triples and the person who understood it has moved on.

ArchitectureImplementationIntegrationHandover docs

03

Stay on the hook after launch

Shipping is the halfway point. I own deployment, monitoring, hardening and the fixes nobody scoped, because a system nobody maintains quietly turns into the next bottleneck.

DeploymentMonitoringHardeningIteration

Where I'm strongest

Three kinds of problem I get called for.

01

Applied LLM systems

The hard part is not calling a model, it is deciding where one genuinely helps and then making it dependable enough to sit in a workflow. Multi-agent orchestration, RAG and vector pipelines, structured outputs and function calling, with a local deployment path for data that cannot leave the building.

AI video pipelineCatalogue generationMulti-model routingPrompt frameworksLocal inference

02

Automation & integration

Most operational pain sits in the handoff between two systems that were never connected. Odoo ERP wired into the leads pipeline. Self-hosted Chatwoot carrying live client messaging across WhatsApp Business and Twilio. Payments and custom REST services underneath, so nobody re-keys data by hand again.

Odoo ERPChatwoot self-hostedWhatsApp Business APITwilion8n · Make

03

Architecture & infrastructure

Platforms that still hold up two years after launch, which is a design decision made early and not a thing you add later. Next.js and Node across AWS, Azure and self-managed VPS, with queues, caching, CI/CD, Linux administration and security hardening.

AWS · AzureDockerQueues & cachingCI/CDLinux hardening

Stack

What I reach for, and why.

A tool list on its own tells you nothing. Here is what each part of the stack is actually for in the systems above.

Languages

Python for AI and data work, TypeScript everywhere a browser is involved, SQL for anything that has to stay correct under load.

Python · JavaScript · TypeScript · SQL

Frameworks

Next.js and React for the product surface, Node for the services behind it, Laravel when a client is already there and a rewrite would be the wrong advice.

Next.js · React · Node.js · Laravel · Tailwind CSS

AI & LLM

Model chosen per task and per cost, never one provider for everything. Local inference when the data is not allowed to leave the building.

Claude (Anthropic API) · GPT-4o · Gemini · OpenRouter · Flowise · Ollama · LM Studio · NVIDIA NIM

Data & backend

Relational by default, because most data turns out to have relationships. Queues and caches anywhere a person would otherwise sit and wait.

PostgreSQL · MongoDB · Redis · Supabase · BullMQ · SQLite · REST APIs

Cloud & DevOps

Managed where it buys time, self-hosted where it saves real money or the data has to stay in a specific country.

AWS (EC2, S3, Lambda, RDS) · Azure · Vercel · Docker · VPS administration · CI/CD · Git

Integration

The layer where most operational time is lost, and the layer where most of it is recoverable within weeks rather than quarters.

Odoo ERP · Twilio · WhatsApp Business API · Chatwoot · Stripe · Clerk · n8n · Make · Zapier

Architecture & practice

The decisions that determine whether a system is still maintainable a year later, made before the first line is written.

Multi-agent orchestration · RAG & vector pipelines · Prompt engineering · Structured outputs & function calling · Local LLM deployment · Systems architecture · SaaS platform build · Workflow automation

Background

Trained as a software engineer first. The AI came after, on purpose.

A three-year engineering diploma sits under the applied AI work, which is the reason these systems get designed before they get built. The 2026 certifications are the current end of that line, not the start of it.

Advanced Diploma in Software Engineering

Aptech Pakistan · 2019–2022

Formal grounding in programming fundamentals, object-oriented design, database management, full-stack development, testing and QA, and software project management.

Digital Marketing & SEO

IDM Pakistan · 2022–2023

Diploma in Graphic & Web Design

Arena Pakistan · 2018–2019

Certifications · 2026

  • Agentic AI Fundamentals: Architectures, Frameworks & Applications
  • Advanced LLMs with Retrieval Augmented Generation (RAG)
  • Building Agentic AI Systems
  • Agentic AI Planning & Reasoning Design Patterns
  • Build with AI: Claude Code Subagents
  • Automate Your Workflows with Generative AI

Contact

Tell me what's broken.

If you have a system that should work and doesn't, that is the conversation I want. Fastest reply is email.