Hiring external capacity to enter another country can be a good decision. A partner brings people, technology, experience and local knowledge that would take time to build. It allows progress without replicating an entire structure from day one.
The problem arises when who carries out each task is defined in detail, but there is barely any discussion of what the institution should learn along the way. Reports and enrolments arrive, while student objections, relationships and the explanation of what works remain outside. Commercial results can be good while dependence is growing at the same time.
What the university needs to keep deciding
Outsourcing requires clarity about what the institution must continue to know and decide. Which segment deserves investment? Which part of the offer needs adapting? What promise can the service sustain? A provider can contribute information and judgement to those decisions, but someone inside must be able to discuss them and take responsibility for them.
This affects six connected areas: strategy, brand, data and CRM, product, relationships and learning. It does not require every activity in these areas to be carried out internally. It requires accountable owners, sufficient information and the ability to intervene.
Academic decisions, rules for using the brand and the experience promised to students need clear institutional points of contact. Regulatory matters require the specialist review appropriate to the programme and market. Dividing up commercial tasks does not, on its own, resolve these questions.
Recovering records does not recover all the knowledge
Contacts are the most visible part. Their context explains much more: why someone rules out a programme, which employer inspires trust, where a payment gets stuck or which objection reappears after a campaign.
A CRM export may return names and statuses without preserving the history, sources, tests carried out or automation logic. If nobody can explain why a message was changed or a channel abandoned, some of the work will have to be repeated.
Learning needs to be linked to decisions. What was tested, with whom, for how long, what happened and what was decided afterwards. Including when a test goes badly. A launch that misses its objectives should leave useful information for making corrections or deciding not to continue.
Ownership, access and control are different questions
Agreeing who owns an account, tool or material is one thing. Having the access needed to use it is another. And having the practical ability to direct the operation, change a process or transfer it to another team is another again.
Putting an account in the university’s name does not guarantee that someone inside knows how to administer it. Receiving a report is not the same as having the information and permissions needed to recreate it, either. These distinctions matter from the moment the collaboration is designed.
Agreements must specify the use of tools and materials, planned access, deliverables and service continuity. Not everything the partner uses has to become the institution’s property. But it is necessary to identify what depends on external licences, systems or capabilities and how the operation will be sustained. Contractual details require specialist review; operational design should provide clear questions and requirements.
An internal team that can direct the partner
The university needs a core team that understands the market. It may be small and draw on regional capabilities, but it must be able to interpret signals, maintain local dialogue and translate what it learns into product, pricing and service decisions.
It does not have to duplicate the agency. It has to understand enough to direct the work and challenge its assumptions. If a campaign does not convert, it must be able to distinguish a messaging problem from an offer that does not fit because of price, recognition, timing or support.
The same applies to relationships. Employers, associations, institutions and alumni need points of contact and institutional continuity. Routing every conversation through a single external person leaves the university with little ability to sustain that relationship.
Knowledge transfer is demonstrated through work
A good partner documents the work, shares context and prepares the team to use it. Dependence is reduced not by accumulating manuals nobody opens, but by checking that someone else can interpret a campaign, handle an exception or continue a process.
That transfer can be incorporated into work reviews: walking through a complete case, explaining a decision and checking access. Knowledge then becomes part of everyday operations. The provider can continue to contribute specialist expertise and results without becoming the only person able to explain how the market works.
Prepare for continuity before launch
Exit arrangements deserve attention before the work begins. Data, advertising accounts, domains, analytics, scripts, procedures, automations, licences and source files all need explicit treatment. For every relevant element, it matters who maintains it, what is handed over, in what format and how its usefulness for continuing the work will be checked.
The transition also needs people, time and an operational test. Receiving files does not demonstrate that the new team can provide support or retain the student’s context. That check protects service continuity, even if the provider never changes.
Expansion seeks enrolments, but also the ability to understand and operate in a market. The question when reviewing a collaboration is simple: beyond the results, what can the university now do that it could not do before?

Marketing and growthB2B, PR and branding are not channels. They are infrastructures of trust. →
Internationalisation and expansionThe United States is not a market. It is an extremely expensive system →