What should StorePulse build next? Roadmap poll + ask me anything about the build š
Hey š ā Sumit here, solo maker of StorePulse.

Thanks for checking out the product. I want this thread to be two things: a place to vote on what I build next, and an open AMA on anything
technical or business about the app.
Vote on what to ship next (reply with the number that hurts you most):
1. Session replay ā anonymized 30-sec clips of pages where an error fired, so you can see what the user did right before
2. GA4 / Klaviyo integrations ā push alerts + metrics into the tools you already live in (Slack, Discord, generic webhook are already shipped ā adding the marketing/analytics ones next)
3. Custom alert rules ā "alert me when conversion drops >20% week-over-week" type compound conditions
4. AI weekly digest email ā "this week, your storefront had X errors, here's the top 3 fixes" auto-summary every Monday morning
5. Multi-store dashboard ā for agencies running 5+ stores under one account
6. Auto-apply AI fixes for more violations ā we already auto-apply alt text + meta descriptions; expanding to other theme-file fixes (with merchant approval before commit) is the next step Reply with the number, or add your own ā every vote counts.
Ask me anything:
- Tech stack: 100% Cloudflare (Workers + D1 + Durable Objects + Queues + Browser Rendering) + Anthropic Claude + Shopify Web Pixel + Theme App Extension. Built solo in ~3 months.
- Happy to talk about Shopify App Store review process, the multi-tenant data isolation patterns, the per-page accessibility scan architecture (Queue + DO), atomic AI credit accounting in D1, or anything else.
- Also happy to share what didn't work ā the v1 accessibility scanner got stuck at 3 pages for weeks before I rewrote it as Queue+DO. The
/app/billing/confirm route required 4 iterations to stop dead-ending merchants at /auth/login. There's a lot of "here's what I tried first and why it failed" if anyone wants to dig in.
Drop your roadmap vote + any questions below š
ā Sumit

Replies