Outreach
Recruiter DM and email drafts that don't sound like AI.
Each draft is grounded in three inputs: the recruiter's profile (so the opener references their actual focus), the role you're targeting (so the ask is specific), and your strongest matching proof point (so the value claim isn't hand-waving). You review, edit, and send manually — no scraping, no automation.
The four-line skeleton
- Reference: a specific detail from the recruiter's profile or recent post.
- Anchor: the role title and req number, no ambiguity.
- Proof: one quantified line — outcome, scope, metric.
- Ask: one concrete question that takes them under 30 seconds to answer.
What we do not do
- × Auto-send.
- × Mass-personalisation across hundreds of recruiters.
- × Scrape protected emails or pages.
- × Promise replies. We optimise for clarity; the human reads what they read.
FAQ
Why don't generic recruiter DMs work?
Recruiters see hundreds of identical openers a week ('Hi, I came across your profile and would love to connect…'). They pattern-match those into the ignore pile within two seconds. RoleWorth's drafts pin the message to a specific role you've already evaluated and a specific proof point that maps to its top requirement — that signals research, which signals reply-worthy.
Will it sound like me?
Drafts are written in a measured, professional voice by default. The tone-match step lets you nudge it warmer, drier, or more direct, and you edit the body before anything goes out. There is no auto-send.
Is sending an unsolicited DM appropriate?
Yes if it's specific, brief, and respects the recruiter's time. The default draft stays under 80 words, names the role, names one matching strength, and asks one concrete question. Outreach that violates platform terms (mass automation, scraped emails) is out of scope — RoleWorth drafts; you send manually.
Product proof
See the product surface behind the claim.
Each page carries the matching RoleWorth surface in a glass-framed proof card: the radar, extension overlay, ATS matrix, review queue, dashboard, or package flow behind the promise.
The public promise, visible above the fold: score first, package second, approve before anything leaves.
Batch scan, ghost-risk skipped count, high-worth jobs, and Apply/Maybe/Skip routing in one product surface.