Who runs Wobble

Wobble is run by four co-founders, and each one owns a different part of the work: automation architecture, growth and client solutions, build and workflows, and marketing and sales. Builders rather than consultants, who have run real operations, failed at them, and worked it out alongside business owners.

Why a page about four people belongs on a company website

Most agency team pages exist so a prospect can check the company is real. That is a fair reason and it is no longer the only one. When somebody asks an assistant who they should hire, the assistant is trying to work out what this company is and whether it can be trusted with the job, and a company that is a logo and a services list is much harder to be confident about than one with four named people who each own something specific.

So this page says who does what, and what each of them did before. Every biography below is the person's own account, taken from the capability document Wobble sends to clients. Nothing has been written about anybody here that they have not already published about themselves.

Moiz Khan, automation architecture

Decides what gets built and how it runs.

Moiz came to systems by an unusually indirect route. He started in medicine, moved into chartered accountancy, spent time in media, and ended up building businesses from the ground up. The mix is the point: it means numbers, operations, sales and delivery are all the same conversation to him rather than four departments that hand work to each other.

He started in digital marketing doing all of it himself, the cold calls, the meetings, the decks, the campaigns and the delivery. When automation became practical for ordinary businesses rather than only for large ones, he moved into building the systems: AI callers, CRM workflows, and the backend automations that remove the manual work slowing a company down.

Two engagements are the proof he points at. As Director of AI for a United States real estate company he led the implementation of AI callers and automation for working agents, which is where turning an impressive demonstration into something that survives a real workflow stopped being theoretical. The second is his own business, Quillon, an Australian training resources company, where the backend service delivery line was rebuilt as a single audited automation. The margin that unlocked is published on the work page with the rest of it.

At Wobble he leads automation architecture. His job is deciding what should be built, how it should work, and how a messy operation becomes a system somebody can actually use. In his words: he does not care about building things that sound impressive in a pitch, he cares about systems that work when a real business has to use them.

Owns automation architecture. He signs the 22 articles on this site about platform choice, agents and retrieval, and what happens to an implementation once the demonstration is over, and every one of those bylines links back here.

Haad, growth and client solutions

Turns a problem into the right build.

Haad spends most of his time working out how a business could run better. In practice that means speaking to clients, understanding what is actually going wrong rather than what was reported as going wrong, designing the solution, and making sure what gets built creates value instead of adding another layer of complexity to a company that already has enough.

His background is marketing, operations and growth. His own description of himself is simpler than that: somebody who enjoys building systems that make people's lives easier.

Owns growth and client solutions. He signs the 19 articles on this site about whether to build at all, what to build first, who should build it and what it gives back, and every one of those bylines links back here.

Ibrahim, build and workflows

Makes the system usable for your team.

Ibrahim works in the space between building the technology and making sure somebody can operate it. Where Moiz leads the heavy automation architecture, Ibrahim focuses on the build itself, the custom workflows and web systems that clear a specific bottleneck.

He describes the moment he committed to this field as realising he could use it to kill the boring, repetitive work that slows a business down. His stated goal is narrow and useful: build tools powerful enough to scale an operation and simple enough that a client's own team can be trained to run them without him. A builder who dislikes complexity and likes watching a system finally click.

Owns build and workflows. He signs the 9 articles on this site about the records, habits and dashboards a client's own team runs after handover, and every one of those bylines links back here.

Ibrahim has supplied no public profile, so this site links to none rather than pointing at an account that might belong to somebody else.

Ali, marketing and sales

Scaled local shops to global clients.

Ali's route was not linear either. He left college after a military school path did not work out, and describes that detour as where the discipline came from.

He started with small local marketing work, helping businesses get their first real conversions. Within three years he had moved from local shops to global clients as a marketing manager, generating millions in sales across borders.

What that taught him is the argument the whole company runs on: most businesses do not need more tools, they need the right ones working together. Which is why Wobble exists as a team that has been in the trenches failing and figuring it out alongside business owners, rather than as a consultancy that sells theory.

Owns marketing and sales. He signs the 18 articles on this site about ads and search, the agencies a business hires, and the enquiries it wins or loses, and every one of those bylines links back here.

There is no public profile for Ali here either. An account found elsewhere under that name has not been confirmed as his, so it is not linked.

Who writes what on this site

Every article here carries the name of the co-founder whose subject it is, in the byline a reader can see and in the structured data underneath it, and each byline links back to the section above. Of 70 articles, the split by author is Moiz Khan 22, Haad 19, Ibrahim 9, Ali 18. It follows what each of them does rather than a rota, which is why the counts are uneven.

The remaining 2 carry no personal byline. Both are broad accounts of AI adoption in Pakistan rather than one person's own work, so they stay published under the company name. Putting a founder's name on them would make this page look fuller and mean less.

What the four of them have in common

None of them arrived from a consultancy. Between them the routes in are medicine, chartered accountancy, media, military school, local marketing shops and running businesses that had to make payroll. That matters more than it sounds, because the failure mode of this industry is people who can describe a system convincingly and have never had to operate one on a Monday morning when it breaks.

It is also the reason the company sells the way it does. Every engagement is published with its actual numbers, the four ways to own a system are set out with the awkward line printed under each one, and there is no price on this site because two businesses buying the same system correctly pay different amounts.

How to reach them

The only route this site publishes is the readiness call, and every intake gets a reply within two working hours. It is a short conversation about one process that is costing you time or losing you enquiries, and if automation is the wrong answer for what you describe, that is what you will be told.

The company is on LinkedIn and Instagram. Wobble works from Karachi with clients in six countries, and how we work sets out the stages against real dates.

See where this applies to your business

The AI Readiness Call is a short, free conversation about where automation would actually pay back in your business. The call is free. The diagnosis is not.

Book AI Readiness Call