# Two reps, one deal: how to record shared credit in Pipedrive

https://salesbond.app/blog/shared-deal-credit-pipedrive/
Published: 2026-10-05 · Updated: 2026-10-26

Pipedrive gives every deal a single owner, so split deal credit between two people has to live in its own fields and in a written rule, not in the manager’s memory. Record who sourced the deal, who closed it and how the win is counted between them before the deal is marked won. Then keep every revenue report on one field only, so an $18,000 deal stays $18,000 on the board no matter how many names are attached to it.

## Last day of the month, 5:10 pm: an $18,000 deal and two people saying “mine”

It’s Tuesday, the last day of the month, and Victor marks the deal won at 5:10. $18,000, an annual contract, the biggest win of the month. He posts it in the team chat. Eleven minutes later the manager gets a direct message from Hana, who does outbound for the team: “The Bergmann deal is on the board under Victor. I booked that meeting in May.”

The names are invented. The message isn’t, and we have seen it arrive in more than one team.

Both of them have a point. Hana found the company, got the first meeting and asked the questions that made it a real opportunity. Victor ran four calls, a proposal and a round with the customer’s legal team. The deal sits under Victor because he was the owner when the button was pressed. Hana’s part is in the timeline, in an activity from May that nobody will scroll back to.

Whatever the manager types back tonight becomes the rule. The next person who sources a deal will quote that chat message, word for word, as precedent.

## What Pipedrive knows about the deal, and what it doesn’t

One owner. Pipedrive’s help on followers says “each item in Pipedrive can only have one owner”, and followers let other users see the deal and get notified about it, without any credit attached ( [Pipedrive: Followers](https://support.pipedrive.com/en/article/followers)); we covered [what followers can and can’t do](https://salesbond.app/blog/pipedrive-followers-rep-out-of-office/) separately.

Participants sound like the colleague field but aren’t. “A deal in Pipedrive can only have one connected person contact”, and other contacts “can be linked to a deal as participants” ( [Pipedrive: Can multiple people be linked to a deal?](https://support.pipedrive.com/en/article/can-multiple-people-be-linked-to-a-deal)): that is the buyer’s side, the people who keep a deal from being [single-threaded](https://salesbond.app/blog/single-threaded-deals/), and it says nothing about who on your side did the work.

So a deal carries one owner, a list of followers (your users), a list of participants (the customer’s people) and a timeline. None of those is a “who gets the win” field. We have not found one in Pipedrive’s help, and the followers article is the closest it gets. If there is a split-credit setting we have missed, write to us. Until then the honest answer is that you build it yourself, and it takes two custom fields. Salesforce has built-in tools for this, and we sort out [who sees the deal and who gets the credit in Salesforce](https://salesbond.app/blog/salesforce-opportunity-teams-vs-account-teams/) separately. On HubSpot, here is how to set up [split credit in HubSpot](https://salesbond.app/blog/hubspot-deal-splits/) and keep the rep report honest.

## Pick the rule before the fields: role, stage or source

Fields only record a decision. Somebody has to make it first, and we have seen three versions hold up. They differ mostly in how much arguing they leave room for.

By role. Whoever does outbound gets sourcing credit on every deal they opened, whoever closes gets closing credit, and the deal’s history does not change that. Simple, and it fits a team where the SDR and AE jobs are actually separate people.

By stage. Credit depends on where the deal was when it changed hands. The fairest rule on paper and the worst one in practice for a small team, because every handover turns into a negotiation about which stage it “really” was in.

By source. Credit follows how the deal entered. Outbound, opened by the SDR: sourced by the SDR. Inbound form, routed by a rule: nobody sourced it, and the closer owns it outright. Partner referral: sourced by whoever holds the partner. The partner fee itself is a separate agreement from this internal split, covered in [referral partner deals in Pipedrive](https://salesbond.app/blog/referral-partner-deals-pipedrive/), and [deals that come through a reseller](https://salesbond.app/blog/reseller-end-customer-deals-pipedrive/) are a different case again.

For four to eight people we would combine the first and the third: credit by role, with the source deciding whether a sourcing credit exists at all. It takes one sentence to explain, and both facts it depends on are in Pipedrive the day the deal is created. For a commission-only rep, that means [marking the source at creation](https://salesbond.app/blog/commission-only-reps-pipedrive-access/), before anyone can argue about it. The stage rule we’d leave to teams big enough to have someone whose job is to referee it.

No percentages here, on purpose. The ratio belongs in the commission plan, and [our piece on commission structures](https://salesbond.app/blog/sales-commission-structures-small-team/) already covers splits; this one gets the two names into the CRM so the ratio has something to apply to.

## Two fields instead of an argument

We add two custom fields to the deal, “Sourced by” and “Closed by”, and make both the User type. Pipedrive describes that type as a way to “tag a Pipedrive user from your Pipedrive account” and lists “previous or secondary deal or contact owners” among its typical uses ( [Pipedrive: What types of custom fields are there?](https://support.pipedrive.com/en/article/what-types-of-custom-fields-are-there)). Two things follow. When you hire someone, they show up in the field without anyone editing a list of names. And nobody can type “Hana (and me)” into it. The owner field stays what it is: whoever is working the deal right now.

| Field | Who fills it | When | What it settles |
| --- | --- | --- | --- |
| Sourced by (User) | whoever creates the deal | at creation; blank means “nobody”, not “unknown” | who found the opportunity |
| Closed by (User) | the owner | the day the deal is marked won | who ran the close |
| Owner | the manager on handover | changes when the work changes hands | who works it now, who sees it in their pipeline |

“Sourced by” is filled at the start, not at the end. If Hana sets it in May when she creates the deal, there is nothing to argue about on the last day of the month. If it gets set on the day of the win, the person setting it is the one with the most reason to leave it blank.

Blank has a meaning, and the rule says what it is. In ours blank means an inbound deal nobody sourced, so the closer takes it whole. Write that sentence into the rule, otherwise every blank becomes a conversation.

“Closed by” exists even though it almost always matches the owner. You need it for the exception: say a rep went on leave the week the contract came back and someone else got the signature. On a deal like that the owner and the closer are different people, and that’s exactly when the question gets asked.

![Pipedrive-style deal card: Owner Victor, User fields Sourced by Hana and Closed by Victor as user chips, plus a pinned note "Handover 14 May".](https://salesbond.app/wp-content/uploads/2026/10/shared-deal-credit-sdr-ae-pipedrive-2.png)

With the fields in place, Hana’s message gets answered by the deal itself. It says Sourced by: Hana, Closed by: Victor, Owner: Victor. The rule says what each of those is worth. All the manager does that evening is check that the fields are filled, which takes thirty seconds.

## Reports: every dollar in one column

Group won revenue by one field only, Owner. Here is the mistake we see right after teams add the second field. Someone builds a report of won revenue by “Sourced by”, another one by “Closed by”, and puts them next to each other. Hana’s column shows $18,000. Victor’s column shows $18,000. The team closed $18,000. Add the two columns and the month looks twice as good as it was and the first person to notice is usually whoever does the accounts.

We keep revenue on Owner because that is where Pipedrive puts the deal and what everyone already looks at. “Closed by” is there for the exceptions, not for a second revenue total.

“Sourced by” doesn’t produce a revenue figure at all. It produces a list. Open the deals list, filter for won deals in the period, add the “Sourced by” column, and you have the deals Hana opened that went on to close. You can total that column if you need to, but label it “sourced, later won” and keep it away from the page where team revenue lives. Two totals that share a dollar should never sit on the same screen.

## When the deal changes hands, and when the rule needs a sentence

Most credit arguments start with a handover nobody wrote down. Hana booked the meeting in May, somebody changed the owner to Victor, and the only trace is a line in teh change history that nobody reads.

Our handover is three actions in the deal, done by whoever changes the owner. Check that “Sourced by” is filled; if the person handing over created the deal, it already should be. Add the previous owner as a follower, so Hana keeps seeing the deal she opened ( [how followers work](https://salesbond.app/blog/pipedrive-followers-rep-out-of-office/)). Then use [the five-line handoff note](https://salesbond.app/blog/pipedrive-notes-mentions-pinned-handoff/), pinned, plus one line: Sourced by: Hana.

Two neighboring questions aren’t credit questions at all: a lead with no deal yet is a matter of [lead routing](https://salesbond.app/blog/lead-routing-pipedrive-small-team/), and a won deal moving to delivery is [the closed-won handoff](https://salesbond.app/blog/closed-won-handoff-pipedrive/).

The rule itself will be wrong a couple of times a quarter. That’s fine, as long as the cases get written down instead of settled in chat. We keep one line per disputed deal in the team’s notes, with the decision and the reason. At the end of the quarter the manager reads the list and asks one question: bad deal, or bad rule? Three disputes about the same kind of handover mean the rule needs a sentence added. One dispute about an odd deal means it’s fine.

One check in Pipedrive helps the the review: won deals in the quarter with “Sourced by” blank. Some are inbound, which is fine. Some are forgotten, which is a habit to fix while it’s still small. The checks that touch pay belong to the commission plan, and the [commission structures piece](https://salesbond.app/blog/sales-commission-structures-small-team/) lists them.

## Where SalesBond fits in

A deal that has just changed hands is the kind that goes quiet, because for a week each person assumes the other one is on it. We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. SalesBond’s Deal Health runs more than 20 rules over each deal in the connected CRM, grouped into Activity, Progression, Data, Ownership and Forecast, gives the deal a health score and shows what pulled the score down. The credit fields are still yours to fill and the rule is still yours to write. [Check your CRM with SalesBond](https://salesbond.app/).