# Service catalog redesign: the data question | SourceX

Canonical: https://refer.sourcex.si/guides/the-data-opportunity-question-during-a-service-catalog-redesign
Last updated: 2026-11-05

A service catalog redesign is one of the few moments when a company's leaders study their own service history on purpose: what was requested, what was delivered, and what should now be merged or dropped. That makes it a fair time to put one question to the CEO, through whoever holds the relationship: would the company like to know whether the history behind its old services could be licensed for AI training and evaluation? Ask at a scheduled review point, keep every question at the level of metadata, and let the CEO decide.

The redesign is the reason to ask, not a reason to hurry: one question, at a meeting the company already planned. Pushed harder, it turns a project about the company's customers into a pitch about the partner's reward.

## What changes when the menu changes

A catalog redesign rewrites the list of services a company offers while the tools and the team often stay put, unlike a ticketing replacement, where the system changes, or a team merger, where the people do. Years of delivered work stay filed under the old names.

Atlassian's guide to IT service catalogs describes a catalog as a broad inventory of an organization's services, reaching teams such as HR and facilities, and a service portfolio as the full record of past, present and future services, including why discontinued ones were dropped (our paraphrase of a search excerpt). A company that sells services to customers has the same split: the catalog shows today's offer, and the history sits behind names the new offer may drop.

| Redesign move | What happens to the history behind it | The metadata question it raises |
|---|---|---|
| Retire a service | Its delivery records stay in the company's systems under a name nobody sells any more | How many years of work sit behind it, and in which system? |
| Merge two services | Two histories start reporting under one new name | Will anyone still be able to tell which records came from which old service? |
| Rename a service | The same work carries a new label from the cutover date | Is there a written map from old names to new ones, and who keeps it? |
| Split a service | One history is divided between two new offers | Does the split change who inside the company owns each part? |
| Re-tier or reprice | Old work was delivered under old service levels and terms | Are the old terms kept alongside the old records? |

Whoever runs the catalog can answer each one in a sentence, with no file changing hands. A data catalog project is a different thing, describing datasets rather than services; the [data catalog and data inventory comparison](/compare/data-catalog-vs-data-inventory) covers it.

## Why the redesign meeting is a fair time to raise it

Three features of a redesign make a licensing question relevant rather than opportunistic.

- **Leaders are already looking backward.** Deciding what to retire means asking which services were requested, how often and with what result, for the company's own reasons.
- **The project has an owner and a calendar.** Review meetings led by a named person give a scheduled place for one question instead of an unsolicited call.
- **Any date is the company's date.** An archive day for old catalog entries comes from the company's plan; mention it only when the company does.

Before raising it, run a four-question timing check:

1. **Did the company tell you, or announce it?** If you heard about the redesign in confidence through paid work, check what your engagement allows before using it.
2. **Is the moment calm?** Wait if the redesign arrives with layoffs, price rises, a customer dispute or an ownership change still being settled.
3. **Is there a path to the CEO?** You, or someone you can ask, must hold a relationship the CEO would answer.
4. **Can the question travel without records?** If it only makes sense with a file attached, it is the wrong question.

Four yeses: ask. Any no: wait, or hand the question to the person who holds the relationship.

## The service-history conversation prompts

Eight prompts, in the order a redesign usually runs, asked of the catalog owner or the relationship holder in conversation, never as a cold questionnaire. Stop as soon as an answer shows the company is not a fit.

| # | Prompt | Best moment | A useful answer sounds like | Never ask for |
|---|---|---|---|---|
| 1 | Which services are leaving or changing, and how many years of delivery sit behind each? | Usage review | "Three services, records from 2012" | Usage reports or exports |
| 2 | Where was that work recorded, and will the old names stay readable after cutover? | Usage review | "Field-service system and billing; old items kept inactive" | Logins or screenshots |
| 3 | Who wrote those records: your staff, your clients or both? | Decision meeting | "Our technicians wrote the job notes; clients filled in the requests" | Sample records |
| 4 | Is there a written map from old service names to new ones, and who keeps it? | Decision meeting | "Service operations keeps a crosswalk sheet" | The sheet itself |
| 5 | Has any of this history been licensed for AI training before, or promised to another party? | Decision meeting | "No" | Copies of contracts |
| 6 | Who owns the redesign, and has the CEO heard this question? | Any point | "The COO owns it; the CEO has not heard it yet" | An introduction the CEO does not know about |
| 7 | Is there a date when old entries or codes are archived or removed? | Before cutover | "Archived at year end, per the project plan" | A deadline you invent |
| 8 | Would the CEO like a two-paragraph note on how SourceX screens companies, to decide whether to talk? | After 1 to 7 | The CEO's own yes or no | Any pressure to answer |

Prompt 3 carries the most weight. Job notes, fulfilment steps, approvals and quality reviews written by the company's own people are the kind of original documentation SourceX's screening guidance describes, while records that are really the clients' property usually fall outside it. Prompt 5 is a gate rather than a detail: SourceX asks a company to confirm its data has not been licensed for AI training before, so an earlier license ends the conversation. Prompt 8 is the only one that asks for a decision, and only the CEO can give it.

**Method note.** The prompts follow SourceX's who-qualifies screening profile and company process page, both read on 2026-10-27, and the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04). The moments follow a typical redesign sequence, not measured outcomes; SourceX has not published response or conversion rates for introductions raised at business-change moments, and this page estimates none.

## Catalog owner, internal sponsor, CEO: three names before any introduction

A redesign has more people with opinions than people with authority. Write down three names, each with the date you confirmed it.

| Role | Usually | What they can do here | What they cannot do |
|---|---|---|---|
| Catalog owner | Head of service operations, COO or service manager | Answer prompts 1 to 4 and 7 from what they know | Agree to a licensing discussion |
| Internal sponsor | Whoever will carry the question to the CEO | Explain the idea in the company's own terms | Speak for the CEO |
| CEO | The chief executive, often the owner in an owner-run company | Decide whether the company talks to SourceX, and sign for it | Hand that decision to a partner |

If the redesign follows a deal, the target's CEO decides before closing and the acquirer's after, and a parent with every subsidiary under it counts as one company for the reward cap. The prompts also feed the published fit facts, which still have to hold: 50 or more full-time employees at the company's peak, contractors excluded; several years of records the company created itself; the rights to license them; a CEO who wants the conversation; and location. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Whether the records match a current program, and whether client contracts limit reuse, SourceX settles in its own review.

## A redesign at a 240-person facilities services firm (Illustrative)

Illustrative. The firm, its numbers and its people are invented, and nothing here predicts how a review would end.

A facilities services firm with 240 full-time staff is cutting its catalog from 14 services to 9. Two inspection services become one, four services are retired, among them site surveys and staff training, repairs get a new name, and installs stay as they are. A consultant in the partner's network advises the firm on procurement and has no role in the redesign.

- **Week 1.** The COO mentions the redesign at a quarterly review. Timing check: the COO raised it, nothing else is in turmoil, the COO can reach the CEO, no record is needed. Four yeses.
- **Week 3.** At the end of a scheduled call, prompts 1 to 3: the retired services hold about eleven years of work orders and inspection reports written by the firm's own technicians, in a field-service system the firm runs, with client request forms alongside.
- **Week 4.** Prompts 4 to 7: service operations keeps the name map, nothing has been licensed for AI training, old items will be archived at year end, and the CEO has not heard the idea.
- **Week 5.** The COO raises it with the CEO, who reads the short note and says yes to a call.
- **Week 6.** The consultant, registered and signed under the Channel Partner Agreement since the spring, sends the introduction with the CEO's agreement. The firm applies itself; SourceX checks fit and rights.

Had the CEO said not now, the record would read "declined, revisit after cutover". And if, after review, the firm licensed data and SourceX paid it $250,000, the default reward would be $62,500 (Illustrative). The firm's payout would be identical with or without the consultant, because section 4 of the terms says "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation."

## Record the question, the answer and the next authorized step

One short entry per company keeps the trigger honest.

| Field | Example (Illustrative) |
|---|---|
| Trigger and where it came from | Catalog redesign, raised by the COO at the quarterly review |
| Prompts asked and who answered | Prompts 1 to 7, the COO, 17 and 24 October |
| The CEO's words | "Happy to take a call," by email, 31 October |
| Next authorized step and its owner | Introduction email, the consultant, 1 November |
| Stop or revisit trigger | If declined: after cutover |

Credit follows dated records, not clicks. Section 2 of the terms credits the earliest valid introduction of a company new to SourceX made within its 90-day attribution window, and only after the company files a verified application; an earlier link click alone does not decide it. Section 3 treats a company that already had an application, lead, account or email exchange with SourceX as a duplicate. When several people in one network know the same firm, only one introduction can be credited and SourceX settles overlaps in its duplicate review, so agree inside the network who asks before anyone does.

## Where the prompts can mislead

- **Client-written history.** In some service businesses most of the record is what clients typed. Prompt 3 can end the conversation, and that is the right result.
- **Other changes ride along.** A platform replacement moves the history question to the migration plan (see [ITSM ticket history](/data-types/itsm-ticket-history) and the [ITSM consolidation moment](/guides/moment-itsm-consolidation-servicenow-consultants)); rewritten service levels give credit history its own rulebook problem, covered in the [SLA redesign inventory](/guides/workflow-service-credit-adjudication).
- **Renamed is not lost.** Many catalogs keep retired items readable. Never imply that history disappears at cutover unless the company says so.
- **Programs move.** A company that misses one SourceX program may fit another later, so a no today carries a date, not a verdict.
- **No published outcomes.** Nobody has published how often a redesign question leads to an introduction. Count your own: prompts asked, CEOs who heard the question, CEOs who said yes. The [metadata-only opportunity map](/guides/metadata-only-referral-opportunity-map) gives a column set for logging them, and other trigger guides sit in the [guides library](/guides).

## 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.

Once the catalog owner has answered the first seven prompts and the CEO has asked to talk, [register as a partner](/register), set the company's facts beside [who qualifies](/who-qualifies), and keep the [program terms](/terms) open while you write the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://www.atlassian.com/itsm/service-request-management/service-catalog
