A support agent that
handles the easy stuff.
Answers routine storefront requests using order and policy data. Refunds and sensitive cases go to a person.
ever has to touch.
Every ecommerce team has this list. Same jobs, every single week.
I build the AI agents and automation that cross them off, and keep crossing them off.
What’s left is the work only people can do.
Monday
Four of these desks already handed a repeated job to an agent. The work still gets done every day; people just stopped doing it. Tap a tag to see which job.
Two hooks are still free. Which job would your team hand over first?
Boring agents your team trusts.
Not a moonshot. One job your team repeats every day, done the same way every time, so people trust it before anything grows.
Good engineering feels like one less thing to think about.
I started on the operations floor, so I learn the job as it is really done: real tickets, real spreadsheets, real handoffs, and the sticky note on someone’s monitor that explains everything.
The agent gets the request, the policy, the tool it needs and exactly one job. Anything that can be a plain rule stays a plain rule. Not everything needs a brain.
Retries, monitoring, the exception nobody mentioned until Thursday. I ship it, then stay and keep it running with the people who rely on it.
Four real systems, still clocking in every day, built with the teams that use them.
Answers routine storefront requests using order and policy data. Refunds and sensitive cases go to a person.
Follows each case across support, operations and finance, so nobody has to ask again what happened.
Replaces disconnected spreadsheets with one shared view of stock, sales, support and finance numbers.
Lets a team work through a whole day’s repetitive jobs in one pass, with stock kept in step automatically.
ZavrAIStaff
Bilal Ahmad
On paper: Co-founder of ZavrAI. Building AI agents that run in production.
ZavrAIStaff
Bilal Ahmad
Honestly: I did the Monday jobs by hand, every department’s, and learned where the work breaks.
Bilal, pronounced Bee-Laal
I started on the team doing these jobs by hand: copying, matching, chasing. So I knew which ones deserved crossing off long before I wrote any code.
Today I lead automation at Nysonian and co-founded ZavrAI. I build AI agents and automation for ecommerce teams.
These days the job is making every team’s Monday list a little shorter: something dependable and boring first, more once people trust it.
ECS
2023 to 2025
Ran the floor. Learned where work breaks, usually at five on a Friday.
Nysonian
Early 2025
Wrote down every manual process. The list was long.
Nysonian
Mid 2025
Built the automation program from scratch, starting with the most boring job.
Nysonian
Aug 2025 to now
Promoted in six months. Now I own the roadmap, the team and the Monday list.
The agent reads your orders and policies, then answers.
One place the records live, and code that checks them.
The store, the stock system and the sheet agree.
The glue between the tools your team already uses.
Short, honest answers. Cross off the doubts before the call.
I build AI agents and automation that take repetitive work off ecommerce teams: customer support, operations, finance, sales, marketing and inventory. I connect your tools, give the agent the context it needs, and keep it running in production after the demo is over.
No. Your first agent should be boring. Start with one task your team repeats every day and make it dependable. Add complexity once people trust it. An ambitious agent nobody trusts gets switched off.
Yes. A support agent can answer routine, low-risk requests like where-is-my-thing and how-do-I-reset questions, and close them quickly. Refunds and sensitive conversations go to a person by design. The goal is a shorter queue, and customers can still reach your team.
Claude API and tool calling for agents, n8n and Python for workflows, PostgreSQL for data, and integrations with Shopify, WooCommerce, Slack and your helpdesk, spreadsheet, accounting and inventory tools. I also work with RAG, Ollama and TypeScript. I pick the tool that fits the problem, not the one with the best launch video.
A focused first automation is usually a few weeks from scoping to live in production. Retries, monitoring and the edge cases nobody mentioned are part of that work from day one, not a phase two that never comes.
I lead automation at Nysonian and co-founded ZavrAI, and I take on selected projects and roles. I work remotely with teams anywhere. The fastest way to check fit is a short discovery call. Bring your Monday list.
I’m here to
A support inbox, a stock sheet, month-end matching, a Monday report. Drop it in the tray and we’ll take it off your team’s list.
30 minutes. You describe the job, I tell you straight whether it’s worth automating. No deck, no hard sell.
I’m in Pakistan (PKT, UTC+5) and work remotely with teams anywhere.
Hi, thanks for scrolling all the way to Friday.
To me, good automation is quiet. It just works, every day, without anyone thinking about it.
If something here stuck with you, say hello.