Senior Product Manager, Pricing

Role Overview

• You'll own the full pricing and monetization domain — from the infrastructure that powers every price we show to the strategy that determines what we charge, how we bundle, and where we expand.
• This is a transformation role. We're migrating from three disconnected pricing paradigms to a unified dynamic pricing system. The roadmap has 11 priorities, a dedicated engineering team, and no full-time product owner.
• Dynamic pricing roadmap: Migrate three legacy pricing systems to a unified pricing service. Sequence the 11-priority roadmap, make tradeoff calls, and ship.
• Pricing strategy: Define pricing for 24+ services across mowing, non-mowing, and emerging verticals. Balance conversion, margin, and Pro economics.
• New revenue models: Unlock bundles, add-ons (e.g., "bag my clippings"), channel discounts, and frequency-based pricing — none of which exist today.
• Service availability: Determine where and when we offer services based on supply, demand, and profitability signals.
• Experimentation framework: Stand up A/B testing for pricing changes, measuring impact on conversion, margin, and Pro claim rates.

Requirements

• AI-native. You use AI daily — scenario modeling, pricing analysis, data exploration, drafting specs. You push AI into parts of your workflow others haven't thought of yet. This is unlikely to be a good fit if you view AI as a novelty rather than a core productivity lever.
• A systems thinker who architects platforms, not just sets prices. You see pricing as a system: inputs, rules, feedback loops, edge cases. You can design a pricing architecture that handles 24 services across 3 brands with different economics — and explain it to an engineer in a way they can build. This is unlikely to be a good fit if your pricing experience is limited to spreadsheets or optimizing a single product's price point.
• Data-informed, not data-dependent. You partner with the data team to define what to optimize and interpret results. You know when the data is insufficient and a judgment call is needed. This is unlikely to be a good fit if you either ignore data or refuse to move without perfect information.
• Technically fluent. You work directly with engineers on API design, discuss schema tradeoffs, and review technical design docs with real feedback. You don't write code, but you earn engineering's trust by speaking their language. This is unlikely to be a good fit if you treat engineering as a black box or need everything translated into business terms.
• A patient builder. The pricing gains require infrastructure first — a pricing API, a data product, migration tooling. You're energized by building the foundation, not frustrated that the payoff isn't immediate. This is unlikely to be a good fit if you need quick wins to stay motivated or lose interest when the work is foundational.
• Monetization-minded. You see bundles, add-ons, service availability, and frequency pricing as revenue levers, not just features. You naturally think about margin, willingness to pay, and Pro economics. This is unlikely to be a good fit if you think of pricing as a one-time decision rather than an ongoing optimization problem.

Benefits

• Base salary: $140,000 – $175,000
• Equity: Pricing decisions directly impact revenue, margin, and conversion at scale. We want you invested in the long-term outcome of the system you're building.
• Healthcare: Medical, dental, and vision
• Fully remote: Pricing work requires deep analysis and focused thinking. We trust you to manage your environment.
• Flexible PTO: We focus on results. Take what you need.