Three ways to work together
Every engagement starts the same way: a free 20-minute call where you bring the problem and leave with how I'd approach it. From there, pick the shape that fits.
~1 week · $500 fixed
You have a problem and want clarity before committing to a build — mine or anyone's. I take one workflow or system idea and return:
- An architecture doc with the reasoning, not just the diagram
- Tool selection, including where the cheap option wins
- A build plan with effort and cost estimates
$500, fixed. The deliverable stands on its own. If you take it to another engineer, it'll still be money well spent.
2–6 weeks · quoted upfront
A defined system, shipped: a RAG pipeline over your internal docs, an agent workflow, an automation backbone, an internal tool. Scoped and quoted before work starts, often straight from a Design Sprint.
- Working system, deployed to your infrastructure
- Handover docs your team can actually operate from
- A walkthrough call, and a window for fixes after delivery
monthly · limited slots
For teams whose AI and automation systems have become load-bearing and need an owner. I extend, maintain, and iterate. Async-first, with a weekly sync.
- Continuous improvements instead of big-bang rebuilds
- Monitoring and fixes before you notice the breakage
- A standing brain for "could we automate…?" questions
Strip the jargon and it's this: work your team currently does by hand — answering repeat questions, moving data between tools, triaging inboxes, chasing leads — gets done by a system instead. Reliably, visibly, and in a way you own outright.
Not sure which shape fits? That's what the free call is for. Book it and come with the messy version of the problem.
Who owns what you build?
You do. Code, workflows, prompts, docs, accounts — everything is set up under your ownership from day one. No lock-in by design: the handover docs exist so you could replace me.
You have a day job. Will my project get real attention?
Yes, because I take on few projects at a time and scope them honestly. You'll know the realistic timeline before we start, and I'd rather turn work down than miss a commitment. The day job is also why my rates buy production experience, not first attempts.
What about the timezone?
Karachi is UTC+5: my working day fully overlaps EU mornings and comfortably reaches US afternoons. I work async-first, with clear written updates, and calls scheduled in your window.
Which tools do you use?
Whatever the problem deserves. The usual suspects: LangChain, LangGraph, CrewAI, FastAPI, Supabase, n8n, Airtable, GoHighLevel, and the OpenAI / Claude / Gemini APIs. If your problem is simpler than an agent framework, I'll say so.
What does it cost?
The Design Sprint is $500, fixed; builds are quoted per scope after the free call; retainers are monthly. No surprise invoices — every number is agreed before work starts.
What happens after delivery?
Every build ships with docs, a walkthrough, and a fix window. If you want the system to keep evolving after that, that's what the Systems Partner shape is for.
Bring me the problem. Leave with how I'd build it.
A 20-minute architecture call. No pitch, no slide deck. If I'm not the right person for it, I'll say so and point you somewhere better.