Launched: Reporting SaaS — automatic Shopify sales reports by email, no more logging into Analytics every week
What it is: a Shopify app that connects to your store and automatically emails you a clear performance report — revenue, recent orders, product catalog — instead of you having to log into Shopify Analytics manually.
Who it's for: Shopify merchants who check their numbers out of habit rather than because they enjoy it, and would rather have the numbers come to them.
What's in it:
- Weekly report delivered automatically by email, no login required
- Period-over-period comparison, with an alert when revenue drops
- Full history of every report ever generated
- Export to PDF or CSV anytime
Current stage, honestly: just launched a few weeks ago, $7.99/month with a 7-day free trial. Still early — I'm not going to pretend otherwise — so feedback from anyone who's dealt with the same "why do I have to check this manually every week" problem is genuinely welcome, whether that's about the product itself or how you'd expect something like this to be priced.
The CSV export is the part I would treat as a product, not a checkbox. Merchants who export do it to reconcile: Shopify orders against the warehouse pick list or the books. The moment two files meet in a spreadsheet, VLOOKUP silently takes the first matching row, so a repeated order number, or a refund line that shares an order id, quietly becomes a match and the reconciliation is wrong with no error shown. If your export carries stable exact keys (order name and numeric order id both, as plain strings, with the # prefix and leading zeros left alone) plus a period column the merchant can key on, your report becomes the file people match against instead of the file they distrust. That is worth more than the email cadence.
Which column do you consider the key in that CSV, and do you guarantee it never repeats within one export?
This is a sharper way to think about the CSV than I had — I've been treating it as "same data, different format" rather than asking what it needs to survive a reconciliation join.
Honest answer: I don't know off the top of my head whether the order id is guaranteed unique within a single export, or whether it's exported as a formatted string (# and leading zeros preserved) versus something Excel/Sheets could silently coerce to a number on open — which is exactly the kind of thing that breaks a VLOOKUP without ever throwing an error. That's a real gap I haven't verified, not something I've confirmed is handled correctly.
Going to go check: which field is actually the row key, whether it's forced to text format, and whether a refund gets its own row sharing the parent order's id — which sounds like exactly the collision case you're describing. Given how specific and correct the failure mode is, I'd rather verify than assume it's already fine.
Appreciate you spelling out the actual failure mode instead of just "make sure IDs are unique" — much easier to actually check against.
Appreciate the honest answer. I’d start by defining what one row represents: an order, a line item, or a transaction. Repeated order IDs may be perfectly valid—the important distinction is between the parent order ID and a unique row key.
A useful test fixture would be one order with two line items and two partial refunds. Export it, open it through the spreadsheet workflow your merchants actually use, and check whether every row remains distinguishable and the totals reconcile.
One clarification to my earlier comment: preserving an ID as text in the CSV doesn’t necessarily prevent a spreadsheet from interpreting it as a number. That import behavior needs testing too.
Once you’ve checked, documenting the row meaning and recommended join key would make the export much easier to trust.
Congrats on shipping — and the "just launched, I'm not going to pretend otherwise" framing is refreshing. That honesty will serve you better than inflated numbers ever would.
Two thoughts, one on the product, one on pricing since you asked:
Product: the "period-over-period comparison with an alert when revenue drops" is the strongest thing here. That alert is what turns this from a report into something people actually keep paying for. The passive weekly email is nice, but the alert is what earns its place in a busy merchant's inbox. I'd consider leading with it — "we'll tell you when something's wrong" beats "here's your weekly summary." One is insurance, the other is a chore they can skip.
Pricing: $7.99 feels low for something tied to revenue. Merchants anchor SaaS spend to how much money the tool touches, not to what it is. If this catches a revenue drop early even once, it pays for itself many times over — so the price should reflect that value, not the effort to build it. I'd test $12–19 with the alert as the headline feature. Underpricing also quietly signals "small tool," which can hurt trust more than a higher number does.
One question: are the reports customizable per merchant, or a fixed template? The stores that live in their numbers will want to pick which metrics land in the email.
Appreciate that — and yeah, the alert being the real headline rather than the weekly summary is a theme that's come up more than once in the sister post on this same topic (someone else framed it almost identically as "insurance against a bad week" vs. automation of a chore). Since then I've actually shipped two things because of that exact feedback: a predictive alert flagging 3 consecutive days of declining revenue, and a plain-language summary explaining what's happening instead of just raw numbers. Too early to know if leading with that framing in the listing/pricing changes anything yet, but the product itself has already moved that direction, not just the pitch.
On your question — yes, report content is customizable per merchant already, not a fixed template. Good prompt to actually surface that in the listing copy, since it's mentioned nowhere right now.
On pricing, honestly haven't tested anything above $7.99. The "underpricing signals small tool" angle is new to me — I'd assumed a lower price mainly reduced friction to try it, not that it actively hurts how seriously it's taken. Have you seen that show up in real conversion data somewhere, or is it more directional intuition at this point?
Fair to push on that — it's directional for me, not something I've A/B tested with hard numbers, so take it as a hypothesis rather than a proven result.
The reasoning behind it: for revenue-tied B2B SaaS, the buyer isn't spending their own fun money — they're expensing a tool against a store that does real revenue. In that frame, $7.99 can read as "hobby plugin" and $19 reads as "actual business tool," and the seriousness signal sometimes matters more than the friction. It's the same reason a $9 and a $49 consultant get judged differently before either says a word.
But your friction point is real and I don't want to hand-wave it — cheaper genuinely does lower the barrier to that first trial. The two effects fight each other, and which wins depends on your buyer. So the only honest answer is: test it. Same listing, same trial, just $7.99 vs ~$15 for a few weeks, watch trial→paid and churn, not just signups. Cheap tools often win the signup and lose the retention.
The predictive 3-day-decline alert + plain-language summary is a great move, by the way — that's the part I'd actually put in the headline. "Catches a bad week before you do" is a much stronger hook than the price either way.
That distinction — watch trial→paid and churn, not just signups — is exactly right and not something I'd have thought to isolate on my own. Cheap winning signups while quietly losing retention would look like success if I were only watching install counts.
Practical problem, though, same one as an unrelated screenshot A/B test suggestion elsewhere in this thread: I've got exactly one store that's ever installed, and it uninstalled same-day. There's no real user base yet to run a meaningful price test against — right now this is "which experiment to run once there's enough volume," not something I can actually start this week.
"Catches a bad week before you do" is going straight into my notes — noticeably sharper than anything currently in the listing or in-app copy. Appreciate you pushing on the pricing point and its counter-argument instead of just picking a side and stopping there.
The "numbers come to you instead of you logging in" framing is clean and the pain is real, merchants do check obsessively out of habit. But the honest challenge, since you asked about both product and pricing, is that this sits in a tricky spot: it's a genuine convenience, but it's a convenience layer on data merchants can already get free inside Shopify. That shapes both problems.
On pricing: $7.99 might actually be working against you, and not by being too high. For a merchant doing real revenue, $7.99 is so low it signals "small utility," and the buying decision becomes "is this worth even thinking about" rather than "is this worth the money." Sub-$10 tools often convert worse than $15-20 ones, because the price tells the buyer how much to care. The problem isn't that it costs too much, it's that the price frames it as trivial. Worth testing a higher number with a sharper value story.
On product, the thing that would move you from "nice email" to "can't cancel this": right now you send data (revenue, orders, catalog). Data is a commodity merchants can already see. Insight is what they can't easily get. "Revenue dropped 12% and here's the likely cause" or "these 3 products drove 60% of growth, lean in" is worth paying for. A merchant can pull numbers themselves, what they can't do is have someone tell them what the numbers mean and what to do. The alert-on-revenue-drop is your seed of this, lean all the way into interpretation over reporting.
The wedge underneath: don't be the tool that shows the numbers, be the one that tells them what to do about them. That's uncopyable in a way "email my Shopify stats" isn't.
That reporting-vs-insight positioning is what I spend my time on, I'm part of the team building Hivemind, an AI strategy copilot. If you want to pressure-test the pricing-and-positioning: https://hivemind.myosin.xyz. Either way, sell insight, not the export.
peer just-launched too so noting this quickly. your honest "avoid checking manually" reply puts $7.99 in cheap-chore-removal territory - a category shopify's own emails commoditize.
the revenue-drop alert is the only feature on your list that isn't automation-of-a-habit. it's a different product wearing the same UI. price and pitch around the alert and you stop competing with a chore, you compete with "insurance against a bad week."
That's a sharp reframe, and it lands close to something I said almost word-for-word in a reply on the other thread — the alert is the one feature on that list that isn't just automating a habit, it's actually catching something. I hadn't put a name on it like "insurance against a bad week" though, and that's a much better hook than anything currently in my listing copy.
Where I'd push back slightly on myself, honestly: I don't have any evidence yet that merchants perceive it that way — right now it's buried as the second bullet in a list of otherwise pretty interchangeable automation features, not leading the pitch. Before I'd trust repricing or repositioning entirely around it, I think I need to actually test leading with it — in the copy, maybe in onboarding — rather than assume the reframe is correct just because it's compelling.
Curious what made you zero in on that specific line rather than the reporting/export list — was it just the wording, or do you have a specific reason "automation of a chore" categorically underperforms "insurance" as a pricing frame?
The interesting question is whether merchants are paying to avoid checking analytics, or because the report helps them make better decisions faster.
What would convince you that automated reporting is the core value, rather than turning Shopify data into clearer actions and recommendations?
Honest answer: right now, probably closer to "avoid checking manually" than "clearer decisions." The core mechanic is automation of something merchants already do (checking Shopify Analytics), not new analysis they couldn't do themselves.
The revenue-drop alert is the one feature that leans toward the second category — it's not just reporting a number, it's flagging that something changed and probably needs attention. But it's a small piece of the product, not the core of it yet.
What would convince me one way or the other: if merchants mostly just skim the weekly email and archive it, that's convenience winning. If the revenue-drop alert specifically is what gets opened immediately and acted on (versus the routine weekly one), that's a real signal the "clearer action" angle is where the actual value is, and probably where I should be investing more — richer alerts, maybe even simple recommendations, rather than more report formats.
I don't have enough usage data yet to know which it is. Have you seen this play out clearly one way or the other in something you've built — automation vs. decision-support ending up being the real reason people paid?