The One Job

Who this is for

The hard part is the nightly sort: deciding which few roles deserve your energy before the deciding itself empties you out.

• Your experience runs deeper than your resume shows, and the roles you want get filled before they are ever posted.
• You are aiming at Chief of Staff, founder's office, EIR, operator-in-residence, GTM, growth, RevOps, international expansion, or first-generalist startup roles.
• Your path is nonlinear, and a resume flattens your experience into something smaller than it was.
• You are serious, short on time, and want a tested pipeline ready.

Months of quiet is a broken pipeline talking. It is not a verdict on you.

Who should not buy this

• You want someone else to apply to jobs for you.
• You want mass applications, hundreds of scraped leads, or auto-sent outreach.
• You are not comfortable connecting Gmail for status checks or using browser access for LinkedIn and X sourcing.
• You are looking for entry-level roles, internships, pure EA roles, or generic job-board automation.
• You do not want to maintain a tracker or make final judgment calls before anything is sent.

The idea

This is the version that already survived more than seven months of hit and trial. You could rebuild it yourself. You would also need the seven months.

Open-ended job-search automation breaks because it tries to do too much. The One Job is intentionally narrow: first it captures your resume and search rules, then it runs seven sourcing angles, a hard cap of 10 roles and 10 people, two outreach lanes, and one boss. The boss is you.

If a week is thin, it says so. No fake leads. No padded lists. No dashboard to babysit.

How it works

Weekly Sweep

Catches roles before they become listings. It reads hiring intent as it appears, a funding round, a VC-portfolio note, a scout or talent-network nod, a community-board or newsletter mention, a hiring post on LinkedIn or X, and pulls the ones with a real seat behind them into one list. If browser access is missing, Prompt Zero asks you to connect it before LinkedIn or X checks run.

Ranked Shortlist

Verifies roles are real, rejects weak fits on compensation, seniority, geography, industry, and exclusions, names the hiring manager or credible contact where possible, finds contact paths, and cuts the week to a usable list.

Weekday Nudge

Each morning, you get exactly two low-friction actions with messages already drafted. Two items get done. Five get postponed. The cap is the feature.

Follow-up Loop

After you send, it reads Gmail for replies, application updates, rejections, interview notes, and late outcomes. It updates the tracker, flags stale threads, and drafts one low-key bump when the timing makes sense. One bump, ever.

Hiring-Manager Drafts

Every strong lead includes a concrete outreach draft tied to the role, company signal, named person, and your proof points. If the system cannot identify a real person or contact path, it marks the gap instead of pretending.

Search Firm Lane

A separate recruiter lane with one simple email, a batching rule, and a list-building prompt. Script included.

What you get

• The complete skill package as a private Google Doc or private GitHub repo, delivered after checkout.
• Prompt Zero: a first-run intake that asks for resume, profile, target roles, compensation, geography, industries, exclusions, browser access, LinkedIn/X, and Gmail.
• The tracker architecture and rules that preserve application dates, statuses, follow-up windows, rejections, recruiter replies, interview updates, and late outcomes.
• The production prompts: Weekly Sweep, Weekday Nudge, outcome tracking, and follow-up drafting.
• Sample output showing how a shortlist, tracker update, and hiring-manager draft should look.
• The Search Firm Lane script and list-building prompt.
• Troubleshooting notes for the ways the system can wobble.
• A living document: future updates are included.

What a good run looks like

A buyer should not get vague rows like "Sarvam leadership" or "hiring team." A strong result names the role, the reason it passed, the exact risk, the person to contact, the source signal, and the draft to send.

• Shortlist row: VP Portfolio Operations, Bangalore. Passed for GTM plus portfolio-ops alignment; flagged because the post asks for 10-15 years and your profile may need a sharp operator narrative.
• Named contact: recruiter or hiring manager name, public profile, and email or credible path. If the person cannot be verified, the row says so.
• Draft: one specific note tied to the company signal and your proof points, ready for you to edit and send.
• Tracker update: application date, last touch, latest Gmail outcome, next follow-up date, and whether the thread is closed, active, stale, rejected, or waiting.

What you need

• Claude Cowork or ChatGPT to run the agents and prompts, with setup notes for both.
• Gmail connected for drafts, sent-mail checks, replies, application updates, rejection emails, recruiter updates, interview notes, and late outcomes. The agents never send anything.
• Browser access through Chrome, Brave, Claude in Chrome, or ChatGPT browser controls for LinkedIn and X intent checks.
• LinkedIn and X open in your browser for live sourcing. Other social platforms can be checked manually, but only LinkedIn and X are part of the tested flow.

No coding needed. Setup is step by step and takes about 45 minutes, once.

The rules

1. Never fabricate. No invented leads, names, emails, replies, or results.
2. Empty runs are fine. Nothing gets padded to hit a number.
3. Drafts only. Anything sent to a human leaves with your hand on it.
4. Your edits win. The system prepares the work; you make the call.

Who built this

I'm Yashasvi Shailly, an operator across early and growth-stage startups: 421K users served at AstroSure AI, a team scaled from 7 to 22 at Revv Growth, and managed-account growth at Fashinza.

A job search is a pipeline: sourcing, verification, outreach, follow-up. Pipelines run better on systems.

Fine print

No subscription. Updates are included. Global checkout is available for buyers outside India.

Updates stay visible. The private GitHub delivery includes version history and the Google Doc delivery carries the latest working copy. When the skill changes, the setup notes say what changed and why.

Support is simple. Reply to the delivery email with the blocker, the AI tool you are using, and where it got stuck. I will either fix the package or tell you exactly what access/input is missing.

Anything breaks, email me. A failed delivery, a link that will not open, or a checkout that hung: you get your copy within 24 hours, or I make it right.

Your details stay between us. Your name and email exist only so your copy can be delivered and supported.

If the work you need fixed sits inside your company instead of your job search, see how I work.