How to Research a Shopify Store Before Pitching a Client

Most advice on how to research a Shopify store is written for the wrong moment. It tells you how to find stores, dozens or hundreds of them, for competitor research or product ideas. That's a different job from what you're doing the night before a discovery call: you already have one named store, a call on the calendar, and twenty minutes to find out what to say. This post is about that second job.

Why the usual guides don't fit this use case

Search for how to find Shopify stores and you'll get long guides on reverse IP lookups, ad library scraping, and niche directories, all aimed at surfacing new prospects from scratch. That's useful if you're building a list. It's not useful once you already have the name of a store and a scheduled pitch, because the question has changed from "which stores should I look at" to "what does this specific store need, and can I prove it."

There's also a cluster of "Shopify store audit" content, but most of it is written for the store's own team after the sale, covering page speed and code quality in a level of depth nobody needs for a first conversation. And a chunk of what ranks for "store audit" isn't even about ecommerce; it's retail-floor audit content for physical shops. None of it answers the narrower question: before you pitch this one store, what should you actually check, and how do you turn what you find into something worth saying on the call.

A research workflow for one store, not a hundred

The order below follows what you can actually see from the outside, without an account, a login, or a tool subscription. Nothing here requires guessing.

1. Confirm the platform and read the theme

Start by confirming the store is actually running Shopify and, if so, which theme. View source or a theme-detection tool will tell you whether it's a stock theme (Dawn and its variants are common defaults) or a paid or custom build. A store still running an unmodified free theme months after launch tells you something different than a heavily customized Plus storefront. If you want to skip manually digging through source code, StorePrism's theme detector reads the storefront and reports the theme directly.

Theme choice by itself isn't a verdict on the business. A store on a free theme can be doing fine; a store on an expensive custom build can still be losing money. Treat it as one data point, not the whole picture.

2. Check what apps are already installed

The app stack tells you what the store has already solved and what it hasn't. A missing email capture app, no review widget, no upsell or bundling app: each of those is a specific, checkable gap, not a guess. StoreInspect's analysis of 7,707 recently launched Shopify stores found that 87.4% had no email app installed and 75.8% had no review app, which means the absence of either is common enough that you shouldn't assume it means something is wrong, but common enough gaps to be worth confirming rather than assuming. (https://storeinspect.com/blog/how-to-find-new-shopify-stores)

A separate StoreInspect study of 8,993 Shopify stores found that in the 10,000 to 50,000 monthly traffic tier, 66% of stores lacked a review app and 94% lacked an upsell tool, and that stores on Shopify Plus carried 2.2 times more apps and 7.8 times more identifiable contacts than non-Plus stores in the same dataset. (https://storeinspect.com/blog/how-to-find-shopify-clients-for-your-agency) If the store you're pitching sits well below that app count for its size, that gap is worth naming directly in your pitch, rather than describing in general terms.

You can check this by hand by loading the storefront and watching network requests and script tags, or with an app detector that lists what's running without you having to read the page source yourself.

3. Estimate traffic and revenue tier

You won't get an exact revenue number from outside a store, and you shouldn't pitch as though you have one. What you can get is a tier: is this a store doing a few thousand dollars a month, or one that's clearly past six figures. That tier changes what you pitch and how you price it. Estimating what a store earns from public signals, not insider data, is exactly what a revenue estimator is built for, and it's worth running before you write a single line of your pitch, because a proposal sized for a store doing a few thousand dollars a month reads as tone-deaf to one that's clearly past six figures, and the reverse undersells what you're offering.

Whatever number comes back, say what it is and isn't. An estimate built from public traffic and pricing signals is a range, not a confirmed figure, and it's worth saying so on the call rather than presenting it as certain.

4. Look for Shopify Plus signals

Plus stores behave differently: more apps, more contacts, and often more complex checkout and multi-store setups, per the StoreInspect data cited above. A Plus badge in the page footer, a .myshopify.com redirect pattern, or Shopify Flow and Launchpad references in the source are all visible signs worth checking before you assume you're pitching a small independent shop. Getting this wrong, pitching a Plus operation like a five-person startup, is the kind of mistake that shows on the call.

5. Turn what you found into two or three talking points

Everything above is only useful if it changes what you say. The goal isn't a research document; it's two or three specific, checkable observations you can open the call with: this store has no review app at its traffic level, this store is still on the stock theme a year after launch, this store's estimated revenue puts it in a tier where an upsell flow would plausibly pay for itself. Each of those is a sentence you can say out loud and defend if asked how you know it.

Running this by hand, opening a site, reading source code, searching for app scripts, estimating traffic, takes real time and isn't reliable if you're doing it for more than one store a week. StorePrism's free tools pull the theme, app stack, and revenue estimate for a single storefront into one pass, so the twenty-minute version of this checklist takes closer to five.

What this research doesn't prove

A missing app doesn't mean a store is losing money, and a stock theme doesn't mean the owner hasn't thought about their site. These are signals, not verdicts. Say what you found and when you found it, not what it means for certain. A theme detector shows the theme running on the page you loaded on the day you loaded it; stores change themes, add apps, and run A/B tests, so a finding from last week's read isn't guaranteed to hold today. The honest version of a pitch says "as of this week, this store's storefront shows X," not "this store has a problem."

The same caution applies to revenue and traffic estimates. They're built from public signals like traffic and pricing, not from the store's actual sales data, so they're directionally useful for sizing a pitch and not something to quote as a confirmed number on a call.

FAQ

How long should this take before a single pitch?

Enough to check the theme, the app stack, an approximate traffic and revenue tier, and Plus status. Done by hand that's closer to thirty or forty minutes; using detection tools for each step brings it down to a handful of minutes per store.

Is it legal to research a prospect's store this way?

Everything described here, reading a public storefront's theme, watching which scripts and apps load on a public page, and estimating traffic from public signals, works off information the store is already showing to any visitor. That's different from anything that requires a login, a scrape of non-public data, or bypassing a paywall. If a specific check you're considering requires bypassing access controls, treat that as a separate question with its own answer.

What if the store shows almost nothing unusual?

That's a finding too. A store with a full app stack, a customized theme, and a healthy estimated revenue tier isn't necessarily a bad prospect, it just means your pitch needs to be about something other than "you're missing the basics." Knowing that before the call is still better than finding it out on it.

Before your next pitch

The research itself isn't complicated: read the theme, check the apps, estimate the revenue tier, look for Plus signals, and turn what you find into two or three sentences you can defend. What's hard is doing it consistently for every prospect instead of only the ones you happen to have time for. Run the Shopify revenue estimator on the next store you're about to pitch and see what tier it puts them in before you write the proposal.