Your Outreach Stack Isn’t Broken. It’s Just Bleeding You Dry.

I’ve audited the GTM stacks of more sales teams than I can count, and the pattern is almost always the same. They know the contract line for Outreach or SalesLoft. They don’t know the actual math.

A typical legacy stack runs $300–500 per user per month (that’s just the software). Then there’s the integration hell: hidden costs to make tools that weren’t designed to talk to each other actually work, custom consulting hours to keep it from breaking every quarter. If you have 8–15 SDRs, you’re probably spending $4,000–8,000/month on tooling alone, before accounting for the human hours filling the gaps.

But the real cost isn’t the tools. It’s what the tools don’t do.

Your SDRs spend only 25% of their working hours actually selling. The other 75%? Manual research. Data entry. Logging calls. Chasing down enrichment that should have been automatic.

With a legacy stack, an SDR runs 104 activities per day and lands a real conversation from maybe 18% of them. That is expensive guessing dressed up as a pipeline engine.

You can’t hire your way out of this problem. SDR turnover runs 30%+ industry-wide — some mid-market companies see 55%. Your reps stay 14–18 months on average. After a 3-month ramp, you’re getting barely a year of actual productivity before the replacement cycle begins.

Replace one SDR? $100K–$160K all-in (salary, benefits, stack costs, training, lost productivity). Do that twice a year on a team of six and you’re spending $200K–$320K just to maintain baseline.

Here’s what I see consistently: leaner, newer companies are running smaller outbound teams and generating more pipeline - because their people aren’t doing the data work. Your team is still staffing the workflow. You’re not losing on strategy. You’re losing on how much of your payroll actually touches a prospect.

Mid-market companies locked into legacy infrastructure have to hire 2–3x more headcount to generate the same pipeline volume as teams running modern AI outbound tools. You’re not overstaffed because your people are weak, rather because your tools are inefficient.

The cost of staying isn’t the monthly bill. It’s the headcount you can’t redeploy. It’s the velocity you’re losing because iteration takes months instead of weeks. It’s the talent you’re burning because nobody wants to spend their day logging calls.

If you’re still running manual list-building + a decade-old sequencer in 2026, your leaner competitors aren’t.

WHAT YOUR LEGACY STACK IS ACTUALLY DOING TO YOU

Built for a Different Era (Now It’s Quietly Throttling Your Growth)

The infrastructure you’ve got made sense when you built it. Maybe 2008 or 2015. At the time, it was the right call, and honestly, getting any repeatable process in place was an upgrade over the chaos that came before it. I’ve seen what pre-process outbound looks like. Your old stack was a genuine step forward.

The problem is what it can’t do now.

The typical mid-market setup: A CRM as your source of truth, Outreach or SalesLoft as your engagement layer, maybe Apollo or ZoomInfo for enrichment, and a lot of human labor gluing it all together. No workflow automation between tools. No AI prospecting layer. No intent signals. Just good people doing slow work.

It breaks for three specific reasons:

First: Research is a bottleneck. Someone manually hunts through LinkedIn, job boards, company websites, news. They stitch together what they can from Apollo or ZoomInfo. Fifteen to twenty minutes per prospect. Multiply that by 50–100 prospects per SDR per week. That’s 12–30 hours of pure research time — and you still end up with gaps. Missing job titles. Incomplete tech stack data. No signal about what’s actually happening at that account right now.

Second: There’s no outbound automation layer. Each step requires a human decision and manual input. Research done? Enrich manually. Enrichment complete? Write the message. Schedule follow-ups. Log it. Each handoff is a friction point. You can’t test a new ICP segment in a week. You can’t run a targeted campaign without a month of planning. Your velocity is capped by how fast humans can move data.

Third: Deliverability is a problem hiding in plain sight. Legacy stacks don’t come with native IP warm-up, DKIM/SPF/DMARC configuration, or domain rotation logic. Gmail placement dropped from 89.8% (early 2024) to 87.2% by Q4 as spam filters tightened. Weak authentication can cause an 80% delivery drop.

The deeper issue: these tools were built for control, not leverage. At 5 SDRs, fine. At 15, you’re choking. At 25, you’re hemorrhaging productivity and wondering why you need to keep hiring just to stay flat.

The teams that stay on legacy stacks assume the answer is “get better people.” The teams rebuilding with AI outbound automation assume the answer is “get better infrastructure.” Guess which one scales.

THE MODERN AI OUTBOUND STACK

What Actually Works — Without Ripping Everything Out

The modernized outreach setup isn’t about chasing AI hype. It’s about efficiency: tools that talk to each other, AI handling the grunt work, and your people doing the thinking. When I build these systems for mid-market teams, I think in four layers — each with one job.

Subscribe now

Layer 1 — AI Prospecting + Enrichment: Tools like Clay, Apollo (upgraded tier), or Smartlead. The job isn’t “build a list faster.” It’s “reduce human research time from 20 minutes per prospect to 2 minutes.” You define the criteria — title, company size, tech stack, buying signals — and the system returns verified matches with context. Not a list. A qualified hypothesis about where your buyer actually is.

This is where AI prospecting automation does its heaviest lifting. Instead of an SDR manually hunting for 20 minutes, a custom workflow pulls, enriches, and scores each prospect before a human ever touches it. I build these as tailored Clay or n8n workflows — configured to your ICP, your signals, your CRM. Not off-the-shelf. Built for how you actually sell.

Real numbers: teams using modern AI research tools report 40–60% reduction in research time per prospect. That frees up 10–15 hours per SDR per week.

Layer 2 — Delivery + Inbox Reliability: Instantly, Lemlist, or your existing sequencer upgraded with proper authentication and warm-up. The job is getting emails into the inbox reliably — not just sending them. Modern tools handle DKIM/SPF/DMARC setup, domain rotation, and IP warm-up so your reply rates don’t crater. Legacy tools leave this to chance.

Modern AI outbound infrastructure maintains 87–90% inbox placement. That’s 12–15 percentage points better than an unmanaged legacy setup — before you change a single word of your messaging.

Read more

There. I said it.

(Yes, I know. Very brave. Please alert the innovation police.)

Right now, the market is having one of those deeply spiritual technology moments where every normal business process suddenly needs to become “agentic.”

Customer support flow? Agent.

Sales research workflow? Agent.

Internal reporting? Agent.

Someone renamed a Zapier automation with an LLM step inside it? Apparently also an agent.

Very powerful. Very futuristic. Very webinar-friendly.

But what’s actually happening in many companies is much less cinematic.

A lot of “AI agents” being deployed in real businesses are just automations with an LLM stapled on top and a more expensive name.

Because apparently “workflow automation” doesn’t get invited to the cool kids’ table anymore.

But “agentic infrastructure”?

Now we’re cooking. Now we have a category.

The Boring Stuff Is Working

The companies quietly getting real value from AI are usually not deploying some magical autonomous goblin that thinks, plans, reasons, files your SOC 2 evidence, and saves Western civilization before lunch.

They’re doing boring things well:

They’re cleaning up repetitive workflows.

Reducing manual work.

Speeding up internal processes.

Keeping humans in the right places.

Making sure someone can audit what happened.

Disgusting, I know. Actual business value.

And this is where a lot of the agent hype starts to wobble.

Because once you move past the demo, the question is not:

“How autonomous can this be?”

The better question is:

“Does this need autonomy at all?”

Most of the time, the answer is no.

Subscribe now

The Expensive Agent Problem

I keep seeing the same pattern.

A founder spends serious money on a “next-gen AI agent” that sounds incredible in the pitch deck.

It can reason.

It can plan.

It can adapt.

It can make decisions.

It can probably write a poem about your pipeline if you ask nicely.

Then it enters the real world and immediately starts behaving like a Roomba in a room full of cables.

It burns tokens like a yacht burns fuel.

It breaks the second a customer behaves like a customer.

It becomes difficult to test, hard to audit, and almost impossible to explain clearly when someone asks the tiny, annoying question:

“So what exactly does this thing do?”

And that question matters.

Especially if you’re building inside a company where compliance, risk, security, or customer trust are not decorative LinkedIn words.

Regulated SaaS Makes This Even Funnier

In regulated SaaS, the agent conversation gets especially entertaining.

HIPAA and SOC 2 reviewers do not want a TED Talk about emergent reasoning.

They want the boring stuff:

What happens?

In what order?

Under what controls?

Where are the logs?

An automation can survive that conversation.

An agent often turns it into a six-month compliance escape room with worse lighting.

And this is not because agents are inherently bad.

It’s because autonomy adds uncertainty.

Uncertainty adds review time.

Review time adds cost.

Cost adds meetings.

Meetings add spiritual damage.

Very simple chain of events.

My Rough Rule

Here’s how I’d think about it.

Clear workflow?

Use automation.

High cost of error?

Use automation.

Compliance review?

Use automation. Twice. Drink water.

Unpredictable inputs, branching decisions, and actual judgment required?

Maybe you need an agent.

Maybe.

That’s the part the market keeps skipping.

Agents are useful when the workflow genuinely requires dynamic reasoning, adaptation, and decision-making.

But many business workflows do not.

They require consistency.

Controls.

Speed.

Visibility.

Repeatability.

Logs.

Basically all the words that make Twitter fall asleep but make operators quietly nod.

The Trend Says “Make Everything Agentic”

The trend says:

“Make everything agentic.”

The operator in me says:

“Maybe don’t attach a flamethrower to the toaster.”

Because autonomy is not automatically maturity.

Sometimes autonomy is just chaos with better branding.

And sometimes the smartest AI system is the one that does the boring thing reliably and shuts up.

That doesn’t sound as exciting.

It probably won’t get 4,000 likes from people who say “the future of work” five times before breakfast.

But it might actually work.

The Market Is Getting Smarter

I think the first wave of AI adoption was mostly curiosity.

What can we automate?

What can we generate?

What can we replace?

What can we call an agent before someone notices it’s a workflow with a fancy hat?

The next wave is different.

The founders and operators who got burned are asking better questions now.

Not:

“How do we use agents?”

But:

“What actually needs autonomy here?”

Where do we need judgment?

Where do we need reliability?

Where do we need a human in the loop?

Where do we need auditability more than cleverness?

Where is an LLM useful?

And where are we just adding a very expensive raccoon to a process that was already fragile?

That’s the discussion worth having.

Not whether agents are good or bad.

But where they actually belong.

Because most companies don’t need more AI theatre.

They need systems that work when nobody is watching the demo.

And right now, a lot of the value is still hiding in the boring automations.

Which is unfortunate, because boring doesn’t trend.

But it does ship.

So I’m curious.

What’s actually working for you right now?

And what keeps breaking the moment it leaves the demo?

No surprise there, because AppSec is a multi-billion-dollar market …

Read more

I’ve worked with early-stage teams across different pricing motions - some PLG-first, some API-based, some open-core. And here’s the pattern that keeps coming up: the pricing model you pick in the early days doesn’t just shape your revenue—it shapes your runway, your roadmap, and your reputation with buyers.

Especially if you’re playing in the AI or developer tooling space, where copying functionality is trivial and infra costs rack up before your Stripe account does.

More than once, I’ve seen open-source become a trap. A team gives away too much for adoption, and when it’s time to sell into enterprise, they realize those companies are already using the free version—and have zero interest in paying for “upgrades” they’ve already hacked around.

That’s not a GTM problem. That’s a pricing blind spot.

If you’re not thinking about monetization from day one, you’re not building a product—you’re subsidizing someone else’s.

The good news? You’re not stuck.

Pricing isn’t a one-time bet—it’s a lever you get to design, test, and evolve. But it has to be intentional.

You can’t just copy Stripe’s tiers, slap on “Pro” and “Enterprise,” and call it a day. (Unless your business model is confusion.)

What follows isn’t a pricing formula. It’s a stack of real strategies I’ve seen work—especially for teams building in the wild world of PLG, AI, and open-source. Pick what fits. Combine where it clicks. And if all else fails, at least you’ll have a better plan than “We’ll figure it out after Series A.”

10 Pricing Strategies That Don’t Suck (Even If You’re Open Source, PLG, or Shipping AI Wrappers)

Pricing isn’t just about revenue. It’s positioning. It’s funnel design. It’s survivability. And in the AI era, where copycats move faster than your Notion updates, you need pricing that does more than look good in a pitch deck.

Here are strategies that can actually work—especially for founders juggling open-source traction, PLG growth, and high infra costs.

Let’s go deeper into the first three, because they’re often the deciding factor between “dev love” and “burnout at scale.”

Share this post with a founder or dev team still figuring out their pricing strategy.

1. Infra-Tiered Pricing

💡 TL;DR: Price based on what actually costs you money - tokens, GPU time, API calls, minutes of video generated.

It’s not sexy, but it’s sustainable. You don’t need to explain features - you just need to not go broke.

🔍 What this solves:

• Prevents free users from tanking your infra bill

• Aligns pricing with real usage (and value delivered)

• Lets you be generous without being reckless

🧪 Real Example (OpenAI):

• You get a few dollars of free usage.

• After that? You pay by token, per model tier.

• No confusion. No surprises. Just: use more → pay more.

[OpenAI’s pricing page with GPT-3.5 vs GPT-4 token tiers]

🧠 Pro Tip:

Don’t charge for features. Charge for the output. If your user sends 2M tokens through your orchestrator, that is the moment of value.

2.Feature vs Control Split

💡 TL;DR: Open-source the engine. Monetize the dashboard, monitoring, role controls, alerts—anything a team needs to stay sane.

🔍 What this solves:

• Devs get to explore and use your tool freely

• Teams, companies, and enterprise buyers still have reasons to upgrade

• You don’t have to cripple your OSS to monetize

🧪 Real Example (Langfuse):

• OSS covers core LLM observability logic

• Hosted version adds role-based access, dashboards, team workflows

• Paid tiers kick in for collaboration and scale

Check out Langfuse pricing page showing open-core vs hosted features

🧠 Pro Tip:

Don’t put login buttons behind the paywall—put control behind the paywall. Give usage. Charge for governance.

3. Dev Team vs Org-Based Plans

💡 TL;DR: Not every user is worth the same. Solo devs ≠ startup teams ≠ enterprise security buyers. Don’t price them like they are.

🔍 What this solves:

• Reduces friction for early adoption

• Encourages small team upgrades organically

• Creates logical upgrade moments without sales calls

🧪 Real Example (Replit):

• Solo devs build for free

• Add team features? Need a Pro or Team plan

• Seamless growth from individual → team → org

Screenshot: Replit’s pricing table

🧠 Pro Tip:

Set limits by project, collaborators, or integrations—not just usage. Most users don’t care about tokens, but they do notice when they hit “Add Member” and can’t.

Should I start with a free plan or go premium from day one?

In my experience: if you’re building a technical product—especially in devtools, infra, or AI - you do need to give some stuff away. But not because freemium is trendy. Because awareness is expensive, and distribution is brutal. Free earns you usage. Usage earns you feedback. And feedback earns you credibility.

But here’s the catch: free can’t be forever. And it definitely shouldn’t be everything.

The smartest early-stage teams I’ve worked with treat “free” like a channel, not a pricing model. They make sure what’s free is:

• ✂️ Trimmable later (no core infra costs or entitlements you’ll regret)

• 🎯 Targeted at the right persona (not random tire-kickers)

• 🚪 Directional toward conversion (with natural upgrade moments)

For example: you might give away self-hosted access or a basic agent config builder—but gate the hosted control plane, team collaboration, premium model access, or enterprise integrations.

Think of your free tier as top-of-funnel UX, not a gift. It should earn its keep by qualifying users, teaching them your value, and pointing them toward the plan that actually pays your GPU bill.

Each strategy includes:

🎯 Who it works for

🧪 Detailed real-life use case

📸 Visual example with screenshot prompt

🧠 Includes: Notion pricing planner, AI calculator sheet, OSS monetization matrix, and more.

Read more

Let’s be honest: the hardest part of early-stage marketing isn’t “what channel should I use?”

It’s:

• What the hell do I say?

• Who actually cares?

• And how do I test that yesterday, without sounding like a try-hard on LinkedIn?

I’ve been there — on both sides. As a fractional CMO and growth partner, I’ve worked with early-stage teams where the funnel looked more like a fog machine. Endless noise, no direction. And when I say “growth plan,” I don’t mean spending two weeks renaming Notion folders.

If you’re building something new and searching for traction, you don’t need another 45-tab Miro board.

You need signal. You need structure. You need speed with a spine.

That’s what these frameworks are for.

What these frameworks actually help with

I’ve spent years helping technical founders turn “we built a thing” into “we’re getting users.”

These five frameworks are my response to all the fuzzy funnel moments I’ve had to fix — too much content, wrong message, great product, zero pull.

Each one is designed to help you:

• Find early traction (not just “create content”)

• Say sharper things in smarter places

• Use speed strategically, not chaotically

If you’re trying to get your first 100 users, build narrative clarity, or stop reinventing your positioning every time you write an email — you’ll want to bookmark this.

Let’s break them down.

TL;DR: You don’t need a massive team — you need the right systems and someone to help you run them

I work with early-stage founders to cut through the noise, sharpen messaging, and launch fast GTM experiments that don’t die in Notion.

In this post, I’m sharing five AI-powered frameworks I use to help you find early traction without hiring a full marketing team or spinning in strategy loops.

1. SCOPE – Quickly turn market signals into testable campaigns with messaging, offers, and channel focus

2. The Alignment Flywheel – Keep your story tight across all touchpoints, even as you move fast

3. Message Engine – Test value props and sharpen narrative before committing to a full relaunch

4. Content Barbell – Balance SEO and social with one idea → many outputs (without burnout)

5. The Traction Stack – Run structured growth tests that actually scale instead of random tactics

You don’t have to do this alone. I bring the structure, the systems, and the speed — so you can focus on building.

1. SCOPE – AI-Powered Campaigns That Don’t Waste 3 Months

Let’s say you’re pre-traction.

You’re staring at a blank doc titled “launch campaign.” You’ve got vague buyer personas, a gut feeling about Reddit, and 20 half-baked content ideas in a Notion graveyard.

SCOPE is the framework I use to build actual campaigns that ship fast, sound sharp, and aren’t pulled out of thin air.

It stands for:

Signals · Content · Offers · Placement · Execution — and AI plugs into every part.

What problem it solves:

You’re not sure what message to lead with, what offer to pair it with, or where to test it.

SCOPE gives you a way to structure all of that in one repeatable loop.

How AI helps:

• Finds early signals (complaints, questions, trends) across Reddit, Hacker News, YouTube comments, forums

  → Tools: Octolens, GummySearch, Perplexity, Glasp, Hacker News search

• Distills market language from transcripts, tweets, or reviews

  → Tools: Claude, ChatGPT, Fireflies.ai, Fathom

• Drafts fast variations of hooks, explainer copy, ad headlines

  → Tools: Custom GPTs, Copy.ai, Jasper

• Suggests offer ideas from trends (e.g. “everyone’s asking for [X], give them a checklist”)

  → Tools: ChatGPT, Airtable for clustering

• Rewrites content per channel — so your cold email doesn’t sound like a blog post

  → Tools: ChatGPT + Typefully / Taplio

• Automates campaign setup

  → Tools: Zapier, Notion, Airtable templates

Use case: A 3-months brand campaign now takes a week — with more creative variation.

If you want the full step-by-step behind how I run SCOPE in real founder workflows — I share the deep dives, templates, and system breakdowns inside the paid newsletter. Worth it if you’re building for speed and signal.

2. The Alignment Flywheel – Keep Your Messaging From Falling Apart

The faster you build, the messier your messaging gets.

One week you’re promising speed. Next week, your product page leans into security. Your emails sound like a SaaS founder, your ads like a self-help coach. No one’s on the same page — because there is no page.

The Alignment Flywheel keeps your message consistent across channels as you scale.

It helps you turn raw insight into reusable message blocks, push those across touchpoints, and evolve your story without rewriting your positioning doc every two weeks.

How AI helps:

Extracts repeated themes from calls, support convos, Slack threads, and demos

→ Tools: Claude, ChatGPT, Fathom, Fireflies.ai

Rewrites your core narrative for different personas, channels, or tones

→ Tools: Custom GPT, Jasper, Notion AI

Audits message drift by comparing what’s working vs. what you’re actually saying across your funnel

→ Tools: Claude, ChatGPT, Loom transcripts, landing page crawlers

Remixes messaging across assets like outbound, onboarding, and paid campaigns

→ Tools: ChatGPT, Taplio, Typefully, Copy.ai

Organizes message blocks into a single source of truth

→ Tools: Notion, Airtable, Coda, Supernormal

What problem it solves:

You’ve got traction, but the story isn’t scaling with you. This framework helps you stay clear, consistent, and aligned — without slowing down.

Want to see how I run this with early-stage teams? The paid newsletter includes a breakdown of how I structure messaging hubs, run async audits, and keep everyone saying the same sharp thing.

3. Message Engine – Sharpen Fast, Test Faster

You’ve got five versions of your value prop, and your team can’t agree on which one actually makes sense. Meanwhile, your website says one thing, your cold emails say another, and your latest deck starts with “We’re revolutionizing…”

Read more

Most are just… calendars in disguise.

The startup default is to build a funnel that looks clean on a slide, tracks “awareness → revenue,” and gets updated every Tuesday at 10 a.m.

But ask anyone what it’s actually telling them, and the answers get foggy. Fast.

Because most funnels don’t generate signal.

They just create motion. Meeti…

Read more

“The future is there... looking back at us. Trying to make sense of the fiction we will have become.” — William Gibson

Everyone’s got their hot take on AI.

Most of them are noise.

On one end, there’s the productivity porn: “I built an AI empire in 72 hours using ChatGPT and 14 Chrome extensions.”

On the other, the doomers whispering about jobless marketers and prompt-replacing overlords.

Meanwhile, the real shift is quieter — and smarter.

AI isn’t replacing marketers.

It’s redefining what great looks like.

Founders aren’t asking, “Should we use AI?”

They’re asking, “Why is our messaging still slow?”

“Why are we guessing what works?”

“Why does it take a team of five to run a funnel?”

Here’s the unlock:

They reach for it instinctively.

To test. To think. To prototype. To scale.

The AI-First marketer isn’t the person who knows the most tools.

It’s the person who knows how to think in systems, build for momentum, and ship faster - without losing the thread.

This is the inflection point:

Not AI vs. humans.

But AI as leverage — and the marketers who know how to wield it win.

Share

What Is an AI-First Marketer?

First off - no, it’s not the person sending ChatGPT “write me viral LinkedIn post” and calling it a growth strategy.

And no, it’s not your colleague who downloaded 12 AI tools and built absolutely nothing.

Being AI-First isn’t about flexing your stack. It’s about defaulting to leverage.

When a new challenge shows up, your instinct is:

“Cool. How do I loop this, automate it, scale it, or make it smarter with AI?”

An AI-First marketer is not:

• A prompt monkey cranking out SEO sludge

• A growth hacker rebranding spreadsheets as “LLM automations”

• A startup mascot who spends more time screenshotting GPT responses than shipping work

Here’s what they are:

• A systems builder with creative taste

• A marketer who can write and wire things together

• Someone who actually understands how ideas turn into motion

They can:

• Turn a messy founder rant into a narrative and a Notion workflow

• Spin up 15 ad angles using customer pain, not “brand adjectives”

• Catch GPT when it’s hallucinating — because they’ve actually read their own outputs

• Stack tools like Clay, Zapier, Notion, and GPT to build growth loops that don’t suck

They don’t worship the tools — they orchestrate them.

They don’t say “let’s test this” and then wait three weeks.

They say “brb, shipping a working draft in 10 minutes and a meme while it renders.”

AI-First marketers move fast.

Not because they’re hustling. But because their systems are.

Voices from the Fields

“AI marketing isn’t just a thing, it’s basically the future. The biggest shift I’ve seen is AI taking the guesswork out of ad performance. We’re testing AI that not only optimizes ads in real-time but also predicts which creatives will perform before we even launch them. It’s making campaign management way more efficient.”

“AI marketing tools are a full-time job to keep up with … but optimising campaigns using reinforcement learning is next-level.”

“AI will not take over digital marketing… [it] will likely redefine their roles. …Digital marketers of the future will focus more on creativity, strategy, and ethical considerations while leveraging AI for data analysis, personalization, and automation.”

“Honestly, if you’re still writing every line from scratch in 2025, you’re either doing it for the love of pain or seriously underestimating your time. […] The real skill now isn’t avoiding AI—it’s knowing when to use it and when to step in so your copy doesn’t sound like it came out of a corporate blender.”

Turns out, the AI-First marketer isn’t a mythical job title — it’s already a Reddit regular with three browser tabs open, one broken Zap, and a strong opinion about reinforcement learning. Some are automating ad campaigns like it’s NBD, others are drowning in tool fatigue, and a few are just trying to stop their copy from sounding like it was written by a well-meaning robot with zero social life. The vibe? AI isn’t replacing anyone. It’s just making it painfully obvious who’s thinking in systems… and who’s still manually updating the Monday board.

Read more

• A single roll-up banner

• A jar of branded mints

• And three people standing around like they’re waiting for their mom to pick them up

You didn’t pay $15K for “brand presence.” You paid to build pipeline and start conversations — or at least that’s what your board deck said.

So here’s a better playbook fo…

Read more

said “Every marketing channel sucks right now.”

And yeah — he’s not wrong. Everyone’s in the same inboxes, fighting over the same tired feeds, remixing the same templates from 2019. Somehow still thinking it’ll break through? That’s delulu, babe.

So the obvious question becomes: What’s left?

And if you’re like me, th…

Read more

Eventually, I started asking what many of us are …

Read more

But - beneath the noise and fake guru hype there’s a sliver of something real. When used right, AI doesn’t replace your brain. It frees it. It doesn’t generate genius. It acc…

Read more

Here are the five lessons I learned while working in hyper-growth B2B SaaS startups and managing a marketing functio…

Read more

Not investing time into detailed persona research

One area where some young companies fai…

Read more