Both teams are usually right about their own job. Innovation protects relationships that took years to build and knows a slow answer can cost one. Legal protects the corporate from commitments it has not read and knows a quick yes can outlive the person who gave it. The handoff between them is where each team's caution meets an incomplete picture of the other's question.
Four words the two teams read differently
A surprising share of the back-and-forth comes from vocabulary. Innovation uses the program's words loosely, and legal reads them as defined terms in a contract it has not yet seen. The sample Channel Partner Agreement settles most of these words on its own, which is why it belongs in the first email rather than the third.
| Word | What innovation usually means | What the documents say | What legal needs to hear |
|---|---|---|---|
| Partner | A friendly working relationship with SourceX | Section 7.1: independent contractors, and "Participation creates no partnership or employment relationship." Section 4.5 bars naming the other side as a partner in public without written authorization | Who would sign as partner, and that no public announcement is planned |
| Referral | An informal mention to a CEO | Section 1.2: an introduction must be recorded in writing; section 3.3 lists the fields the record carries | That nothing is recorded until the CEO agrees, and who will keep the record |
| Vendor | SourceX as a supplier to the corporate | The agreement's opening: "SourceX licenses directly from suppliers; Partner makes introductions." | That the corporate buys nothing, so procurement onboarding does not apply |
| Pilot | A trial with a startup, data included | No data moves through the partner: section 4.2 gives the partner no authority to share a supplier's records | That the trial is a handful of asks, not a pilot project; see pilot versus referral |
Three seats inside one request
Legal's first question is usually some version of "what is our relationship with this company?", and the honest answer often has three parts. Writing them separately is the fastest way to stop the question coming back.
- The corporate. The venture unit, or the employee who would register as partner. Legal reviews whether either may take part, who signs and whether anyone may accept money.
- The vendor tie. Any commercial link with the company: procurement buying from it, a sales team selling to it, an operations team hosting its systems. Legal needs to know whether a tender, renewal, price discussion or dispute is open, because an ask during one can look like leverage.
- The operating company. Its CEO decides whether to discuss licensing and signs for it, and SourceX's screening guidance treats an introduction the decision maker never heard about as usually not a fit. Neither team can approve anything on the company's behalf, and the company's records never pass through the corporate.
The stakeholder handoff diagnostic
Score the last request innovation sent legal on the six facts below, 0 to 2 each, for a total out of 12. A low score does not mean the request was wrong, only that legal had to ask before it could answer. In our working rule, each fact scored 0 tends to cost one round trip, and the diagnostic's job is to make those round trips visible before they happen. Score legal's reply too, on three checks, because friction runs in both directions.
- Every condition has an owner. "Subject to compliance review" with no name attached is a condition nobody will clear.
- Every condition has a date or a trigger. "Not during the renewal" is usable; "later" is not.
- Each question gets its own yes, no or open. A single paragraph answering six questions at once sends innovation back to ask which part applies.
| Fact | 0: missing | 1: partial | 2: complete | Usual symptom when missing |
|---|---|---|---|---|
| Company named | A sector or "our portfolio" | A brand name | The legal entity and its current CEO, dated | Legal asks which company before reading further |
| Corporate's seat | Not stated | "They're a supplier" | Every tie listed: stake, board role, supply, sales or hosting contract, with any open tender, renewal or dispute dated | Legal asks about conflicts, then about timing |
| Partner of record | "We" would partner | Entity or person, undecided | The named entity or employee, and who signs for it | The agreement review cannot start |
| Money | Not mentioned | "There's a referral fee" | The published basis, the greater of $50,000 plus 5% and 15% of Actual Supplier Payout on a company's first qualifying transaction and 15% on repeat transactions within the Repeat Window, with no cap, who would receive it and how the CEO is told | Legal escalates to the outside-compensation policy owner |
| Draft words | Nothing drafted | Talking points | The exact first message to the CEO | Legal reviews a hypothetical, then reviews again |
| Source of facts | Unclear what is known or how | Facts listed without sources | Each fact tagged public, said by the CEO, or confidential and therefore left out | Legal asks whether board or diligence material is involved |
One handoff note instead of five emails
The note is the diagnostic turned into a form: one page, the six facts at full score, and the documents legal will otherwise ask for. Attach them rather than linking a sales page. SourceX's terms page, Version 2026-11-04, links an unsigned sample of the Channel Partner Agreement with the standard reward terms, so legal can read the contract before anyone registers. The terms send unresolved disputes to confidential binding arbitration under the JAMS Comprehensive Arbitration Rules, and JAMS publishes those rules on its own site; its page lists the current version as effective June 1, 2021, and, in our paraphrase of Rule 3, the version in force when an arbitration starts applies unless the parties agreed otherwise. Sending the rules with the agreement saves a request.
- Request. One sentence: may this corporate, through this partner of record, ask this CEO whether the company wants a licensing conversation with SourceX?
- The six facts. As scored above, each at 2.
- Documents. The terms version, the sample agreement, the JAMS rules link and SourceX's screening page.
- Draft message. The words the relationship owner will send the CEO, including who could be paid.
- What the corporate will never do. Handle records, logins or samples, or say the company qualifies.
- Decision asked of legal. Yes, no or open, for each of participation, signer, wording and timing.
- Owner and date. Who on the innovation side answers follow-up questions, and when the relationship owner plans to ask.
Who owns which approval, so neither team waits on the other
Friction also comes from each team waiting on a step that belongs to someone else. Innovation owns the relationship owner's agreement to ask and the ask itself. Legal and compliance own participation, the signer, the wording and the confidentiality screen; the substance of that review is in what compliance teams review. The operating company's CEO owns the only decision about the company. SourceX owns its review, its earlier-contact check and credit: a company with any earlier lead, account or email correspondence with SourceX is a duplicate, and when several partners know one company, only one introduction can be credited and SourceX settles the overlap in duplicate review. The sequence of sign-offs is laid out in the two approval paths, and the difference between a founder's enthusiasm and a company's authority in founder permission versus corporate authority.
One request, scored twice (Illustrative)
Illustrative: an invented request about an invented company, scored before and after the handoff note.
A business-unit head emails legal: "Can we partner with SourceX to refer a 300-person distributor we work with? Their CEO mentioned AI data at dinner." Legal replies with five questions over three weeks. The platform manager rewrites the request as a handoff note naming the venture unit as partner. Legal's next reply raises one point: policy lets the unit introduce but not accept the reward. Because the published terms do not cover a partner who turns a reward down, that open question goes to SourceX in writing before anything is submitted.
| Fact | First email | Score | Handoff note | Score |
|---|---|---|---|---|
| Company named | "A 300-person distributor" | 1 | The legal entity, its CEO, checked this week | 2 |
| Corporate's seat | "We work with" them | 1 | Procurement buys from it; no tender open; renewal due in nine months | 2 |
| Partner of record | "We" | 0 | The venture unit as entity, treasury signs | 2 |
| Money | Not mentioned | 0 | Published basis stated; the CEO is told in the first message | 2 |
| Draft words | None | 0 | Four-sentence message attached | 2 |
| Source of facts | "Mentioned at dinner" | 1 | Two public facts and the CEO's own remark, tagged | 2 |
The first email scored 3 of 12 and took five round trips; the note scored 12 of 12 and took one. Both counts are invented to show how the diagnostic is read.
A six-week trial of the note
Use the note on the next three requests and measure what changes: round trips per request, days from request to legal's answer, conditions that arrived without an owner, and anything the CEO says about how the eventual ask felt. Compare against the three requests before. If round trips fall but CEOs report pressure, the handoff improved and the asking did not; fix the asking first. SourceX has not published approval times or how often CEOs agree, and none are published here; the trial produces your own figures.
When the diagnostic misreads the friction
- A real disagreement. Some corporates bar outside compensation or this kind of program outright. A perfect note gets a fast no, which is a better outcome than a slow one; the CEO can still apply directly.
- Capacity, not content. If legal has no time for any non-core request, a complete note waits in the same queue. The diagnostic cannot fix staffing.
- Completeness is not correctness. A note can score 12 and still contain a fact learned through a board seat. Legal's confidentiality screen exists for that reason.
- The note as a pressure tool. A polished package can make the ask feel inevitable to the CEO. The note governs the internal handoff only; the CEO's answer stays open.
- Company-side limits. Rights, client-owned material and whether the records match a current program are settled in SourceX's review, and a company that misses one program may suit another later.
Method note. The six facts and three reply checks come from the questions SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the sample Channel Partner Agreement (version 2026-10-19) and the screening page leave for a corporate to answer itself, read on 2026-10-27; the money row and the version reference were brought up to terms Version 2026-11-04 on 2026-11-04. The 0 to 2 scale and the one-round-trip-per-missing-fact rule are a working method, not measured data. The example is invented. Approval times, CEO response rates and outcomes are not measured.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
When the handoff note scores 12 and legal has answered each question, register the partner of record, recheck the company on who qualifies and keep the program terms version legal read with the note.
Whether innovation and legal can agree on a referral is a different question from whether SourceX merits investment; readers with the second question can ask for investor materials on the SourceX investor overview.
This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.