Outreach
The follow-up email that gets a reply.
RoleWorth times each follow-up against your last logged contact and drafts language matched to the stage you're in: post-screen thank-you, post-loop check-in, post-offer-deadline nudge. You never wonder "is it too soon?" — the tracker tells you, and the draft is ready when the timer opens.
After recruiter screen
24–48 hours
Brief thank-you, one specific point from the call, restate availability for next steps.
After interview loop
24 hours, then weekly
Thank each panelist (one note each, varied detail), then a weekly status check until you have an answer.
After offer deadline
Same day
Polite, direct, asking for an updated timeline. Flags the stale lead in the tracker.
FAQ
When should I send a follow-up?
Stage-dependent. After a recruiter screen: 24–48 hours for the thank-you, then a status check at the recruiter's stated timeline + 3 business days. After a final loop: 24 hours for the thank-you, then weekly until you have an answer or three weeks pass. RoleWorth times each one against your last logged contact so you don't double-send or go silent for a month.
How do I follow up without being pushy?
The draft adds new value, not pressure. Each follow-up references something concrete — a clarification you've thought about, a relevant case study, an updated availability — instead of repeating 'just checking in'. Tone shifts with stage: warm after the screen, professional after the loop, briefly direct after the offer deadline.
What if I get no response?
Two follow-ups, then archive the role and move on. The pipeline tracker marks the lead as ghosted with the date so you can spot company patterns over time. Continued silence is information; chasing a fourth or fifth time costs you reputation and time.
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.