> ## Documentation Index
> Fetch the complete documentation index at: https://www.scrums.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Talent Primitive

> The Talent primitive: individual experts, dedicated teams, and the CXO network — one vetting, contracting and matching model behind three shapes.

## Overview

Talent is one of the four catalog primitives. It covers every way Scrums.com supplies people to your delivery.

The primitive has **three shapes**. They share one vetting, contracting, onboarding and matching model. They differ in what unit you receive and who manages it day to day.

| Shape                                                     | You receive                                  | Day-to-day management                       |
| --------------------------------------------------------- | -------------------------------------------- | ------------------------------------------- |
| [Individual Experts](/docs/products/talent/individual-experts) | One or more engineers, embedded in your team | You                                         |
| [Dedicated Teams](/docs/products/talent/dedicated-teams)       | A complete delivery team                     | Scrums.com, with you setting direction      |
| CXO Network                                               | Senior technology leadership                 | Shared — advisory alongside your leadership |

**Billing Model:** Subscription / Hourly / Seat / Block<br />**Delivery Model:** Scrums-managed / Client-managed

<Note>
  Projects are invoiced on the **1st of every month**. Hourly engagements include a quarterly reconciliation — unused billed hours are credited and any shortfall is invoiced. See [Billing & Usage](/docs/administration/billing) for full terms.
</Note>

## Choosing a shape

Ask what the gap is.

* **Capacity or a specific skill** on a team that already works → Individual Experts.
* **A whole unit of delivery** you do not want to build or run → Dedicated Teams.
* **Direction, governance or technical leadership** → CXO Network.

<Note>
  CXO Network is not yet documented here. Speak to your Enablement Partner, or see [Support & Contact](/docs/resources/support).
</Note>

Shapes combine. A dedicated team and a fractional CTO is a common pairing.

## How Matching Works

When you request a team member or team, SEOP's AI-assisted matching system evaluates candidates against:

* **Technical requirements** — Stack, seniority, specialisation (e.g. React, Python, AWS, Kubernetes)
* **Timezone compatibility** — Overlap with your core team's working hours
* **Delivery model fit** — Experience with your preferred methodology (Scrum, Kanban, SAFe)
* **Industry context** — Familiarity with regulated sectors (FinTech, Banking, Healthcare) where relevant

A curated shortlist is delivered to your Enablement Partner within 48 hours for client review and confirmation.

## Scaling Teams

Teams can be scaled up or down on a monthly basis. Common scaling scenarios include:

* Adding a specialist role (e.g. DevOps Engineer) for a migration sprint
* Increasing engineering headcount ahead of a major release
* Reducing team size after a product launch
* Swapping roles as tech stack requirements shift

All scaling requests are managed through your Enablement Partner. Changes take effect at the start of the following subscription month.

## Related

* [Catalog Overview](/docs/products/catalog) — how the primitives are organised
* [AI-Assisted Vetting & Matching](/docs/products/talent/ai-vetting)
* [Deployments](/docs/products/deployments) — how a Talent engagement is tracked