Drafts a Partner Agreement, each side's work, who each introduces to the other and why it serves the client, how introductions are made and the loop closed, fee and client disclosure questions for a qualified adviser, and a review date. Use for "run net-partner-agreement", "networking partner", "another firm keeps sending me work", "write down our introduction arrangement", "should I pay a fee for introductions", "partner agreement draft", part of the Claude for Networking on LinkedIn Pack by...
Installs into .claude/skills of the current project.
Are you the author of Net Partner Agreement?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/polar-bear-org-net-partner-agreement)
---
name: net-partner-agreement
description: Drafts a Partner Agreement, each side's work, who each introduces to the other and why it serves the client, how introductions are made and the loop closed, fee and client disclosure questions for a qualified adviser, and a review date. Use for "run net-partner-agreement", "networking partner", "another firm keeps sending me work", "write down our introduction arrangement", "should I pay a fee for introductions", "partner agreement draft", part of the Claude for Networking on LinkedIn Pack by Polar Bear.
---
# Partner Agreement
## When To Use
Another firm keeps sending you work, or could, and nothing about it is written down. Use it before the next introduction, while both sides still remember why it started. It answers: who do you each introduce, how, what does the client hear, and what questions go to an adviser?
## When Not To Use
If a friend is simply helping you find people, the Shared Introduction List is enough. If one introduction just came in and you want to say thank you, run the Thank-You Note. This is not a contract: it is a working draft and a list of questions for a qualified adviser.
## Inputs
- Your work and the partner's, in a line each, and the introductions that have happened so far (your own record)
- How introductions happen today, and what each side tells the other afterwards
- Whether money or any other benefit has been mentioned
If you have none of this, I start from the two lines of work and mark the output as a first draft.
## Approach
A partner arrangement (common practice, described generically): two businesses whose work meets write down who each introduces to the other and why it serves the client. On fees, one profession's rule is a useful example: CFA Institute Standard VI(C) asks members to disclose to clients any benefit received or paid for a recommendation. That is one standard, not general law. The failure it prevents: a client who later learns a fee changed hands, and two partners who each think the other owes them.
## Workflow
1. Ask three questions: who is the partner, who has each side introduced so far, and has a fee or benefit been mentioned?
2. Write each side's work in one line and where they meet: who you introduce to them, who they introduce to you. No contact details anywhere in the document.
3. Write why each introduction serves the client, from the client's side. If an introduction only serves the partners, it is out of scope.
4. Set how introductions are made: double opt-in, your Forwardable Intro Blurb, and who writes to the client.
5. Set how the loop is closed: who tells whom what happened, and what may be shared about the client. Only what the client agreed to share; default "we spoke, thank you".
6. Write fees only as questions: is there a fee or other benefit; how and when is it disclosed to clients; does a professional rule, tax or contract point apply? Each ends "check with a qualified adviser". No terms, rates or advice.
7. Add client disclosure points and a review date both sides set.
## Output Format
```markdown
# Partner Agreement Draft
**Partners:** [you] and [partner] · **Drafted in:** [Claude Docs (beta) / any document] · **Review date:** [date]
## Our work
| Side | Work in one line | Who we introduce to the other | Why it serves the client |
|---|---|---|---|
| [you] | [ ] | [ ] | [from the client's side] |
| [partner] | [ ] | [ ] | [from the client's side] |
## How introductions are made
- Double opt-in; [who writes the introduction; forwardable blurb used]
## Closing the loop
- [who updates whom, when; only what the client agreed to share]
## Fee and benefit questions
- [Is there a fee or benefit?] Check with a qualified adviser.
- [How is it disclosed to clients?] Check with a qualified adviser.
- [Does a professional rule, tax or contract point apply?] Check with a qualified adviser.
- Client disclosure: [what the client is told about the arrangement, and when]. Check with a qualified adviser.
## Decision
You and [partner] review this draft and take the fee questions to a qualified adviser by [date], before any fee is agreed.
```
## Done When
- Each introduction direction has a reason written from the client's side
- The loop-closing rule limits what is shared to what the client agreed
- Every fee, tax, contract and disclosure point is a question ending "check with a qualified adviser"
- The document holds no contact details and no client details
## Quality Bar
- No fee terms, rates or legal advice anywhere
- The client's interest comes before either partner's
- Introductions always double opt-in
- A review date both sides set
- Fee and disclosure points are questions for a qualified adviser; the client's interest comes first, and you send the draft to your partner yourself.
## Next
Run net-thank-you-note (Thank-You Note) to thank the partner when an introduction comes in.
## About the makers
This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).