What Kando is, and who it's for
Kando is a growth-marketing consultancy that builds and runs a company's growth engine, then hands it to the in-house team. It works with pre-seed to Series B startups entering the GCC and with established brands expanding across the region, covering both B2B and DTC. The common thread isn't the industry — it's a company facing a real market-entry or growth question across the UAE, Saudi Arabia, Kuwait, Qatar, Bahrain, Oman or Lebanon.
What sets the starting point apart is what Kando doesn't do first. It doesn't open a relationship by pitching paid media, SEO or a specific tactic. It opens by identifying the actual business question — should we enter Saudi before the UAE, why is retention dropping, is our funnel measuring the wrong thing — and only then works backward to the channels and systems that answer it.
We start with the business question, not the channel.
There's a flip side worth stating honestly. The companies that aren't a fit are the ones without an in-house team to eventually own the work, or without a genuine business question to answer. The whole model depends on someone being there to receive the handover — a growth engine transferred to nobody is just an engine left idling.
How an engagement starts
It starts with a strategy call, not a sales pitch. That first conversation exists to understand the real business question — a launch, a stalled funnel, a market entry — before any channel or tactic gets proposed. There's no generic proposal template; scope is built around what the business needs to be true in six months, then worked back into a timeline and a transfer date.
From there, the engagement takes one of three shapes. A Project is a defined scope on a fixed timeline. A Retainer is monthly, ongoing execution across channels. A Sprint is a focused intensive on a single urgent question. Many clients start with a Sprint or Project to prove the model works, then move to a Retainer if there's ongoing scope — always still working toward a transfer date.
A defined scope on a fixed timeline — a GTM build, a launch, a specific rebuild.
Monthly ongoing execution across channels, embedded with your team.
A focused four-to-six week intensive on one urgent business question.
Three shapes, one destination — all working toward a transfer date.
Whichever shape fits, the scoping conversation is the same: book a strategy call and describe the decision you're actually trying to make. The models are just different-sized containers for the same Build, Run, Transfer arc.
How Kando builds a growth strategy
Strategy begins with the business question, not a channel plan — what has to be true for this to count as a win, and what the funnel data says about where it's actually breaking. Only after that diagnosis do strategy and channel selection follow. Weeks one and two are spent diagnosing where the funnel leaks and what's already working; the plan is built backward from the answer, not forward from a list of tactics someone felt like trying.
This is why two clients in the same industry can end up with completely different growth engines. The tactic that fixes a stalled DTC funnel is rarely the one that cracks a B2B market entry, even when the businesses look similar on paper. Starting from the diagnosis avoids the common failure mode where a company buys a channel because it's trendy rather than because it fits the problem. For the full build playbook, see the services overview.
What a growth sprint covers
A Kando Sprint is a focused four-to-six-week intensive built around one specific business question — diagnosing a stalled funnel, testing a new market, or rebuilding a broken measurement setup. It ships and measures in two-week cycles, so there's visible progress before the sprint even ends rather than one big reveal at the finish.
It's the right entry point when you don't need a full retainer relationship but do need dedicated attention on a defined problem, fast. For companies specifically entering the region, the equivalent front door is the MENA Growth Gateway: a free entry diagnostic first, then a focused Market-Entry Growth Sprint if there's a fit.
How Kando works with your in-house team
Kando works with the in-house team, not instead of it. During the Run phase, Kando's specialists and the client's marketers work the same campaigns and the same dashboards together, so knowledge transfers through doing the work — not through a document dropped on the last day. This is the part most retained agencies aren't structured to do, because their incentive runs the other way.
The reason it's built this way is simple: the goal is ownership, not dependency. By the transfer date, the in-house team should be able to run the growth engine without Kando in the loop. If the team can't operate it alone at the end, the engagement didn't do its job.
The AI-Enabled Marketing Ops service
AI-Enabled Marketing Ops rebuilds a team's real workflows — reporting, content production, lead handling — with AI woven directly into each step, rather than bolting a chatbot onto the existing process. It starts with an audit of where time actually goes, then rebuilds the highest-friction workflows first. Engagements typically run eight to sixteen weeks and follow Build, Run, Transfer exactly.
The end state is a documented, working set of AI-enabled workflows the client's own team runs without Kando — not a dependency on an outside agency and not a tool nobody adopts. It can also run as a shorter four-to-six-week Sprint for a narrower scope. The full breakdown lives on the AI-Enabled Marketing Ops service page.
What gets handed over at transfer
At transfer, the in-house team receives the full working system: documented playbooks for each channel, live dashboards, any automations or AI workflows built during the engagement, and the historical performance data behind them. Nothing is a black box — the team can run and adapt what was built without needing Kando in the room. Because the team is trained during Run, transfer day is a meeting, not a scramble.
Diagnose the business question, then build the growth engine — strategy, stack, tracking, campaigns.
Operate it alongside your team, in your accounts, against an explicit, agreed transfer date.
Hand over documented playbooks, live dashboards and the data. Your team owns it outright.
Every engagement states that transfer date up front, so both sides are working toward independence rather than drifting into an open-ended retainer. For the plain definition, see The Transfer Model.
Transfer day is a handover meeting, not a scramble.
Documenting workflows so they keep improving
A handover is only as good as its documentation. Kando writes every workflow at runbook level — the exact prompts, data sources, tools, decision points and owners — so someone new could pick it up without a live walkthrough. Each workflow is documented as it's built, not reconstructed from memory at the end, so it survives beyond the person who set it up.
The documentation also carries a review cadence, so a workflow doesn't quietly go stale as tools change or the market moves. This isn't an optional extra — it's a required deliverable of every Transfer. The point is a system your team can not just run but keep sharpening after Kando is gone.
How fast to expect results
Results show up in two-week cycles, since work ships and gets measured on that rhythm rather than at the end of a quarter. Full timelines vary by shape: a Sprint runs four to six weeks, a GTM build six to ten, and an AI ops rebuild eight to sixteen. You steer early rather than waiting for transfer day to find out whether the strategy is working.
Meaningful business results — pipeline, revenue, retained customers — typically take longer than the first cycle to compound. But because everything is measured on a fortnightly rhythm, a ninety-day plan produces several checkpoints, not one big bet at the end.
How pricing is determined
Kando doesn't publish a rate card. Pricing is scoped per engagement based on the work involved, usually during or right after the strategy call. Cost depends on the model — Project, Retainer or Sprint — the channels involved, and the timeline to transfer.
The reason is practical: scope varies too much between a four-week sprint and a sixteen-week AI ops rebuild for a flat price to mean anything honest. The fastest way to get a real number is to book a call and describe the business question you're solving.
How Kando is different from a GCC agency
The core difference is the end date. Most GCC agencies are structured to keep a client on retainer indefinitely — the incentive rewards the client staying dependent. Kando builds toward a named transfer date and hands the engine to the in-house team, which flips that incentive: get paid to build something that works without you, not to stay indispensable.
The second difference is where it starts. Kando begins from the business question rather than a channel, so it isn't selling paid media or SEO by default — it's diagnosing what the business actually needs first. That combination — Build, Run, Transfer, plus in-house teams doing the work alongside Kando rather than watching from the sidelines — is what most traditional retained agencies aren't set up to offer.
The free tools, and whether they're really free
Kando publishes roughly 40 free tools — calculators, scorecards, technical checkers, CSV audits and AI copilots — plus free templates and a glossary. None of the core results sit behind a paywall: you can run a full audit or generate a full brief without paying. The only optional step is creating a free account to save results for later, and it isn't required to see the output.
They're built to be genuinely useful on their own, not gated lead magnets — you don't need to talk to Kando to get value from them. For companies that want a diagnosis turned into an executed engagement, the tools are also a natural entry point into a strategy call, but using them creates no obligation either way.
Is your CSV data safe in Kando's tools?
Yes. Every CSV audit tool in Kando's free set — the Paid Media Waste Finder, Creative Fatigue Detector, Ad Performance Auditor, Outreach CSV Auditor, CRM Hygiene Analyzer, Pipeline Leak Finder and Content Decay Detector — parses your file entirely client-side, in your browser. The file is never uploaded to a server, so raw ad account, CRM or Search Console data never leaves your machine.
That means you can safely audit exports containing real customer or account data without a data-sharing conversation. The analysis happens locally, and only the results are yours to save. It's the same principle that runs through the whole model — you keep ownership of what's yours.