Find out who is on the other side of the relationship
AWS's Partner Network and GitLab's work with alliances, service partners and resellers illustrate why partner work can include technical delivery and enablement. It is not simply keeping a list of business contacts.
| Arrangement | What the other organization does | A useful question |
|---|---|---|
| Direct customer | Buys the product for its own use | What makes this customer ready to buy? |
| Referral partner | Introduces prospective customers | When is an introduction accepted and credited? |
| Reseller | Participates in selling the product | Who contracts with and supports the buyer? |
| Technology partner | Connects complementary products | Who builds and maintains the integration? |
| Services partner | Implements or operates the solution | Who owns delivery quality and handoffs? |
Use the distinctions below when reading a posting. One relationship can combine several arrangements; ask who sells, bills, delivers and handles support.
Example: partner-sourced revenue is not automatically more profitable
A fictional $10,000 annual subscription has $2,000 of variable delivery cost. The partner receives 20% of the subscription price, and the company spends $500 on extra onboarding. The direct route instead costs $2,500 to acquire the customer. These are assumed commercial terms, not real program rates.
| Item | Partner route | Direct route |
|---|---|---|
| Subscription revenue | $10,000 | $10,000 |
| Variable delivery cost | −$2,000 | −$2,000 |
| Referral payment | −$2,000 | $0 |
| Extra partner onboarding | −$500 | $0 |
| Direct acquisition spending | $0 | −$2,500 |
| Contribution after listed costs | $5,500 | $5,500 |
Both routes contribute $5,500 per customer after the listed costs. If the partnership also costs $15,000 to set up, five genuinely additional customers contribute $27,500 before setup and $12,500 after it.
Change the alternative and the conclusion changes. If those same five customers would have bought directly at the stated direct-acquisition cost, the direct route contributes $27,500. The partner route is then $15,000 worse, not a $12,500 improvement. Ask what business the partnership actually adds.
Test the handoff before proposing a large launch
For a small practice pilot, define the customer segment, what counts as an accepted introduction, who follows up and who handles duplicate claims. Track introductions, accepted opportunities, evaluations and sales separately.
If the pilot is too short for sales to close, report the intermediate results rather than inventing revenue. Also define when to pause, such as repeated introductions outside the agreed segment or an unresolved support handoff.
Build a proposal that exposes the difficult questions
Use a real public product description with clearly fictional partner terms. Explain what each company and the customer gain, map the handoff, calculate the economics and propose a limited test.
Include one disagreement: payment for every introduction versus payment only after a sale, for example. Explain the incentive and recordkeeping consequences rather than attempting to draft a legal contract. For a sales application, adapt the exercise into a plan for understanding one end buyer's needs.
Ask what a productive week looks like
‘Would I be booking sales meetings, researching potential partners, supporting integrations, coordinating campaigns or maintaining partner records?’ Follow with: ‘How does the team distinguish business a partner sourced from business it merely influenced?’
Those answers help you choose the relevant sample. A student-club collaboration can demonstrate coordination and negotiated responsibilities, but describe it as that rather than renaming it a commercial distribution agreement.