# Portfolio product shutdowns and data referrals | SourceX

Canonical: https://refer.sourcex.si/guides/a-product-shutdown-can-change-the-referral-conversation
Last updated: 2026-11-04

A product shutdown changes the referral conversation in three ways. Customer data in the product is returned or deleted when the service ends, under customer contracts and rules such as GDPR Article 28, so it leaves the discussion. The company's own records of building, selling and supporting the product stay and may justify a licensing review. The people who understand those records may be leaving. An operations lead's job is to spot the dated triggers, ask the CEO before the team disperses and stop if only customer data remains.

The company itself keeps operating, and that is what separates a product retirement from a wind-down: the CEO, the legal entity and most systems stay put, while one slice of history loses its owner, its users and its budget on a known date.

## What leaves, what stays and who walks out

| Part of the product | What happens at shutdown | What it means for an introduction |
|---|---|---|
| Customer data inside the product | Exported to customers, then returned or deleted under their contracts | It is not the company's to license; it leaves the conversation |
| The company's own product records: support resolutions, QA records, release notes, incident reviews, design decisions | Stay with the company unless the product line is sold with them | These match the kinds of documentation SourceX's screening page lists |
| What the product team knows | Reassigned, laid off or leaving | Without them, nobody can describe the records accurately |

For personal data, the first row is written into the processing contract itself. Article 28(3)(g) of the GDPR requires that contract to say that the processor, "at the choice of the controller, deletes or returns all the personal data to the controller after the end of the provision of services relating to processing". The Commission's standard clauses for controllers and processors spell out the same exit: delete and certify the deletion, or return the data and delete the copies. A shutdown date can therefore carry a deletion date with it, and that deletion is a duty, not an opportunity.

The second row is where the referral question lives, with one caution. Support tickets and incident notes can mix the company's own work with customers' names and details, and SourceX's screening guidance requires that licensing not breach client confidentiality, employee privacy or third-party contracts. Which parts of a ticket history are in scope is a rights review question, not something an operations lead settles.

The third row has its own dated signal in some cases. The Department of Labor's WARN Act page says covered employers, generally those with 100 or more employees, must give at least 60 calendar days' written notice of a plant closing or mass layoff affecting 50 or more employees at a single site. A product retirement may never reach that threshold. When one does, the notice date tells you when the people who know the records start leaving.

## Find the product's records and the person who still decides

A product's history rarely sits in one place: a helpdesk, an issue tracker, code review threads, a documentation wiki, CRM notes and product analytics. Product analytics describe what customers did and belong with customer data; the other systems mix customer content with the company's own work. The head of product or the support lead knows where each part lives. The CEO decides whether any of it is discussed.

Two situations move that decision. If the product line is being sold, the deal documents decide which records travel with it; the [comparison of selling product IP and licensing product records](/compare/license-data-vs-sell-ip-product-sunset) covers that trade-off. If the whole company is being acquired, the acquirer's CEO decides once the deal closes, as the [exit-stage authority map](/guides/who-can-authorize-an-introduction-after-a-portfolio-exit) traces step by step. SourceX's glossary entry on [data as a product](https://sourcex.si/glossary/data-as-a-product) describes a well-run dataset as one with documentation, versioning and a named owner; a retired product tends to lose all three at once, which is why the brief below records who knows what before they go.

## The product-retirement referral trigger brief

One page per retirement, kept by the operations lead and filled only with what the company tells you. Every entry in the last column is Illustrative.

| Field | What to write | Who supplies it | Example entry (Illustrative) |
|---|---|---|---|
| 1. Product and entity | The product, the legal entity, the CEO and since when | The CEO's office | Scheduling add-on; the operating company; CEO since 2019 |
| 2. Shutdown dates | End of sale, end of support, service off | The company's customer notice | End of sale 2026-11-30; service off 2027-02-28 |
| 3. Customer data exit | What customers get back or have deleted, and when | Customer contracts, via counsel | Exports until service off; deletion 30 days later |
| 4. Company-created records | Systems, years and rough counts; metadata only | Head of product or support lead | Helpdesk 2018 to 2026, about 41,000 tickets; issue tracker, about 3,200 bugs; release notes |
| 5. Knowledge holders | Roles, not names, and their expected last day | The CEO or HR lead | Support lead and two engineers through 2027-03-31 |
| 6. Line sale | Is the product, or any of its records, being sold? | The CEO | No buyer; retired outright |
| 7. Holds and duties | Any hold or retention duty on the product's records | Counsel | None reported |
| 8. CEO's answer | Wants a review of company records, not now, or no | The CEO | Wants a review of support and QA records |
| 9. Next check | When the brief is reread | The operations lead | 2026-12-01 |

Fields 3 and 4 do the sorting: one lists what is leaving, the other what may be discussed. Field 5 sets the real deadline, which can fall well before service off. Field 8 comes last on purpose: the CEO answers with everything else already known. The brief never holds a ticket, a sample, a customer name or a login. For the customer-facing notices themselves, the [end-of-life notice template](/resources/end-of-life-notice-template) pairs the notices with a records plan, and the [product sunset plan guide](/guides/product-sunset-plan) covers the company's own records step before shutdown.

## End-of-life dates against custody, control and the introduction (Illustrative)

Illustrative. The same scheduling add-on, read across its milestones. Custody is where records sit, control is who decides, and the introduction is a separate choice the CEO may never make.

| Milestone | Customer data | Company records | Who decides | Introduction move |
|---|---|---|---|---|
| Board approves the retirement | In the product, held for customers | In company systems | The CEO | The operations lead opens the brief |
| Customer notice sent | Export window opens | Unchanged | The CEO | Ask the CEO fields 6 to 8 |
| End of sale | Unchanged | New tickets slow | The CEO | If the CEO wants a review, the relationship holder shares a partner link |
| Team reassignments begin | Unchanged | Knowledge thins | The CEO | The company applies while people can still describe the records |
| Service off | Returned or deleted under contract | Archived, if the company keeps them | The CEO | Continues for company records only |
| Infrastructure decommissioned | Gone | Archive only, or gone | The CEO | Closed unless an archive was kept |

Control never moves in this example, because the company is not being sold. Custody of customer data ends on schedule whatever happens to the introduction. For an internal system switch-off rather than a customer-facing product, the [system retirement timeline](/guides/the-referral-window-before-a-portfolio-company-retires-a-system) covers the cutover milestones instead.

In this Illustrative case, a 260-person HR software company retires the add-on after seven years. The CEO asks for a SourceX look at the support and QA records, and ticket text that carries customer details goes through rights and privacy review before anything is scoped. Nobody knows yet whether a license follows. If one did and produced an Actual Supplier Payout of USD 40,000, it would fall below the USD 100,000 Minimum Transaction and pay no reward unless SourceX agreed in writing; at USD 400,000 the partner's default reward on a first qualifying transaction would be USD 70,000. Both figures are Illustrative arithmetic from the published terms, not a forecast, and any payment waits for the Acquisition Partner's final written acceptance, completed handoff and the other conditions in the terms.

## Choose the window while the people are still there, or stop

The window opens when the shutdown is dated and closes when the knowledge holders leave or the systems go dark, whichever comes first. Those dates come from the company's notices, which makes them the only urgency worth citing.

Stop, and note why in field 8 or 9, when:

- the CEO declines, or prefers not to raise anything while customers are being told;
- once customer data is removed, nothing of the company's own remains;
- the product line is sold with its records, so the buyer's side now decides;
- a hold or retention duty covers the records in question;
- the company enters a formal process, where the CEO alone may not be enough.

Once the CEO agrees, the person submitting needs a signed SourceX Channel Partner Agreement, and the fund should decide internally who is partner of record before anyone writes. On attribution, section 2 is explicit: "The first valid introduction of a new company within the 90-day attribution window receives credit when that company submits a verified application." The portfolio side of the program is covered for [venture platform teams](/for/venture-platform-teams).

## Where a shutdown makes the conversation worse

- **Customer trust.** Customers hearing about licensing during a retirement may read it badly, even when only internal records are in scope. Timing is the CEO's call.
- **Rights.** Ticket histories mix company work with customer content, and client-owned material is usually not a fit, so the reviewable slice can be thinner than it looks.
- **Demand.** SourceX checks relevance to current data needs in review, and a retired product's records may not match any program.
- **People under strain.** A team facing reassignment or layoffs has little spare attention, and asking them to describe records spends goodwill.
- **A later buyer.** If someone may still buy the product line, a license of its records could complicate that sale; the deal documents need to say who keeps what.

**Methods note.** The trigger brief's fields come from SourceX's published screening guidance and terms, checked 2026-10-27, together with the GDPR's processor clause, the Commission's standard clauses and the Department of Labor's WARN page as examples of dated duties around a shutdown. Not measured: how often retired products lead to an introduction, how many CEOs opt in or what any review produces. SourceX has not published those figures.

## 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 the brief shows company-created records, knowledge holders still in place and a CEO who wants a look, [register as a partner](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before the relationship holder shares a link. For wind-downs, exits and other moments when records change hands, browse the [guides hub](/guides).

Tracking a product retirement is referral work, and evaluating SourceX as a business is a separate decision; investor materials for that are available on request from the [SourceX investor overview](https://sourcex.si/investors).

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.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng
- https://eur-lex.europa.eu/eli/dec_impl/2021/915/oj
- https://www.dol.gov/general/topic/termination/plantclosings
- https://sourcex.si/investors
