mudpie

Operator research · 5 min read

What to learn from Sam Blond about GTM in 2026

Five operating decisions from Sam Blond’s public interviews: customer selection, pipeline, first sales hires, AI’s role, and launch distribution.

Published · Updated

Automating sales is not the same as creating demand.

That is the useful thread in Sam Blond’s GTM advice. Software can find accounts, prepare a call, and chase the next step. None of that tells you whether you picked the right customer or gave them a reason to care.

Blond now runs Monaco, so his 2026 interviews mix operating lessons with a pitch for his company. I read them with that conflict in mind. The interesting question is what a founder can borrow without buying the pitch.

1. Check who enters the funnel before rewriting the pitch

In his June 2026 interview with Turner Novak, around 30:50, Blond describes a Brex finding: finance buyers converted at roughly four times the rate of controllers. He says the team changed its first outreach toward finance personas.

That is a reported historical result, not a controlled experiment. The interview does not give the sample size or establish that changing the persona alone caused the improvement.

But it suggests a better question than “How do we send more emails?”

Which customers make the rest of the funnel work?

Here is a hypothetical example, not a Brex result. Two segments each produce 20 meetings. One produces six qualified opportunities and the other produces two. A dashboard that rewards meetings calls them equal. A founder who has to turn those meetings into revenue should not.

Before increasing volume, break the funnel down by customer type. Keep the definition of “qualified” fixed. Show the raw counts next to the percentages. Three wins from ten opportunities is interesting; it is not yet a stable 30% forecast.

2. More opportunities and better conversion are different bets

In his July 2026 Uncapped interview, Blond argues that a thin pipeline can disguise itself as a closing problem. One delayed deal feels existential when it is the only deal.

The arithmetic explains the instinct. At a fixed contract value, doubling qualified opportunities or doubling the win rate can each double expected revenue. The arithmetic does not tell you which is easier, cheaper, or sustainable.

My diagnostic would be:

What you see What I would investigate first
Few qualified conversations, decent conversion Where similar buyers can be reached
Many meetings, few qualified opportunities Targeting and the promise used to book the meeting
Qualified buyers repeatedly stall at the same step Product fit, proof, procurement, or the sales process
Wins increase but customers leave quickly Whether acquisition is recruiting the wrong customer

This table is a decision aid, not a benchmark. A founder should be able to point to the row they are in before buying another tool.

3. Hire against a sales motion you have actually seen

Blond’s 2024 conversation with Harry Stebbings makes a useful distinction: get non-friends-and-family customers and some repeatability before expecting an early sales hire to take over. He favors experience with a comparable startup stage, deal size, and customer segment over domain familiarity alone.

That is older advice. AI does not make it newly discovered advice in 2026.

I would turn it into a hiring artifact: five actual deals, including losses. For each, write who initiated the conversation, what changed their urgency, what evidence they requested, who approved the purchase, and why it closed or failed.

If every deal tells a different story, the next hire needs to help discover the motion. Say that in the job. Do not hire someone to scale a process that exists only in a spreadsheet forecast.

4. Automate preparation without abandoning the hard conversation

The 2025 SaaStr discussion describes a different role for AI in smaller deals versus large enterprise commitments. The latter still involved human reassurance and technical trust. These are operator accounts, not evidence that a particular contract value determines whether AI can sell.

For an early team, I would draw the boundary by consequence. Let software assemble public research and draft the follow-up. Have a person own claims about security, contract terms, implementation commitments, and what the product cannot do.

Then measure where the saved time goes. If preparation falls from an hour to ten minutes but the founder still avoids customer calls, the business has gained spare time, not a better sales motion.

5. Borrow the distribution plan, not the launch stunt

Blond’s February 2026 launch post describes a product-led video, planned amplification from employees, investors and customers, and repeated follow-through after launch. Monaco also used physical gifts and LED trucks. The post does not establish a return on those campaigns.

The distribution sheet is more portable than the trucks.

For your next launch, list who can reach the right buyer, why they would genuinely share it, what proof they can point to, and who owns the follow-up. Give customers room to describe their own experience. Do not write a testimonial for them and call it customer advocacy.

Then make the next week part of the plan. A release is one reason to contact the market. A useful customer example, a measured result, or an honest failure analysis is another.

The first thing I would copy from Blond is the attention to demand quality. Before adding an agent or an account executive, count the qualified opportunities and read the last five losses. Those two inputs should make the next decision less abstract.

About the author

I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.

First1000 ↗ · X ↗