We started with a simple goal: build the best product to find the emails and phone numbers businesses need to reach the right people. Most enrichment tools rely on a single data source. That means patchy coverage and inconsistent quality. We took a different path. FullEnrich aggregates 20+ data providers into a single waterfall system, automatically testing each source until we find the best possible contact info. The result is the highest coverage on the market, with better data quality. As we grew, we expanded our vision to become the trusted B2B data source powering every workflow and every team. That led us beyond core enrichment:
We've built a product people love and talk about. Word of mouth has been our biggest growth lever so far, but we've barely scratched the surface of what's possible with intentional growth work. We have not optimised our cancellation flow, no referral system, and plenty of low-hanging fruit waiting to be picked.
We're hiring our first Growth Product Manager to turn organic traction into a scalable growth engine.
You'll own the metrics that matter most: Activation, Conversion, Retention, and Referral.
You'll report to the CPO (based in San Francisco) and work with a dedicated growth squad: 2 engineers (front and back) fully focused on growth initiatives, with access to a product designer when needed. This is just the starting point. We're planning to double our engineering team and dedicate 30% of engineering bandwidth to growth product, which means your squad (and the growth PM team) will scale with impact.
What we need is someone who will live and breathe these metrics, constantly asking: what's the fastest way to test if this moves the needle?
With your squad
You write the specs and wireframes, but you don't work in a silo. You involve engineers early in the process to explore technical solutions together. We try to create a culture where engineers are responsible for making sure what they ship is on-spec and bug-free. Your job is to set the pace: growth moves faster than core product, with a higher tempo of experimentation.
You also know how to make trade-offs. Sometimes experimenting means accepting more technical debt. We expect you to give your squad permission to cut corners when it makes sense, and refactor later.
Month 1 to 3: We have a backlog of high-conviction bets we haven't shipped yet. Your first weeks will be about getting those live, learning the product, and building context.
After that: You own your roadmap. You'll decide what's worth testing based on data, user research, and your own judgment.
A typical week might look like: analyzing signup-to-activation funnels in PostHog, setting up a test on the upgrade flow, reviewing churn reasons in support tickets, shipping an in-app nudge via Intercom, running a user interview to dig into why some features have not the expected retention.