hello
01 — Who

I help clients turn AI opportunities into real digital transformation — building practical, reliable solutions that improve operations, customer experiences, and business outcomes.

Impact
40%
Manual effort removed
30+
Problems shipped to prod
Faster delivery cycles
Open for
Agentic AIAutomation workflowsComputer visionCloud infrastructureFull-stack product
Kamal

I build AI thatships.behaves.scales.

Scroll to read the story ↓
PythonTypeScriptLangGraphGeminiOpenAIAWSAzureDatabricksTerraformReactNext.jsPostgresPythonTypeScriptLangGraphGeminiOpenAIAWSAzureDatabricksTerraformReactNext.jsPostgres
02 — Story

Four chapters.

How a curious kid with a slow laptop ended up shipping AI for enterprise floors.

Chapter 01 · 2019

It started with a slow laptop.

I learned to code because the machine I had couldn't run anything heavy — so I had to understand what every line cost. That constraint became the habit: build small, measure, then grow.

First build2019
Chapter 02 · 2023 — 2025

Enterprise taught me the unglamorous half.

At AVASOFT and Zeb I shipped into environments where a failed retry is a phone call at 2am. Logging, idempotency, handoffs, rollback plans — the parts no demo shows.

On the floorAVASOFT
Chapter 03 · Now

Now I make AI behave itself.

Agents with guardrails. Retrieval that cites its source. Pipelines that page me before a client notices. Generative AI is only useful when it is boring in production.

Orchestration2026
Chapter 04 · Next

Looking for the next hard problem.

Fixed scope, honest estimates, documentation you can actually read. If your AI feature is stuck between a demo and production, that's the gap I work in.

Next buildOpen
3+
Years shipping
12
Products delivered
4
Case studies
3
Cloud platforms
04 — How I can help

Three ways in.

01 · Fixed scope
Ship one AI feature

A defined build — retrieval, an agent flow, an internal tool — scoped in a week, delivered with docs and tests.

4 — 8 weeks
02 · Retainer
Be your AI engineer

Ongoing capacity across model work, backend and frontend. You get one person accountable for the whole path.

Monthly
03 · Audit
Unstick a stalled build

A read of your pipeline, prompts, evals and cost — then a prioritised plan you can hand to any team.

2 weeks
How I work
“Scope agreed before code. Honest estimates, even when the honest answer is slower. Documentation you can hand to the next engineer.”
My commitment on every engagement
01Define

Scope, success metric and constraints agreed in writing before any code.

02Design

Flows and interfaces first, so we argue about the product on paper, not in a sprint.

03Develop

Small reviewable increments — evals and logs land with the feature, not after.

04Deploy

Shipped with runbooks and handover docs the next engineer can actually read.

05 — Contact

Tell me what you're building.

Send a short brief — what it does, who it's for, when you need it. I reply with scope, timeline and price in one message.