Non-Compete and Non-Solicit Clauses in IMO Agreements

Non-compete and non-solicit clauses in IMO agreements decide something very simple and very personal: what your business life looks like if the relationship ends. If you sell life insurance or annuities, these clauses can shape who you can call, what products you can keep selling, and how painful a move to a new IMO becomes, so it pays to understand them before a rough Friday afternoon turns into a long month.

What non-compete and non-solicit clauses mean in an IMO agreement

A non-compete clause in an IMO agreement limits your ability to do similar business after you leave. In plain English, it tries to control where, when, or how you compete with the IMO once the relationship is over. A non-solicit clause is narrower. It usually does not stop you from working elsewhere, but it tries to stop you from contacting or moving certain people, such as clients, agents, recruits, staff, or vendors connected to the IMO.

That distinction matters right away. A non-compete asks, “Can you do this kind of work after you leave?” A non-solicit asks, “Who can you take with you or try to move?” If you confuse those two, the whole contract starts to blur.

In the insurance marketing organization world, that blur gets expensive fast. You may assume you are free because nobody can stop you from earning a living. But the catch is that a contract does not always need to block your entire career to cause a serious problem. If it blocks access to your downline, your warm client relationships, or your favorite carrier path, that alone can change your income.

Why these clauses show up in life insurance and annuity distribution contracts

IMOs use these clauses to protect the parts of the business that took time and money to build. That can mean carrier relationships, downline structures, sales systems, lead programs, training, scripts, seminar models, case design support, and goodwill with policyholders. If an IMO spent two years helping you grow and you leave with half the network, the business reason for the restriction becomes pretty obvious.

In day-to-day terms, the IMO is trying to stop a clean transfer of value from its platform to your next platform. If you received recruiting support, lead flow, marketing help, or access to a hierarchy you did not build alone, the agreement may try to keep you from turning that support into a quick exit package.

The same logic shows up around clients. If your contract says the IMO helped create or maintain the relationship, the IMO may try to limit your ability to replace policies, move assets, or service accounts after departure. That can feel strange when your cell phone is the number clients saved three years ago, but contracts often treat relationship ownership very differently from how the relationship feels in real life.

Where you’ll usually find them in the agreement

Sometimes these clauses sit in a clearly labeled “Restrictive Covenants” section. Sometimes they hide in the termination language, the confidentiality section, or an addendum that looks harmless at first glance. You may also find pieces of the restriction in producer hierarchy exhibits, recruiting schedules, lead program terms, and compensation attachments.

That is why skimming the signature pages is not enough. The non-compete may be in one section, the non-solicit in another, and the practical teeth of both buried in a definition section that quietly expands words like “client,” “affiliate,” or “producer.”

If you have ever signed one of these agreements at 6:40 p.m. in a hotel lobby before a product launch meeting in Dallas, you already know how easy it is to miss the sentence that matters most.

How an IMO agreement works before the restrictive clauses even matter

Before a non-compete or non-solicit can make sense, the basic IMO relationship has to make sense. An IMO often acts as a distribution platform between carriers and producers. Your place in that platform can affect commissions, overrides, appointments, support, release rights, and the shape of your hierarchy.

If you produce personally, the agreement may focus on your own writing numbers and client servicing. If you recruit, the agreement may also cover overrides on subagents, ownership of the hierarchy, transfer rules, and what happens when a recruit wants out. Those business mechanics matter because restrictive clauses rarely work alone. They usually sit on top of commission rules and carrier processes that already limit how cleanly you can move.

The relationship is a little like renting space in a building where the hallways matter as much as the office. You may own plenty of your production effort, but if somebody else controls the doors, elevators, and access cards, leaving is not only about packing your desk.

The role of carrier contracts, hierarchy, and release rules

A restrictive clause often works together with carrier rules. Even if your contract language looks survivable, the carrier appointment process may slow down your next move. Carriers may require a release, a waiting period, or a formal transfer process before a new IMO can place you. So the legal restriction is only one layer. The operational restriction can hit just as hard.

That is why a transition can stall without any lawsuit at all. If a release drags, new business may pause. If a hierarchy cannot transfer cleanly, overrides may freeze. If carrier access gets blocked or delayed, your production plan can wobble even if you believe the clause itself is weak. A deeper look at how release delays affect agency moves makes this point painfully clear.

A lot of confusion comes from assuming the contract is the only battlefield. It usually is not. Carrier procedures, hierarchy ownership, and release timing often decide the practical outcome before any court gets involved.

Why the same clause can feel very different for a solo agent versus a growing agency

A solo producer with a self-generated client base may look at a one-year non-solicit and think, “Annoying, but manageable.” A growing agency with thirty active subagents, shared lead campaigns, and override income sees something else entirely. The same sentence can either be a nuisance or a threat to the whole business model.

If your income depends mostly on personal production, your main concern may be clients, renewals, and carrier continuity. If your income depends on a team, then recruiting restrictions become the real story. A clause blocking contact with agents in your hierarchy can cut deeper than any line about geography.

That practical difference is easy to miss because contracts use one-size-fits-all wording. But your exposure is not one-size-fits-all. It depends on how you actually earn money.

Non-compete clauses: what they usually restrict

A non-compete clause is not just a generic promise not to compete. It usually has several moving parts: what work counts as competition, how long the restriction lasts, where it applies, and what event triggers it. If you only read the heading and not the details, you can miss the entire point.

The phrase “competing business” is often the slippery part. In plain English, it means a business that overlaps enough with the IMO’s activities that your work there would count as competition. But overlap can be defined broadly. Selling similar life products, annuities, or recruiting into another distribution platform may all get pulled inside that phrase.

Restricted activities

Some non-competes focus on sales activity. You cannot sell the same or similar products through another IMO for a certain time. Others reach recruiting. You cannot move to another platform and recruit from the same network or assist someone else in doing so. Some go further and restrict servicing or replacing business tied to the prior relationship.

The word “assist” deserves attention. If your agreement bars you from directly or indirectly competing, a clause may try to capture more than your own sales. Referrals, consulting help, introductions, back-office support, or support for a spouse’s agency can all become arguments in a dispute.

That sounds aggressive because it is. The broadest clauses are drafted to create room for interpretation later. If the language is vague, the other side gets more leverage when emotions rise.

Time limits

Duration is where the contract becomes real. Six months, one year, and two years are not small variations. In an industry built on pipelines, annual review cycles, renewal patterns, and product windows, each extra month can change your options.

A six-month limit may be painful but survivable if your client base is sticky and you can plan around it. A one-year limit can interfere with replacement cycles, seminar calendars, and recruiting momentum. Two years can be a serious business event, especially if your relationships depend on regular contact.

Longer is not automatically enforceable just because it is written down. But longer still raises the pressure. Even a questionable two-year clause can shape behavior if you want to avoid a fight.

Geography and market scope

Older non-competes often rely on geography: a state, a county, a radius around an office, or an assigned territory. That model makes less sense in a business where your next policyholder may live three states away and your Zoom calendar covers half the country before lunch.

Still, geography language shows up all the time. You may see restrictions tied to states where you were appointed, territories where you produced, or regions where the IMO claims active business presence. If your work is virtual, the wording can get awkward fast. What is your territory if your client base came from webinars and referrals?

That awkwardness does not make the clause irrelevant. It just means old-school territorial language can collide with modern remote sales. Courts and contract fights still have to deal with the words on the page, even if the market has moved on.

Trigger events

You also need to know when the non-compete starts. Some apply only if you resign. Some apply only if you are terminated for cause. Others apply after any termination, including nonrenewal or a no-fault split. That difference matters more than most people expect.

A clause limited to bad-actor exits tells one story. A clause that springs into effect no matter how the relationship ends tells another. If the restriction starts after almost every exit path, your flexibility shrinks even when you did nothing wrong.

That is one of the first things to circle in red. The trigger event tells you whether the clause is aimed at misconduct or simply aimed at control.

Non-solicit clauses: what they usually restrict

A non-solicit clause is usually narrower than a non-compete, but in practice it often hits closer to home. Instead of restricting your ability to work in the industry generally, it tries to stop you from approaching specific people or accounts connected to the IMO.

That may sound mild. It often is not. Insurance distribution runs on relationships. If your strongest next move depends on familiar clients or trusted agents, a non-solicit may do more damage than a broad non-compete that nobody seriously expects to enforce to the hilt.

Clients and policyholders

Client non-solicits often bar you from contacting, moving, replacing, or attempting to replace policyholders you serviced during the relationship. Some cover only active clients. Some cover prospects, leads, former clients, referral sources, and anyone “introduced” to you through the IMO.

Watch the wording around inbound contact. Some agents assume a client can always call first and solve the problem. Not necessarily. A clause may restrict not only initiating contact, but also accepting transferred business, servicing replacement transactions, or encouraging movement after contact begins. If the policyholder reaches out because a policy anniversary notice sparked a question, the contract language still matters.

This is where the client relationship can feel deeply personal and legally impersonal at the same time. A client may think of you as the advisor. The agreement may treat that relationship as protected business goodwill belonging elsewhere.

Agents, downlines, and recruits

For anyone building an agency, this is often the part that matters most. Agent non-solicits can restrict contact with downline agents, recruits, producers in your hierarchy, or even broader networks connected to the IMO. The clause may prohibit recruiting, inducing departure, discussing transition plans, or helping somebody else move an agent out.

If you helped train those producers personally, that can feel unfair. But fairness is not the first question in a contract dispute. The first question is usually what the agreement says, how broad the definitions are, and whether your activity falls inside them. If team ownership is a big part of your value, it helps to understand what control over the hierarchy really means before a transition ever starts.

Recruiting restrictions also catch people because casual conversations count. A “just keeping you posted” text to a subagent can later be described as inducement. Context helps, but wording comes first.

Employees, staff, and vendors

Some non-solicits extend beyond clients and agents to employees, marketers, case managers, lead vendors, call centers, and other service partners. If your assistant, marketer, or preferred seminar vendor became part of your workflow during the relationship, the clause may try to keep that network in place after you leave.

That can create quiet operational problems. Maybe you can legally join a new IMO tomorrow, but you cannot bring the case manager who knows your process or the vendor that built your seminar funnel. On paper, that may not look dramatic. In practice, it can slow everything.

The real difference between non-compete and non-solicit clauses

The cleanest way to remember the difference is this: a non-compete limits where or whether you can compete, while a non-solicit limits who you can pursue. One focuses on your activity in the market. The other focuses on your contact with protected people or accounts.

Think of it like moving apartments in the same city. A non-compete says you cannot live in certain buildings or neighborhoods for a while. A non-solicit says you can move, but you cannot take the neighbors with you.

That is why people often underestimate non-solicits. You may still be free to work. You just may not be free to work with the people who made your work most productive.

Why companies often use both together

An IMO may use confidentiality, non-solicit, and non-compete clauses together because each one covers a different kind of risk. Confidentiality protects information. Non-solicit protects relationships. Non-compete tries to slow direct competitive activity. Stack all three together and the business gets multiple ways to push back when somebody exits.

Even if one restriction looks shaky, another may still matter. A broad non-compete may draw skepticism, but a more targeted non-solicit or confidentiality clause may hold more weight. That is why reading one sentence in isolation is a mistake.

Which one usually causes more trouble in practice

Non-solicit clauses often cause more real-world trouble than agents expect. Here’s the thing: your next move is usually less about whether you can keep selling insurance somewhere else and more about whether you can keep the relationships that make production easier.

If you cannot contact clients you serviced, agents you trained, or recruits you sourced, the new platform may feel far less valuable. Relationship restrictions hit both revenue and momentum. That is why transition disputes so often center on people, not only places.

What courts usually look at when deciding enforceability

Courts usually do not stop at the label. Calling something a non-solicit instead of a non-compete does not automatically save it, and calling something standard does not make it reasonable. The typical question is whether the restriction is tied to a legitimate business interest and whether the scope is reasonable.

This is not a 50-state map, because state law differs too much for that. But the basic framework is pretty consistent: what interest is being protected, and did the contract go further than necessary?

Legitimate business interest

A legitimate business interest is the business reason offered to justify the restriction. Common examples include trade secrets, confidential information, customer goodwill, specialized training, and stable business relationships.

Translated into plain English, trade secrets and confidential information usually mean valuable business knowledge that is not public, such as lead data, sales processes, marketing systems, pricing details, internal reports, or strategy. Customer goodwill means the value in ongoing relationships with clients or referral channels. Specialized training means more than generic onboarding. It suggests the business invested in teaching methods or systems worth protecting. Stable agent relationships means the IMO wants to prevent sudden poaching of producers inside the network.

Not every claimed interest is equally strong. “You learned how to sell life insurance” is weaker than “you had access to a protected lead database and a managed hierarchy built through the platform.”

Reasonableness of scope, duration, and reach

Courts often ask whether the clause is too broad in time, geography, or activity. A restriction can sound normal at first and still reach too far once the details show up.

If a clause bars you from working in any competing capacity anywhere the IMO does business, for two years, after any termination, with a broad definition of competing business, that combination starts to look aggressive. If it instead limits contact with current clients you serviced during the last twelve months, the argument for reasonableness can look stronger.

The trick is that “reasonable” is not a magic word. A contract can use it and still overreach. Facts and drafting still matter.

State law differences you cannot ignore

State law can change the whole analysis. Some states are more open to enforcing restrictive covenants. Some are much less friendly to them. Some draw sharp lines based on worker category, income, or the type of restriction. If your agreement includes a choice-of-law clause and a venue provision, the fight may happen under rules different from the state where you live and work.

That can be a nasty surprise. You may assume local law controls because your clients are local. The contract may point elsewhere. Location matters, sometimes a lot.

Blue-pencil and reformation rules

Blue-pencil and reformation rules describe whether a court can trim or rewrite an overbroad restriction rather than throw it out entirely. In some states, a court may narrow the clause to something reasonable. In others, bad drafting can hurt the party trying to enforce it.

That matters because “too broad” does not always mean “gone.” An overreaching clause may still produce a narrower but enforceable result. So counting on sloppy drafting to save you is not a very good plan.

IMO-specific issues that make these clauses tricky

General contract rules only get you part of the way. IMOs and FMOs add distribution realities that make restrictive clauses messier than standard employment examples.

The practical fight is often less about a dramatic courtroom showdown and more about who controls access, relationships, data, and cash flow during the transition.

Who owns the client relationship

This question sits near the center of many disputes. If the contract says client relationships developed under the IMO belong to the agency platform, then your ability to service or replace that business may be limited even if you personally made every call. If the contract recognizes your independent ownership of self-generated clients, your position may look different.

Ownership language can also vary by source. A self-sourced referral, a seminar lead paid by the IMO, and a house lead from a shared campaign may not be treated the same. If this point is fuzzy, trouble usually follows.

Who owns leads, marketing systems, and training materials

Leads, CRM records, seminar systems, scripts, underwriting workflows, recorded trainings, and marketing assets often become part of the restriction story. You may feel that because you closed the sale, the whole chain belongs to you. Contracts often disagree.

If a lead was subsidized, assigned, co-branded, or generated through the IMO’s system, ownership may be claimed elsewhere. The same goes for CRM notes, templates, and campaign data inside a platform account. What feels like your business memory can be treated as somebody else’s protected information.

Vesting, renewals, and chargeback exposure

Restrictions are not only about who you can call. They can overlap with money already in motion. Vesting schedules, renewal streams, and chargeback liability can all change the leverage around a departure. If leaving early jeopardizes future renewal income or leaves you exposed on chargebacks without easy access to replacement production, the practical pressure rises.

That is why a departure review should include how vesting and payout timelines really work and not only the restrictive covenant paragraph. The paper restriction and the money restriction often reinforce each other.

Transfers, releases, and blocked carrier access

Sometimes the biggest pain point is not a lawsuit at all. It is a delayed release, a frozen hierarchy transfer, or lost access to carrier appointments that supported your product mix. In the middle of a transition, timing matters. If a carrier lineup goes dark for even a few weeks, that can hit production, client service, and recruiting confidence.

This gets even more tangled if a team move is involved. If you are sorting out how a hierarchy shift can affect your producers, the contractual restriction and the carrier process start feeding each other. One slowdown creates another.

Red flags to notice before you sign

You do not need a law degree to spot language that deserves a closer look. You just need to read for business impact instead of legal drama.

The big red flags are usually not flashy. They hide in vague verbs, undefined terms, and open-ended timing.

Vague terms like “indirectly,” “assist,” or “compete”

These words can quietly expand the restriction far beyond obvious conduct. “Indirectly” can pull in support roles, referrals, introductions, consulting, or behind-the-scenes help. “Assist” can turn a casual handoff into alleged participation. “Compete” can mean direct sales, recruiting, marketing support, or something even broader if the definitions stretch.

Ambiguity is not harmless here. In a dispute, unclear language creates room for aggressive interpretation. That alone can pressure you.

Restrictions with no clear end date

Some clauses renew automatically or tie the end date to fuzzy events. Others mix termination timing with later conduct in a way that makes the finish line hard to spot. If you cannot tell exactly when the restriction ends, slow down.

A clean end date matters. So does a clean trigger. If either one is muddy, your exit options can stay muddy too.

Clauses that apply after any termination, for any reason

This is a bigger problem than it first appears. A clause that applies only after cause-based termination at least suggests a misconduct focus. A clause that applies after any termination, including a no-fault split or nonrenewal, can take away flexibility even when the relationship simply stops making sense.

That kind of language says control matters more than fault. You should notice that.

Stacked remedies and fee-shifting language

Watch for injunction language, liquidated damages, commission clawbacks, and attorneys’ fee provisions. Even before anybody proves the clause is enforceable, the threat of fast court action or a fee bill can push settlement pressure hard.

This is why broad contract language still matters even if “nobody enforces these.” Sometimes the leverage comes from the process, not the final ruling.

What these clauses can look like in real life

Contract language gets easier once you picture an actual transition. The legal words are not the point. The point is what happens on Monday morning after you leave.

Scenario: you leave and want to keep working with existing clients

Suppose you leave one IMO and join another, but many policyholders know your direct number and trust you personally. You may assume you can keep helping if somebody calls first. Maybe. Maybe not.

If the clause bars soliciting, replacing, accepting transferred business, or servicing covered clients, inbound contact may not fully solve the problem. A policyholder asking for help with a replacement or review could trigger conflict if the contract defines that account as protected. The gray area usually shows up around service versus movement. Answering a question is one thing. Guiding a transfer can be another.

Scenario: you built a downline and want to move your team

This is where agent non-solicit language becomes very real. Your recruits may feel like your people because you trained them, answered their late-night underwriting calls, and coached them through the first rough applications. The contract may still treat them as protected relationships within the hierarchy.

Outreach about your move, even friendly outreach, can be framed as inducement. If override income is involved, the financial stakes rise quickly. Before attempting a team move, it helps to understand how agency transitions are usually structured so you do not confuse a business plan with a contract breach.

Scenario: you join a new IMO that sells many of the same products

A move to another IMO that offers similar life products or annuities does not automatically violate a non-compete, but it can. Everything turns on overlap, timing, territory, and wording. If the clause bars competing through another distribution organization for twelve months in states where you produced, that is a different risk from a clause that only bars soliciting certain clients.

The details decide whether the move is routine, restricted, or arguable. That is why “same industry” is too broad to be a useful answer.

Common misunderstandings about non-compete and non-solicit clauses

A lot of bad advice floats around this topic because people confuse what should happen with what often happens. The difference matters.

“If it seems too broad, it’s automatically unenforceable”

No. A clause can be overbroad and still create cost, delay, leverage, and partial enforcement risk. Some courts narrow clauses. Some businesses send demand letters and force a response long before enforceability gets tested fully.

The practical burden starts earlier than the final legal answer.

“If a client contacts you first, you’re always safe”

Also no. Inbound contact is not a magic shield. If the contract bars accepting, servicing, replacing, or moving certain business, the source of the first call may not end the issue. The exact wording matters, especially around policy transfers and replacements.

“An independent contractor agreement means these clauses don’t count”

Independent contractor status does not erase restrictive covenant issues. Many IMO agreements impose these clauses on independent agents, agencies, and recruiters. The contract structure may differ from employment, but the restriction can still matter a great deal.

“If the clause is never enforced, it doesn’t matter”

That is one of the most expensive myths in the business. A clause can matter through demand letters, onboarding interruptions, release delays, frozen appointments, and nervous recruits even if no judge ever rules on it. Friction alone can change outcomes.

How to review these clauses without getting lost in legalese

You do not need to decode every Latin-sounding phrase to get useful clarity. Read for business effect.

The simplest approach is to turn the clause into plain questions and force the contract to answer them.

Start with four questions

Ask four things. What exactly is restricted? Who is protected? How long does it last? What happens if there is a dispute?

Those four questions strip away a lot of noise. If the contract cannot answer them clearly, that is already a signal. You are not looking for pretty drafting. You are looking for operational consequences.

Map the clause to your actual business model

A clause only becomes meaningful once you compare it to how you actually earn income. If your book is mostly self-generated life cases, client restrictions matter most. If your growth plan depends on recruiting and mentoring, agent non-solicits matter more. If your product mix relies heavily on carrier access through the IMO, release timing and appointment continuity become central.

This is where generic advice fails. Your risk lives in your business model, not in somebody else’s.

Check the definitions section before anything else

Definitions often do the real work. “Client,” “producer,” “confidential information,” “affiliate,” “lead,” and “solicit” can all be defined much more broadly than normal usage suggests. A short clause can become far bigger once those defined terms snap into place.

If you want a sharper lens for spotting contract landmines, a broader rundown of the clauses that tend to cause brokerage owners trouble is worth studying alongside the agreement in front of you.

When and how to push back before signing

Restrictive language is often more negotiable than it looks, especially if you bring production, niche expertise, recruiting power, or a real book of business. The best time to fix a bad clause is before signatures and hurt feelings enter the picture.

Confidence helps here. Not bluster, just clarity.

Terms you can ask to narrow

You can ask for a shorter duration, a tighter client definition, and a narrower description of restricted conduct. You can push to remove blanket geographic limits that make no sense for virtual business. You can ask for carve-outs covering preexisting relationships and self-generated clients. You can also ask for passive announcement carve-outs so a basic transition notice does not become a violation.

For team builders, agent non-solicit language deserves special attention. If you recruit independently, broad restrictions on all producers in the network may be far too wide for your role.

Better alternatives to a broad non-compete

A targeted confidentiality clause, a focused client non-solicit, clear lead ownership rules, and specific data return requirements often protect real business interests better than a sweeping non-compete. That framing can help the negotiation stay practical instead of adversarial.

The point is not to strip protection away. The point is to match the protection to the actual risk.

Why side letters and email promises are not enough

Informal assurances are comforting right up until they are useless. If somebody says, “Don’t worry, that clause is never enforced,” but the signed agreement says otherwise, the contract usually wins unless the revision is properly documented and integrated.

If a change matters, it belongs in the agreement, the amendment, or another formal document that clearly overrides the original text.

What to do if You’re already bound by one

If you already signed and now want to switch IMOs, restructure, or move a team, panic is a bad strategy. Quiet preparation is better.

The goal is to understand the document set, sort the facts, and avoid accidental missteps before outreach begins.

Gather the contract set, not just the signature page

Pull the main agreement, amendments, schedules, compensation addenda, producer exhibits, lead program terms, policies, and later updates. A lot of disputes turn on a document that seemed minor at the time.

Do not assume the latest PDF in your inbox tells the whole story. Many relationships evolve through add-ons.

Document your relationships and business sources

Separate house leads from self-generated leads. Separate preexisting clients from clients acquired through the IMO relationship. Separate personal recruits from assigned hierarchy relationships. That sorting can matter a lot if the contract draws distinctions by source or ownership.

Dates help. Sources help. Written records help. Memory alone is not a great file system when a transition gets tense.

Get legal advice before making outbound moves

Before contacting clients, agents, staff, or vendors, before moving CRM data, and before announcing a transition, get the agreement reviewed. A one-hour legal review can save months of cleanup.

That is not fear talking. It is basic damage control. Most mistakes happen in the first burst of activity after somebody decides to leave.

Questions to ask before signing an IMO agreement

Good questions force vague clauses to become specific. That is exactly what you want.

Who exactly can’t you contact if you leave?

Get clarity on whether the restriction covers only active clients, all prospects, inactive policyholders, downline agents, former recruits, staff, vendors, or carrier contacts. “Anyone connected to the business” is not a useful answer.

What happens to renewals, vesting, and carrier appointments?

Do not treat restrictive clauses as a separate issue from money flow. Ask what happens to renewals, chargebacks, vesting, release timing, and appointment continuity. A contract that looks tolerable can feel very different once those pieces are connected.

Is there a realistic path to leave cleanly?

Ask about notice requirements, release timelines, transition support, waiver options, carve-outs, and any buyout path. A healthy contract should not pretend breakups never happen. It should make them manageable.

The one move that can save you the biggest headache later

Here’s the thing: the best protection is usually not a dramatic negotiation tactic. It is a pen, a highlighter, and twenty quiet minutes before you sign.

Mark every sentence that controls who you can work with, who you can call, what counts as competing, how long the restriction lasts, what happens to renewals and hierarchy access, and where a dispute gets heard. Then ask for written revisions while the relationship is still easy and everybody is still optimistic.

Try one simple exercise today: pull the last IMO agreement you signed and highlight every line that limits your next move. If you cannot explain those lines in plain English by the time you finish, that is the problem to fix first.