AGENCYSCRIPT
CoursesEnterpriseBlog
👑FoundersSign inJoin Waitlist
AGENCYSCRIPT

Governed Certification Framework

The operating system for AI-enabled agency building. Certify judgment under constraint. Standards over scale. Governance over shortcuts.

Stay informed

Governance updates, certification insights, and industry standards.

Products

  • Platform
  • Certification
  • Launch Program
  • Vault
  • The Book

Certification

  • Foundation (AS-F)
  • Operator (AS-O)
  • Architect (AS-A)
  • Principal (AS-P)

Resources

  • Blog
  • Verify Credential
  • Enterprise
  • Partners
  • Pricing

Company

  • About
  • Contact
  • Careers
  • Press
© 2026 Agency Script, Inc.·
Privacy PolicyTerms of ServiceCertification AgreementSecurity

Standards over scale. Judgment over volume. Governance over shortcuts.

On This Page

Types of AI Agency PartnershipsReferral PartnershipsCo-Delivery PartnershipsWhite-Label PartnershipsStrategic AlliancesTechnology PartnershipsThe Core Partnership Agreement Template1. Partnership Purpose and Scope2. Roles and Responsibilities3. Revenue Allocation and Payment Terms4. Intellectual Property5. Confidentiality and Non-Disclosure6. Quality Standards and Dispute Resolution7. Non-Solicitation and Non-Compete8. Liability and Insurance9. Communication and Governance10. Termination and TransitionNegotiating Partnership TermsBefore the NegotiationDuring the NegotiationAfter the NegotiationManaging Ongoing PartnershipsYour Next Step
Home/Blog/A Handshake Deal on 280K Got Ugly Fast
Operations

A Handshake Deal on 280K Got Ugly Fast

A

Agency Script Editorial

Editorial Team

·March 20, 2026·11 min read
ai agency partnershipspartnership agreementsagency collaborationstrategic partnerships

Two AI agency founders in Chicago agreed over drinks to partner on a large healthcare project. They shook hands, split the work informally, and delivered a great result. The client paid $280,000. Then the conversation about money got uncomfortable. One founder expected a 50/50 split. The other argued that their team did 70% of the work and should receive 70% of the revenue. Neither had documented the arrangement. The dispute took three months to resolve, destroyed the personal relationship, and ensured they would never partner again. The client, who had been delighted with the work, was never able to engage both agencies together again.

This story repeats constantly across the agency world. Partnerships are powerful: they let you take on bigger projects, access new markets, and offer broader capabilities. But without clear agreements, partnerships become sources of conflict rather than growth. The irony is that the same agencies that would never start a client project without a contract routinely start partnerships with nothing more than a verbal agreement and goodwill.

Types of AI Agency Partnerships

Different partnership types require different agreement structures. Identify which type of partnership you are entering before drafting the agreement.

Referral Partnerships

Structure: You refer clients to each other for services outside your respective specialties. A web agency refers AI work to you; you refer web work to them.

Revenue model: The referring party receives a referral fee, typically 5-15% of the referred project's value.

Agreement complexity: Low. A simple one-page referral agreement covers the key terms.

Co-Delivery Partnerships

Structure: Two agencies collaborate on a single client project, each delivering a portion of the work.

Revenue model: Revenue split based on work allocation, typically with one agency as the prime contractor (client-facing) and the other as a subcontractor.

Agreement complexity: Medium. Needs clear scope division, quality standards, and revenue allocation.

White-Label Partnerships

Structure: One agency delivers work under the other agency's brand. The client does not know a partner agency is involved.

Revenue model: The white-label provider receives a negotiated rate (typically 60-70% of what the client-facing agency charges the client).

Agreement complexity: Medium. Needs brand usage terms, quality standards, and strict confidentiality.

Strategic Alliances

Structure: A deep, ongoing partnership where both agencies invest in joint capabilities, shared marketing, or co-developed intellectual property.

Revenue model: Varies. Can include revenue sharing on joint clients, shared investment in IP, or cross-selling arrangements.

Agreement complexity: High. Needs comprehensive terms covering scope, governance, IP, exclusivity, and dissolution.

Technology Partnerships

Structure: Partnership with a technology vendor (cloud provider, AI platform, data provider) for preferred access, co-marketing, or revenue sharing.

Revenue model: Typically involves certification requirements and revenue commitments in exchange for discounts, co-marketing funds, and lead sharing.

Agreement complexity: Medium. Often uses the vendor's standard partnership agreement with some negotiable terms.

The Core Partnership Agreement Template

Regardless of partnership type, every agreement should address these ten elements. Adapt the detail level to the partnership complexity.

1. Partnership Purpose and Scope

State clearly what the partnership is for and what it is not for.

Include:

  • The types of projects or activities covered by the partnership
  • Geographic or market scope (if limited)
  • Duration (fixed term with renewal, or ongoing with termination provisions)
  • What falls outside the partnership

Example language: "This partnership covers the co-delivery of AI solutions for clients in the healthcare and financial services industries in North America. Each party may independently pursue opportunities outside this scope."

2. Roles and Responsibilities

Define what each party contributes and is responsible for.

For co-delivery partnerships:

  • Which party is the prime contractor (client-facing, holds the contract)?
  • Which party delivers which components?
  • Who manages the client relationship?
  • Who handles project management?
  • Who provides quality assurance?
  • Who handles post-delivery support?

For referral partnerships:

  • What qualifies as a valid referral?
  • What is the expected timeline for following up on referrals?
  • How are referral outcomes communicated back to the referring party?

3. Revenue Allocation and Payment Terms

This is where most partnership conflicts originate. Be painfully specific.

For co-delivery partnerships:

  • Revenue split percentage and the basis for the split (fixed percentage, or proportional to actual hours/effort)
  • Who invoices the client?
  • What happens if the client does not pay?
  • Payment timeline between partners (how quickly does the prime contractor pay the subcontractor after receiving client payment?)
  • Handling of change orders and scope expansions

For referral partnerships:

  • Referral fee percentage
  • When the fee is earned (upon contract signing, upon first payment, upon project completion)
  • How long the referral relationship persists (if the client comes back for more work in 12 months, does the referral fee still apply?)
  • Payment timeline for referral fees

For white-label partnerships:

  • The white-label rate (per hour, per project, or per deliverable)
  • Payment schedule
  • Rate adjustment mechanism (annual review, tied to inflation, negotiable)

Specific payment terms to address:

  • Net payment terms (Net 15 or Net 30 between partners, not Net 60)
  • Late payment penalties or interest
  • Disputed payment resolution process
  • Right to withhold payment for quality issues (be very specific about conditions)

4. Intellectual Property

Address IP ownership for any work created through the partnership.

Key questions:

  • Who owns IP created by each party independently during the partnership?
  • Who owns IP created jointly?
  • Can each party reuse techniques and methodologies learned during joint projects?
  • What happens to jointly developed IP if the partnership ends?

Recommended approach:

  • Each party retains ownership of their pre-existing IP
  • IP created for a specific client belongs to the client (per the client contract)
  • Jointly developed methodologies and tools are jointly owned with each party having the right to use them independently
  • Include a residuals clause allowing both parties to use general knowledge gained

5. Confidentiality and Non-Disclosure

Both parties will share sensitive information: client details, pricing strategies, technical approaches, and business metrics.

Include:

  • Definition of confidential information
  • Obligations of the receiving party (protect with reasonable care, limit access to those who need to know)
  • Exclusions (information that is publicly available, independently developed, or received from a third party)
  • Duration of confidentiality obligations (typically 2-3 years after partnership termination)
  • Special handling for client confidential information (subject to client NDA terms)

6. Quality Standards and Dispute Resolution

Define quality expectations and what happens when they are not met.

Quality standards:

  • Technical standards (coding conventions, testing requirements, documentation standards)
  • Communication standards (response times, reporting expectations)
  • Delivery standards (deadline adherence, revision policies)
  • Review and approval process for partner-delivered work

Dispute resolution:

  • Step 1: Good-faith discussion between designated contacts (10-day resolution window)
  • Step 2: Escalation to senior leadership at each organization (15-day resolution window)
  • Step 3: Mediation (30-day window, costs split equally)
  • Step 4: Binding arbitration (final resolution, losing party pays costs)

Include a provision for continuing to serve clients during any dispute. Partnership disputes should not affect client deliverables.

7. Non-Solicitation and Non-Compete

Protect your business from your partner poaching clients or employees.

Non-solicitation of clients:

  • Neither party will directly solicit the other party's existing clients for services that compete with the partnership
  • Duration: during the partnership and 12-24 months after termination
  • Exception: if a client approaches the other party independently

Non-solicitation of employees:

  • Neither party will recruit or hire the other party's employees or contractors during the partnership and for 12 months after
  • Exception: general job postings not targeted at the partner's team

Non-compete considerations:

  • Full non-competes between agencies are usually too broad and may be unenforceable
  • Instead, focus non-compete terms on specific accounts or specific opportunities introduced through the partnership
  • Keep the duration reasonable (12 months maximum)

8. Liability and Insurance

Allocate risk appropriately between partners.

Liability allocation:

  • Each party is responsible for the quality and timeliness of their own deliverables
  • Each party indemnifies the other against claims arising from their own work
  • Limitation of liability: cap each party's liability at the revenue received from the partnership in the prior 12 months

Insurance requirements:

  • Each party maintains professional liability insurance with minimum coverage (typically $1M-$2M)
  • Each party maintains cyber liability insurance
  • Certificate of insurance provided upon request

9. Communication and Governance

Define how the partnership is managed on an ongoing basis.

Governance structure:

  • Designated partnership lead from each organization
  • Monthly partnership review meeting (30 minutes)
  • Quarterly strategic review (60 minutes)
  • Annual partnership evaluation

Communication norms:

  • Primary communication channel
  • Response time expectations
  • Escalation procedures
  • Client communication protocols (who says what to the client)

10. Termination and Transition

Plan for the partnership ending, whether amicably or not.

Termination triggers:

  • Either party can terminate with 60-90 days written notice (no-fault termination)
  • Immediate termination for material breach (with cure period for non-material breaches)
  • Immediate termination if either party becomes insolvent or faces legal action that could affect the partnership

Transition requirements:

  • Obligations to complete in-progress client projects (do not abandon clients mid-project)
  • Timeline and process for transitioning client relationships
  • Data and document handover requirements
  • Final financial settlement (outstanding payments, referral fees, shared costs)
  • IP usage rights after termination

Negotiating Partnership Terms

Before the Negotiation

Know your value. Understand what you bring to the partnership that the other party cannot easily get elsewhere. Technical expertise? Client relationships? Market presence? Specialized tools?

Know your alternatives. Could you do this without a partner? Are there other potential partners? Having alternatives strengthens your position.

Know your non-negotiables. Decide in advance what terms you will not compromise on. For most agencies, these include: IP ownership of pre-existing assets, non-solicitation of clients, and payment terms.

During the Negotiation

Start with alignment. Before negotiating specifics, make sure both parties agree on the purpose and goals of the partnership. If your goals do not align, no contract structure will make the partnership work.

Negotiate revenue allocation based on value, not just effort. The partner who brings the client relationship may argue for a larger share even if they contribute fewer hours. The partner who brings rare technical skills may argue similarly. Acknowledge that different types of contribution have different value.

Build in flexibility. Partnership dynamics change over time. Include mechanisms for reviewing and adjusting terms (annual reviews, revenue threshold triggers, scope expansion provisions).

Use a pilot period. For new partnerships, agree to a pilot period (one project or three months) with simplified terms. If the pilot succeeds, formalize the full partnership agreement. If it does not, both parties can walk away cleanly.

After the Negotiation

Get it in writing. No handshake deals. No "we will figure it out." Every term discussed should be documented in a signed agreement.

Have legal review. Both parties should have their own attorney review the agreement. This protects both sides and catches issues that business people often miss.

Share the agreement with your teams. The people who will execute the partnership need to understand the terms: scope, responsibilities, communication protocols, and quality standards.

Managing Ongoing Partnerships

The agreement sets the framework. Ongoing management determines success.

Monthly check-ins. A 30-minute monthly conversation between the partnership leads keeps the relationship healthy. Review current projects, discuss upcoming opportunities, and address any friction early.

Transparent financials. Share relevant financial information openly. If a project is over budget, discuss it before it becomes a dispute. If a referral did not convert, explain why.

Joint retrospectives. After completing a joint project, conduct a retrospective together. What worked? What did not? What would we do differently? This continuous improvement strengthens the partnership over time.

Celebrate wins together. When a joint project succeeds, celebrate it. Acknowledge each partner's contribution. Shared victories build relationship equity that sustains the partnership through difficult moments.

Your Next Step

If you have an existing partnership that operates on a handshake, schedule a conversation with your partner this week. Frame it positively: "Our partnership is valuable, and I want to make sure we protect it by putting our agreement in writing." Use the ten-element template above as your agenda. You do not need a perfect legal document today. You need a written understanding of roles, revenue, IP, and termination that both parties can review, refine, and eventually formalize with legal counsel. Every week that passes without a written agreement is a week where a misunderstanding could turn into a dispute that destroys a valuable relationship.

Search Articles

Categories

OperationsSalesDeliveryGovernance

Popular Tags

prompt engineeringai fundamentalsai toolsthe difference between AIMLagency operationsagency growthenterprise sales

Share Article

A

Agency Script Editorial

Editorial Team

The Agency Script editorial team delivers operational insights on AI delivery, certification, and governance for modern agency operators.

Related Articles

Operations

Understaffed or Overstaffed? Both Camps Were Right.

You cannot manage what you cannot see. Here is how to build a team capacity dashboard that prevents burnout, eliminates bench time, and keeps projects staffed correctly.

A
Agency Script Editorial
March 21, 2026·12 min read
Operations

Optimizing Daily Standups for Distributed AI Agency Teams

Optimized standups keep distributed AI agency teams aligned without consuming the focused work time that engineers need to ship quality deliverables.

A
Agency Script Editorial
March 21, 2026·10 min read
Operations

Complete Utilization Rate Management Guide — The Metric That Makes or Breaks Agency Profitability

A 5% shift in utilization can swing agency profit by 30% or more. Here is the definitive guide to measuring, managing, and optimizing the most important metric in your agency.

A
Agency Script Editorial
March 21, 2026·13 min read

Ready to certify your AI capability?

Join the professionals building governed, repeatable AI delivery systems.

Explore Certification