The Monday job from an earlier track already watches your pipeline and refills the queue when it dips. It works, and it has one obvious limit: it only knows what the public web will tell it.
This episode hands it the keys to Apollo, and it's the culmination of the whole track.
Everything we built by hand over the last several episodes gets described once, in one long plain-English instruction, and turned into a scheduled task. Read Who We Sell To, How I Write, and My Market. Refresh research on the top three Ready targets and draft a first-touch email in my voice on each page. For anyone marked Contacted, check sent mail and the inbox, and if it's been five days with no reply, draft a two-sentence bump. Count open deals, and if there are fewer than ten, promote the strongest Waiting targets to Ready until three are teed up, and say why you picked them. Then, if fewer than three Waiting targets are left, search Apollo using My Market, enrich up to five, never spend more than five credits, and log exactly what you spent. Finish with a summary under ten lines at the top of the CRM page.
Then the three hard limits, which are the reason this is safe to leave running. Never send anything. Never create or touch an Apollo sequence, ever, because Apollo will happily blast email at volume from your address. Never spend past the credit number you set. Research, draft, file, report.
The scheduling itself has changed, and it's worth watching. I never open the scheduled tasks panel. I just keep talking, Claude asks what time on Monday, I say 6 a.m., and it's scheduled. Then I retire the old public-web version of the job so the two aren't duplicating work, and click Run Now to test it. Three of five credits spent, full rundown, sources attached.
What's running on Monday morning is worth being clear about. It's your judgment, your voice, your market, your decisions. On a leash, with an allowance and a clock. The only unautomated parts are the ones that should stay that way forever: the edit button, the send button, and the handshake.
One new detail on screen: this task runs in the cloud rather than on my always-on Mac mini, because every piece it touches, the CRM, Apollo, Claude, already lives there. If any step needed the local machine, the always-on computer from the earlier track would still be required.
We didn't learn a new tool in this track. We described a job to an assistant, gave it a place to keep its knowledge, put it on a clock, and gave it a budget, the same way you'd onboard a virtual employee.