@buildbetter

BuildBetter by BFGhttps://paragraph.com/@BuildBetter Lessons for building better products, teams and businesses, focused on getting clients, sales, and growth.Sun, 19 Jul 2026 02:39:29 GMThttps://validator.w3.org/feed/docs/rss2.htmlhttps://github.com/jpmonette/feedenBuildBetter by BFGhttps://storage.googleapis.com/papyrus\_images/93b508beea291347887e019fc997c5b5eaabab3d9c334b82e3cfe13fa4ff5709.jpghttps://paragraph.com/@BuildBetter

All rights reserved<![CDATA[The Sunbed Delusion: Why Comfort Is Killing Your Next Big Move]]>https://paragraph.com/@BuildBetter/sunbed-delusion-comfort-trap kku3VXGjShzzk6pUp9BBSat, 27 Jun 2026 14:07:17 GMTThe Tony Fadell three-generation rule tells us it took three tries for Nest, the iPod, and the iPhone to actually work. If a certifiable genius needs three tries, what makes you think you can design a flawless three-year master plan while working on your tan?

Hint: You can’t.

You’re sitting on a sunbed—or maybe just in your comfy office chair—watching the waves roll in. Or, more likely, watching your X feed and HackerNews with a fresh cup of coffee.

Ahead of you are three months of absolute freedom and zero financial pressure. Infinite space to build. It sounds like the ultimate founder dream.

But there’s an uncomfortable emptiness creeping in.

Here’s the thing: unlimited comfort is a cognitive trap. When you can do absolutely anything, you end up doing nothing because every new direction requires an uphill climb. You tell yourself you’re just “exploring,” but laziness wins because you lack a conviction engine.

I’ve written before about how your brain gets hooked on easy loops—like when I ditched social feeds for a private notebook. It’s the same trap here. Your brain doesn't actually want peace. It wants meaningful friction. If you don’t actively choose your challenges, your mind will invent stupid ones just to stay occupied.

You don’t need more rest. You need to figure out what you are doing, with whom, and why.

Subscribe

The Framework for Post-Comfort Building

Stop staring at a blank slate of infinite possibilities. That is exactly how you stay paralyzed or intellectually numb—what I call Level 1 on The Dopamine Ladder. You need to narrow the field using constraints that filter out the noise.

I’m not gonna lie: I’m feeling it again too. My way out, that I used in the past and I will probably use again, is to start with people and make testing ideas feel quick and short.

1. The “High-Signal People” Filter

Forget the product ideas or the market sizes for a second. Look at the people you want to spend your mornings arguing with in private Telegram channels, WhatsApp groups, or over coffee and a good cigar. If a space lacks high-signal operators who are actually fun to build with, do not enter it.

Your next move must start with finding ten people who actually give a sh*t about solving (or even just exploring) the same hard problems you care about and you can have a beer with them (even if virtual one).

2. The 48-Hour Micro-Sprint

You are too lazy to commit to a six-month exploratory project just to see if you like it. I feel you, me too. And that is completely fine. I don’t fight the laziness anymore — I bypass it.

Compress your exploration into a 48-hour micro-sprint:

Do not look for long-term commitment. Look for immediate, raw feedback to spark your interest fire. If you need a playbook for this, look at how Tony Fadell structured his cycles in Make It. Fix It. Fix the Business - and shorten it.

3. The Reality Check for Utility

Are you building a real system that turns code into distribution leverage, or are you just chasing vaporware?

Too many founders make the mistake of building broad, empty spaces. It’s why I tell builders to stop building communities and build the tools they’re missing instead.

Please, only choose actions that provide clear, undeniable utility.

If an idea doesn’t solve a glaring bottleneck or an existential pain point for a specific, high-intent group — leave it on the beach. Your efforts would just drown in the noise that's getting worse and without a chance to stand out with clear positioning.

Let’s Bring This Home

The summer break is wrapping up, and the beach crowds are thinning out. The goal isn’t to invent a perfect, flawless 10-year master plan while tanning.

The goal is to pick one fight worth winning with people you actually respect and want to spend time with.

Focus on people, instead of product ideas, is probably the best hack I see now.

Get off the sunbed, close the browser tabs, and design your first constraint.

Share

TLDR Takeaways

Till next time, let’s BUILD BETTER!

— Pete (aka BFG)

Subscribe

]]>buildbetter@newsletter.paragraph.com (BFG (aka BrightFutureGuy))founder choice paralysislife strategy for entrepreneursbusiness strategymindset constraintsovercoming lazinesspost-success boredomthe comfort trapmental modelsstartup strategy<![CDATA[Make It. Fix It. Fix the Business.]]>https://paragraph.com/@BuildBetter/make-it-fix-it-fix-the-business OUmoDZ7mApBU6Y1NXD3AThu, 18 Jun 2026 09:18:51 GMTTLDR: Great products almost never work on the first try. They take three iterations — make it, fix it, fix the business. The iPod, the iPhone, the Nest Thermostat all followed the same path. The trick isn't being a genius on v1. It's hanging in there long enough to reach v3.

Tony Fadell said something on Lenny’s podcast last week that I have used as a reminder in several conversations already, so I can’t stop thinking about it — maybe it deserves to be repeated here as well:

"You make the product, then you fix the product, then you fix the business. Even the iPod took three generations before it became successful."

Here's the thing — this guy built the iPod, co-created the iPhone, and founded Nest. If anyone gets to claim first-try genius, it's him.

And he's telling you it took three generations. Every single time.

Why it always takes three

Generation 1 — Make it. You ship the thing. It exists. It mostly works. It's also rough, weird, and missing half of what people actually want. That's fine — the only job of v1 is to prove the idea isn't insane.

Generation 2 — Fix it. Now you know what's broken, because real people told you. You fix the product itself — the bugs, the friction, the stuff you were too close to see. This is where the thing starts feeling good.

Generation 3 — Fix the business. The product works… but the pricing is off. Or the distribution is wrong. Or the scale is small, and margins don't math. v3 is where you fix everything around the product so it can actually make money.

Make it. Fix it. Fix the business.

Share

The part nobody likes

Most founders quit somewhere in Generation 1.

They ship v1, it's clunky, the numbers are bad — and they conclude the idea was wrong. Spoiler: the idea was probably fine. They just confused "first version" with "final version."

The iPhone we worship today? Not v1. The Nest everyone copies? Not v1. They're all v3-and-beyond products we pretend sprang fully formed from a keynote.

You're not failing. You're on Generation 1. That's exactly where you're supposed to be 😅

What to actually do with this

Consider this - maybe the builders who win aren't smarter. They just refuse to bail early

Hang in there.

Let's BUILD BETTER 💪

— BFG

Subscribe

]]>buildbetter@newsletter.paragraph.com (BFG (aka BrightFutureGuy))<![CDATA[Why I Ditched Social Feeds for a Private Notebook]]>https://paragraph.com/@BuildBetter/why-i-ditched-social-feeds-for-a-private-notebook PH3tAS7DAbIRwT4abVgjFri, 22 May 2026 15:44:01 GMTThere used to be tens of blogging platforms you could use for free. It seemed like the internet was only going to get better.

Apparently, it only got worse. I was recently looking for a platform for random, not-yet-fully-formed thoughts. I don’t want to pay for it because it’s just a hobby, not a business. No multimedia, nothing big—just pure writing.

Asking the LLMs got me nowhere but frustrated.

The Landscape: Social Networks vs. Pure Text

Turned out my only obvious choices were big social networks like X, BlueSky, or Farcaster (the decentralized version of X). Or other networks like Nostr or Lens.

Even Tumblr is still kicking, which surprised me because I thought it died years ago.

But proper blogging platforms have too much UI overhead just to post a short thought. Micro-blogging it is.

Golden Rule of Capture For Me: If the friction to post a random thought requires more than two clicks, your framework is broken. Keep the pipeline stupidly simple.

My old favorite from 2020, Write.as, was beautifully designed just for writing and supported anonymous posts. They had a free tier and an iOS app. Too bad that app hasn’t seen an update in seven years, and the free tier is dead. Starting at nine bucks a month for a fun side project makes zero sense.

Then there is Micro.blog and Mataroa. Mataroa is too techie and lacks a native iOS app. Micro.blog almost won because five bucks a month is cheap, but I really didn’t want to pay. Bear Blog was another clean possibility, and I thought about Substack Notes, but you can’t download your data in bulk. Once it’s posted there, it’s lost unless you screenshot it.

Share

The Pivot to an Unexpected Creative Vault

I thought I’d be swimming in options, but it felt like choosing different types of pain.

Since nobody likes pain, I almost gave up. I didn’t want to use Apple Notes because it gets chaotic too fast.

Then I had a last-minute idea: I created a private collection (like a notebook) inside the Sublime app.

I am chronologically saving my thoughts there. The magic happens when I review my text. Sublime resurfaces potentially relevant ideas and notes from other users inside the ecosystem. Reviewing my random thoughts became a much more fun and inspiring experience than I ever expected.

If you haven’t tried the Sublime app yet, you need to. For creative thinkers, it is a brutally under-promoted and under-appreciated tool.

TLDR Takeaways

  1. The free tier era is dying: Most legacy text platforms have killed their free tiers or abandoned their mobile apps.

  2. Beware of locked ecosystems: Avoid hosting your raw thoughts on platforms where you cannot download your data in bulk.

  3. Clarity requires low friction: Traditional blogging setups have too much layout overhead for raw, stream-of-consciousness writing.

  4. Sublime is a hidden gem: If you want an organized, chronological space that connects your notes to broader inspiration, try the Sublime app.

Till next time, let’s BUILD BETTER!

Pete (aka BFG)

Subscribe

]]>buildbetter@newsletter.paragraph.com (BFG (aka BrightFutureGuy))<![CDATA[Every Founder Is Building Agents. Nobody Is Building Trust.]]>https://paragraph.com/@BuildBetter/know-your-agent-billions-evin-mcmullen bTwMnMs3zK9GIqUWIwvRSat, 09 May 2026 12:43:37 GMT51% of internet interactions today come from unidentified bots. Your AI agent is one of them — until it has a verifiable identity.

In this BuildBetter episode, Evin McMullen (co-founder & CEO of Billions Network, ex-Disco, ex-Privado ID, Consensys) walks through Know Your Agent (KYA) — the trust layer agentic commerce needs to actually work.

TLDR

Share

Pull Quotes

“More than 51% of online and onchain interactions today come from unidentified, unaccountable bots.” — Evin McMullen, [00:00]

“Identity isn’t the thing. It’s the thing that gets you to the thing.” — Evin McMullen, [16:50]

“We cannot be making payments at scale if we don’t know who we are paying.” — Evin McMullen, [14:20]

Trust and Identity problem

There’s a number that should bother every founder building with AI agents right now.

51%.

More than half of all internet and onchain interactions today come from bots. Unidentified. Unaccountable. Anonymous by default.

Your agent is one of them.

It has no papers. No verifiable link back to you. When it talks to another agent, neither side can prove who — or what — they’re actually dealing with. That’s not a future problem. It’s the current state of the stack.

Evin McMullen has been working this problem for nearly a decade. First as a researcher adjacent to the Ethereum identity space. Then as the founder of Disco — the data backpack concept, the idea that your credentials should travel with you the same way your tokens do. Then through an acquisition by Privado ID (a ZK identity spinout from Polygon). And now as co-founder of Billions Network, which launched at ETH Denver 2025 and is already the third-largest ecosystem of onchain verified agents on earth.

Second only to Ethereum. By about 100 agents.

What is Know Your Agent (KYA)

How does my agent know it’s talking to your agent — and not a bad actor pretending to be you?

Right now, it doesn’t. There’s no standard answer. There’s no trust layer. And without one, agentic commerce — agents transacting, negotiating, paying on behalf of humans — can’t scale. You can’t pay someone if you don’t know who you’re paying.

Billions Network built KYA. Know Your Agent. It assigns a verifiable identity to an AI agent instance, cryptographically linked back to the human who deployed and controls it. Your agent becomes a function of you — provably.

Same ZK technology that lets you prove you’re over 18 without handing over your passport. Same infrastructure, now extended to the agents acting on your behalf.

Here’s the part most founders miss.

Billions didn’t ship a product and build a sales motion. They open-sourced the primitive.

Their ZK libraries are the most widely used on earth. Worldcoin uses them. The European Commission has run sandboxed proofs with them. They’re the #1 identity skill on OpenClaw — the agent capability repository that works like a GitHub for AI behavior.

The distribution logic is clean: make the infrastructure so foundational that builders can’t avoid it. Let the ecosystem pull you forward. Then build the application layer on top of an installed base you didn’t have to cold-call.

That’s not luck. That’s a deliberate choice to build a primitive instead of a product — and to open-source it so adoption compounds.

You might also wanna read or listen to

Billions roadmap is in three phases.

First: distribute the identity foundation. Get the data backpacks into the world. That’s now.

Second: introduce reputation. Layer in attributes — age, KYC, location, humanity, uniqueness — for both humans and their agents.

Third: the trust economy. Multi-step agentic workflows that actually move value based on verified reputation. Agentic commerce, at scale.

They’re in phase one. Phase three is where the real gravity is.

One more thing worth sitting with.

Evin made a point about the surveillance false dichotomy that I keep coming back to.

Governments and platforms keep framing online identity as binary: total anonymity or full disclosure. Hand over your passport, or stay anonymous. Pick one.

That’s wrong. And the people promoting that framing — Meta, certain legislators — know it’s wrong.

Zero-knowledge proofs are the third option. Prove you’re over 18. Don’t reveal your birthday. Prove you’re human. Don’t reveal your face. The technology exists. The open standards exist. The only thing missing is the will to use them — and infrastructure that makes them accessible without a PhD in cryptography.

That’s what the ZK query language Billions built is for. Drop-down menus. Pick your requirements. Generate the proof circuit. No cryptography background required.

The wall between “builders who understand ZK” and “builders who can use ZK” just got shorter.

Subscribe

Full podcast video with Evin McMullen

Timestamps

Resources & Links

BuildBetter

BuildBetter HQ is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.

Subscribe

]]>buildbetter@newsletter.paragraph.com (BFG (aka BrightFutureGuy))aidigitalidentityreputationbillions-networkfoundersai-agents<![CDATA[7 Unconventional Social Proof Strategies for B2B Services]]>https://paragraph.com/@BuildBetter/unconventional-social-proof-b2b 1h9XOnGeyTIg0gs1qQNTWed, 06 May 2026 11:12:07 GMTAre you even chasing down your B2B clients for those testimonials? Well, I hope so, but still - it's time to rethink your approach.

If you run a B2B service business — agency, consultancy, dev shop — generic case studies aren't moving prospects anymore. Here are 7 unconventional social proof strategies that get ideal clients seeking you out.

TLDR:

Social proof strategies for B2B service businesses

Share

1. Micro-Milestone Video Snippets

Collect short, excited videos from clients after each project milestone. Systematize identifying key moments and automate the ask. These authentic snippets pack a punch:

"Just wrapped up user testing and wow — the insights from [Your Company] are transforming our onboarding flow. The best part? It took half the time we budgeted. These guys are wizards."

2. Metrics-Driven Mini Case Studies

Surface key metrics and outcomes to create data-driven success stories:

"By restructuring our Postgres schema based on [Your Expert's] suggestions, we saw a 43% query speed boost and cut infrastructure costs by 23%. I couldn't believe the impact from a single consulting session."

This is where positioning and proof meet — see my eight-step positioning framework for how to frame the before state so the metric actually lands.

3. Testimonials as a Team Sport

Empower your whole team to gather client wins. Make it part of your culture:

Institute a "client win story" agenda item in standups. Whoever shares the best one that week gets their favorite dessert delivered.

4. Mine "Overheard" Moments

Scour Slack communities, Twitter threads, and industry forums for positive mentions. Reach out for permission to quote them:

You spot an Indie Hackers comment: "Their Python optimization service is unreal. 2 hours of their time saved us 3 weeks of debugging." Jackpot.

Want help wiring all of this into your client process? Schedule a call and we'll map it together. 😉

5. Embed Proof in Your Process

Build feedback collection into your workflow. Make giving a testimonial the default offboarding step:

Include "What would you tell another founder about working with us?" in your post-project survey, with "Post this on your site" and "Use in a case study" opt-ins.

6. Establish Expertise Through Content

Showcase your expert process through content, speaking, and open source. Show, don't just tell, how you solve problems:

You present at a CTO roundtable on your novel Kubernetes migration approach. An attendee tweets the key slide: "How [Your Company] helped us cut deploy times by 85%."

This is also why distribution is a Day One problem — proof points compound when you have a place to put them.

7. Conduct Comparative "Lift" Studies

For established clients, coordinate a study comparing results with vs without your service:

In the past decade, whenever founders started using some of these tactics regularly, their qualified pipelines grew 45–150% compared to running just sales, BD, and marketing on traditional plays.

Pair this with a problem-first cold outreach approach and your inbound and outbound start reinforcing each other.

Make these part of your regular project delivery process.

Make them part of your client contracts and offers.

Make them part of your SOPs.

It's evergreen content and proof.

Want to see these social proof strategies in action? Schedule a call, and let's put them to work for your business. Together, we'll craft an arsenal of unignorable proof points that have ideal clients seeking you out.

Till next time, let's build better businesses via small improvements.

Cheers,

Pete (aka BFG)

BuildBetter HQ is a reader-supported publication.

To receive new posts and support my work,

consider becoming a free or paid subscriber.

Subscribe

]]>buildbetter@newsletter.paragraph.com (BFG (aka BrightFutureGuy))b2bsocial-prooftestimonialsgtmfoundersservice-business<![CDATA[Hire When It's Almost Too Late — The Founder Super Power Nobody Builds]]>https://paragraph.com/@BuildBetter/bfg-hire-late-rather-than-early km305zQsr78ROAuEfw9FThu, 30 Apr 2026 10:27:53 GMT

TLDR

• Hiring is the most under-rated founder super power. It's a skill, not luck — and almost nobody trains it.

• Hire almost too late, until your product earns the next hire.

• Every hire has to move "product lovability" or "distribution velocity." Anything else is decoration.

• The 4 mistakes that kill early teams: hiring out of fear, hiring out of habit, hiring junior, and waiting for the unicorn.

• Build the muscle: write the JD yourself, run the first five calls yourself, and steal people you've already worked with.

Most founders treat hiring like dental work or coffee break job. Necessary, painful, or fearful, postponed. Don't be that guy/gal.

The ones who build durable companies treat it like the actual job — the highest-leverage thing they do all month. The difference shows up later, when the product they shipped is good, and good is simply not enough these days. The team they assembled is mediocre. Not "Navy Seals" as Elon calls the exceptional hires, and by then it's too expensive to fix.

Hiring is a super power. And like any super power, it's built — not granted. 💪

Subscribe

Your goal as CEO is to build a team that runs your entire company better than you.

Codie Sanchez

@Codie_Sanchez

Your goal as CEO is to build a team that runs your entire company better than you.

311 5:32 PM • Apr 24, 2026

"First ten hires set the ceiling for the next hundred. Get them wrong and you're building on sand." — Ross Starkey

That's the whole game in two sentences.

Why founders dodge it

Founders dodge hiring for two reasons.

One, nobody taught them how. They learned to code, and sometimes to pitch — they didn't learn how to spot, attract, and close a great talent — whether for sales or an operator.

Two, hiring confronts them with their own gaps, and sometimes ego gets in the way. Every JD is a public confession of what you can't do alone. That's uncomfortable, so most people skip the confession and write a generic "looking for a marketer" post on X or LinkedIn.

I'm gonna be blunt: if you can't articulate exactly what "outcomes" your next hire will own, what bar they have to clear, and what would make you fire them in 90 days — you're not ready to hire them. You're ready to feel less anxious about hiring them.

Big difference. 🎯

Hire almost too late

Until your product reaches PMF, you should stay as small as humanly possible. The pressure to "build a team" usually comes from outside — investors who confuse headcount with progress, or your own anxiety dressing itself up as ambition.

A hire is only worth it if it moves one of the two needles I keep coming back to:

If a candidate doesn't move one of those, they're decoration. And decoration that is expensive for any size of the team.

"If you're starting a business today, you don't need to hire a team on day one. It's the biggest change in the Startup playbook in decades." — Sergio Pereira

You should hire when the shift from "vibe coding" to "software engineering" happens. But then you need to hire hard! And you should already know whom you will want to hire -- most likely someone you've worked with before. 👀

See, the tools changed. The math on early hiring changed with them. AI lets a single founder ship what used to take five people — use that runway to find the right people, not just people.

The 4 mistakes that kill early teams

After watching this play out across dozens of startups, the same four mistakes show up almost every time:

1. Hiring out of fear. The business isn't going where you hoped, and someone's whispering "you need a head of growth."

Spoiler: you need different positioning, not a head of growth. If you don't naturally feel the need, don't hire. Anxiety is a terrible recruiter.

2. Hiring out of habit. Corporate background creeping in. "We need a process for this, so we need someone to manage that process."

Wrong. If you, as the founder, can't keep a 5-person team aligned around a lovable product, no process and no hire will fix it.

3. Hiring junior, or project managers. Stop. Unless it's a temp intern for your X campaign.

Also, "junior" implies a senior to learn from — which you don't have. Hire for potential at full trust, not at junior titles. Either bet on someone, or don't. And, there's nothing a project manager can do in a 12-person startup that a founder can't do in 20 minutes a day.

4. Waiting for the unicorn. The "ideal hire" is mostly a coping mechanism for not deciding. Real hires are 70% of what you wanted with one absolutely non-negotiable strength. Hire that, support them, and let the other 30% emerge.

Share

Build the muscle

Here's the part most founder content skips: hiring is learnable. It's a sequence of habits, not a personality trait. The founders who become great hirers all do roughly the same things:

"The shortcut to early recruiting is hiring people you've already worked with. You don't have to guess what they're like under pressure. You already know." — Scott Case, via @calbucci

Exactly this. The most successful early teams I've seen weren't assembled from LinkedIn — they were assembled from someone's old contact list.

The two roles that beat "process" every time

If you're building hardware, software, Web3, or anything in between, the early team that takes you from "founders + engineers" to "ready for scale" is almost always the same two people:

Skip the project managers and the junior-everything. Hire those two right, and you'll do more in six months than 20 engineers and a recruiter will do in two years. ✅

Last word

If you take one thing: hiring is not the founder's chore. It's the founder's leverage — and one of the five core roles only you can own. Build it like you'd build any other muscle — deliberately, painfully, on purpose.

Hire almost too late.

Hire for what moves the needle.

And steal the people you'd already trust. 😉

Till next time, let's BUILD BETTER!

Pete (aka BFG)

ICYMI: Don't Use Agencies — Build Your Own Muscles — the companion piece on why agencies don't fix what hiring should.

Subscribe

]]>buildbetter@newsletter.paragraph.com (BFG (aka BrightFutureGuy))teamhiringfoundersoperatorsplaybook<![CDATA[Capital Concentration Is a Pricing Distortion — Even for SF]]>https://paragraph.com/@BuildBetter/capital-concentration-is-a-pricing-distortion-even-for-sf zUiudppY0rXND8jcU0E1Mon, 27 Apr 2026 11:39:04 GMTI posted yesterday about that SF wealth concentration chart making the rounds. Quick gut reaction — here's the longer version.

Pete (aka BFG) | Lab2094

@aka_BFG

This is what’s wrong with the markets and the world atm …

sorry, but SF is really the worst place to be and even if the numbers were correct it should never be that concentrated and that’s what next revolution is gonna be about … peaceful or violent

h/t to Moonshots

0 12:57 PM • Apr 26, 2026

The specific number is almost beside the point.

The SHAPE is what should worry everyone.

Here's the thing nobody wants to say out loud:

When 90% of capital, talent, and decision-making lives inside one Bay Area zip code, you don't get more innovation. You get more correlation.

Every "contrarian" SF founder is reading the same blog posts as 50,000 other contrarian SF founders. Every investor is hearing the same pitch 17 times. Different words, same thesis.

That's not a market. That's a feedback loop.

And feedback loops do something specific to value — they inflate it.

Here's the part most people miss: the over-concentration we're seeing in US public and private markets right now isn't just inequality. It's a pricing distortion. When the same handful of names absorb most of the capital, "fair value" stops meaning anything. You're not paying for the company. You're paying for the consensus around the company. And consensus, as anyone who's lived through a cycle knows, is rented — not owned.

That's bad for everyone outside the bubble.

Share

The Eye of the Storm Has the Furthest to Fall

But it's worse for everyone inside it.

Because when the consensus shifts — and it always does — the people living in the eye of the storm have the furthest to fall. The same concentration that made them feel safe is what makes the unwind brutal.

The interesting bets keep coming from the wrong cities anyway. Berlin. Lagos. Buenos Aires. Bucharest. Sofia.

Not because the people are smarter. Because the feed is different.

If you're building outside SF and wondering if you're behind — you're not. You're decorrelated. And in a market this concentrated, decorrelation is the only edge that compounds.

Till next time, let's BUILD BETTER!

BFG

ICYMI: Technology Cycles and The Anti-FOMO Playbook (Carlota Perez) — the framework for spotting which phase of the cycle we're actually in.

Subscribe

]]>buildbetter@newsletter.paragraph.com (BFG (aka BrightFutureGuy))macrocyclesdistributionfoundersconcentration<![CDATA[Cold Outreach in 2026: The Problem-First Playbook (PAS, BAB, 4T, NOR)]]>https://paragraph.com/@BuildBetter/cold-outreach-is-alive-but-for-2026-it-has-changed yNMky65Qq9uDEgPU5A04Thu, 02 Apr 2026 13:37:23 GMTCold Outreach in 2026: The Problem-First Playbook (PAS, BAB, 4T, NOR)

The shift from "about you" to "about the problem" — and the four frameworks that still work.

TLDR

You (or your agent) spent 15 minutes researching your prospect.

You found out where they went to college. You read their last three LinkedIn posts. You noticed they ran a marathon last spring. You opened your email with “Hey Sarah, saw you’re a fellow Stanford alum and just crushed a half marathon — respect!”

You sent 200 of those.

You got two replies. Both said “unsubscribe.”

Here’s the uncomfortable truth: you weren’t doing hyper-personalization. You were doing hyper-stalking and we’re sooo over it.

In 2026, the game has changed in ways most founders haven’t caught up to. AI flooded inboxes with “personalized” emails that all start the same way — your name, your school, your recent post, your job title. Prospects got so numb to this pattern that their brains filter it out in under two seconds. Faster than you can say “I hope this finds you well.”

Which it doesn’t. Because that line is dead.

I’ve talked about this before — the shift isn’t from low-effort to high-effort. It’s from about you to about the problem.

The single insight that separates the 4% reply rates from the 0.4% ones: the prospect doesn’t care about you knowing some facts about them. They don’t care about your company, your funding, or your story. They care about one thing — is this person (you) aware of the exact problem I’m fighting right now?

That’s it. That’s the whole game.

Nobody needs more people “to know” them, but we all need someone to solve our immediate problems.

New personalization is a “problem”, not a person

Old personalization: “I noticed you went to MIT.”

New personalization: “Most SaaS teams scaling past 50 people watch their onboarding completion rate fall off a cliff. Usually around the time they stop doing white-glove demos.”

The second message is personalized to their reality, not their résumé. I didn’t need to stalk their LinkedIn to write it. I needed to understand (or guess) their situation enough to name the pain they’re living.

This is the difference between mentioning someone’s marathon and knowing exactly what mile they hit the wall.

The prospect reads that second message and (hopefully) thinks: this person has been inside companies like mine. That thought — that split-second recognition — is worth more than a thousand correctly spelled names.

Share

What a good cold message actually looks like in 2026

Short. Shorter than you think. Under 100 words is an ideal, not a limitation.

Here’s the anatomy:

You open with the problem. Not “I saw that you...” — the problem itself. State it like a doctor names a symptom. Precise. No warm-up.

Then you briefly make the cost of that problem visible. Not in an aggressive way — just enough to confirm you understand the stakes. One sentence. Maybe two.

Then you connect it to an outcome or a question. Not a 30-minute demo request. Something almost frictionless: “Worth a look?” or “Is this on your radar for Q2?”

This simple structure is enough. Problem → Stakes → Low-friction ask (PAS).

The PAS framework (it's official name) — Problem, Agitate, Solve — has been around for decades for a reason. It works because it mirrors how human decision-making actually functions.

We notice pain before we notice opportunity. We act to escape discomfort before we act toward reward. Any message that leads with your solution before establishing the problem is asking the prospect to care about an answer before they’ve felt the question.

The 4 cold outreach frameworks that still work in 2026

There’s no single best framework. There’s the best framework for the specific situation. If you only master PAS, you’ll be fine. But let’s expand your horizons.

PAS — Problem, Agitate, Solve

What it is: Name the problem, show what it costs, offer the fix. Use it when the prospect already knows something’s wrong but hasn’t made it a priority.

When to use it: Warm-ish ICP, mid-market buyers, known pain. You’re not educating — you’re reactivating urgency.

Here’s what that looks like in practice. Say you’re selling a team knowledge management tool — something like Fibery — targeting an engineering lead at a 40-person SaaS company. The wrong message looks like this:

“Hey Marcus, saw you’re leading engineering at Acme and just shipped your v2 — congrats! I’m reaching out because we help teams like yours stay aligned. Would love 15 minutes to show you what we’ve built.”

That’s about Marcus. Marcus does not care about Marcus in the context of his inbox. He’s drowning. The right message looks like this:

“Most eng teams past 30 people hit the same wall: decisions get made in Slack, rationale never gets written down, and six months later nobody knows why the architecture looks the way it does. The new hire onboarding cost alone is brutal. Fibery connects the decision trail from product spec to code. Worth a look?”

Same product. Same prospect. Completely different nerve. The second message works because Marcus reads it and thinks: someone has been inside teams like mine . That thought takes less than three seconds to form. That’s your entire window.

BAB — Before, After, Bridge

What it is: Paint the before state, paint the after state, name the bridge that connects them. Best when your product creates a visible transformation.

When to use it: The contrast between before and after is dramatic enough to make someone stop scrolling. Think automation, efficiency plays, time-savings.

Before: “Right now, your SDRs spend 40% of their time on manual data entry.” After: “In six weeks, that number is zero, and they’re back on the phone.” Bridge: “We built the connection layer that makes that switch.”

BAB is a movie trailer for your product. Use it sparingly, use it well.

4T — Trigger, Think, Third-party, Talk (Josh Braun)

What it is: A real trigger event + a reframing question + a third-party credibility point + a soft ask to talk. Sophisticated, slower to write, higher reply rates on big-ticket deals.

When to use it: Large deal size, sophisticated buyer, a real observable signal you can point to (funding round, new hire, product launch).

You need a trigger — a real, observable signal that this is the right moment (a funding announcement, a new hire, a product launch). Then a think — a question that reframes their current approach. Not “do you have this problem?” but “most teams that do X end up hitting Y — have you run into that?” Then a third-party credibility point: a company they’ve heard of that faced the same thing. Then a soft talk — are you the right person to decide on this?

This framework takes work. You can’t fake the trigger. But for the deals worth fighting for, 4T gets meetings that PAS can’t.

NOR — Needle, Outcome, Request

What it is: What specific metric are you moving? What does moving it mean for their business? What’s your ask? Forty words. Maybe forty-five if you need a breath.

When to use it: High-volume outreach, agent-run sequences, automated DMs. Built to survive AI spam filters because it reads like a human who respects the prospect’s time.

Which, if you’re thinking about it correctly, is exactly what it is.

Share

Cold outreach is not just email

This is the part many founders also miss.

In 2026, cold outreach lives across every asynchronous channel where your prospect already spends their working day. LinkedIn DMs still get higher reply rates than cold email for B2B — but it’s changing quickly. Slack communities, Discord servers, and even WhatsApp broadcast lists have become legitimate outreach channels for the right verticals.

The rule doesn’t change. The medium and the channel does.

A cold LinkedIn DM that opens with “I loved your recent post on...” gets ignored. A cold LinkedIn DM that opens with “Most growth teams I talk to are seeing their LinkedIn CPL go up 30% this year while their email lists decay — is that pattern showing up for you?” much more likely gets a reply.

The channel is just the pipe. The problem-first message is the water.

What’s changed operationally: Your technical setup now matters as much as your copy. In email, if you’re sending from your primary domain ( yourcompany.com), you’re already behind. Secondary domains ( getcompany.com, trycompany.io) keep your sender reputation clean while you’re in the testing phase. Your SPF, DKIM, and DMARC records need to be configured correctly or you’re landing in Promotions before anyone reads a word. Gmail and Outlook have hardened their filters significantly. Infrastructure is table stakes.

Agents change the game (without changing the rules)

AI sales agents can now research prospects, identify trigger events, write first drafts, and send messages across multiple channels simultaneously. That sounds like a distribution advantage. And it is — but only if the underlying message is right.

Here’s where many make the mistake: they automate the old playbook. They build agents that scrape LinkedIn for profile details and plug them into templated “personalized” intros. What they’ve built is a faster way to be ignored at scale.

The right way to think about agents in outreach: they should be doing the research legwork that surfaces real triggers — a company’s recent pricing change, a job posting that signals a strategic shift, a product launch that creates a new problem they’re now facing.

The agent’s job is to find the signal. Your job is to turn that signal into a problem statement the prospect recognizes as true.

A well-built agent running a 4T framework — with a real trigger, a real reframe, and a real soft ask — can outperform a human SDR on volume without sacrificing the quality of the signal. The output still sounds human because the underlying logic is human. The agent is doing the detective work. You’re providing the insight about what the clues mean. And the agent can improve itself — and even the frameworks it’s using — as it goes.

What I think is the winning motion in 2026:

You’re not automating personalization — you’re automating trigger identification so you can personalize around problems that are actually live.

And you should always, always, always review any message before it gets sent out en masse.

The cocktail party test (I like it a lot)

Before you send anything — email, DM, Slack message — read it out loud.

If you wouldn’t say it to a person standing next to you at a professional event, it’s not good enough. Delete it. Rewrite it. The words you use with a real human at a real event are the words that work now.

The English grammar and polite blabla they taught you at school is over.

“I hope this finds you well” — would you say that at a party? No. You’d say: “Hey, I keep seeing teams in your space struggle with X. Is that something you’re dealing with?”

See the difference? Feel the difference? That’s what you can send.

Builder’s takeaway

If you’re a founder doing your own outreach right now — or building an agent to do it — here’s your operating framework:

Pick one ICP segment. Understand their world deeply enough to name three specific problems they’re living with right now. Not hypothetically, but right now, in Q2 of this year.

Write one problem-first message for each. Keep each under 80 words. Don’t mention your company name until the second message. Choose the channel where they actually have their attention — LinkedIn before email if you’re in B2B SaaS, Discord or Slack if you’re in developer tooling, email if you have a warm signal, etc.

Test your messages. When a message gets a reply, ask yourself: what did they recognize? That’s the nerve you found. Go back and make the next message hit that same nerve harder.

The founders who win outreach in 2026 aren’t the ones with the best product. They’re the ones who can make a stranger feel most understood in forty words.

That’s not a sales skill. That’s a writing skill. And it’s learnable.

FAQ

What is the PAS framework?

PAS stands for Problem, Agitate, Solve. You lead with the problem the prospect is living, briefly make the cost of that problem visible, then connect it to an outcome or a low-friction ask. It mirrors how humans actually decide — pain first, solution second.

Is cold email dead in 2026?

No. Hyper-stalking intros are dead. Problem-first messages still work — they just have to sound like a human at a cocktail party, not a VA reading off a LinkedIn profile. Reply rates of 4%+ are still achievable when the message names a real, live problem.

How long should a cold email be in 2026?

Under 100 words is the ideal, not a limitation. 40–80 words for high-volume sequences (NOR). Longer is almost always worse. If you can’t state the problem, the stakes, and the ask in that range, your thinking isn’t sharp enough yet.

Which cold outreach framework should I use?

Is personalization still worth it?

Yes — but redefine it. Don’t personalize to their résumé (school, marathon, last post). Personalize to their reality — the problem they’re living with right now. That’s what gets read.