One-click capture of the profile in front of you

It is worth being blunt about what the downside actually looks like. A recruiter whose sourcing account is restricted or removed loses their connection network, their message history, their saved searches, their project lists and, on a professional network, a large part of how the market recognises them. It typically happens without warning and often in the middle of a live search where the shortlist was being built from exactly those saved lists.

That is not a support ticket. It is a severe customer incident that the software vendor cannot remediate, cannot appeal on the customer's behalf and cannot compensate in any meaningful way. Restoring an account is between the recruiter and the platform, and the outcome is frequently that it is not restored. When a tool creates a risk it cannot carry, the right answer is to draw the scope so the risk does not exist, which is why this extension will do less than the ones you have been demoed.

Every capture will start with a click on a profile the recruiter has already navigated to and is currently looking at. The extension will not read pages the recruiter is not on, will not walk through search result pages collecting profiles, will not run on a schedule and will not do anything at all while its panel is closed.

The confirmation step is part of this rather than a formality. Before saving, the extension will show exactly what it parsed: name, headline, current employer, location, the experience and skills it extracted, and the source URL. The recruiter can correct a field, add a note about why they are keeping this person, tag the record or attach it to a live requisition, and then save. If the parse is wrong, it is corrected before it enters the database rather than becoming another record somebody has to clean up later.

The extension will never ask for a platform username or password, and will never store a session cookie or authentication token from a sourcing site. There is no server-side robot logging in as the recruiter, because there is nothing for it to log in with. Anything the extension can read is something the recruiter is already looking at in their own browser.

The connection back to Surhires uses your own Surhires account, scoped by your normal permissions. Records captured go into your tenant with you as the owner. Nothing is pooled into a shared dataset, sold, or used to build a database that competes with the one you are paying to keep.

Capture is only worth doing if what lands is usable. The extension will write a structured candidate record rather than a screenshot and a link: normalised current title, seniority, location, employer history, skills as separate values, and the profile URL for provenance. That is the same structure the resume parser produces, which is what makes a captured profile searchable alongside the rest of your database instead of sitting in a corner of it.

Duplicate detection runs at the moment of capture. If the person already exists, the extension will say so, show you the existing record, and offer to enrich it with anything new rather than creating a second copy. Silent duplicate creation is the fastest way to make a database untrustworthy, and a sourcing extension pointed at a network your team has all been using is the single most likely source of it.

Capture puts the person in the database. What happens next belongs in the CRM, where it can be seen, reported on and handed over: match scoring against live requisitions, an outreach draft built from the person's actual history, enrolment in a cadence, or a task to call. The extension deliberately stops at the boundary rather than becoming a second, hidden outreach tool running inside a browser tab.

That boundary is also why LinkedIn steps in any future sequence will be manual reminder tasks. The extension will not send the message for you, and neither will the sequence runner. It will open the profile with a drafted note and let the recruiter send it themselves, which keeps the activity indistinguishable from normal human use because it is normal human use.

The extension is in build for the Wave 1 release. Until it ships, profiles reach the database through resume upload, bulk import with column mapping, or manual entry, all of which work today. Nothing in this page is available in a trial yet, and the description is written in the future tense for that reason.

When it does ship, expect a small thing that works reliably rather than a broad thing that works sometimes. Parsing quality varies by site and by how complete a profile is, and no extension parses a sparse profile into a rich record. The confirmation step exists precisely because the parse will occasionally be wrong and a recruiter noticing that before saving is worth more than an extra field of automation.