We measure a brand's visibility inside AI answers. When someone asks ChatGPT, Perplexity, or Google's AI Overviews "what's the best X," we tell brands whether they show up, how often they get cited, and how to improve it, all delivered through Slack, where marketing teams already work.
We're a small, fast-moving team building in a category that barely existed a year ago (GEO / AEO, generative engine optimisation). The product is live with real clients, we're heading into paid launch, and the surface area is growing faster than the team. That's where you come in.
The role in one line
You own the parts of the product that customers actually touch: onboarding, landing pages, the lifecycle/CLM engine, and pricing, and you ship them end to end.
This is a builder role, not a maintainer role. You'll take a rough idea ("suggest which Slack channels a current user should connect, and why") and turn it into a shipped, tested flow. You lean frontend and product, but you're comfortable wiring the backend logic and data that sits behind those flows.
What you'll own
Onboarding & the activation funnel
The single most important surface in the product. You own the flow a new user hits from landing page to signup to connected to activated, across all entry states (email-only, Slack-connected, fully-connected). Your job is to make it convert and make it feel effortless.
The CLM (customer lifecycle) engine
We nudge users at the right moments with the right message (email + Slack) based on where they are in their lifecycle and what their real data says (spend, ROAS, competitor moves, alerts). You'll own the lifecycle sequences, the message templates, the admin triggers, and the backend wiring that pulls the correct data into each message, through to launch and iteration.
Pricing & billing surface
The customer-facing pricing experience and the logic behind it, working alongside our backend lead on the Stripe/payments path. Getting this right is directly tied to revenue.
Landing p
📌 Product Engineer (India)
🏢 Fyndr
📍 India