If you're selling something that every competitor in your market also sells - the same software, the same service, the same solution - cold email feels impossible. Your prospect's inbox is flooded with identical pitches from 10 other companies. Your product doesn't have a unique angle. Your margin is thin enough that outbound feels like a luxury you can't afford.

Here's the problem: you're trying to win on product differentiation when you should be winning on insight.

Commoditized products are actually some of the easiest to sell with cold email, but only if you stop selling the product and start selling the result. This post breaks down exactly how to do it.

The Core Problem With Commoditized Product Cold Email

When your product is commoditized, your prospect doesn't care about features. They care about one thing: "Will this solve my problem better or cheaper than what I'm already using?"

Most cold emails for commoditized products fail because they lead with the product. They say things like: "We offer web development services with a 48-hour turnaround." Or: "Our CRM integrates with Salesforce and HubSpot." Or: "We're a digital marketing agency specializing in paid ads."

Your prospect has heard that pitch 47 times this month. It doesn't land because it doesn't answer their real question: "Why should I care? What's different about you?"

The solution is to lead with a specific observation about their business, not your service. This works because insight sells better than features every single time.

The Framework: Start With a Specific Business Observation

Instead of opening with what you do, open with something you noticed about their business that most competitors miss. This can be based on publicly available information - their website, recent news, their LinkedIn activity, or their tech stack.

The observation has to be specific enough that it could only apply to a narrow group of prospects. Generic observations don't work. "Your company is growing fast" applies to 100,000 companies. "You're a SaaS company using Stripe but your checkout drop-off rate is 8% higher than the industry average" applies to maybe 50 companies - and all of them will read that email.

Here's what a specific observation looks like for a web development agency selling to mid-market e-commerce companies:

I noticed you've been running the same Shopify theme for 3+ years. Most stores that do that end up with 2-3x slower checkout experiences than newer builds, which usually costs about $50-80k per month in abandoned orders.

That's specific. It's not about the agency's process or team or experience. It's about a concrete business problem and a concrete cost attached to it. A prospect reading that will either think "That's not us" or "Wait, how did they know that?"

The observation doesn't have to be negative. It can be positive too:

I saw you just launched three new product categories in Q1 alone. That's aggressive. Most teams scaling that fast either hire 2-3 more full-time devs or they use an agency. Curious which direction you're leaning.

Both of these openings work for commoditized services because they prove you actually looked at the prospect's business. You're not mass-blasting. You did 30 seconds of research. That alone puts you ahead of 95% of the competition.

How to Turn an Observation Into an Actual Meeting Request

An observation by itself isn't enough. You have to connect it to a next step. Here's the full email structure that works:

1. The Observation (2-3 lines) - What you noticed about their business.

2. The Implication (1-2 lines) - What that observation likely means for them.

3. The Soft Question (1 line) - A low-pressure ask that invites conversation, not a sales call.

Here's a complete example for an IT services company selling to mid-market manufacturers:

I noticed you're still running on-premise servers for your main production database. Most manufacturers your size are either getting hit with unexpected maintenance costs or they're overstaffing IT to keep up with it. Wondering if you've looked at hybrid approaches, or if on-prem is locked in for compliance reasons?

Notice what this email does: it doesn't mention the IT company at all. It doesn't say "We provide managed IT services." It doesn't offer a free consultation or a discount or a demo. It just asks a question that moves the conversation forward. The prospect either answers the question (which means they're engaged) or they ignore it (which means they're not a fit).

The soft question is critical. Replace "free consultation" and "let's discuss" with actual questions about their business. "Are you managing that internally or working with a vendor?" or "How are you thinking about scaling that?" or "Did that decision come from the ops side or the finance side?" These invite actual responses instead of just declining your offer.

The Specificity Problem: How to Find These Observations at Scale

The challenge with this approach is finding enough specific observations to justify a cold email campaign. You can't personalize 500 emails with hand-researched observations - that takes forever.

Here's what works: identify 3-5 common business situations that your ideal customers face, then create observation templates for each one.

For example, if you're a web development agency selling to e-commerce companies, your templates might be:

Now instead of researching every prospect individually, you're identifying which template category they fit into, then writing variations on that template. This lets you scale the approach to 100-200 prospects per week without it feeling templated.

The key is to make each email feel like it has a specific observation, not a category. So you don't say "I see you're using Shopify." You say "I noticed your Shopify store hasn't been updated since 2021 based on your code quality and checkout flow." Same template structure, but it feels specific because it has one concrete detail.

Response Rates You Should Expect

With observation-based cold email for commoditized products, you should be targeting:

These numbers assume your list is tight (targeting the right companies), your observations are actually specific, and you're following up properly. If your reply rate is below 6%, your observations aren't specific enough or your list is too broad. Fix that before scaling.

Why This Approach Works for Commoditized Products Specifically

Commoditized products are competitive on price and features, so the prospect's decision usually comes down to execution and trust. When you lead with an insight about their business, you immediately establish that you understand their world better than the generic competitor who just listed features.

This approach also filters your list naturally. If a prospect doesn't care about the specific observation you've made, they're probably not a good fit anyway - which saves you time on unqualified conversations later.

The final piece is following up correctly. Follow-up cadence matters more for commoditized products because prospects are busy and they're comparing you to other options. Your first email plants the seed. Your follow-ups need to add new information or new reasons to care, not just repeat the same pitch.

The Gap Between Knowing This and Doing It at Scale

Everything in this post is doable independently. But there's a real gap between understanding this framework and actually running it well.

You need to identify the right prospect list (not too broad, not too narrow). You need to research enough observations per prospect to feel specific without taking forever. You need to write the copy consistently. You need to manage deliverability so your emails actually land in inboxes. You need to handle replies the same day because commoditized products move fast. You need to follow up the right number of times without being annoying. You need to track what's working and adjust it weekly.

Most service businesses and agencies try to do this in-house and end up managing 20% of the process, then wonder why they get 2% reply rates. If you want to move past knowing this framework and actually run it at scale with the infrastructure to support it, that's where dedicated outbound teams come in.

Related Guides