Lead Product Manager

LeanLaw provides legal billing software and revenue management tools for law firms. The Lead Product Manager will own the product roadmap for revenue intelligence and fintech, including making revenue leakage visible, managing money movement workflows, and defining measurable product outcomes. The role also involves direct customer discovery, data-driven prioritization, and collaboration across the connected product system.

Responsibilities:

• You'd own the roadmap. Not a queue handed down — the sequence of what we build and why, driven by what customers tell you and what the product data shows
• You'd also have a real hand in defining what legal revenue operations means as a category
• Make each firm's leak visible and quantified automatically, whatever their billing model
• Move reporting from data to insights and make the system proactive, so a firm hears from us in week one of a slow collections month instead of week four, and knows where to go to fix it
• You'd work directly with our embedded payments partner on rails, pricing, and the tradeoffs between standard ACH, same-day, and instant
• Define the business outcome and the metric before the build, instrument for it, then check whether the number moved
• Carry it through launch with marketing and sales, and feed what you learn back into what we build next
• Revenue intelligence and money movement are where the weight sits, but the product is one connected system and you'd have a voice across all of it
• You'd talk to firm owners and the people doing their books, sit in on sales calls, and go find the answer yourself rather than waiting for someone to summarize it for you
• You'd bring the evidence and make the call, then own what happens next
• You don't need to have built eval suites before, but you should want to, and you should understand why "it seemed fine when I tried it" isn't a standard

Requirements:

• 3–6 years in product management, with meaningful time on fintech or financial software : payments, banking, lending, accounting, treasury, billing, or reconciliation
• You've worked on product that moves or accounts for other people's money , and you know what that changes: settlement timing, funds availability, reconciliation, audit trails, regulatory constraints
• You think in operator economics . Given a firm's numbers, you can find the leak, put a number on it, and design the product that surfaces it without a human in the loop
• Data fluency. You write your own SQL or get close, and you treat product analytics as a working instrument
• Spec-first. Precision in a spec turns directly into quality in the build
• You close the loop. Customer conversations and product performance data are your roadmap inputs, not a report you read afterward, and you can point to what they changed about something you built
• You want feedback, you change your mind when the evidence moves, and you push through ambiguity instead of waiting for it to resolve
• Remote-first and US-based, with flexible scheduling
• Occasional travel for team offsites and customer visits
• Helpful but not expected: QuickBooks or Xero integration work, vertical SaaS, payment operations depth