The Reseller-of-Record Trace: Target Account to a Graded Partner Route

Run this trace on a named target account before you commit a sequence to it. It finds the reseller, VAR, or managed service provider that holds the account's purchasing in your product category. It is for founders selling their own product, account executives, SDR leads, and partnerships teams. In under 45 minutes per account you get a named partner, a grade on that finding with the dated evidence behind it, and one of three routes: go direct, register through the partner, or co-sell.

Why trace the partner before the first touch?

On most accounts the purchase closes on a partner's paper. The partner holding that paper decides whether your first touch turns into a deal or a channel conflict. If you know who it is up front, you know whom to call, whose registration you might trip over, and whose contract the deal will be signed on.

The base rate is high. Channel analysts at Canalys, now part of Omdia, put the share of customer spending on technology, IT services and telecom services that flows through partners at 73%, then 71%, then a forecast 70% over three consecutive years. Omdia's later outlook has partners' share of the total addressable IT market falling to 66.7%. The share is slipping, but it is still about two dollars in every three.

It moves with category and region:

• Cybersecurity: more than 90% of a projected $281 billion in spend is expected to involve partners.
• Latin America: the highest partner-delivered share, at 78.1%.
• EMEA: 72.2%.
• Customer size, and public versus private sector: no named analyst has published how the share varies. Do not assume large enterprises buy direct. Trace them like any other account.

Terms used in this guide

• Paper: the contract and purchase order a deal closes on. The party that issues the paper is the party the buyer pays.
• Reseller of record: the partner on the paper for a given purchase, in a given category, at a given date.
• VAR (value-added reseller): a reseller that bundles its own services, such as integration or support, with the products it sells.
• MSP (managed service provider): a firm that runs part of a customer's IT under an ongoing contract and often buys licences on its own paper for that customer.
• Deal registration: a partner's timestamped claim on a specific opportunity, which protects that claim for a fixed window.
• Co-sell: the vendor's rep and the partner work the account together, and the deal closes on the partner's paper.
• Cooperative contract: a contract competed once, which a whole pool of public buyers can then buy through, often only via named authorized resellers.

A finished trace has five parts:

1. One named partner.
2. A grade.
3. The dated evidence behind the grade.
4. An estimated renewal month.
5. A route agreed with whoever settles channel conflict on your side.

Where does evidence of a reseller relationship live?

There are four places to look, strongest first: your own CRM and partner portal, public award records, vendor contract and locator pages, and provider artifacts such as case studies, press releases and staff profiles. Public-sector accounts can often be traced to a documented finding. Private-sector accounts usually stop at corroborated, because there is no public register of who buys through whom.

Public sector: the reseller gets its own column

The cleanest source I know of is the Texas Department of Information Resources (DIR) cooperative contracts dataset. It is an open list of all current active contracts awarded to vendors through DIR's Cooperative Contract program. Its 16 columns keep the two roles apart: Primary_Vendor_Name holds the prime vendor, and Reseller_Vendor_Name (API field reseller_name) holds the authorized reseller on the contract. Contract_Start_Date and Contract_Termination_Date date the relationship.

Vendor pages for the same contracts show how purchases are routed. Cisco's page for DIR-CPO-5347 lists its authorized resellers and states: "Cisco Systems, Inc. ("Cisco") requires Purchase Orders to be processed through our Authorized Resellers." When a manufacturer says that, there is no direct route to that buyer pool for that product, and your only real choices are register through or co-sell.

Other public registers carry less:

• EU eForms award notices record winners and subcontractors through Organisation Role (BT-08) and Subcontractor ID Reference (OPT-301), but they have no manufacturer field. You learn who won, not whose product they supplied.
• US FPDS and USAspending name the awardee. I have not confirmed a separate manufacturer field in FPDS, so treat that as unverified. The EFF warns that "the vendor brand name we know from their marketing or news media is not the same entity that is awarded government contracts", so search by legal entity names as well as brand names.

Nobody has published how often the reseller field is filled in any of these datasets. Before you rely on one, pull twenty rows for your category and count the blanks. That tells you how much a miss in your search actually means.

Private sector: dated artifacts, nothing more

For a private company, the trace depends on what providers publish about themselves: named-client case studies, joint press releases, and profiles of account managers that name the client accounts they cover. Nobody has published what share of MSP or VAR case studies name the client rather than anonymising it. I have not tested how reliable staff profiles and job postings are as evidence. Treat each one as a single artifact with a date, never as proof on its own.

The reseller-of-record trace, step by step

The trace is seven steps and takes about 45 minutes, starting inside your own house. The time split is mine because no source documents step timings, so adjust it after your first ten accounts.

Notes on the steps:

• Why your own house comes first. Registration timestamps decide conflicts. The most expensive mistake is finding a convincing partner on the open web and then learning a different partner registered the deal last month. Sources disagree on this: rules-of-engagement guides start with registration evidence, while procurement guides start with award notices. I start with registrations because they can end the trace in five minutes.
• Step 2 only applies where there is a public buyer. For a private company, skip to step 3 with your best candidate partners and spend the ten minutes you saved on step 4.
• Step 4 is where profile search earns its time. Doing this by hand means guessing provider names and paging through results to find an account manager at the provider whose profile names the account. Refolk takes a plain-English description of the people you want and returns them from LinkedIn, GitHub and the open web. You can then check who, at which provider, says they cover the account.

Keep one record per account. The format below doubles as the evidence pack a channel manager asks for when settling a conflict.

Account:
Product category:
Own-house check (date searched): registrations found, with timestamps / none
My open opportunity created on:
Candidate partner:
Partner industry confirmed (services page checked): yes / no
Evidence 1: source | what it shows | date
Evidence 2: source | what it shows | date
Award category matches my product: yes / no / not applicable
Contract termination or registration expiry date:
Contract type and estimated renewal month:
Term transferable between partners: yes / no / unknown
Grade: documented / corroborated / inferred
Route: go direct / register through / co-sell
Channel manager consulted (name, date):
Re-check on:

How do you grade a reseller-of-record finding?

Give every finding one of three grades, documented, corroborated, or inferred, based on the strongest evidence you hold, and write the date of that evidence next to the grade. The grade tells your channel manager how much weight the finding can bear. It also tells you how hard to lean on it in your first message.

What each grade proves, and how it lies:

• Documented. Evidence: an award record naming the partner for your category, or a registration in a portal you can see. Proves: the partner held paper or a claim on that date. Lies when: the award covers a different category (hardware rather than software, for example), or the contract has passed its termination date.
• Corroborated. Evidence: two independent, dated artifacts pointing at the same partner, such as a named-client case study plus a current staff profile at that partner that names the account. Proves: a relationship existed recently. Lies when: both artifacts come from the same original announcement, or both predate a partner change.
• Inferred. Evidence: one artifact, an authorized-reseller listing with no purchase behind it, or an assumption based on contract type. Proves: the partner is plausible. Treat it as a hypothesis to test in discovery, not a fact to build a route on.

Choosing the route: go direct, register through, or co-sell

Pick the route from two inputs: whether you hold a prior, timestamped claim on the account, and how well the partner's hold on it is documented. Then take the decision and the evidence to your channel manager before the first touch, because a partner registration you cannot see overrides everything else.

The conflict hierarchy

The published conflict procedures I found are all vendor-neutral guides. I found no vendor's own channel-manager playbook. The documented hierarchy is:

1. Registered beats unregistered.
2. Incumbent beats net-new.
3. Certification status breaks ties.

One partner-management model adds that a direct rep keeps an account a partner has registered only if the rep has an open CRM opportunity created before the registration. The only vendor policy I found, from a small vendor, goes further: "The manufacturer's direct team will refer any inquiry from a registered account to that partner." Dell's terms make a deal ineligible if it is "already registered to another Partner excepted where multi-registration is permitted."

To settle a dispute, a channel manager asks for four kinds of evidence:

• Registration timestamps.
• CRM opportunity creation dates.
• Activity history.
• Any emails from the buyer.

One published policy template sets a 48-hour decision deadline and another sets three business days. If your trace record already holds this evidence, the ruling arrives inside that window instead of after your sequence has started.

Registration windows

Registrations expire, so a registration you find today may lapse before you engage. Check the vendor's current terms, because windows differ by program and change over time.

Two practical reads from this table. First, a Dell registration that has not reached the 30% opportunity stage lapses at 90 days from Dell's notification. Second, incumbents are set up to keep renewals: under the legacy RSA program, the incumbent registered renewals within 90 days of expiry and could request a single 180-day extension, 45 days before expiry.

Category changes the default

In security, more than 90% of spend involves partners, against 66.7% for IT as a whole. Finding the security buyer before the partner does is not a good enough reason to go direct on a security account. Default to register-through or co-sell unless your own timestamped claim predates the partner's.

Who settles the conflict

The person who rules on conflicts is usually a vendor-side channel or partner account manager. How many of those people exist varies sharply by market.

In the US, Channel Account Manager is the more common title: 67.9% of the 2,262 combined profiles, against 32.1% for Partner Account Manager. KnowBe4 was the most common employer in both 25-profile samples, with 3 in the US and 4 in the UK. Samples that small say nothing about market share. They only suggest that security vendors run visible channel teams, which fits the category's partner-heavy spend. If you are a founder with no channel team, you are the one settling the conflict. Apply the hierarchy to yourself honestly, because the partner will apply it to you.

When does the account open up? Reading the renewal clock

Accounts open up at renewal, and you can usually estimate the renewal date from the contract type. Estimate the month before the first touch. A partner-switch pitch made in the wrong month, or against a term that cannot transfer, goes nowhere.

Terms to know, using Microsoft as the worked example because its terms are well documented:

• Microsoft EA (Enterprise Agreement): a fixed 3-year term.
• Microsoft CSP (Cloud Solution Provider): monthly, annual or 3-year subscriptions, held on a partner's paper. 3-year Microsoft 365 E3 and E5 terms are available in CSP.
• CSP in an extended service term: cannot be transferred from one partner to another at all.
• Legacy RSA renewals: the incumbent registered within 90 days of the expiry date.

Microsoft ended EA renewal eligibility for organisations with roughly 2,400 or fewer users and moved them to CSP or MCA-E. My read, which is inferred rather than sourced: midmarket Microsoft accounts below that size probably gained a new partner of record at their first renewal after the cutoff. For those accounts, a case study naming an earlier EA partner is weaker evidence than it would be for a larger account. Check the current threshold on Microsoft's licensing pages before you rely on it.

The timing rule is also inferred, not sourced. Approach before the term ends, early enough that you are in conversation before the incumbent's renewal-registration window opens. Once the incumbent has registered the renewal, the hierarchy favours them twice: registered, and incumbent.

How the reseller-of-record trace goes wrong

Most failed traces don't name the wrong partner outright. They name a real partner with the wrong scope, the wrong date, or the wrong kind of evidence. Each failure below says what it looks like and the check that catches it.

1. Acronym collision. "MSP" matches non-IT firms. In Refolk's index, a US search for account managers with "MSP managed services" in the headline returned only 16 profiles, and 2 were at "MSP (Mailing Services of Pittsburgh)". What it looks like: a candidate partner with no IT services anywhere on its site. Check: confirm the company's industry and read its services page before the name goes on the trace record.
2. The awardee is not the reseller of record for your category. An award can cover hardware and not software, or one product line and not yours. What it looks like: a documented-looking award for the right vendor and the wrong scope. Check: match the award's category codes to your product.
3. A contract listing is not a purchase. Being an authorized reseller on a DIR contract shows the partner can sell to the buyer pool, not that this account ever bought through them. What it looks like: a confident "documented" grade resting on a locator page. Check: grade it inferred unless you hold an award or purchase order record.
4. Stale contract. Contracts expire. Microsoft's Texas DIR contract DIR-CPO-4471 expired and was not renewed. What it looks like: a reseller relationship pinned to a contract that no longer exists. Check: read Contract_Termination_Date on every award you cite.
5. Old case study. A named-client case study may predate a change of partner. What it looks like: a polished success story several renewal cycles old. Check: find the publication date, then corroborate with a current artifact such as a staff profile.
6. Unseen registration. Another partner may hold a registration in a program you cannot see. What it looks like: a clean trace, then a channel-conflict email a week into the sequence. Check: ask your channel manager before the first touch, every time.
7. Transfer blocked. A CSP subscription in an extended service term cannot move between partners, so a "switch your partner" pitch fails whatever its merits. Check: confirm the term status before building the pitch around a switch.

Brand mismatch is the federal version of failure 1. The entity on a federal award may carry a different legal name from the brand you searched for, so a miss in USAspending is not evidence of absence until you have searched the legal entity names too.

Before the first touch, and keeping the trace current

The trace is done when every item below is true and the channel manager has seen the record. It stays current only if you re-run it when one of its dates passes.

Re-run the trace when any of these happens:

• A registration on the account reaches the end of its window, for example 90 days for Dell.
• The award's Contract_Termination_Date passes.
• The estimated renewal month approaches the incumbent's renewal-registration window.
• A new case study, press release or staff move names the account.

Staff moves are easy to miss because nothing alerts you. A saved plain-English search in Refolk for the partner's account managers covering the account's sector lets you see when the person who corroborated your finding has moved on.

Send this before the first touch, with the trace record attached.

Subject: Pre-touch check: {Account}, {category}

Hi {Name},

Before I open {Account}, can you confirm whether any partner holds a registration on it for {category}, including in programs I can't see?

What I found:
- Candidate partner: {Partner}, graded {documented / corroborated / inferred}
- Evidence: {source}, dated {date}; {source}, dated {date}
- My own claim: {open opportunity created on date / none}
- Estimated renewal: {month}; term transferable: {yes / no / unknown}

Proposed route: {go direct / register through {Partner} / co-sell with {Partner}}.

If there is a conflict, I'd like a ruling in the usual order: registered beats unregistered, incumbent beats net-new, certification breaks ties. I'm holding the first touch until I hear back.

Thanks,
{Your name}