To shift a services-oriented company to a product mindset, frame productization as a competitive advantage. Repeatable, productized solutions offer greater market differentiation than purely custom builds, leading to more effective competition and new deal wins. This tangible benefit helps secure buy-in from sales and leadership.

To prevent engineers from gaming output-based pay, 10X assigns a "Technical Strategist" to each project. The engineer is paid for output, but the strategist is incentivized by client retention and account growth (NRR), creating a healthy tension that ensures high-quality work is delivered.

During a transformation from services to product, identify and commercialize the reusable tools that services teams have already built to support clients. Instead of starting from scratch, productizing these existing "mini-products" aligns them with the broader product strategy, saves development time, and leverages proven solutions.

Project-based companies operate on a cash flow mindset, accepting any custom work that brings in immediate revenue. A true product company uses an investment mindset, strategically saying 'no' to short-term revenue to invest in building a scalable asset that can win a market long-term.

Assigning expansion quotas to Customer Success (CS) is a critical mistake. CS should focus on implementation, adoption, and value realization, creating the conditions for growth. However, the act of selling the expansion is a core sales responsibility that requires a sales skillset and incentive structure.

Engineering often defaults to a 'project mindset,' focusing on churning out features and measuring velocity. True alignment with product requires a 'product mindset,' which prioritizes understanding the customer and tracking the value being delivered, not just the output.

In a truly product-led company, the product organization must accept ultimate accountability for business-wide challenges. Issues in sales, marketing, or customer success are not separate functional problems; they are reflections of the product's shortcomings, requiring product leaders to take ownership beyond their immediate domain.

Product leaders often try to implement agile best practices within their team, but fail because the surrounding organization still operates on a project-based model. The rest of the company treats the product team like a feature factory, handing over requests and demanding deadlines, creating immense internal friction.

In an organization still running in project mode, the 'Product Manager' title is misleading. The role is often relegated to organizing work and scheduling tasks for engineering. A true product model requires empowering these roles with the mandate, skills, and market access to make strategic decisions.