I’m narrowing the AnveVoice Shopify launch around a very specific test:
not “put a voice agent across the whole store,” but one high-intent page where shoppers already hesitate.
The pages I’m most interested in:
The test is simple:
I’m not looking for vanity installs. I’d rather work with 5 Shopify stores where the page genuinely has unanswered buyer questions.
We’re giving the first 100 Shopify stores 2 months free for the native integration. If you run a Shopify store or work with Shopify clients, I’d value brutal feedback on whether this is a useful wedge or still too early.
I wrote the longer framework here:
https://adarshknt1.hashnode.dev/shopify-voice-ai-should-start-on-high-intent-pages-not-the-whole-store
Shopify app:
https://apps.shopify.com/anvevoice?utm_source=indiehackers&utm_medium=post&utm_campaign=shopify_native_first_100
Hi, the fragmentation problem is real and underserved — most job boards optimize for enterprise clients, not for the candidates who'd benefit most from seeing what smaller companies actually have open.
One honest feedback point: the value proposition of "jobs not on LinkedIn" needs to be the first thing a visitor sees, not something they discover by browsing. If that's your edge, lead with it explicitly.
Good start. Curious how you're handling freshness — careers pages go stale fast.
Hi, the page-specific wedge is the right call. Voice across an entire store is a solution looking for a problem — but a technical product page where someone needs to know if a part fits their model before they buy is a very specific job to be done.
The B2B and wholesale pages are the one I'd watch most closely in your test. Those conversations are already happening by phone or email, the buyer intent is high, and the cost of a missed question is an abandoned quote rather than an abandoned cart. If voice can intercept even a fraction of that, the ROI case writes itself.
I work with Shopify clients on the automation side and the hesitation point you're describing on spec and compatibility pages is real — it's one of the gaps that's hard to solve with static FAQ content alone.
Curious what you're seeing on conversion lift versus support deflection as the primary metric. Depending on the store, those pull in different directions.
If any of the store owners in this thread want to think through where voice fits alongside their existing automation stack, happy to connect: https://teams.live.com/l/invite/FBAk3iOSJkDyS11JQ?v=g1
I think focusing on a single high intent page first is the right move
Compatibility, sizing, and B2B quote pages seem like the strongest candidates since that's where shoppers usually have the most unanswered questions
I would be curious which page type ends up generating the most meaningful conversations once you start collecting data