The Transfer Model.

The Transfer Model, properly understood

The Transfer Model has three phases with an explicit end date baked in from the start, not an open-ended relationship that renews by default. Build is the setup phase — strategy, channel selection, tracking infrastructure, creative systems, and the first working version of the growth engine, run primarily by Kando. Run is the operating phase, where Kando executes day-to-day — media buying, content, reporting, optimization — while the client's team works alongside it, gradually taking on more of the execution as capability grows. Transfer is the handoff phase, scheduled from day one with an actual calendar date, where ownership of the dashboards, the playbooks, the vendor relationships, and the weekly optimization work moves fully to the client's team, and Kando steps back to a lighter-touch, typically quarterly, advisory role rather than continuing as the operator.

This model was built for how growth work actually plays out for ambitious companies across the Gulf and wider MENA region: many teams need an outside partner to stand up a growth engine fast — the paid media discipline, the SEO and GEO foundation, the tracking infrastructure — but don't want permanent external dependency for something that should eventually be a core in-house capability, especially as regional talent pools mature and hiring a dedicated in-house marketer becomes realistic. A Transfer Model engagement typically sets the transfer date based on how fast the client's internal hire or team can be onboarded and trained during the Run phase, not on an arbitrary contract-renewal calendar, so the timeline is a planning input from the start rather than a surprise at the end of a retainer.

The model only works if the transfer date is real and defended, not a soft target that quietly slides every quarter — the whole point is fixing a misaligned incentive: in a standard retainer, an agency profits from the relationship continuing indefinitely, while Kando's stated position is that the win condition is the client no longer needing it. It's worth being explicit about how this differs from Build-Operate-Transfer (BOT), a term borrowed from infrastructure and public-private partnerships: BOT typically describes a much longer operate phase — sometimes years or decades — before a large-scale asset like a toll road or power plant transfers to a government or owner, usually as a financing and risk-sharing structure. The Transfer Model compresses that logic into a marketing engagement timeline of months, not years, and the thing being transferred is operational capability and systems, not a physical asset. A misread worth avoiding: treating the Run phase as a slow handoff by default — without a deliberate training and documentation plan running throughout Run, the Transfer date arrives and the client isn't actually ready, regardless of what the calendar says.

Pair a Transfer Model engagement with clear internal capability milestones during Run — can the client's team run a campaign unsupervised, read the dashboard without translation, make an optimization call correctly — rather than measuring readiness only by calendar time elapsed. It stands in direct contrast to the standard agency retainer, where success is often measured by renewal rate rather than by the client's growing independence; judging a Transfer Model engagement by that same yardstick misses the point entirely.