Why this firm exists.
(First-person — Islam, founder)
I started Mezura because the consulting market that grew up around AI is structurally misaligned with what mid-market operators actually need.
Big firms sell projects, not outcomes. Their fee structure rewards activity, not results. Boutique consultancies are pre-sales motions for vendors — paid more when buyers buy more. AI labs route services through partners with the same conflict. None of them have skin in the game. None of them are accountable to outcomes the way an operator is.
The advice market is broken in three structural ways: big firms sell projects; boutiques are paid by the vendors they recommend; none of them face consequences if the advice doesn't work. Buyers spend in this market and get told their AI initiative failed because the model wasn't quite right, or because the change management was incomplete, or because their team wasn't ready. The advice doesn't have to be correct because nobody's economics depend on it being correct.
Mezura is what I wanted as an operator. The senior person who sells the engagement is the senior person who delivers it. Vendor-neutral by structure — no software resale, no partnership economics, no economic interest in any AI tool. Approximately 30% of Chapter 3 fees aligned with outcomes the firm has moved before, paid only if those outcomes are achieved. Three to five active engagements at any time, deliberately, so senior attention is real and not allocated.
What I have actually built.
Twenty years building and rebuilding revenue and operations engines — at a YC-backed startup (Pathrise W18, 2024), Series-stage growth companies (inDrive across seven MEA markets, RemotePass, Justlife), and mid-market growth businesses (fetchr's e-commerce infrastructure in KSA). The methodology that runs every Mezura engagement was built there. The pattern matters more than any single role: I have been the person responsible for the operating outcome, repeatedly, across different contexts.
The methodology engagement — a YC W18 portfolio company, 2024.
Engaged as Lead Systems Architect to re-engineer the operations stack of a Y Combinator-backed career-services company. The problem wasn't human effort; it was a fragmented operating model leaking conversion. I rebuilt four layers in a ten-week sprint — input quality, decision protocols, automation handoffs, incentive alignment — using AI-driven workflow automation to strip out the manual drag and align the funnel. Application-to-interview conversion went from 0.5% to 2.3%. A 4.6× lift, with no new product, no new team, no new capital. That four-layer rebuild is the pattern that now structures every Mezura engagement.
inDrive — seven MEA markets.
I ran logistics expansion across seven key markets while the company scaled from regional player to global competitor. Growth was bottlenecked by a broken payment process — proof that operational friction is not solved by working harder. I integrated mobile-wallet infrastructure to bypass the cash-collection bottleneck, cut payment processing cost by 63%, and built a courier-recruitment engine that onboarded 3,000 drivers in 100 days by fixing the operational logic underneath.
fetchr — the KSA delivery backbone.
I led the infrastructure build-out for e-commerce in Saudi Arabia. This was not "sales" — it was constructing the delivery backbone for a country: partnerships across 90% of the Saudi e-commerce market, a cross-border logistics deal that cut global shipping cost 46%, and the operational playbook that let the business scale to five cities at once.
Justlife and RemotePass.
Justlife (then Justmop): a "market entry in a box" launch into a new MENA territory in 30 days, working around regulatory friction rather than through it. RemotePass: a high-velocity UK market-penetration sprint built on a data-driven targeting protocol — $678K ARR closed in 28 days, 282% of annual quota. Each taught a different version of the same lesson: the work that determines whether a business compounds happens in the operating model, not in the tech stack. AI did not change that. AI made it more important — because operating models that worked at human scale break differently when AI is layered on top of them.
Why Cairo, why MENA-primary.
Mezura operates from Cairo, with engagements running primarily across MENA and the Gulf, secondarily in the United States (with a focus on manufacturing exposed to China-decoupling), tertiarily in Western Europe. The geography is a strategic choice, not a constraint.
The MENA and Gulf markets are mid-cycle on AI deployment. Adoption is high, EBIT impact is low, and the operating-model gap is more visible here than in mature markets where buyers have already cycled through two to three failed AI initiatives. The pattern recognition compounds faster, and most of my demonstrated track record — inDrive's seven MEA markets, fetchr's KSA build-out, Justlife's MENA launch — is in exactly this region.
The United States is reweighted to secondary, not tertiary. The current macro creates real demand for operating-model work, with manufacturing exposed to China-decoupling as the strongest sub-segment. US engagements carry a time-zone tax and are priced accordingly, but the structural opportunity is large enough to prioritize above Western Europe.
The MENA orientation is not an Arabic-language firm. Engagements are run in English. The cultural fluency matters more for things like family-office decision cadence (relationship-first, long-horizon), Sharia-compliance considerations, and Gulf-specific regulatory environments (QCB, ADGM, DIFC, SAMA) than for any linguistic preference.
What this firm is not.
A solo-delivery firm by deliberate design. Vendor-neutral by structure, not by marketing claim. Selective, not scalable. These are constraints, not features in disguise.
Solo by design. The senior person who sells the engagement is the senior person who delivers it. No associate pyramid, no subcontracted delivery, no junior handoff. The firm caps at 3 to 5 active engagements at any time. A 6th simultaneous engagement is not available regardless of fee.
Vendor-neutral by structure. No referral fees from any AI vendor. No partnership tiers. No preferred-vendor lists. No software resale. The firm is paid only by the operators who hire it — contractually enforceable and publicly stated.
Selective. About half of buyers continue past Chapter 1; Mezura actively declines roughly 20% to 30%. A 100% continuation rate would mean the firm is selling continuation regardless of fit.
Honest about limits. If the data environment is too immature to support baseline definition, Chapter 3's skin-in-the-game structure doesn't apply (the engagement is structured as firm-fee instead). If the primary need is product-market fit, fundraising, or executive recruiting, Mezura is not the right firm.