Launch one or two high-value workflows
Custom scope Best for early validation
- Focused on a narrow slice of the storefront journey.
- Usually discovery, recommendations, or support-heavy FAQs.
- Best for testing demand and shaping the product vision.
Custom pricing
Pricing is custom because the right build depends on your catalog and scope.
A managed-service offer, not a self-serve product. The initial engagement is scoped around the workflows that matter most to your store.
Engagement tiers
Three scopes, each priced around what the pilot needs to prove.
Expand into more storefront actions and merchandising
Custom scope For teams ready to deepen usage
- Add-to-cart flows, more store context, advanced routing.
- Broader coverage across product, service, and post-purchase.
- Fit once the pilot already proved the widget belongs on-site.
Multi-store, high-volume, or complex requirements
Custom scope For larger rollout plans
- Useful when data sources, governance, or tooling are complex.
- Can include rollout support, analytics, and operational guardrails.
- Planned around architecture, traffic, and internal workflows.
What affects pricing most
- Catalog size, structure, and merchandising context needed.
- The number of workflows the assistant should handle in v1.
- Whether it needs read-only knowledge, live storefront actions, or both.
- The level of tuning, analytics, and iteration support after launch.
What the conversation should cover
- Where shoppers currently get stuck before purchase.
- Which support questions repeat most often.
- What data sources are already available and trustworthy.
- What a successful pilot would need to prove for your business.