You pick a niche because you know it. Writing jobs. Climate. Design. A corner of the market where LinkedIn is noise.

Then Monday shows up.

You open ten career pages. You copy titles into a doc. You check if last week's roles are still live. Half of them aren't. You rewrite the blurbs because the ATS dump is unreadable. You hit send. Your list is happy. You just spent the afternoon being a data janitor.

That is not why you started the newsletter.

The job you actually hired a workflow for is simple: get this week's live jobs to your list. Not become a scraping company. Not learn Workday's JSON. Not maintain a graveyard of closed roles so you don't embarrass yourself on Thursday.

I have watched operators do this by hand for years. Some of them are good at it. None of them wanted it to be the product.

Isabella runs Content Writing Jobs. Same daily newsletter, 28,000 subscribers. Curation and sending used to take 10 hours a week. Now it takes 1.

The difference is not a better spreadsheet. It is treating the feed as infrastructure.

A jobs API for a newsletter is not "more jobs." It is:

• Filters that match the audience you already chose (role, location, seniority, company, skills).
• Listings that are still open, with salary and location filled in instead of "see posting."
• A digest you can send, or a webhook you can hook, without recopying the internet every Sunday night.

If your list trusts you, stale jobs are how you lose them. Missing a role is a gap. Shipping a closed one is a lie.

The work worth keeping is the taste. Which companies belong. Which roles are actually for your people. The intro you write because you know the beat.

The work worth deleting is the copy-paste.

That is the job. You pick the niche. We source, clean, and keep the feed live. You send the newsletter.