From “we received a mandate” to “these are the people to call first.”

A job description names a title and a list of skills. The people who can do the work often hold a different title, in a different industry, with the skills in a different order. Sourcing starts from the requirement as the client wrote it and works out who it is really for.

The role is read across the things a recruiter would weigh: the role and the function, seniority, years of experience, skills and capability, the industry background, whether GCC experience matters, the type of employer, the career path that leads to the role, the location, and the adjacent experience that would also do. The result is a candidate persona written out before the search begins.

The same kind of person appears under many titles across GCCs. Agentic Taxonomies apply structured families of roles, functions, skills, capabilities, seniority levels, career paths, adjacent roles, transferable skills and employer categories to the persona, so a search does not depend on exact titles or on a hand-built Boolean string.

The point is to translate the requirement into how the market is actually organised.

Widen it in controlled steps and see why. Adjacent titles, related skills, comparable capabilities, similar industries, transferable GCC experience, nearby locations, the employer clusters that already hold similar people, and one level of seniority either way where it makes sense. Each addition has its reason attached, and the size of the pool shows the effect.

Once the persona and taxonomies are set, the relevant market is shown as a whole: its size, how many are a strong match, the spread of experience and location, which employers hold most of it, which skills cluster in it, how many have GCC experience, how many roles are open for the same persona now and what it costs.

The pool is ordered by how closely each profile fits the requirement and persona, so the most relevant people are read first. Each profile shows why it surfaced: the role fit, the skills present, the GCC experience, the experience band, the industry background, the employer, the career progression, the location.

There is no unexplained score. If a profile is near the top, the reasons are on the page.

Where the strongest personas sit across the market: the companies with the most relevant talent, the GCCs that have built the capability at scale, the employers to source from first, and where similar personas cluster.

A profile brings together the person's current role and company, experience, skills, GCC history, location, the match rationale and, where it is held, a professional email address and phone number. Contact details are a means to the conversation. What makes the conversation worth having is the reason you are making the call.

Move chosen profiles into a working shortlist and compare them across persona fit, role fit, skills, experience, employer, GCC background, location, whether they can be contacted and the match rationale. The outcome is a list of the people to approach first, in an order you can explain.