How to Compete Without Trashing Competitors (and Still Win Deals)

A practical playbook for Indie Hackers selling B2B without burning bridges or sounding insecure

If you’re building a B2B product as a solo founder or tiny team, you will hit this moment:

“We’re also looking at [Big Incumbent Tool]. Why should we pick you?”

This is where a lot of founders freeze and default to one of two moves:

Bashing the competitor (“they’re bloated / slow / terrible support”), or
Listing features and hoping something resonates.

Both usually backfire. One makes you sound insecure, the other unfocused.

A better approach is simpler and calmer:
help the buyer understand the trade-offs they’re actually making.

This post walks through how to do that in a way that:

Works for solo founders and very small teams
Keeps competitive intelligence lightweight and usable
Improves trust without pretending you’re a mini-Salesforce

1. Stop thinking “us vs them,” start thinking “what’s the buyer trading off?”

When a prospect compares you to a competitor, they’re not asking you to win a debate.

They’re asking:

“Given my constraints (time, budget, team, risk), which option makes the most sense right now?”

So instead of framing it as:

“They’re bad, we’re good”

Reframe it as:

“Here’s what you gain, and give up, with each option, based on what you told me matters.”

To do that well, you need to be clear on five things for each real competitor:

Their core strength
The trade-off or cost of that strength
Your specific edge for this type of buyer
Proof that edge is real
The business impact of choosing you

You’re not attacking the competitor.
You’re clarifying the decision.

2. Use a single, central battlecard instead of scattered notes

As an Indie Hacker, the problem usually isn’t lack of competitive insight, it’s that it lives everywhere.

A bit in your head.
A few bullets in a Notion doc.
Some half-written thoughts in Slack, emails, or call notes.

That’s how competitive conversations end up inconsistent and improvised.

Instead of multiple docs or one-off notes, aim for one central battlecard per competitor that becomes your source of truth.

Not a massive deck.
Not a “competitive intelligence program.”
Just one clean, structured place where your thinking is already done before the call happens.

Why a central battlecard works better than ad-hoc notes

A single battlecard forces discipline:

You decide once how you talk about a competitor
You stop re-inventing the comparison on every call
You remove emotion and defensiveness from live conversations

For a small team (or solo founder), this matters more than polish.

A good central battlecard gives you:

Consistency – you explain the same competitor the same way every time
Clarity – strengths, trade-offs, and differentiation are obvious at a glance
Confidence – you’re not scrambling when a competitor comes up
Reusability – sales calls, website copy, emails, and decks all stay aligned

Instead of relying on memory or gut feel, you’re working from a calm, buyer-first narrative.

Where a tool like Playwise HQ helps (especially for small teams)

You can build battlecards in docs or Notion, and many founders start there.

The downside shows up as soon as you:

Add more competitors
Start refining your positioning
Want to reuse the same logic across sales, marketing, and content

This is where using a lightweight tool like Playwise HQ makes sense.

Rather than turning CI into a heavy process, Playwise HQ is designed to keep battlecards:

Centralized
Structured around buyer trade-offs (not feature lists)
Easy to update as you learn more from real deals

The free tier is particularly useful for Indie Hackers and small teams:

You can capture competitive insights as you go
Keep everything in one place instead of scattered docs
Build battlecards that are actually usable on live calls

The real benefit isn’t “more data.”
It’s less thinking in the moment, because the thinking is already done.

Your battlecard becomes:

Your mental script on calls
The backbone of “Why not just use X?” messaging
A guardrail that keeps you from slipping into competitor bashing

The tool just makes the habit easier to maintain.

3. Turn the insights you save into natural founder talk tracks

The goal isn’t to read the info loud.
It’s to sound credible and calm when a competitor comes up.

Here’s how that battlecard turns into a real conversation:

Acknowledge their strength

“Yeah, [Big Tool] is a solid platform. If you’re trying to standardize across multiple departments, that’s what it’s built for.”

Name the trade-off

“The trade-off is usually rollout time and complexity. Most teams I’ve seen spend months getting real value.”

Anchor to the buyer’s priorities

“From what you shared, your priority this quarter is fixing this one workflow and showing impact quickly.”

Position your edge

“That’s where we’re different. We’re focused on just that use case, which is why teams typically go live in about two weeks.”

Tie it to impact

“So you’re trading breadth for speed and simplicity — which tends to work better when you’re trying to prove value fast.”

No bashing.
No defensiveness.
Just adult, founder-level clarity.

4. Why this matters more when you’re small

As a bootstrapped or early-stage founder, you cannot win by playing the incumbents’ game.

You won’t out-feature them.
You won’t out-roadmap them.
You won’t out-brand them.

Your real advantages are:

Speed (shipping, onboarding, support)
Focus (one painful problem solved well)
Control (you’re not tied to platform politics)
Alignment (your success depends on customer success)

Buyer-first competitive positioning lets you:

Turn “we’re small” into a strength
Win deals without pretending to be something you’re not
Avoid building features just to keep up with a checklist

This is how small teams beat big ones without burning credibility.

5. Avoid these common Indie Hacker mistakes

When you’re emotionally invested in your product, these are easy traps to fall into.

1. Emotional competitor bashing

Saying things like:

“Their UI is awful”
“They’re impossible to work with”
“Everyone hates their support”

Even if true, it makes you look biased.

Instead: describe trade-offs calmly and let the buyer connect the dots.

2. Competing on feature count

If you find yourself saying:

“We also do X, Y, Z, and A, B, C is coming soon…”

You’re playing the wrong game.

You win by being the obvious choice for a specific buyer with a specific problem.

3. Overpromising to stay in the deal

Saying “yes” to everything just to keep up leads to:

Custom one-off features
A diluted product
Burnout

Being clear about what you don’t do — and why — builds more trust than trying to match an incumbent feature-for-feature.

6. How this shapes your product and GTM over time

Once you get serious about competitive positioning, it affects everything.

Product

You stop chasing every competitor feature
You double down on where you consistently win
Your roadmap becomes strategic, not reactive

Marketing

Your homepage answers “Why not just use X?” clearly
Your case studies focus on outcomes and trade-offs
Your content attracts the right buyers

Sales

Competitor mentions stop feeling threatening
Calls feel calmer and more confident
Buyers trust you because you help them think clearly

This is leverage Indie Hackers need:
clarity instead of scale.

TL;DR for Indie Hackers

If you’re selling B2B as a founder:

Don’t trash competitors — it erodes trust
Do keep competitive intel simple and usable
Use a one-page view: strength → trade-off → your edge → proof → impact

You don’t need to be the biggest player to win deals.

You just need to be the clearest, most honest option for the right buyer at the right time.