The operational history behind a fast-growing support team: an eight-field worksheet that dates the tickets, playbooks and QA trail before anyone calls it a data opportunity

Short answer

A support team that doubled tells you tickets are piling up; it does not tell you how many years of resolved work the company holds, in which system, or who owns it. Treat the hiring as a prompt to date the support history: when the helpdesk started, which migrations broke the trail, whether playbooks and QA reviews exist, and whether employees or an outsourcer do the work. Introduce the company only when that history, the rights and a willing CEO line up.

Visual briefFull-size diagram
Split panel: on the left, an Illustrative support team grows from 6 to 22 people while another stays near 40; on the right, the growing team's support history spans two years with an unopened export, and the flat team's spans 2012 to 2026 with QA reviews since 2016.
Illustrative. Two invented support teams scored with the worksheet on this page; the signal and the history point in opposite directions.

Growth is a discovery signal, not proof of fit or of dataset value. The deepest support record in a network often belongs to a team that has not hired anyone in years.

What the support-growth signal measures, and where it comes from

Support growth reaches a research lead in several forms. Write down the definition and the date of each before it goes on a list.

SignalUsual sourceDefinition to recordCommon trap
Open support rolesCareers page, dated job postsNumber of roles, date posted, tier or levelReposted ads and roles never filled
Support headcountBoard materials for portfolio companies, or the company itselfFull-time support employees on a stated dateContractors and outsourced agents counted in
New support channelsCompany announcement, help centerChannel added and launch dateA new channel has no history yet
First head of supportAnnouncement or hiring postRole and start dateOften arrives with a brand-new system

Nationally, the trend runs the other way. The Bureau of Labor Statistics' Occupational Outlook Handbook projects employment of customer service representatives to decline by about 5 percent over its ten-year projection period and links the decline to automation. A support team growing against that trend may reflect a product launch, a move in-house or a complicated product. A flat or shrinking team may still hold the longest record. Neither fact says what the record contains. Market-level questions sit with the AI data market growth forecast; this page stays on the company in front of you.

The support-history discovery worksheet

Eight fields, all metadata: what exists, how much, since when, in which system and who runs it. Nobody asks for tickets, exports or logins.

FieldQuestion to askStronger answerWeaker answerWhy it matters
1. Helpdesk startWhen did the current support system go live?2014, one system since2024, "we just switched"Usable history starts here
2. MigrationsHow many platform changes, and were older tickets carried over or archived?One migration, full archive kept and readableOld tickets left in a lapsed vendor accountA broken trail shortens the history
3. Retention settingsIs any automatic deletion or retention rule switched on?Reviewed yearly; nothing deleted without a decisionA deletion schedule nobody remembers settingDeletion is a dated event
4. Volume and spanRoughly how many tickets are resolved a year, across how many years?Tens of thousands a year over a decadeA few thousand since last yearScale and span, never exact counts
5. Resolution depthAre internal notes, escalations, macros, knowledge articles and QA scorecards kept?Internal notes on most tickets; monthly QA since 2016One-line replies; no QAThese artifacts carry the reasoning
6. Staffing modelEmployees, outsourced agents or contractors?In-house full-time teamA vendor's agents working in the vendor's systemHeadcount and record location both depend on it
7. Customer contentHow much of each ticket is customer-supplied material or personal data?Mostly the company's own troubleshooting and decisionsTicket bodies are customer documentsRights and redaction depend on it
8. OwnersWho administers the system, and who is the CEO?A named administrator; a CEO reachable through a relationship ownerNobody knows who holds the admin loginThe support lead describes; the CEO decides

Field 3 is easy to skip and expensive to miss. Some helpdesks can delete old tickets on a schedule. Zendesk's documentation, for example, describes deletion schedules that automatically delete archived tickets once they meet conditions an administrator sets. A schedule about to remove years of history is a real, dated reason to raise the conversation now; a quarter-end is not.

Field 5 maps to the published screening. SourceX's screening page lists support workflows, QA records, internal knowledge bases and SOPs among the original documentation it looks for. The customer support workflows page and the QA-scored interactions page describe what those records look like.

Field 6 decides two things at once. Contractors and outsourced agents do not count toward the 50 full-time employees at peak, and tickets handled by a vendor may live in the vendor's system under the vendor's contract.

A doubling team and a flat one, side by side (Illustrative)

Illustrative. Two generic companies with invented facts; no outcomes implied.

The doubling team belongs to a 140-person B2B software company. Support grew from 6 to 22 people in eighteen months after a product launch. The current helpdesk went live in 2024; tickets from the old tool were exported then and never opened. Tier-1 work is partly outsourced, and QA reviews started this year.

The flat team belongs to a 380-person utility billing services company. Its support team has stayed near 40 for a decade. The same helpdesk has run since 2012, with one migration in 2019 that kept the archive, monthly QA scorecards since 2016 and a library of about 600 macros, all maintained in-house.

FieldDoubling teamFlat team
1. Helpdesk start20242012
2. MigrationsOne, in 2024; old export unopenedOne, in 2019; archive kept
3. Retention settingsUnknownReviewed yearly; no automatic deletion
4. Volume and spanRising fast, two yearsSteady, fourteen years
5. Resolution depthShort replies; QA started this yearInternal notes; QA monthly since 2016; about 600 macros
6. Staffing modelTier 1 partly outsourcedAll in-house
7. Customer contentMostly customer configuration filesMostly billing explanations written by staff
8. OwnersNew head of support; CEO is a portfolio founderLong-serving administrator; CEO reachable through an LP
ReadingRevisit once the 2024 export is checkedFirst conversation

The hiring signal pointed at the doubling team. The worksheet points at the flat one. The worksheet also records what would change the reading: if the unopened 2024 export holds years of readable tickets, the doubling team moves up. And the flat team's tickets still name customers, so how they would be de-identified, and whether the company's contracts allow reuse, stay open for the company's counsel and SourceX's review; the guide to anonymizing support tickets explains the work involved.

Does the hiring reveal history, or only volume?

New hires answer new tickets. Whether those tickets add to an operating history depends on what gets written down:

  • Escalation trail. Tier-2 tickets with internal notes show how a problem was diagnosed and decided; password resets do not.
  • Playbook age. A macro library and knowledge base built over years encode a company's decisions; one written last quarter mostly encodes the launch.
  • QA trail. Graded reviews kept over years show what good work looked like and how it changed.
  • Continuity. A history that survived a migration intact is worth more than two short histories in two systems.

A system change can also be the moment to talk. The helpdesk migration guide covers that dated event.

Rank support-led conversations with ownership and capacity in view

SourceX has not published conversion rates or typical payouts, so rank on what you can observe:

  1. History you can date. Fields 1 and 2 give the span; longer and unbroken ranks higher.
  2. Rights and staffing. Records the company's own employees wrote, in its own system, rank above vendor-held or customer-supplied material.
  3. A path to the CEO. The support lead can describe the system; the CEO authorizes a licensing discussion and signs for the company. Rank rows with a relationship owner who has agreed to ask.
  4. A dated event. A scheduled migration or an active deletion schedule.
  5. Capacity. A team in a hiring surge is busy onboarding, and the administrator who must describe the system may have no time; set a revisit date instead of pressing. On your own side, cap how many open asks each relationship owner carries.

When the support work is outsourced, the vendor can be a candidate in its own right, as the page for outsourced support providers explains. Tickets it handles for clients usually belong to those clients, though, and SourceX's screening treats client-owned material as usually not a fit; the vendor's own SOPs and QA methods are a different matter.

Where a support signal misleads

  • Automation. If BLS's projected decline plays out, teams shrink while their archives stay. The hiring signal disappears exactly where the history is deepest.
  • Outsourcing. Headcount excludes contractors, and the records may sit with the vendor.
  • Customer content. Tickets carry customer material and personal data; rights review and redaction can narrow what is licensable.
  • Deletion. Retention rules can remove history quietly, before anyone in your network notices.
  • Demand. SourceX applies each program's own criteria and checks relevance to current needs in review. A strong row can still be declined today, and the same company may suit a different program later on.

Methods note. The worksheet records eight metadata fields about a company's support history and sorts conversations by datable span, rights, path to the CEO, dated events and capacity. It was built from SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04) and screening page, with BLS for the national employment trend and Zendesk's documentation for one example of retention settings, all checked 2026-10-26. It does not measure ticket quality, demand for any company's records, price or payout, which only SourceX's review assesses.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When a worksheet row shows a long, unbroken support history the company owns and a relationship owner ready to ask the CEO, register for a partner link, compare the row with who qualifies and read the program terms before the first message goes out.

Dating a portfolio company's support history is referral work; evaluating SourceX as a possible investment is a separate task, and anyone taking it on can ask for investor materials through the SourceX investor overview.

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is a fast-growing support team a good reason to introduce a company?

It is a good reason to ask questions. Hiring shows ticket volume rising; the screening looks for years of records the company created and owns, at 50 or more full-time employees at peak, with a CEO who wants the conversation. Date the support history first.

What if the company's support is outsourced?

Outsourced agents and contractors do not count toward the 50 full-time employees, and the tickets may sit in the vendor's system under the vendor's contract. Ask where the records live and who owns them before anything else.

Should a platform lead ask to see sample tickets?

No. Partners stay at metadata level: system, start year, migrations, rough volume, which artifacts exist and who administers them. Any look at records happens inside SourceX's review, under the company's control.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. bls.gov/ooh/office-and-administrative-support/custom…
  4. support.zendesk.com/hc/en-us/articles/6388012977306-Creating-tic…
  5. sourcex.si/investors

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment