Paid subscribers can listen to this in convenient podcast form or watch the video explainer. They can also download the Study Guide, Briefing Doc, and FAQ. See below.
Sometimes it’s okay to prioritize commercial interests over customer features.
Especially when it comes to product delivery.
Two stories to show you what I mean.
Story 1
During the COVID pandemic, our team was racing to launch an innovative product to help physicians and nurses remotely check in on isolated patients.
We had done our homework. Demand was clear. Customers had validated the demo. We knew the features, the budgets, the price sensitivity. And development was running smoothly.
We just couldn’t get our pricing model past the Finance Committee.
To get the margins they wanted, we’d have to price the product way above what customers would pay.
That meant risking pressing STOP in our development work, opening the door to competitors and, worse, leaving hundreds of thousands of patients without the care they desperately needed.
Lives were at stake.
We re-visited our analysis. Scrutinized every assumption. Eventually, we found the problem.
We had baked too much of our shared platform costs — AWS, video tech, security, monitoring, tools — into this one product. Some of it was human error (the pandemic was stressful). Some of it was my faulty assumptions about year-one volumes.
We fixed the model. We needed to allocate only 5% of platform costs, stripping $10,000 in monthly expenses from the P&L.
Voila! Now the numbers worked. We had an affordable price and healthy margin. Finance approved, we launched, and countless patients got care they wouldn’t have otherwise.
Damn, it feels good to be a product manager!
Story 2
Enterprise SaaS platform. Big logo clients. Strong growth. Ambitious goals: increase bookings by 25% and hit 90% retention.
By December, we had a well established strategy and aggressive roadmap to achieve these goals.
Then, in Q1, the CFO began to beat the drum of “faster revenue recognition.” The culprit? Our long client implementation times.
A quick primer on how enterprise SaaS revenue works:
When a customer signs a contract for your enterprise SaaS product, the business is able to report that to the board as a “booking” — i.e., anticipated revenue.
However, accounting principles state that the revenue can be recognized on the income statement only once the product has been delivered — i.e., once your product has been implemented for the customer and the customer has started using it.
So, the longer it takes to implement the product, the bigger the delta between “bookings” and actual revenue recognition.
This is why an enterprise SaaS company can show $10M in annual bookings, but $4M in annual revenue — that $6M gap represents unfinished client implementations.
This is the type of thing that keeps your CFO awake at night.
Professional Services approached me: “We need to cut implementation time by 35%.”
The problem was our Admin Console — critical for client implementation configuration — was underdeveloped. Not uncommon for growth products where customer features are the product development priority.
Fixing the Admin Console properly would 4 months of dev time, jeopardizing our roadmap and company goals. A non-starter.
So, we got creative.
With Pro-Serv and R&D, we mapped the big vision but delivered incrementally, releasing iterative improvements each quarter. Pro-Serv stayed closely involved as primary users.
By year’s end, we had:
Reduced implementation by 20%
Accelerated revenue recognition by millions of dollars
Set ourselves up for another 15% reduction the following year
While also achieving our top-line company goals
The Overlooked Side of Product Management: Delivery Economics
In both stories, there was a net customer benefit. In the first, the got affordable access to a lifesaving product. In the second, they reaped value faster.
But the primary driver behind pursuing these efforts was business impact.
Most PMs are hyper-focused on customer features. But some of the biggest wins come from improving product delivery and cost levers.
How to identify and prioritize these is what I’m going to teach you today.
Remember:
Product Management’s job is to drive the business growth of the product
ROI is driven by net revenue growth and margin velocity
Margin velocity is driven by:
Product development — the investment needed to build the product
Product delivery — the investment needed to deliver the product to the customer
I talked about the product development side in a previous essay. Today, I’ll cover the product delivery side.
In this issue:
Driving Outcomes Through Product Delivery
Product delivery is the investment involved to actually get your product into customers’ hands. It breaks down like so:
Customer Implementation. This is the work needed to install, deploy, or configure your product.
For software, this varies depending on the type of business:
B2C: Typically zero implementation costs.
Self-Serve B2B: Little to no cost.
Enterprise B2B: Big price tag — tens of thousands to millions.
Infrastructure: The costs to run the production environment — AWS, DevOps, security, monitoring, etc. Your Engineering or IT usually own these, but they impact your product margins.
3rd Party Software Fees: Services you pay for to delivery feature capabilities. Examples: systems integrators; data transmitters; data aggregators; paid APIs; even plugging the paid version of ChatGPT into your product.
While other departments may carry each of these costs, you have strategic levers as a PM. Here are four:
1. Reducing Client Implementation Time
Can you build capabilities that help Implementation, Pro-Serv, or Customer Success get customers live faster?
Example: Our team once had to set up each user manually. 4 hours to set up just one customer with 20 users — days to set up one with over 100. We built a bulk upload feature that let them configure hundreds of users in seconds. At $45/hour for an Implementation Specialist, the savings added up fast.
2. Increasing Client Implementation Efficiency
Sometimes it’s about speed and who needs to be involved.
Example: At one of my companies, setting up a customer’s SSO used to take 4 weeks, $30K, and three different roles — an Implementation Manager, a Systems Analyst, and an Engineer. With automation, we cut the engineer out of the process and reduced setup to 2 days — an 85–95% savings. Plus, the engineer was freed to work on revenue-driving features.
3. Reducing Infrastructure Costs
IT may own them, but they matter to your product’s P&L.
Example: One company discovered that as customer usage scaled, their Oracle costs ballooned even faster than revenue. Growth was actually eroding margins. That insight led to prioritizing a switch to a cheaper, more scalable cloud infrastructure.
4. Reducing or Re-negotiating 3rd Party Contracts
Sometimes it’s a build vs. buy trade-off.
Example: While launching a GenAI product, I faced a choice: use an expensive 3rd-party service (17% margin hit) or delay launch by 3 months to build it ourselves. And the vendor was dangling a 20% discount and license fee waiver if we signed a 3-year contract.
Instead, we took the short-term margin hit, signed for one year, and launched fast. With a live customer ready to deploy and a $500K – $1M pipeline on the line, speed mattered more than margins. We agreed to build our own replacement the following year.
Your Action Steps
Look for initiatives that drive healthier margins or trade-offs with clear economic advantages. Your CFO and COO will love you for it.
This week:
Map your product delivery costs.
Spot opportunities to save cost, speed cycles, or improve the experience.
Prioritize them against your current roadmap.
That’s it for today.
Have a joyful week, and, if you can, make it joyful for someone else too.
cheers,
shardul
Whenever you’re ready, there are 4 ways I can help you:
Inner Circle Membership: In addition to weekly battle-tested real-world PM tactics and strategies to take control of your career, get unlimited community events access, a strategic resume review, and exclusive PM Exchange roundtables. We’re not just building a community, we’re building a movement. Upgrade here.
One Week Product Roadmap: Learn to design a clear, outcome-driven roadmap in just 7 days — fast, practical, and stakeholder-ready. Read the reviews here.
Corporate Training & Strategy Workshops: Transform scattered priorities into a clear, actionable strategy through a customized workshop or level up your product team to think strategically, craft impactful roadmaps, and deliver results that matter. Book a call.
Improv Based Team Building Workshop: Boost creativity, trust, and collaboration through improv. Your team will problem-solve faster and work better together. Book a call.
Shardul Mehta
I ❤️ product managers.