The TycoonX Special Sourcing Desk: A Structured Service for Off-Catalogue Specifications

Definition

The Special Sourcing Desk is a structured service for off-catalogue project specifications, the requirements that do not fit cleanly into the standard product set of any one of the nine TycoonX product divisions. It sits alongside the nine division surfaces as a single, defined intake point for items that fall outside the standard division product set.

The Desk is a service inside the TycoonX project supply platform. It is a defined project-supply service rather than a generic sourcing inbox, marketplace, buying office, procurement agency, catalogue lookup, or we-can-supply-anything operation. It is a defined service with a defined intake, a defined working flow, and a defined response discipline. The structured-service character is the load-bearing fact: the Desk is structurally distinct from a freeform sourcing message thread, and that distinction is what makes the service operationally useful to consultants, contractors, developers, hospitality teams, and procurement teams.

The Desk's product universe is deliberately defined. Its scope is off-catalogue items adjacent to the platform's nine divisions and the Saudi project-supply context. The Desk handles cases that intersect the platform, items that map to one of the nine divisions but fall outside its standard product set, items that straddle two or more divisions, equivalent-product cases against a consultant specification, and structured fabrication-or-engineering proposals where no off-the-shelf product fits. Cases entirely outside that scope are routed outside the Desk's service frame.

Why off-catalogue cases need a dedicated structured service

Generic sourcing fails when specifications are undefined or incomplete. A vague RFQ, we need something like X, in this size, by this date, produces inconsistent supplier responses because each supplier answers a slightly different question. The replies arrive on different bases (price-only, price-plus-lead-time, sample-included, sample-excluded, documentation-included, documentation-excluded), and the project team is left comparing items that are not comparable.

Unstructured sourcing also tends to miss the project-side discipline that giga-project programmes require. Performance constraints get under-specified at intake; sample discipline gets handled informally; supplier documentation arrives partial; the project's approval workflow is treated as a downstream problem rather than an upstream input. The result is a case that looks like it is moving forward but cannot actually close because the inputs were not assembled cleanly at the start.

The Desk is a service inside the project supply platform definition, the same operating logic that runs the platform applies to the Desk. The Desk is the platform's structured route for off-catalogue work, operating inside the same project-supply logic.

The five stages

A sourcing case at the Desk is structured through five stages. The stages are sequential, each stage produces the input for the next, and each stage carries its own boundary discipline.

Intake

Intake is the controlled capture of the case. Through the Contact route, the useful inputs include: specification text, drawings if available, project context, target programme, performance constraints, budget if available, delivery location, quantity, required documentation set, and the project's approval pathway. The fuller and tighter the intake input, the cleaner the case progresses through the next four stages.

Boundary discipline:

• Intake is a review step. Submitting a case starts assessment before the Desk confirms whether it can take the case on as a sourcing engagement.
• The Contact-route submission is followed by the Desk's case-level acknowledgment under the response standard.

Sourcing brief

Sourcing brief is the conversion step. TycoonX converts the intake input into a structured sourcing brief, a routable document that translates the consultant or contractor specification into terms manufacturers, suppliers, and fabricators can respond to consistently.

The brief reduces ambiguity for the supplier side: it states what is being asked for, on what basis, with what supporting documentation requirement, and against what target programme. The brief is the input that lets the case route to the right manufacturer, supplier, fabricator, or production-network set inside the platform's qualified relationships.

Boundary discipline:

• The sourcing brief supports the consultant's specification responsibility. The consultant's specification remains the authoritative project document; the brief is a routing-and-clarification layer that supports it.
• Building a brief is a routing and clarification step before project approval, supplier endorsement, or supply commitment can be considered.

Qualification

Boundary discipline:

• Qualification is separate from project approval. The project's own approval workflow, consultant submission, comment cycles, approval-in-principle, and formal approval routes remain under the project owner, consultant, and main contractor.
• Supplier documentation remains supplier-source documentation. TycoonX coordinates supplier documentation while the supplier-source certificates, test reports, and material certificates remain with the issuing source.

Sample

Sample is the technical-validation step where a sample is required to support the case before supply commitment. Samples are case-specific: sample requirements vary by case, and sample availability, timing, and cost vary case-to-case. Where samples are required, the Desk manages the sample workflow against the project's programme.

Boundary discipline:

• A successful sample review remains separate from project approval; the project's own approval workflow remains the authoritative route.

Supply

Supply is the transition step. After qualification and sampling where applicable, the selected item moves into project supply discipline, quotation, production coordination, supplier documentation, logistics and delivery where included in scope, and Saudi-side handover against the agreed project scope. From this point forward the case is running on the platform's standard project-supply discipline; it is operating on the platform's standard project-supply discipline.

Boundary discipline:

Operational response standard

The five stages above describe how a case is structured through the Desk. Sitting alongside the five stages is the Desk's operational response standard, how the Desk communicates with the case-submitter and what the case-level outcome shape looks like:

• Acknowledgment within two business days. Case officer assignment within two business days.
• Response within four to five business days with one of three defined outcomes:
  1. Sourced product route, a specification-matched product is identified and a sourcing-and-delivery basis is structured.
  2. Fabrication or engineering proposal route, where no off-the-shelf product fits, a partner-backed fabrication or engineering proposal is structured against the brief.
  3. Alternative recommendation route, where neither of the first two outcomes is viable, a commercially honest alternative is documented for the project team.

How the Desk relates to the nine divisions

The platform's standard product-family surfaces are the nine outdoor and architectural divisions. The Desk is the off-catalogue companion to that divisional product set, the structured route for items that do not fit cleanly inside any one division's standard scope. The boundary between division route and Desk route is operational, not arbitrary: items that fall inside a division's standard scope are routed through that division; items that do not are routed through the Special Sourcing Desk.

The Desk is what allows the division pages to remain coherent product-family surfaces rather than expanding into open-ended catalogues of unusual one-off items. Each division carries its standard scope; the Desk carries the off-catalogue work.

The examples above are deliberately generic. Project-owner-named sourcing examples are not used on this page. Project supply references are published on the dedicated project pages, not in cornerstone explanatory content.

Scope, responsibilities, and boundaries

The Desk works because its scope and responsibilities are clear. The sections below set them out in plain terms.

Service scope

The Desk is a structured sourcing service inside the TycoonX project supply platform. It operates as a structured sourcing service inside the TycoonX project supply platform, with a project specification as input rather than a product-browsing or buying-agent model. Its input is a project specification, not a product code, and it operates inside the project-supply commercial chain.

What the Desk handles

The Desk handles off-catalogue items adjacent to the platform's nine divisions and the Saudi project-supply context: items that map to a division but fall outside its standard set, items that straddle divisions, equivalent-product cases against a consultant specification, and structured fabrication-or-engineering proposals. Cases are processed through the five-stage flow against a defined input set, not through freeform chat or unstructured back-and-forth messaging.

What remains outside the Desk

• A guaranteed sourcing outcome, the three-outcome response standard explicitly includes the alternative recommendation route, so some cases end in a practical alternative recommendation rather than a sourced product.
• Guaranteed pricing, pricing is case-specific and subject to manufacturer and supplier quotation.

Approval and compliance responsibilities

• Project approval remains project-led, the project's own approval workflow stays with the project owner, consultant, and main contractor.
• The Desk issues no certifications, approvals, or compliance designations.
• Consultant, contractor, specialist-manufacturer, testing-lab, and authority responsibilities each remain with those parties.
• Authority and program participation is handled through the relevant application and review processes; no licence, endorsement, or registration is implied.

These boundaries are how the Desk operates in public, its commercial usefulness rests on running honestly within them.