Recruiting has spent years accumulating profiles. Applicant-tracking systems store past applicants. Sourcing platforms index public work histories. Agencies maintain private networks. Companies buy access to databases containing millions of people.
Yet when a role opens, the question is rarely “Can we find anyone with roughly this background?” The harder question is:
Who is relevant, open to a move, interested in this specific opportunity, and willing to have a conversation now?
A resume database can help with the first part. It usually cannot answer the rest.
A profile is not the same as intent
A professional profile describes what someone has done. Candidate intent describes what they may want to do next and under what conditions.
Those are different kinds of information.
A resume may show that someone is a senior software engineer in Abu Dhabi. It will not reliably tell you that they are open to a founding role, unwilling to relocate, interested only in applied AI, targeting a certain compensation range, or quietly curious about one particular company despite not actively job hunting.
Intent includes details such as:
whether someone is actively searching, passively open, or not open at all;
which functions, industries, and problems interest them;
preferred locations and work arrangements;
compensation expectations and timing;
company-stage, team, and scope preferences;
reasons a particular opportunity is or is not compelling.
Without this context, a database returns possible matches. It does not return willing participants.
The first thousand relevant profiles may expand a hiring team’s options. The next million often expand its outreach queue.
Large databases appear valuable because they create abundance. In practice, recruiters still have to identify plausible people, infer whether each person might move, personalize a message, send it, follow up, wait, and interpret silence.
That work is not a small operational detail. It is where much of the cost of outbound recruiting lives.
When the database is old, the problem compounds. People change roles, locations, skills, compensation, and priorities. A technically correct profile can still be commercially useless because the person is unavailable or the opportunity is wrong for them.
The result is a familiar funnel: many profiles, fewer reachable people, fewer replies, fewer interested candidates, and a very small number of serious conversations.
Intent turns matching into a live question
Candidate intent is not a permanent label. It changes.
Someone may be happy in their role but become open to a stronger mission. They may stop considering relocation after a family change. They may finish a major project and become ready for a larger scope. They may want to hear only about roles that cross a specific threshold.
That means intent should be treated as a live signal, not a one-time field collected during registration.
Useful systems give candidates control over that signal. A person should be able to describe what would make an opportunity worth considering, update those preferences, remain private, and decide whether to be introduced.
For active candidates, search behavior can express intent too. The roles someone saves, hides, opens, and applies to provide more current evidence than a generic “open to work” badge. The aim is not to surveil behavior or make hidden decisions about people. It is to let candidates provide context deliberately and use it to improve relevance.
Intent improves the experience on both sides
For hiring teams, intent removes false availability from the top of the funnel. A smaller set of relevant and interested people is more useful than a larger set of names that require speculative outreach.
For candidates, it changes the nature of the interaction. Instead of receiving repeated messages for loosely related roles, they can evaluate a specific opportunity against preferences they chose to share.
This does not mean every interested person is qualified, or every qualified person will be interested. It means the system acknowledges both conditions before asking humans to invest time.
That is a better starting point for a hiring conversation.
Privacy and agency are part of the model
Intent data is more sensitive than a public work history because it can reveal that someone is considering a move. It should not become another database sold without context.
The candidate should remain in control:
identity stays private until there is a reason to share it;
preferences are used to assess relevant opportunities, not to generate indiscriminate outreach;
no introduction happens without the candidate’s interest;
matching and introductions remain free for talent;
optional candidate tools are separate from access to employer-funded matching.
These constraints are not friction to remove. They are what make the signal trustworthy.
From database access to represented interest
The traditional sourcing product sells access: here are many people you may contact.
An intent-led hiring service provides a different outcome: here is a relevant person who has seen enough context to say that a conversation is worth having.
That outcome requires more than software. It requires market data, good matching, thoughtful outreach, candidate context, and human judgment about when an introduction is genuinely useful.
Fursa is building toward that model. Our live job index shows where demand exists. Candidate context and preferences help us understand potential fit. Fursa Hire uses both to help employers move from a hiring brief to relevant, interested talent.
The goal is not to build the largest resume warehouse. It is to create the shortest credible path between a real role and a person who may genuinely want it.
