# Partner program for a small team: tracking partner-sourced deals in Salesforce without a PRM

https://salesbond.app/blog/partner-program-salesforce-without-prm/
Published: 2026-10-20 · Updated: 2026-10-26

A small team can run a partner program in Salesforce with a partner account, a partner-source field on the opportunity and a one-page deal registration rule. Buy a PRM when partners need their own portal, not before. At five to fifteen people, everything a program needs is bookkeeping: who the partner is, which deals they touched, who owns a contested deal, and a report that tells you which partners are worth the quarterly call. A CRM already does bookkeeping.

This article is about the program as a whole. A single referral deal, with its attribution window and payout, is covered in [referral partner deals in Pipedrive](https://salesbond.app/blog/referral-partner-deals-pipedrive/), and the buyer-versus-end-customer question for one reseller order is in [reseller and distributor deals in Pipedrive](https://salesbond.app/blog/reseller-end-customer-deals-pipedrive/). Here we start a level up: tiers, registration, conflict policy and the partner report.

## What a partner program needs that a CRM already has

A partner program is the set of rules and records for selling with and through other companies: who your partners are, which deals they bring, and what they earn. PRM (partner relationship management) software is a portal on top of that, where partners register deals, pick up materials and see their own results. The CRM is where your team keeps the same records. Whether a program pays off at all is the question of [channel sales vs direct sales](https://salesbond.app/blog/channel-sales-vs-direct-sales-small-team/) for a small team.

Vendors of partner software describe the program as something you run on their platform, with a portal, deal registration, training and content ( [Magentrix: PRM](https://www.magentrix.com/glossary/prm)). Salesforce covers program types and benefits on its own partner-program page, right next to its PRM product ( [Salesforce: partner program](https://www.salesforce.com/sales/partner-relationship-management/partner-program/)). Both are written for a company that is already shopping. Strip the portal out and what is left is four records and two rules.

The records: a partner, the partner’s tier, a deal the partner touched, and the role the partner played on that deal. The rules: what counts as a registered deal, and who wins when two parties claim the same customer. The portal only matters when the partner, not your rep, has to type those records in. With a handful of partners, your rep types them, and that holds until the typing becomes the bottleneck.

We think small teams usually make the opposite mistake. They skip the records because a PRM feels premature, and run the program in email. Six months later nobody can say which partner sourced which opportunity and the first commission dispute is settled from memory. The records are cheap. Put them in Salesforce on day one.

## Three fields: partner source, partner account, registration status

Three fields carry the program. Two live on the opportunity, one on the account.

**Partner account.** Every partner is an account in Salesforce, the same object as your customers, marked as a partner so it stays out of customer reports. The marker can be an account record type for partners ( [Trailhead: create record types](https://trailhead.salesforce.com/content/learn/projects/customize-a-salesforce-object/create-record-types)) or a custom checkbox you create. On that account, a picklist for the tier: Referral, Reseller, Gold, whatever yours are called, three values at most. If your team already separates new and renewal business, [record types for new vs renewal opportunities](https://salesbond.app/blog/salesforce-record-types-new-vs-renewal-opportunities/) shows the same pattern.

**Partner source on the opportunity.** A custom lookup field you create from the opportunity to the partner account, filled when a partner sourced or influenced the deal and empty otherwise. Why not text? Because by March a text field holds “Acme”, “ACME Ltd” and “acme partners”, and the partner report dies with them. Next to it goes a small picklist, Partner role, with two values: Sourced and Influenced. Sourced means the partner brought the customer. Influenced means the customer was already yours and the partner helped close. That distinction decides the commission and drives the partner report below, so it belongs on the opportunity, not in the notes.

**Registration status.** A picklist on the opportunity: Registered, Approved, Rejected, Expired. Blank means the deal was never registered, which is fine for direct deals and for partners whose tier doesn’t include registration at all. This one field is deal registration in miniature.

None of this is a partner-side feature. These are custom fields your admin creates and your own reps fill in. If a partner deal also needs internal credit shared between two of your reps, that is a separate mechanism, [opportunity splits](https://salesbond.app/blog/salesforce-opportunity-splits/), and it doesn’t replace the partner lookup.

## Deal registration without a portal: a form and one rule

Deal registration is a promise. The partner tells you about a customer before they start selling, and you promise not to sell direct, or let another partner in, for a set time. The promise is the product; the portal is packaging.

Without a portal the registration arrives by form, and a form is enough. It can be a Web-to-Lead form on your site, which collects leads straight into Salesforce ( [Trailhead: create and convert leads](https://trailhead.salesforce.com/content/learn/modules/leads_opportunities_lightning_experience/create-and-convert-leads-lightning)), or a shared form whose answers a rep copies into the CRM in two minutes. Ask for five things: partner name, customer company, the contact the partner has spoken to, what the customer wants, and the expected close month. A rep reviews it and sets the status within two business days, a limit written into the partner agreement, because a registration that sits for a week is one the partner stops trusting.

The one rule goes on the first page of the partner agreement:

1. A registration is approved only if there is no open opportunity with that company in your pipeline. An existing open opportunity means Rejected, with a one-line reason, the same day.
2. An approved registration protects the partner for a fixed window from the approval date. The length depends on your sales cycle; we set it the same way as the attribution window in the referral article, so the arithmetic isn’t repeated here.
3. Inside the window the partner is the Partner account on any opportunity created with that company, with Partner role set to Sourced. After the window the status goes to Expired, and a new registration starts a new window.

The check in rule one happens in Salesforce, not from memory. Before approving, the rep looks up the account and its open opportunities. A duplicate account under a slightly different name will slip past a name search, so the rep checks the website domain too. Salesforce’s duplicate and matching rules can flag some duplicates as records are entered ( [Trailhead: duplicate management](https://trailhead.salesforce.com/content/learn/modules/sales_admin_duplicate_management/sales_admin_duplicate_management_unit_1)), but they don’t make the approval decision for you. This step fails most often, and the dispute always surfaces after the win.

What a portal adds here is self-service: the partner submits, sees the status and gets the expiry warning without emailing your rep. With five partners that’s an email a week. With fifty it is somebody’s job.

## Channel conflict: who owns the deal, decided in writing

Channel conflict is two parties claiming the same customer; a small team settles it with a four-row policy written before the first collision. The deal-level version, a partner introducing a company your rep is already working, has a mechanical answer in the referral and reseller articles: check for an open deal, first in wins, say so the same day. The program-level question is which party wins by policy when two legitimate claims collide.

![Table of four channel conflict rules: for each situation, who owns the deal, partner or your rep](https://salesbond.app/wp-content/uploads/2026/10/partner-program-salesforce-without-prm-2.png)

Here is the policy in plain words. A partner who registers a company with no open opportunity owns it for the length of the window. If your rep already has an open direct opportunity there, the rep keeps it and the registration is rejected the same day. When two partners register the same company, the earlier approved registration wins, and the second partner hears the date of the first. And if a registered customer calls you directly inside the window, the partner keeps the registration: your rep adds the partner to the opportunity and tells them.

That last case is the one teams argue about, and it decides whether partners trust you. A customer registered by a partner who then calls your sales line is still the partner’s customer for the window. If your rep takes the deal direct because the customer “came to us”, the partner learns registration is worth nothing, and you won’t get a second one. We would rather pay commission on a deal we could have taken direct than teach every partner to hide thier pipeline from us.

Two more decisions belong on the same page. Who settles a dispute the policy doesn’t cover: one named person, usually the head of sales, within five business days, by email, so the decision has a date. And what happens to a partner who registers companies they have never spoken to, just to block competitors. Our answer is one warning, then the tier drops, and a note on the partner account records when and why.

Credit between two of your own reps on a partner deal is a separate, internal matter: see [opportunity teams vs account teams](https://salesbond.app/blog/salesforce-opportunity-teams-vs-account-teams/).

## Reports: partner-sourced vs partner-influenced pipeline

Two reports, built from the three fields, run the quarterly partner review. Both are opportunity reports grouped by the partner lookup, filtered to the period and split by Partner role.

The first is pipeline and won revenue where Partner role is Sourced. Partner-sourced revenue is what the partner is paid on, and it ranks your partners. Read it per partner, per quarter, as won amount and as count of opportunities created. Twenty registrations and one win is a different partner from three and two: the count shows the quality of their introductions, the amount shows their customers.

The second is pipeline where Partner role is Influenced. Partner-influenced revenue is softer, and we keep it out of commission unless the agreement says otherwise. But it is the report that justifies partners who never source anything and still matter, like the consultancies and integrators who sit beside your buyer. Without it they look like dead weight at renewal time and get cut.

![Quarterly partner review table: sourced and influenced rows, count of opportunities and won amount per partner](https://salesbond.app/wp-content/uploads/2026/10/partner-program-salesforce-without-prm-3.png)

One report isn’t worth building: partner-sourced pipeline by stage with a forecast attached. Partner deals move on the partner’s calendar, which you don’t control, and a forecast built on them is a guess dressed as a report. Count them and keep them separate from the direct forecast.

A disclosure, since this is where the fields get checked: we build SalesBond, a sales management layer on top of the CRM a team already uses, and it works with Salesforce among others. Deal Health checks every deal in the connected CRM against more than 20 rules, covering activity, progression and data among other things, and shows the violations. It doesn’t know your registration rule; that stays with whoever wrote the agreement. If you’d rather have gaps in deal data flagged for you: [Check your CRM with SalesBond](https://salesbond.app/).

## The signs you need a PRM

A PRM pays for itself when partners are doing work inside it that your reps used to do for them. Four signs, roughly in the order they show up.

Partners ask about the status of their registrations more than once a week, and the answer is always “let me check”. That is the the self-service portal asking to be bought.

You have more than one tier with different registration rights, and the rep approving registrations has to look up a partner’s tier before answering. A PRM enforces that by role. A picklist only records it.

Partners need materials, pricing or training, and get them as email attachments with version numbers in the file name. Content distribution is the part of PRM a CRM can’t fake.

The partner report gets pasted into a slide every quarter for a partner who wants to see their own numbers. Giving partners a login to their results is where a portal stops being a luxury.

Salesforce sells partner software of its own, and its guide to choosing PRM software is a reasonable starting point once these signs apply ( [Salesforce: PRM software](https://www.salesforce.com/sales/partner-relationship-management/software/)). We haven’t compared licenses or prices on purpose; that’s a conversation with the vendor. Until then, three fields and a one-page rule will carry a program of ten or twenty partners further than most teams expect.

## FAQ

**What is the difference between PRM and CRM?**
 A CRM is where your team records accounts, deals and activity. A PRM adds a partner-facing layer on top: a portal where partners register deals, get materials and see their own results. Small teams can keep partner records in the CRM until partners need that self-service.

**What is deal registration?**
 Deal registration is a partner telling you about a customer before selling, in exchange for protection from direct sales and other partners for a fixed window. Without a portal it can run on a form and one registration-status field.

**What is the difference between partner-sourced and partner-influenced revenue?**
 Partner-sourced means the partner brought the customer. Partner-influenced means the customer was already in your pipeline and the partner helped close. Sourced usually drives commission; influenced shows which advisory partners matter.