This is Part 3 of a 4-part series for MSPs and IT firms. Part 1 covers why website work is a strong referral category. Part 2 covers qualifying the request and making the introduction. Part 4 covers how to vet a web agency partner.
Part 2 covered the handoff. The structural question behind it is how the operating rules are documented before the first client introduction happens. Referral partnerships are easier to trust when those rules are explicit early.
Decide the Relationship Model First
The agreement should reflect the actual model being used.
Direct referral means the client knows the agency by name and works with them directly on the web scope.
White-label delivery means the agency operates behind the MSP’s brand and communication process.
Hybrid arrangements exist too, but they still need explicit boundaries. If the model is vague, the client relationship usually becomes vague as well.
Put Client-Protection Terms in Writing
The most important account-protection language is usually some form of non-solicitation. The exact wording should be reviewed appropriately for the relationship, but the practical questions are straightforward:
- Which client relationships are protected
- Whether the restriction covers inbound as well as outbound solicitation
- How long the protection lasts
- What happens if the client asks the agency directly for unrelated work
The point is not to create a hostile agreement. The point is to remove ambiguity before there is money or urgency attached to a live project.
Define Scope Boundaries Clearly
The agreement should spell out what kinds of work the agency can and cannot pursue inside the referred relationship. That includes more than web design.
Examples worth clarifying:
- Can the agency sell SEO, paid media, or other marketing services to the referred client
- Can the agency take on unrelated technical work
- What happens if the project expands beyond the original website scope
- Whether the agency may continue into an ongoing retainer after launch, and under what terms
Scope ambiguity is one of the fastest ways for a referral relationship to drift into account-risk territory.
Document the Revenue Terms
If money changes hands, document the mechanics. At minimum, define:
- What counts as a qualifying referral
- Whether compensation is a one-time project fee, recurring retainer share, or white-label margin
- When payment is due
- What happens if the client pauses, cancels, or expands the engagement
Referral revenue is easiest to manage when it behaves like any other documented vendor arrangement rather than a verbal understanding.
Set Communication and Escalation Rules
The partnership should define:
- Who speaks directly with the client
- How project updates are communicated back to the MSP
- Who handles escalation when the client is unhappy
- What the response expectation is for urgent issues
This matters in both direct and white-label models. If the communication path is unclear, the first problem will expose it.
Plan for Credentials, Deliverables, and Offboarding
Web projects create assets: code, content, hosting access, domain details, API credentials, design files, and documentation. The agreement should make clear how these are handled during the project and what happens if the relationship ends.
The safe default is simple: the client’s assets remain retrievable, the MSP is not locked out of anything it needs to support the client relationship, and the handoff process is documented before anyone needs it under pressure.
Structure Creates Trust
Most MSPs do not need a complicated legal framework to start a partnership. They do need clarity. A written structure protects both sides, reduces misunderstanding, and makes it easier to decide whether the partner is worth using in the first place.
Part 4 covers that evaluation directly: how to vet a web agency partner before you put your client relationship behind them.
Previous: Part 1: Why Website Work Is Your Best Referral Opportunity | Part 2: Qualifying the Request and Making the Introduction Next: Part 4: How to Vet a Web Agency Partner
Related reading: The MSP’s Guide to Web Agency Partnerships, Part 2: Qualifying the Request and Making the Introduction, The MSP’s Guide to Web Agency Partnerships, Part 4: How to Vet a Web Agency Partner, and How MSPs Can Deliver Custom Client Portals Without Taking on the Development Work.