I was flying blind running my Shopify store. So I built the tool I wished existed — here's what happened
Six months ago, I was staring at my Shopify dashboard at11 PM trying to figure out why my revenue had dropped 30% that week. 😰
I had numbers. Lots of numbers. But zero answers.
Which product caused the drop? Which customer segment disappeared? Did I miss a peak sales window?
The dashboard just... stared back at me. 📊❓
💸 The tools that solve this cost a fortune
I looked at the tools that solve this:
🐋 Triple Whale — $129/mo
📈 Glew — $79/mo
📊 Lifetimely — $99/mo
For a store doing $5-10k/month, that's eating 1-2% of revenue just on analytics. Before inventory, ads, or anything else.
So I kept flying blind. Like most small Shopify merchants do. 🙈
🔨 Then I did something about it
I'm a software engineer by day. So I started building.
Not another dashboard with more charts — I had enough charts. I wanted something that would just tell me what to do. 🎯
I called it ShopSight.
Here's what I built in 2 weeks:
📊 Real-time revenue & order tracking
🛍️ Best-selling products with revenue breakdown
🌍 Customer geography and behaviour
🤖 AI insights (powered by Claude) that give you specific, actionable recommendations
📧 Weekly email digest so you never miss what's happening
The AI part was the key insight. Instead of showing you more data, it analyzes your store and tells you things like:
💡 "new customers, zero repeat purchases. Critical retention window closing in 7-14 days. Launch a post-purchase email sequence."
Not a chart. An action. ✅
🏗️ The build journey
Week 1: Core dashboard, Shopify OAuth, revenue tracking
Week 2: AI insights engine, customer analytics,
products page
Week 3: Payment integration hell 😅 (Stripe doesn't
work for India cross-border — switched to
Lemon Squeezy), weekly email digest, CSV export
Week 4: Bug fixes, privacy/terms pages, Vercel
deployment, custom domain
Built it solo while working full-time at a
telecom company. ⚡
Tech stack: Next.js 14, Supabase, Tailwind, Claude API,
Lemon Squeezy, Vercel.
📈 Where I am now — day 2 of real marketing
→ 👀 visitors from 5 countries
🇺🇸 🇳🇱 🇵🇱 🇸🇪 🇮🇳
→ 🔗 Traffic from Reddit, Twitter, Facebook groups
→ 🚀 But the funnel is moving
🎯 The universal problem I'm solving
Every small Shopify merchant faces this:
❌ Shopify's built-in analytics show you WHAT happened
❌ Nobody tells you WHY it happened
❌ Nobody tells you WHAT TO DO about it
❌ The tools that solve this are priced for enterprise
ShopSight is the affordable, AI-powered alternative.
Built by a merchant, for merchants. 💚
💰 Pricing:
✅ Free plan — always free
✅ Starter — $15/mo
✅ Pro — $29/mo
vs Triple Whale's $129/mo 🐋
Same insights. 8x cheaper. 🎉
🙏 What I need from this community
- 🔍 Brutal feedback — what's wrong with my landing
page? (getshopsight.com) - 🛍️ Would you use this? — if you run a Shopify store,
does this solve a real problem for you? - ❓ What am I missing? — what features would make you
pay $15/mo immediately? - 📣 Marketing advice — I have zero audience. How did
you get your first 10 paying customers?
I'm building in public from here. 🏗️
Will share weekly updates on revenue, signups,
and learnings.
Happy to answer any questions about the build, the stack, or the journey! 💬
— Munish
👉 getshopsight.com
🆓 Free plan available · No credit card · 2 min setup
Love the founder mindset here. You didn't build another analytics dashboard—you built something to solve a problem you personally experienced. That's exactly how we're approaching Framerfy too. We saw merchants wanting Framer's design flexibility without giving up Shopify's commerce engine, so we built around that need. Wishing you the best with ShopSight—always great to see more founders building for the Shopify ecosystem. 🚀
Congrats on shipping this — the weekly digest angle is smart, that's the feature merchants actually open vs. a dashboard they forget to check.
One thing that trips up a lot of reporting tools: period-over-period comparisons get messy once you cross month boundaries or handle merchants in different timezones. Comparing "this week vs last week" when a store's admin timezone differs from UTC can quietly shift orders into the wrong bucket — an easy bug to miss until a merchant complains their numbers don't match Shopify's own admin.
Also curious how you're handling order data completeness — relying on webhooks alone, or reconciling with a periodic pull from the Orders API? Missed webhooks are rare but they happen, and for a revenue-drop alert feature specifically, one silently missed webhook can trigger a false alarm.
Curious how you approached this!
I like the shift from showing data to recommending actions. That feels closer to what busy merchants actually want.
My question would be: how do you build trust in the AI recommendations? If the AI says "launch an email campaign," do you plan to explain why it reached that conclusion? Transparency might become a key differentiator.
We've actually built transparency right into it — for one of our test stores, ShopSight flagged: "Zero repeat customers, single product catalog, $101.50 AOV." Then the AI recommendation was: "Add 2-3 complementary products to increase cross-sell opportunities." The merchant can see exactly what data points led to that suggestion. No black box — every action has a clear "because" attached to it.
I'd be careful with one thing.
The interesting question may not be whether merchants want better analytics or AI insights.
It may be what specific decision they're actually trying to make when they open the product.
Those sound similar, but they can lead to very different conclusions about positioning, adoption, and what signals deserve confidence early on.
I wouldn't make that call casually from the current data.
Really valuable pushback. You're right that "AI insights" is vague — the specific decision ShopSight is built around is: "What should I do with my inventory and catalog right now?" Concretely — which products are underperforming and need restocking, which are doing well and should be scaled, and where gaps in the catalog are limiting cross-sell. That's the exact moment a merchant opens ShopSight for. Still early and talking to first users to validate this, but that's the hypothesis we're building around.
Possibly.
The reason I stopped short earlier is that I don't think the interesting part is the hypothesis itself.
I think there's a more important decision sitting underneath it.
That's one of those things that can feel validated surprisingly early while still sending the product in very different directions.
I wouldn't try to unpack that properly in a thread.
If you're curious, drop your email and I'll put together the tighter version.