What the team does

Product at Recart isn't an abstraction layer between sales and engineering. It's a function that works directly with merchant data, LogRocket sessions, Appcues experiments, and live A/B tests to understand what's working and what isn't, then turns that into product decisions.

Soma, Recart's CEO, is the team's most demanding user: submitting bug reports, proposing features, and stress-testing every release from enterprise merchant demos. CS is the daily feedback pipeline. The Product team's job is to filter the signal from the noise, scope the work with engineering, and ship things that move metrics.

They're also responsible for one of the most interesting product challenges in the space: building a platform that's simultaneously powerful enough for a $1.4B Shopify store and self-serve enough that a small DTC brand can onboard without hand-holding.

What they work on

• Smart Trigger - an AI-backed popup retrigger mechanism that delivered 10–28% SMS opt-in uplifts across pilot merchants, now rolled out to all accounts
• A/B testing infrastructure - a full analytics page with revenue attribution, lift percentages, funnel charts, and export; the team shipped, monitored adoption via Appcues, and iterated based on real usage data
• OneClick opt-in - a frictionless single-click subscription flow, from silent release to full promotion with in-app educational content
• Expiring unique discount codes - end-to-end: popup display, welcome flow sync, Klaviyo/Postscript integration, and expansion to all automated flows
• Automated list cleaning - daily removal of deactivated and high-risk numbers with a merchant-facing savings estimator; shipped fast, shipped right
• Modular popup editor - a multi-quarter architectural initiative toward a fully component-based editor, shipping piece by piece (resizable elements, style unlinking, multi-CTA, form item redesign)
• Messenger sunset - a major platform transformation moving the product fully to SMS + email, with zero data loss for existing merchants
• Klaviyo deep integration - segment sync and event-based message triggering (Klaviyo email open/click → SMS flow)

How Product works

Product at Recart is embedded, not isolated. PMs and designers sit in daily standups alongside engineers, share the same Shortcut boards, and write scopes that engineers read before picking up a ticket. There's no waterfall here: design reviews happen continuously, prototypes (including AI-assisted Figma Make builds) go into the team channel for quick feedback, and feature flags let the team release safely and iterate in production.

Decisions are backed by data: LogRocket for UX analysis, Appcues for feature adoption, experiment trackers for popup performance. When a Smart Trigger test shows 28% uplift, the team moves fast. When A/B test revenue data is wrong, they hold the promotion and fix the root cause first.

What kind of problems they solve

"Merchants don't understand why their popup CR is low. Build an analytics page that makes it obvious."

"OneClick works, but without a fallback setup, it's a liability. Design the promotion flow to nudge merchants into best practice."

"Our A/B test revenue data is distorted by historical carry-over. We can't promote the feature until it shows real numbers, figure it out."

"A $1.4B brand wants to demo Recart tomorrow. What's not ready?"

Who thrives here

You'll do well here if you're comfortable in ambiguity and get energy from being close to the business. Product at Recart isn't a quiet planning function, it's in the thick of things, with real merchants, real stakes, and a fast feedback loop.

The role rewards people who can write a clear scope, prototype quickly, read data critically, and change their mind when the evidence says to.

Size & structure

Product Managers working directly with our Head of Product, engineering team leads and the CEO.