You've got a process that eats hours every week. I make it run by itself.

I build automations in n8n, Make.com and Zapier, and I write the code myself when those hit a wall. One system I built in March is still running without me.

Book a call Email me instead

Twenty minutes · no deck · you'll know by the end whether it's worth doing

Muhammad Arsal Murad
Workflow automation

4–5 hrs → 30 minWeekly job, one client

12,500+Meals processed

0Weeks I've touched it since June

Zapier Solution Partner, Silver / n8n Certified / Make AI Agent Builder / IBM AI Developer — every one clickable

Start here

Does any of this sound like your week?

01
Somebody on your team rebuilds the same report every Monday, and it takes them most of the morning.
02
Enquiries land in three different places and someone has to remember to check all of them.
03
Quotes and invoices get typed out by hand from data that already exists somewhere else.
04
Orders arrive from a few channels and turning them into one workable list is a person's whole afternoon.
05
Two of your tools hold the same information and somebody keeps them in step by copying and pasting.
06
Something was automated once, by someone who's gone now, and nobody dares touch it.

If you recognised even one of those, that's a twenty minute conversation. I'll tell you on the call whether it's worth automating.

Book a call

The work

Things I've actually built

Three of them, in detail, with the numbers left in and the client names taken out where there's a client to protect.

Client system · live in production

Five order types, one weekly job

A subscription kitchen in Japan lost four to five hours every Monday turning five separate order sources into a cook list and a shipping list by hand. The system I built does it now, and holds back anything it can't verify rather than guessing.

~30 minWas 4–5 hours

24+Weeks running

0Weeks I've touched it

Read the full case study →

Loading walkthrough

n8n build · submitted as a template

A video pipeline that survives three unreliable APIs

Takes an Instagram reel, finds every cut, and rebuilds it shot for shot around a different product. The interesting part isn't what it does, it's what it took to stop it falling over. Twenty-eight nodes, every slow step polled rather than waited on.

10,324 msRebuilt timing, exact

28Nodes

3API contracts corrected

Read how it was built →

Own build · open source, live demo online

The failures are quiet. This finds them first.

An installer and verification toolkit for an agency running the same AI receptionist install for many small businesses. Thirteen automated checks run against the live install, not a mock of one, and report PASS, FAIL, or SKIPPED for each.

13Automated checks

9Work against any install

3Bugs only running it caught

Read the full case study →

Interactive · runs in your browser

Run the compiler yourself

I rebuilt the kitchen system's compile logic against invented orders. Hit run, see what it refuses to process, fix those rows and watch the reports rebuild. Nothing to install and no client data anywhere near it.

Try it →

Your process won't look like either of those. The judgement about what to automate and what to leave for a person is the same either way.

Book a call

Credibility

Why I bothered with the certifications

Hiring a stranger for something that touches your orders or your invoices is mostly an act of trust. These exist so that less of it has to be. Every one links out to the issuer, so you can check rather than believe.

Zapier Solution Partner

Silver tier · Zapier

Reviewed and approved into Zapier's own partner directory, where the listing sits on their site rather than mine.

See the listing →

Professional Certificate in n8n

September 2026 · n8n

Issued by n8n's own education team against their platform, not by a third-party training company.

Verify →

AI Agent Builder

Credly badge · Make

Make's advanced agent track, hosted on Credly so the badge is independent of anything I control.

Verify →

IBM AI Developer

Specialization · IBM

Building applications that use AI, which is the background behind deciding what an AI step is allowed to decide on its own.

Verify →

A certificate says somebody passed an assessment. It doesn't say what happens when an API fails at 3am. Here's the honest version of what each one covers.

Book a call

Working together

How it goes

A call, about twenty minutes

You walk me through the thing that's eating your time. I'll ask a lot about what happens when it goes wrong, because that's usually where the actual work is.

I write it down before anything gets built

What it'll do, what it won't, what I need from you and how long it takes. You approve that first, so there's no moment later where we disagree about what you were buying.

I test it against your real data before it touches anything live

Anything the system can't verify, it holds back for a person instead of guessing. On the kitchen system some orders carried allergy information, and a confident wrong answer there reaches somebody's plate.

The part that matters

You keep everything, and you can replace me

It's built on your accounts, your credentials and your subscriptions. You get a handover doc covering how to run it, what breaks and where every credential lives. If you stop working with me tomorrow you keep all of it, and any competent developer can pick it up. The kitchen system has run since June without me touching it, which is the whole point.

Nothing gets built until you've approved what it does in writing.

Book a call

Before you book

The things that stop people

What happens if it breaks after you're gone?

The handover doc covers the failures that actually happen. Past that I'm around, and we agree what support looks like up front rather than you finding out later.

Do I pay for Zapier or n8n on top of paying you?

Usually yes, and it's your subscription rather than mine, so you're not renting access through me. I'll tell you which tier you actually need before you go and buy anything, and quite often it's a cheaper one than you'd expect. Here's how I pick between them.

You're in a different timezone to me.

I'm in Pakistan, UTC+5. That overlaps most of the European working day and US mornings. I'll work your hours when a project needs it.

Can you fix something somebody else built and abandoned?

Yes, and it's a decent chunk of the work. Sometimes the honest answer is that rebuilding costs less than repairing, and I'll say so if that's what I find.

How small is too small?

Nothing's too small to ask about. If it's a twenty minute job I'll tell you it's a twenty minute job and point you at how to do it yourself.

Will you use AI to build it?

For parts of it, yes, same as most developers now. The logic and the testing are mine, and that's the part that decides whether the thing survives contact with real data.

Do you sign NDAs?

Yes. The client behind the kitchen case study is confidential, which is why you're reading about a subscription kitchen in Japan and not a company name.

If something in your week is eating hours every time it comes round, let's look at it.

On the call
You describe the process. I ask where it goes wrong. Twenty minutes, no deck, no pitch.
Within a day or two
A written scope if it's a fit, or an honest no if it isn't. Either way you're not chasing me.
Nothing to lose
You approve the scope before anything is built, so you're never paying for something you haven't seen described.

Book a call Email me instead

You'll be talking
to me, not a team