Ruben Khachatryan

Growth Product Manager

EasyDMARC

OtherPLG AssistedConsultative
Posted by Ruben Khachatryan

Overview

You manage the product features and flows that drive growth metrics - signups, trial-to-paid conversions, feature adoption, and account expansions. You're not building core email authentication tech; you're optimizing how people discover value, upgrade, and expand usage. You work with product, engineering, data, and the sales team to turn product signals into pipeline.


Role Snapshot

AspectDetails
Role TypeGrowth Product Manager
Primary FocusAcquisition, Activation, Monetization
Product StageMature product in niche category
Team StructureReports to Director of Product
Cross-functionalWorks with Eng, Data, Sales, Marketing
Success MetricsTrial conversion rate, PQL volume, expansion revenue

Company Context

Stage: Bootstrapped or early venture-backed (funding info unavailable)

Size: 128 employees

Growth: Actively hiring for growth-focused roles, indicates revenue scaling phase

Market Position: Niche player in email authentication/DMARC space - not crowded but technical product that requires buyer education

The Product Reality:

  • DMARC compliance is becoming mandatory (Google/Yahoo requirements driving demand)
  • Buyers are often IT/security teams who don't understand DMARC until they have a problem
  • Competitive with dmarcian, Valimail, Proofpoint - differentiation is in ease of use
  • Mix of self-serve (SMB) and sales-assisted (enterprise) motion

GTM Reality

How People Find EasyDMARC:

  • Inbound via free tools (DMARC checker, SPF checker) - high volume, mixed quality
  • Organic search (people Googling "DMARC compliance" or "how to fix DMARC")
  • Some outbound from sales team to IT/security leaders
  • Partner/MSP channel exists but unclear how mature

The Growth Challenge:

  • Free trial users often don't understand the problem deeply enough to convert
  • Enterprise deals need sales touch, but lower-tier deals should self-serve
  • Product has to educate AND convert in the same flow

What You'll Actually Do

Time Breakdown

Experiment Design & Analysis (35%) | Roadmap/Planning (25%) | 
Cross-functional Meetings (25%) | User Research (15%)

Key Activities

  • Running Experiments: You design A/B tests on signup flows, onboarding sequences, feature prompts, pricing page variations. You write specs, work with eng to ship, then analyze results. Most experiments fail or show marginal lift.

  • Analyzing Funnels: You live in Amplitude/Mixpanel (or similar) looking at drop-off points. Where do trial users churn? Which features correlate with conversion? Which accounts should sales prioritize? You create dashboards and share insights weekly.

  • Shipping Product Changes: You own things like in-app upgrade prompts, paywall logic, onboarding checklists, email notification triggers. These aren't sexy features - they're growth levers. You write PRDs, work with 1-2 engineers, and ship iteratively.

  • Working with Sales & Marketing: You help sales identify which trial accounts are "hot" based on product usage. You give marketing data on which campaigns drive quality signups. You sit in pipeline reviews to understand what's blocking conversions.

  • User Research: You talk to users who didn't convert, or who churned, or who upgraded. You're trying to understand friction points. Sometimes you do this via Zoom calls, sometimes via in-app surveys or support ticket analysis.


The Honest Reality

What's Hard

  • Technical Product, Non-Technical Buyers: Most trial users don't deeply understand DMARC. Your growth work has to educate them without overwhelming them. This is harder than optimizing a consumer app.

  • Small Team = Slow Shipping: With 128 employees and likely 15-25 engineers, you don't have a dedicated growth eng team. You're competing for resources with core product work. Experiments take longer than you want.

  • Attribution Is Messy: Did that trial user convert because of your onboarding flow or because a salesperson called them? Growth attribution in B2B is always fuzzy, especially with a hybrid self-serve + sales-assisted model.

  • Experiments Often Fail: Most A/B tests show no significant lift. You spend weeks on something that moves conversion 0.3%. That's the job - lots of small wins, occasional breakthrough.

What Success Looks Like

  • Trial-to-paid conversion rate improves from X% to X+2% over 6 months
  • PQL (Product Qualified Lead) volume increases by 20-30%, giving sales better pipeline
  • You ship 8-12 experiments per quarter, with 2-3 showing meaningful results
  • Sales team regularly uses your product usage data to prioritize accounts

Who You Work With

Internal Stakeholders:

  • Director of Product: Your manager - sets growth priorities, approves roadmap
  • Engineering Team: 1-2 engineers assigned to growth work (not full-time dedicated)
  • Data/Analytics: Probably 1 person or shared resource - you rely on them for experiment analysis
  • Sales Team: AEs and SDRs who need your PQL scoring and trial insights
  • Marketing: Demand gen person who drives signups - you tell them what converts

What They Need From You:

  • Sales wants more qualified leads and better trial intelligence
  • Engineering wants clear specs and realistic timelines
  • Director of Product wants evidence that your work moves revenue metrics

Requirements

  • 2-4 years in product management, with at least 1 year focused on growth/monetization
  • Experience running A/B tests and analyzing funnel metrics (Amplitude, Mixpanel, or similar)
  • Comfortable with SQL for pulling your own data and doing exploratory analysis
  • B2B SaaS background preferred - understanding of trial conversions, PLG motions, and sales-assist models
  • Ability to work autonomously in a small team - you won't have a growth org around you
  • Technical enough to work with engineers on implementation details, but not expected to code

The Real Trade-offs

You'd Want This If:

  • You like being close to revenue and seeing direct impact on conversion metrics
  • You enjoy experimentation and data analysis more than big feature launches
  • You want broad scope in a small team vs specialized role in a big growth org
  • You're interested in technical B2B products where education is part of the growth challenge

You'd Hate This If:

  • You want a dedicated growth engineering team and fast shipping velocity
  • You prefer working on core product features over monetization levers
  • You need a mature growth org with established playbooks and mentorship
  • You want consumer-scale volume and rapid experimentation cycles