Work with me · Taking new work

AI automation for founders and agency owners stuck in the day-to-day

I'm Hamza Akbar, COO of Zelevate. I build automations for operations and sales, so the work your team repeats every week runs on its own and you get your time back for growth. I build inside the tools you already pay for.

Send details How it works

Last updated

Who this is for

Founders and agency owners whose business still depends on them showing up every day to keep delivery moving. You'll probably recognise a few of these:

  • You're still the one checking, chasing and approving most of the daily work.
  • The same reports, updates or handoffs get done by hand every week.
  • You bought a tool, or someone built an automation, and the team quietly went back to the old way.
  • Follow-ups with leads depend on whoever remembers to send them.
  • You know the business could grow, but delivery eats the hours you'd spend on it.

Probably not a fit if

  • You're not sure yet what you want the tool to achieve. We'd end up building it twice.
  • Nobody on your side has time to walk me through how the work is done and check what the system gives back.
  • You run an Amazon brand and want ad management. That's Zelevate's work, and this page is about something else.

From first message to handover

  1. Send a few details and book a time.The form takes a couple of minutes.
  2. First call.You tell me what keeps going wrong. I'll ask a lot about how the work gets done today.
  3. Written list.Within 3 business days you get it in writing, and we go through it on a second call.
  4. Build.I work with the person who does the job, so the logic matches how the work really happens.
  5. Check it against real results.Your team compares what the system produces with their own work. It doesn't get handed over until they match.
  6. Hand over, or I keep it running.Your call.

Three ways to work together

Process review

You pick the work that eats the most time, or the part you suspect is broken. On a call, you or your team take me through how it actually gets done today, workarounds included. Within 3 business days I send a written list of what to automate and what to fix first, in order. Then we go through it together on a second call.

Takes3 business days from the first call to the written list.
You end up withA priority list you can act on with me, with your own team, or not at all.

Build one system

We pick one process. I work through the logic with the person who does that job every day, then build it in the tools you already use. Usually a working version is live for you to test within 7 working days. Bigger builds take longer, and you'll know that before we start.

Your team then checks what it produces against their own work until they trust it.

You end up withA working system in your own accounts, and a written guide on how it runs.

Ongoing help

For when you want more than one system, or want someone looking after them. It works one of two ways. I build systems your team runs day to day with a little support from me, or I run and maintain them myself. Open-ended, and shaped around what you need.

You end up withSystems that keep up as the business changes, and someone to build the next one.
Price, for all three: Depends on scope. You'll get a number once I understand what's involved.

What I'll need from your side

Access to the tools the system touches. Only what you approve.
One person who does the task today and knows the steps behind it. They're the one who tells me if the output is right.
Some of that person's time while I build and while we test.
Someone who can make a decision when the logic needs one. Often that's you.

What I've built so far

35people on the team I run at Zelevate
70+brands the team works with
20+systems I've built for it
6 → 10brands each operations manager now handles

Some of those systems, and what I learned building them:

Case studyDiagnosing a stalled product: 2–3 hours down to 5 minutesA tool that tells project managers why a product stopped growing. 300+ analyses run so far.ExampleWeekly brand updatesFrom 8–10 min per brand to under 1 min a week.ExampleAmazon support ticketsReplies stopped getting missed, without buying new software.PostHow I decide what to automateThe two tests every tool has to pass, and a 2-minute check you can run on your own task.

Questions people ask first

Do I need to know code?

No. You tell me how the work gets done and check what comes out. I don't write the code by hand either. I work out the logic, build it with Claude, and test it against real work.

What tools do you build on?

Mostly what you already have. Google Workspace, Apps Script, Claude, ClickUp, Slack, Zapier and others. I'll only suggest new software if the job really needs it, because every new subscription is a cost you keep paying.

Do you still run Zelevate?

Yes, I'm still COO. That's on purpose. Running a business every day keeps me thinking like an operator, so I build for the people who'll actually use the system.

How long does it take?

A process review's written list comes within 3 business days of the first call. A first automation is usually live for you to test within 7 working days. If yours will take longer, you'll know before we start.

We've tried tools and automations before and they didn't stick. Why would this be different?

Usually one of two things went wrong. Either the tool couldn't finish the whole task, so someone still did part of it by hand. Or a founder saw a problem and built a fix without asking the people who'd use it, and the team treated it as one more job instead of something that helped. I build with the person who does the work, and nothing's handed over until it completes the task end to end.

Who on my side needs to be involved?

One person who does the task now and knows the logic behind it. They help me get the steps right and check the output against their actual work.

Who fixes it if something breaks later?

Everything sits in your own accounts and tools, so you own it and your data stays with you. I only access what you approve. Your team gets a written guide to run it, or I can keep maintaining it on a retainer.

Taking new work

Tell me what's eating your team's week

Send a few details about how things run now and I'll take it from there.

  • I read every message myself
  • Reply within 24 hours with a time to talk
  • Remote, or on-site in Pakistan. Calls in most time zones.
Hamza AkbarCOO, Zelevate

So I can read up before we talk.

A few lines is fine. Write it the way you'd say it.

Tools, automations, hires, anything.

I'll only use your details to reply to you.