Product Management Due Diligence List


  • Conducting due diligence is a skill typically relegated to consulting and investment firms, but it is equally as critical to product managers when evaluating products that they may decide to buy versus build or partner

  • While due diligence typically encompasses all divisions at a given company (financial, legal, sales, marketing, engineering, etc.), we’ll focus on conducting diligence on software products from the perspective of a product manager. 

    • Note that despite this being a product focused list, we will necessarily wander into other divisions of the company due to the nature of product management’s widespread interaction and influence. 

  • This list aims to be as comprehensive and exhaustive as possible, so as to be useful not only during diligence but also as a check for product teams as they build products to ensure they are thinking objectively about their product’s success.

  • Even though lists are difficult to summarize by their nature, the key question to continue to ask about the aspect of each product during diligence is simple - why?

  • Similar to the 3 Levels of Product Thought, diligence can be thought of similarly:

    • Phase 1 - Discover the Current Product 

      • The objective in this stage is not to form an opinion, your role is that of a detached and curious observer intent on understanding the product in its current form. 

    • Phase 2 - Understand the Product’s History

      • The objective in this stage is to understand why the product acts / feels / was designed / was priced / was coded / was released / was sold / was marketed in the way that it has been. 

      • Historical product choices were made for a reason, those decisions and their rationale may be illogical or irrelevant, the goal in this stage is to understand how and why those decisions were made, and begin to form an opinion as to whether those were the right ones. 

    • Phase 3 - Form an Opinion on the Product’s Future 

      • The objective in this stage is to incorporate your understanding from Phase 1, and your historical research from Phase 2, in order to form an opinion on the product’s future.

      • Just as we asked a series of questions in Phase 1 and 2, we will now be providing our opinion in order to answer those exact same questions. 

      • These answers will help us determine if this is truly a product our company wants to purchase. 

  • Downloads - I’ve converted the framework and question lists into downloadable PDF and Word versions.

Detailed Discussion

As the overall due diligence framework was discussed in the summary, we’ll use the detailed discussion section to break down in further detail the exact questions I would, and have used, to evaluate products for potential acquisition. 

The framework above is how you should be thinking about and evaluating the information that you obtain with the following list of questions. Ideally you are using the following questions to build your layers of understanding, but you’ll ultimately need to organize the information provided in to the framework above as it is almost always provided in an ad hoc manner

I have historically tried to pre-solve this problem by structuring my questions around each phase, asking one after the other, but product management is complicated, and answers will frequently interweave information that will be valuable at each stage of your understanding. 

Given the reality of the diligence process, your role as a product manager or analyst is to first capture all the information required and then organize it in to the above framework. In my experience, it is virtually impossible to ask the following list of questions so that the verbatim output and answers are neatly formatted and analyzed. Organizing the information is half the value provided during diligence. 

  • Product Management Due Diligence Question list

    • Customer Observation and Interview - Minimum 10 customers. 

      • While it can sometimes be a challenge to convince the company to let you sit with their customers, it is absolutely critical to understand from a customer perspective how that product is utilized. 

        • One “hack” around the difficulty in obtaining customer access is to watch YouTube tutorials of the product from individuals not associated with the company. These tutorials will often illuminate the flaws in the product that only users will uncover. 

      • Ideally, you interview and observe customers from each of the customer personas and segments discovered during diligence, this can help your team understand where potential opportunities / gaps remain. 

    • Customer Product Experience

      • In addition to watching the customer use the product, it is important to understand their qualitative experience about the product as well. 

      • Feelings

        • How does the product make them feel? Efficient? Happy? Sad? Annoyed? Ignored? 

      • Onboarding

        • How are customers onboarded? Is this automated? Why or why not? Is this the right approach? 

          • Most B2B companies have manual onboarding steps, most of which can be automated at no cost to the customer experience 99% of the time. This is one of the most straightforward product improvements to try to find. 

        • What is each customer’s time to value (The time it takes from when they are sold to when they actually derive value from the product)? Break out by persona / segment / cohort?

          • This can be surprising as well if companies have long sales and installation cycles. Massive improvements can be had in customer satisfaction by fixing this step. 

      • Billing

        • Relating to pricing, how do customers actually pay for the product? Credit card / ACH / Invoice / Check?

        • Are there any issues with billing? Are customers happy about it or would they prefer another way? 

          • You can often produce huge improvements in customer product satisfaction by simplifying the billing process. One would think that companies would be incentivized to make it as easy as possible for customers to pay, but this is not always the case. 

      • Support

        • How are customers supported? Email / phone / chat / text / social channels / in person / support system (Salesforce / Zendesk)? Are these channels good / bad / worthwhile?

        • Is there a public knowledge base? Is it used? Why / why not?

        • Are customers happy with the responses they get? If not, why? If so, why?

        • How, if at all, does customer support relate to customer churn? 

      • Contracts & Service Level Agreements

        • What is the contract signing experience like? What are sample contracts for each persona and customer segment? 

        • What are customer service level agreements? Are they profitable for the company? Are they too strict / too lax? Have they been routinely violated?

        • What are the termination dates? By cohort / product / persona / segment? Is there a termination “cliff” where many contracts come up for renewal at once? 

      • Localization

        • Are all customers English speaking? Are there localization issues? Would the product perform better if localized? Would it reduce complexity to have one product language?

    • Product Team

      • Who are the members of the team? Are they effective? What performance review process exists? Is it effective? Do you want to retain all / some / none of the product team? 

      • What is the product culture? Is it the same as yours? Is it focused on growth / stability / security? What incentive scheme does it operate under? Is the team effective? Will the culture merge with yours? 

      • How is knowledge shared and capture? How are features and product artifacts managed? 

      • Is the product team all in one office? Different offices? Are they remote or in office? 

    • Product Artifacts

      • Competitive Landscapes

        • Who are the primary competitors in the space? 

        • Who are the secondary competitors? Are they worth buying? Why are they secondary? 

        • Who does your sales team see in the sales process? Who do they lose against? Who do they win against? Why do they lose? Why do they win? 

        • Are their substitutable goods / services / products that have been ignored? 

        • Are there competitors that the company is losing against that they are not tracking? Are there competitors on the horizon?

      • Market Maps

        • Market maps are different than competitive landscapes as they include products and services that are in adjacent spaces and industries. These are important to understand both for future product opportunities as well as potential competitors.  

        • What is the space that the company operates in? Is it one of fierce competition (productivity tools) or quasi-monopoly (Uber / Lyft)?

        • Why are they in that space?

          • Most would assume that the company operates in a space that is optimal which is not always the case. Companies can long operate in business spaces and segments that are sub-optimal for a multitude of reasons, some rational, some less so. 

      • User Stories

        • How does the product team produce their user stories? Obtain examples for a recent release. 

      • Customer Personas & Segments

        • Who are the customer personas? What do the product’s customers look like? 

        • What are the customer segments? Are they the same as the personas or different? Why are they different?

      • Product Vision

        • What is the product vision? Why is that the product vision? Is there a product vision or is there just a list of features to be developed?

          • Having a product vision incorporates all of the elements discussed in this list to produce the why behind the value to be delivered to customers.

          • Many companies simply have a long list of prioritized features that are divorced from or ignore the ultimate value they provide to the user. 

      • Go To Market & Target Market Analysis

        • How has the company gone to market with new products and features? 

        • What is the rollout process? For product? For engineering? For marketing? For sales? For services? For customer success?

          • It is important to ask each of these departments independently and without product team members in the room. The goal here is to understand from each division’s perspective how the go to market process works without product influence. 

      • Pricing

        • How are products priced? Monthly / Quarterly / Yearly? Recurring subscription / one time payment / combination? 

        • Are there discounts given? Why are there discounts given? Should they be given?

          • Education / military / special segment discounts?

        • Are products sold at list price or are there discounts given? If so, what are they and why are they given? To what personas / segments?

        • How are those prices displayed to customers? Are they on the website? Do customers have to call or request a quote? How long does it take for a customer to obtain a price for a product?

        • Are the prices reasonable or should they be lowered / raised?

          • It is shocking the level of leverage companies can obtain by simply raising their prices. While this can have many effects, in general it will weed out the customers that are most costly to you / the company and keep the most profitable customers to you / the company. This occurs because raising prices forces those customers to evaluate whether your solution is really worth paying for on a recurring basis.

      • Product & Feature Priorities

        • Relating to product vision, what are the current priorities for each product and how are those broken down into features? 

        • Why are they the current priorities? How were they prioritized (Value, CEO/VP Edict, Big Customer Request)?

          • How products and features are prioritized will tell you a great deal about how products are built, how the product organization functions, and where power is held within the organization. 

      • Product Roadmap - 3 / 6 / 12 Month

        • Relating to product and feature priorities, how do those priorities come together to form the product roadmap for the next 3/6/12 months? 

        • Where is the product roadmap stored? Who has access to it? Why is that the case? 

      • Partner Ecosystem

        • Who are the current partners? What functionality do they provide? Why were those partners selected over other partners in the space? 

        • Are any of those partner solutions better integrated through either building those solutions or acquiring them?

    • Data & Metrics

      • Cohort Analysis

        • What are the retention rates for both customers and revenue, on a per product / customer segment / user persona basis?

        • If you gave me one data point about a product, this would be it. Nearly every other issue can be fixed in this list, but if you can’t retain customers and/or sell them more over time, the product has fundamental issues. 

      • Customer Acquisition Cost - CAC

        • How are customers acquired? What channels? At what cost? Are some channels better / worse than others? Are some channels not being used? 

      • Customer Life Time Value - CLTV

        • What is the lifetime value of your customers? By segment? By persona? 

        • Are all of these profitable? If so, could they be more profitable? If not, why not? 

          • This is another high leverage question, more often than not, there are opportunities to cut underperforming customer segments and raise prices on better performing segments. 

      • Product Usage Metrics

        • How is the product being used? How is that being measured? Time on site / DAU/MAU, core actions taken? 

        • What tools are used to measure this (Google Analytics, Optimizely)? Are staff trained on these tools? Why / why not? 

    • Technical Diligence

      • While technical diligence is an entirely different essay, it’s worth considering some of the questions that can affect the product. 

      • 3rd Party Resources

        • Does the team rely on any consultants? Have they signed the appropriate legal agreements (Ex - IP Assignment, NDA)?

        • How much of the product was developed / designed in house vs outsourced? 

          • This can matter if you are buying just the IP or the team as well.

      • Engineering Process

        • What process does engineering run on? Agile? Waterfall? Hybrid? Is it effective? Why / why not? 

        • Are there dedicated test and staging environments? If so, how are they used? If not, why not? 

        • What systems do you use for code collaboration and revision? 

        • How are secrets (AWS Keys, Encryption Keys, Logins) handled and shared? What are your access controls? What personnel have access to these items? An ability to change them? 

        • Does each product manager have their own engineering resources? Or do multiple product managers assign tasks to one engineering team? 

      • Data Handling, Backup, Recovery

        • What is your disaster recovery plan? Has it been tested? When was it tested? What was the result? 

        • How is data backed up? Has it been tested? When? What was the result?

        • How is data secured? Have you ever conducted security audits? If so, what were the results? If not, why not? 

        • Where is customer data stored? Cloud / on premise / hybrid? 

      • Technology Stack

        • What languages is the product built with? Does your company have expertise in these languages? If not, are you prepared to obtain them? If so, is the level of expertise the same?

          • This is a critical question, as often tech being on a different stack can rule out an acquisition entirely. 

Affirm the Absent


  • At the root of this post is the concept of checking and confirming assumptions – confirming that an issue doesn’t exist, while superficially appearing to not provide any additional information, is actually quite valuable in terms of providing comfort that the present course does not need to be altered.

    • A quick example of this would be instead of remaining silent if a project’s timeline is proceeding as planned, an employee should tell their collaborators that the project remains on course based on the current data and information.

  • This not only provides comfort to those involved in the project, but also serves as a secondary check to see if any of the employee’s collaborators have pertinent information that has not yet been communicated.

    • Affirming that there is no fire is just as valuable to team awareness and communication as finding a spark.

  • If practiced consistently, Affirming the Absent will reduce the chance of Type 2 Errors occurring, or when an action should be taken and isn’t.

Detailed Discussion

Affirming the absent is most valuable in environments where timelines, input variables, resources, and staff are in constant flux.

The reason AtA is so valuable in these environments is because team members may not always be aware of, or be able to control, every factor that may affect deliverables they are responsible for as an individual contributor.

This is particularly true in software product management where a high number of stakeholders are involved in varying capacities and degrees with each product launch.

This concept is also helpful for subject matter experts who are relied upon for their opinions for certain aspects of each project. SME’s can mistakenly assume that those they report to, and collaborate with, possess the same level of knowledge and understanding. SME’s should recognize the information asymmetry and attempt to even the playing field by affirming when the course is proceeding as scheduled. Hearing this affirmed by the SME provides significant comfort to those involved who may be afraid or unable to ask the correct questions to determine if the project is on track.

Additional Examples

  • Airline pilots and staff run through a checklist before every flight, where they positively affirm to each other than there are no issues with the equipment, route or staff. This check of basic assumptions is a key component to making air travel safe and efficient.

  • Project managers providing confirmation that a project is on track given a certain set of assumptions affirms to the team that, if the present course continues, the project’s goals will be achieved. This continuous affirmation can catch hidden assumptions or factors that team members may not otherwise voice which could delay or impact the project.