2
4 Comments

20+ comments, zero clicks — can I ask you something?

Quick context if you're new to this thread: Inventory Sync is a small Shopify app that stops multi-channel sellers from overselling — the classic "sold it in-store, forgot to update online, refunded an angry customer" problem. Built it myself, still early, still validating.
I've gotten some of the sharpest product feedback I've ever received on this post. Write-back race conditions, event ledgers, silent drift, reservation windows — genuinely expert-level stuff, some from people who've built this exact thing at the ERP level. I've taken almost all of it seriously and I'm building around it right now.
But here's the honest number: install count is still 1. My own test store.
I think that's actually on me, not you — I never made it easy or obvious to just go look at the thing we're all talking about. So let me fix that:
👉 https://inventory-sync-starter.onrender.com/landing.html
What it actually does right now:

Connects to your Shopify store via OAuth and pulls live inventory into one dashboard
Shows stock across channels in one place, so you can catch mismatches before a customer does
Per-SKU safety buffer — hold back 1-2 units on high-risk products to cover the sync-window gap
Billing runs through Shopify's own Billing API — no separate checkout, no card details going anywhere sketchy
More channels (Etsy, manual in-store counts) and deeper real-time sync are next, based directly on feedback from this thread

There's a 14-day free trial, no card required, so there's zero risk in actually connecting a dev store and poking around instead of just reading about it.
Here's why I'm asking instead of just quietly building: this community is one of the only places where strangers will spend real time thinking hard about a stranger's problem, for free, because they've been exactly where I am. That's rare, and I don't think it works if we only ever trade advice back and forth without anyone actually looking at what the advice is about. A comment thread full of smart theory and zero real eyes on the product isn't quite finishing the loop.
So — if you've got two minutes, I'd genuinely rather have your reaction to the actual landing page than one more idea for the roadmap. And if you're building something too, drop it below — happy to return the favor and actually go look at yours.

on July 15, 2026
  1. 1

    You cannot diagnose landing-page conversion from zero visits. Put the link only in front of sellers describing a recent oversell, then track thread view, landing visit, OAuth start, and connected store. That isolates urgency, click-through, and onboarding as separate losses. More expert comments on the architecture will not answer any of those.

  2. 1

    The interesting signal isn't one install—it's 20+ thoughtful comments and almost no product visits. I'd keep validating whether the bottleneck is the landing page, or whether readers still understand the problem intellectually without feeling the urgency to see the solution. Those require different fixes.

    1. 1

      Good catch — this is actually the same split as the "insurance vs. nice-to-have" question from earlier in the thread, just showing up as a real number now instead of a theory.
      Two different problems: either the landing page itself isn't converting curiosity into clicks, or people here understand the problem intellectually without having felt it, so there's no real pull to look. My honest guess is the second — this thread is full of sharp, experienced people engaging with it as a design problem, not multi-channel sellers who've actually had the "sold it twice" moment.
      So the real test isn't more visibility here — it's putting the link in front of people who've already lived it (Shopify Community, Reddit, wherever sellers vent right after an oversell happens). That's a cleaner read on whether the landing page itself works.

      1. 1

        That's exactly the part I found interesting.

        Reading your reply gave me one thought about the assumption underneath that test. I don't think I could explain the reasoning properly in a thread because it really depends on the product you're building rather than a generic growth principle.

        If you're interested, what's the best email to reach you on?

    2. 1

      This comment was deleted 2 months ago

  3. 1

    This comment was deleted 2 months ago