Most founders stay in the CEO seat too long.

Tony Jamous didn't.

In this episode of TLDR, I spoke with Tony (founder of Oyster) and Hadi (new CEO) about stepping back when the company needs something different.

Not because the company was failing. Because it needed something different to scale.

Tony asked himself: "What needs to happen for Oyster to reach $10 billion?"

The answer? A different CEO.

That realization took months to accept. Oyster was his baby. The mission - anyone, anywhere can access great jobs - was deeply personal.

But 360 feedback from his team made the gap clear. They needed someone closer to operations. Someone built to scale multi-billion dollar companies. Someone with different strengths for the next chapter.

So Tony went to the board and said we need to make a change.

The process:

Hired top-tier executive search. Interviewed 40+ candidates globally. Required a case study: "How would you make Oyster more successful than anyone imagined?" Let the board vote without him voting.

Hadi got 100% of votes. Clear #1.

But the hire was just the beginning. The transition required 18 months of prep. Tony flattened the org, brought in new leadership, worked with an executive coach to make his role less critical. Half the leadership team shifted to set Hadi up for success.

The handoff happened from a position of strength. Oyster had its best financial year before the transition.

Hadi's first 90 days:

Listen and learn.
Establish trust through communication.
Build a 3-year strategy.
Walk backwards from the goal.

No wholesale changes for the sake of change. Protect what works. Fix what's broken. Invest where it scales.

The thing most founders miss:

Letting go of control maximizes enterprise value. Staying attached destroys it.

Tony's now Executive Chairman. Guards the mission, stays as the external face, advises Hadi. He's not gone. He's in the right role for this chapter.

Most founders simply ask:
“How long should I stay?”

That’s the wrong question.

The real question is:
“At what point does the company outgrow me?”

And then:
“Do I have the courage to act on that?”

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Everyone says cold email is "saturated."

But what they really mean is: the usual way of doing cold email is dead.

In this episode of TLDR, I spoke to Rey Fernando (CEO, eight25), who's generating 300+ enterprise meetings/year, ~$10-12M pipeline, and $3–7M closed revenue from outbound.

But nothing about his system looks like what most teams do.

Most outbound advice today centers on finding better signals, writing better templates, and scaling volume.

Rey just flipped all of it. Here’s how,

1. Signals don't tell you WHO to reach. They tell you HOW to reach.

Most teams use signals to reduce their list. Rey doesn't. He reaches out to everyone in the ICP consistently. Signals simply help in shaping the angle of the message.

2. The job of your email isn't what you think

Not to explain your product. Not to build trust. Not even to drive conversion. Each part has one job: subject line gets the open, email gets the meeting, offer reduces friction. That's it. Don’t overthink this.

3. Good outbound ≠ clever hacks

I kept asking for systems, automations, shortcuts. But his answer was annoyingly simple: "You just have to write good emails."
Before AI, his team wrote 2,000 custom emails per week manually. Timed. Trained. Iterated.

4. The real constraint isn't volume. It's data quality.

Most teams think they're emailing 3,000 people. They're not. Bad targeting leads to irrelevant emails, which leads to spam reports, which kills deliverability, which breaks the entire system.
Rey's team verifies roles manually, checks relevance before sending, They don't just check 'do we have data?', they check 'is this data actually accurate?'"

5. The most underrated insight

Don't blast everyone in an account at once. Reach out to one person per company per week, rotating through your buying committee.
Result: each person hears from you monthly, the company hears from you weekly. This way you stay present without creating fatigue, and you increase surface area over time.

In short, outbound isn't broken. Lazy outbound is.

The teams winning today aren't doing more. They're just doing the fundamentals way better than everyone else.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Most B2B marketers treat events like a channel.
Book a venue. Get people in. Hope something comes out of it.

And that's also why they fail.

In this episode of TLDR, I spoke with Taryn Talley (30+ events, $2.4M in revenue over 4 years).

Her approach is completely different.

She doesn't start with pipeline targets or event logistics.

She starts with: "Who do we actually want to build relationships with?"

Then she builds a system around deepening those relationships.

B2B deals need 7-12 touches to close. Events are just high-value touches in that sequence.

Her biggest deals came from people who attended 3+ different events over time.

Not one big event. A deliberate sequence of events.

Here's how the system works:

Build a network, not an invite list: Start with 100-1,000 core relationships. Track them in a spreadsheet. Document engagement history, pain points, last meaningful touch. Goal: grow this network 20% annually.

Vary the format: Mix intimate dinners (20 people), networking events (150 people), multi-day experiences (30-40 people). Don't hit the same people with the same format twice.

The real work happens after: Track every conversation. Document pain points shared. Schedule follow-ups: lunches, sports events, smaller dinners. Tag everyone in CRM. Track multi-touch progression.

Her 2023 Growth Marketing Summit: 3 days in Park City, 30-40 executives, cost ~$80K.

Result? The WhatsApp group stayed active for 12 months. Attendees invested in each other's companies. Multiple deals closed.

Here’s the shift:

Most marketers optimize event logistics (venues, catering, attendance, swag bags).

Taryn optimizes relationship infrastructure (network growth, touch sequences, conversion tracking).

That's the difference between treating events as a channel vs. treating them as systematic relationship building.

This is operator-level thinking you can't learn from playbooks.

If you're still running campaigns without direct customer context, you're just guessing.

Hosted on Ausha. See ausha.co/privacy-policy for more information.