M

Grok Bot is insane - I built a full agency and stopped paying middlemen for offers.

6 min readView source ↗

Cover image

Five named bots on a shared cloud PC hunt listings, score who employers actually want, and draft outreach. You spend ~10 minutes on approval packets - not two hours scrolling.


Job search is a pipeline problem - not a motivation problem.

Recruiters take 15-25% or a monthly retainer. Premium boards tax your attention. A chat tab forgets yesterday. This agency replaces middlemen and tab-hopping - not your judgment at Send.

Why this exists

Replace middlemen and tab-hopping - not your judgment.

Article image

The shift: middlemen and tab-hopping vs. a file pipeline you approve

  • You are the only sender

Recruiters blast your CV. Ink stops at a draft. Gage checks facts. You read the packet and click Send - reputation stays yours.

  • Files beat chat memory

Every offer gets a path: raw-offer → scorecard → draft. Vera’s proof map tells Ink exactly which metric to cite. No “what were we talking about?”

  • Night shift on Grok’s cloud PC

Teach Reed one Greenhouse path. Schedule a routine. Reed hunts while you sleep; you meet the work at breakfast with 3-5 approval packets.

  • Who it’s for

Senior ICs and staff engineers running a systematic search - remote EU, fintech, platform roles - who already have proof points in a profile, not beginners spraying Easy Apply.

  • What it’s not

Not a job guarantee. Not auto-spam. Not a replacement for networking - it clears the boring layer so you spend time on conversations that matter.


Org chart on Agent Computer - not one overloaded chat

Grok Bot gives persistent browser, files, and routines. This repo is the roster: paste briefs, create folders, run kickoff.

> Rule 1: no bot hits Send / Apply / Connect without APPROVE in Offer Agency HQ.

Who does what

Human at the gate. Bots never send.

Article image

Roster - one role per bot, human owns Send

File pipeline

Work lives on Agent Computer - not chat memory.

Article image

Stages on Agent Computer - rejects never reach Ink

Night run timeline

Six stages while you sleep - horizontal timeline.Laptop closed · cloud PC runs · breakfast meets the work

Article image

Night run timeline - six stages from 23:30 to 06:00 while laptop is closed

BotOne jobCan send?
SlateRoute · caps · checkout locksNo
ReedHunt → raw-offers/No
VeraScore ≥ 7 → WRITENo
InkDraft + approval packetNo
GageQA PASS / BLOCKNo

What Reed searches - sources, filters, caps

SourcePatternCollect
Greenhouseboards.greenhouse.io/<co>Role · location · requirements (quoted)
Ashbyjobs.ashbyhq.com/<co>Comp if visible · remote policy
Leverjobs.lever.co/<co>Team · seniority · visa
Careers pagecompany.com/careersPrimary source - check first
Wellfoundcompany pageStartup · equity signal
LinkedIn Jobslisting URLAfter login on Agent Computer · Easy Apply OFF

Search brief (profile + kickoff)

roles: senior backend · platform engineer
geos: remote EU · UTC±3
comp_floor: €100k
hard_nos: body-shop recruiters · unpaid trial · crypto gambling
keywords_must: Go OR Rust · distributed systems
daily_cap: 12 raw · 8 scored · 5 drafts

LinkedIn - teach once, save as routine

Keywords backend Go OR platform · EU + Remote · Past week · Mid-Senior · Easy Apply off. Per listing: URL + quoted requirements → one markdown file.

Raw offer file

One listing = one markdown. No invented URLs.

Article image

Reed output - one markdown per listing, quoted requirements

Scorecard

Vera decides WRITE / PEEK / REJECT before Ink touches it.

Article image

Vera gate - score ≥ 7 unlocks the Writer


17 steps in Grok Bot

  1. Clone repo

git clone https://github.com/rimtoln/grok-bot-offer-agency.git

  1. Open Grok Bot
  • desktop or iOS · plan with Agent Computer
  1. Verify Agent Computer

in menu

  1. Create Slate
  • paste

agency/bots/00-slate-chief.md + stop-lines.md

  1. Create Reed, Vera, Ink, Gage
  • same pattern, exact names
  1. Group chat
  • Offer Agency HQ · all bots + you
  1. Folders on cloud PC
  • /agency/inbox/raw-offers/ · scorecards · drafts · sent-log
  1. Profile

agency/bots/00-slate-chief.md + stop-lines.md

  1. Kickoff
  • paste agency/routines/kickoff.md with your search brief
  1. Teach Reed
  • "Watch me. Save as routine daily-offer-hunt."
  1. Schedule
  • morning · 1×/day
  1. First cycle
  • hunt → score → draft → QA
  1. Daily you
  • APPROVE → Send manually → log sent-log.md

Setup path

No npm. Copy prompts into Grok Bot.

Article image

~15 minutes to stand up the agency

Offer Agency HQ

One thread. File paths, not walls of chat.

Article image

HQ thread - paths and packets, not chat amnesia


The edge is not the model. It is the org chart.

Most people treat Grok Bot like a smarter chat tab. That is the wrong product. The product is a night shift that files work on a shared disk while your laptop is closed - then a ten-minute morning gate where you still own Send.

Recruiters sell access. Boards sell attention. This repo sells neither. It sells roles, files, checkout locks, and a hard stop before outreach leaves your name. You are not replacing judgment. You are replacing the two hours of scrolling that never made it into a scorecard.

If the swarm hallucinates, Gage should catch it. If Gage misses it, you catch it. If you skip the gate, you deserve what you get. The uncomfortable part: the people who win this loop will look lazy from the outside - and quietly ship five better applications before breakfast.

Stop hiring middlemen for the boring layer. Hire a roster. Keep the click.


https://github.com/rimtoln/grok-bot-offer-agency

Related articles