And for any new readers, welcome to Signal // Noise — the newsletter read by founders, CEOs, and scrappy builders every Thursday. Each week, what I’m listening to, one deep dive, notes from the field, three links worth your time. No buzz, no bullshit.

Yardbirds were the original superband before superbands were even a thing. They only lasted five years, but my oh my what they all went on to become…

🎧 Want the whole vibe? The 2026 playlist is right here.

I’ve spent almost two decades in and around the media space and almost a thousand times I’ve heard some version of: “I need to hire someone to grow my newsletter. That’s a Head of Content, right?”

Probably not.

Most newsletter operators or founders with a newsletter don’t need someone that senior. They may not even need a traditional “content” role or editorial lead.

First, just start with the problem you are trying to solve. What does success look like? What metrics move after 90 days?

The truth is, you need to go through a quick role definition exercise, and most likely, you’ll find what you’re after is more subs (of course you need to have great content, but that’s table stakes).

So what moves the needle is someone who can run or manage Meta ads, build a referral engine, chase partnerships, find organic lift through SEO/AEO. And that’s probably not a Head of Content, rather a sharp generalist (could be marketing manager), an agency, a fractional growth operator.

Either way - the JD you write for that looks very different from the Head of Content JD you were about to post before.

I have some version of this conversation a few times a month with my coaching clients. And obviously it has nothing to do specifically with a Head of Content role, moreso, it’s the same reflex that shows up everywhere, across all hires.

For a long time, founders and CEOs (and shit, just everyday senior operators) treated hiring as the default answer to ambiguity, challenge, or missed opportunity.

And no shade on that.

Sometimes that’s the right answer, and if you were actually good at spotting talent and hiring, it probably worked, too, because labor was the most leveraged unit of capacity you could buy.

But… that’s starting to change.

A $300 to $500/month agent stack can absorb 40 to 60% of the tasks that used to justify a $120K hire. Fractional operators, agencies, and sharper internal process pick up most of the rest. The cost of the wrong hire is the same as 2018.

But the cost of the right alternative is now just a fraction.

So if you’re opening up a job req today, it means one of two things: either you've examined the system and decided a human is the right unit, or you're buying a person to avoid the work.

Make sure it's the former.

And make sure anyone on your team that says "we need to hire" isn't just air cover for "I haven't truly evaluated the system yet."

Before any founder I coach writes a JD, I take them through a five-question role definition exercise. Question 4 is the one this Signal is talking about: is this actually a full-time role, or could it be solved another way?

There are three ways to actually answer that:

Ask these honestly and the answer may change for a real chunk of the roles people thought they needed.

A $20M company that even partially runs this filter can avoid 1 to 3 unnecessary hires per year. That's $300K to $500K in burn that doesn't walk out the door, and a leaner org that compounds instead of slows you down.

Hiring well is still one of the highest-leverage things a founder does. But hiring as a reflex, in 2026, is the most expensive way to avoid the work you should be doing.

Before you ever write a JD, make sure you get super clear on the actual role (most times, you’re wrong). There are 5 questions you need to answer, and I share them in the new product I’m building, the Hiring OS.

It's the 6-phrase playbook I take every founder client through to make sure they're actually hiring the right person for the right reason. Drops late June, sign up to grab it early and get one of the $1k discounts.

Paul Stansik's take: balls constantly get dropped, and that's just a byproduct of running a real business. The best thing you can do is assume it’s gonna happen, and not be embarrassed when it does. In contrast - get good at catching them when they do drop. He walks through three examples of where this usually shows up in B2B SaaS, & a mindset to pass along to your team.

Lenny distilled his latest interview with Every's Dan Shipper into a quick thread summary. The standouts: SaaS isn't dead (Shipper would buy the stocks), CLIs are over, automation's distorted because more automation means more humans, and the full-stack designers are the future’s new superheroes.

In January’s Davos sit-down with WSJ, Anthropic's CEO argues that intelligence is now on its own compounding curve, the way Moore framed transistors back in 1965. Whether you buy the analogy or not, it's powerful. Also hear what Dario has to say about AI safety, getting “Claude-pilled”, and the breakout moment of Opus 4.5.

One last thing:

if you're a founder reading this who's about to write a JD for a critical role and you’re not 100% convinced you have it scoped right, let me know.

Free advice & response to the first few people that reply.

And until next time, thanks for reading.

Jordan