We were celebrating. The dashboards were all green, projecting a beautiful hockey-stick curve onto the big screen in the office. Our North Star Metric, Weekly Active Users (WAU), had just crossed a major milestone we’d been chasing for two quarters. The product and engineering teams were buzzing. We had shipped features, optimized funnels, and driven engagement. By our own measure, we were winning.
But while we were high-fiving in the product pit, the finance team was in a conference room staring at a sea of red. Our burn rate was accelerating, our LTV:CAC ratio was trending the wrong way, and our average revenue per user was stagnant. The C-suite was getting nervous, and rightfully so.
The product org was telling a story of spectacular growth. The P&L was telling a story of impending crisis. The horrifying truth slowly dawned on us. Our North Star Metric, the single number meant to guide our entire company toward success, was lying to us.
This disconnect isn’t unique. I’ve seen it play out in scale-ups and established tech companies alike. We, as product and technology leaders, have been conditioned to worship at the altar of engagement. But engagement without economic value is just a hobby. It’s time for a fundamental shift in how we build and measure. It’s time to pivot to Product-Led Finance.
The Seductive Lie of the Engagement-Only North Star
The idea of a North Star Metric (NSM) is powerful. It’s a single, unifying metric that is supposed to capture the core value your product delivers to customers. For Airbnb, it’s nights booked. For Spotify, it’s time spent listening. For many SaaS companies, it defaults to something like Daily Active Users, Weekly Active Users, or a count of actions, like “projects created” or “messages sent.”
These engagement metrics are seductive for a few reasons. They are easy to measure. They move quickly, providing the instant gratification of a rising chart. They are also easy to rally a team around. “Let’s increase WAU by 15% this quarter!” is a simple, clear directive.
The problem is that these metrics are often vanity metrics in disguise. They measure activity, not value creation. High activity doesn’t automatically translate to a healthy, sustainable business. We fell into this trap. Our WAU was soaring, but a deeper look revealed a troubling pattern. The majority of our active users were on the free plan, using resource-intensive features that had a high cloud infrastructure cost. The features we were building to drive WAU were not the same features that convinced users to upgrade to a paid plan.
We were building a product for users, but not for customers. Our North Star was leading us toward a bigger, more active, and completely unsustainable version of our company. It was a sugar high. It felt great in the moment, but it was devoid of the financial nutrition needed to build a lasting enterprise.
The Disconnect: When Product and Finance Speak Different Languages
This leads to a classic organizational divide. The product team lives in a world of user stories, friction logs, and engagement loops. They talk about user love and delight. The finance team lives in a world of GAAP, cash flow statements, and cohort retention analysis. They talk about net revenue retention (NRR) and contribution margins.
This isn’t a failure of people. It’s a failure of the system and the language we use.
Imagine a quarterly planning meeting. A Product Manager presents a roadmap focused on a new collaboration feature. The justification? “Our user interviews show this is a top request, and our models predict it will increase WAU by 20% by driving more invitations.” The team gets excited.
Then the CFO asks, “That’s great, but how does this impact our expansion revenue? Will these new users be on the free plan or the enterprise plan? What is the projected hosting cost for this feature, and how does it affect the gross margin of our Pro tier?”
Silence. The PM often doesn’t have the data to answer those questions. Their analytics tools, like Mixpanel or Amplitude, are brilliant at tracking user clicks but are disconnected from the billing systems, like Stripe or Zuora, and the CRM, like Salesforce. The product team is optimizing for one variable (engagement), while the business needs to solve a multi-variable equation involving revenue, cost, and profitability.
This two-language problem creates friction, misaligned incentives, and ultimately, a bloated product. Teams end up shipping features that are popular but not profitable, creating a product that is a mile wide and an inch deep in value.
Introducing Product-Led Finance: Marrying User Value with Business Viability
Product-Led Finance is the discipline of instrumenting your product and your team to directly connect user behavior to financial outcomes. It’s not about turning PMs into accountants. It’s about empowering them to be true business owners of their domain. It’s about building a common language between product, engineering, and finance, with data as the translator.
This approach is built on three core pillars:
1. Cost & Unit Economic Awareness: Every feature has a cost. It costs engineering time to build and maintain. It costs cloud resources to run. A Product-Led Finance mindset demands that we understand these costs. We should be able to ask, “What is the Cloud Cost per Active User for Feature X?” or “What was the fully-loaded engineering cost to develop this, and what is our expected payback period?” This stops us from building expensive features for low-value user segments.
2. Value & Willingness-to-Pay Mapping: The most important “aha” moment isn’t when a user becomes engaged. It’s the moment they realize so much value that they are willing to pay for it. Product-Led Finance means obsessively mapping the user journey to find these moments. We need to answer, “Which feature adoption has the highest correlation with a free-to-paid conversion?” or “Do customers who use our reporting suite have a 25% higher Net Revenue Retention?” This transforms the roadmap from a list of user requests into a strategic portfolio of revenue-driving initiatives.
3. Predictive Financial Modeling: When your product and financial data are unified, you can move from reactive to predictive. You can see the leading indicators of churn inside your product analytics weeks before a customer actually cancels their subscription. You might see a team’s usage of a key integration drop off, or their active users decline. This is a churn signal. You can then trigger a proactive intervention from your customer success team. You are using product engagement data not just to report on the past, but to forecast and shape the financial future of the company.
The New Stack: Metrics and Mindsets for a Financially-Aware Product Org
Pivoting to Product-Led Finance requires a change in your metrics, your tools, and most importantly, your culture.
First, evolve your North Star. Instead of just “Weekly Active Users,” consider a metric that binds activity to commercial reality. Examples include:
Weekly Monetized Active Users (WMAU): Tracks active users within paying accounts.
Value-Action Rate: Measures the percentage of users completing a specific action that strongly correlates with retention or upgrades.
Net Revenue Retention (NRR) driven by Product: A more complex but powerful metric that attempts to isolate how much of your NRR is due to product improvements and feature adoption, versus sales-led upsells.
Second, build a unified data stack. This is the technical foundation. You need to pipe data from your product analytics tools, your billing system, your CRM, and your data warehouse into a central location. This allows you to build a single customer view where you can see that a user who performed `action_x` in the product is part of `account_y` which has an ARR of `z` and is up for renewal on `date_a`. This is not a trivial engineering task, but its strategic value is immeasurable.
Finally, change the conversation. The questions asked in product reviews and sprint planning must evolve.
From: “Will users like this feature?”
To: “Which user segment will find this so valuable that it deepens their commercial commitment to us?”
From: “How can we increase engagement?”
To: “How can we increase the number of teams completing the key workflow that underpins our Business pricing tier?”
Your Next Move
The shift from chasing engagement to driving profitable, product-led growth is the defining challenge for today’s leaders. Your North Star Metric may be giving you a clear direction, but it could be pointing you straight off a financial cliff.
Don’t let your dashboard lie to you. Start building a bridge between the product you create and the business you run.
Here are three things you can do this week:
1. Schedule a meeting with your CFO or Head of Finance. Don’t go to present, go to listen. Ask them: “What are the one or two business metrics you are most worried about? How can the product team help you understand the leading indicators for those metrics?”
2. **Pick one feature your team recently shipped.** Do a back-of-the-envelope calculation. Try to estimate the engineering cost to build it and the infrastructure cost to run it. Now, look at your analytics. What percentage of your paying customers are actually using it? The answer might be uncomfortable, but it will be illuminating.
3. In your next roadmap planning session, introduce one “financial” question. It could be as simple as, “How does this proposed feature strengthen our pricing tiers?” or “How does this help us win against a competitor in the higher-margin enterprise segment?”
Start small. Ask the hard questions. Begin the pivot. Build a product that users not only love, but that also builds a business that lasts.