Key Takeaways
Turn expertise into a product, or growth stays chained to headcount
The business model changes. Productization means packaging a repeatable tool or program so it can be sold at a defined price, often with technology helping deliver it at scale. A consulting firm that sells only expert hours must usually add people to serve more clients. If it packages its data, methods, or training into a product, it can serve more buyers without increasing staff at the same rate.
Start at the edge. Empower, a Cincinnati media agency with roughly $250 million in annual revenue, began exploring new revenue streams through small employee teams. Over five years, it developed offerings including a media-buying platform and a planning tool for smaller companies. The aim is not to abandon services, but to combine them with scalable products. The book cites typical gross margins of 60 to 90 percent for product businesses, compared with about 40 percent for customized services, while emphasizing that product development takes upfront investment.
The central shift is from selling scarce expert attention to selling an asset that can be reused. That is an economic change, but also a change in what the firm considers valuable: knowledge becomes valuable when it is made usable beyond the person who first applied it. The strongest version preserves human expertise for judgment, trust, and complex exceptions while products handle repeatable needs. The margin comparison is useful as a strategic signal, not a guarantee. Software, data, and subscription offerings still require support, maintenance, and customer acquisition, costs that can erode the apparent advantage.
Standardize repeatable value before trying to automate everything
Scale has several rungs. The Innovation Ladder describes a progression from customized services, through standardized service packages and standalone products, to ongoing subscription offerings. A productized service still needs people to deliver it, but customers buy a defined package rather than a bespoke engagement. A standalone product can be sold to many buyers, while a subscription provides continuing access to a standardized offering.
Mix the ingredients. Each offering combines intellectual property, technology, and service in different proportions. A consulting firm might first package a repeatable workshop, then sell a report, and later provide continuously updated data through a subscription. Armstrong’s Productize Pathway treats this work as an iterative journey: build organizational support, identify a worthwhile customer problem, shape and test an offer with others, bring it to market, and improve it through use. Firms need not climb every rung.
This continuum helps avoid a common false choice: either remain a bespoke service firm or become a software company. Standardization can create value before automation, and technology is only useful when it makes a validated offer easier to deliver or use. The framework also invites a practical question: which elements must remain human because they require judgment, and which repeat often enough to package? That distinction matters because over-automation can strip out the very trust or adaptation that makes a professional service worth buying.
Treat culture and capacity as product infrastructure, not HR polish
People make the transition. A product-friendly culture is an organization prepared to develop repeatable offers, learn from experiments, and work across functions. It takes more than hiring a product specialist. Leaders need to explain why the shift matters, model openness to testing, and make room for skills in design, technology, product management, marketing, and analytics. Dedicated capacity matters too, because urgent client work otherwise consumes the time meant for innovation.
Make the vision concrete. Linkage, a leadership-development consultancy, aimed to expand its impact to 500 organizations. Customized work alone could not support that ambition. Its CEO introduced shared behaviors, such as asking questions, adopting technology, and seeking different perspectives, then reinforced them in leadership meetings and performance processes. The company also brought in product expertise and reorganized work around collaboration rather than relying only on existing service teams.
The key insight is organizational: a new product cannot thrive inside routines designed to reward customization, billable utilization, and immediate client response. A compelling vision gives people a reason to tolerate the discomfort of changing those routines, while concrete behaviors turn the vision into daily practice. Diverse teams can widen the range of problems and solutions considered, but diversity alone does not guarantee good decisions. Leaders must create conditions where disagreement is safe and useful, then give teams enough authority and time to act on what they learn.
Protect innovation funding from client work's gravitational pull
Allocate before urgency wins. Product development rarely succeeds as an after-hours assignment for client-facing staff. Existing work delivers immediate revenue, so it will usually crowd out a product whose payoff is uncertain and delayed. The book offers rough benchmarks, not universal rules: around 2 to 3 percent of revenue for early exploration, with substantially larger budgets possible for development and launch. The crucial discipline is deciding in advance how ideas earn further investment.
Make tradeoffs visible. One company selling training reduced the share of its product team’s effort devoted to custom requests from about 40 percent to 15 to 20 percent within five months. It required sales staff to document the business case for each exception, with senior leaders deciding whether it justified the diversion. Firms can also compare ideas using estimated revenue, confidence, and effort, but should define those measures clearly and revisit them as evidence changes.
This is a capital-allocation problem disguised as a creativity problem. A firm that funds innovation only with leftover time has already chosen its priority, regardless of what its strategy says. Separating product decisions from routine operating budgets can help protect uncertain opportunities from being judged by mature-business metrics. At the same time, scoring systems can create an illusion of precision: early revenue estimates are hypotheses, not forecasts. Their value is to expose assumptions and support comparison, not to turn uncertainty into a supposedly objective ranking.
Validate urgent, expensive pain, not the problem customers mention most
Find the costly cause. A frequently mentioned complaint is not necessarily a problem customers will pay to solve. In one example, professionals working away from home often described loneliness, but interviews revealed greater urgency around uncertain job assignments and finding temporary housing. An airline faced complaints about delays, yet its data suggested the deeper frustration was inconsistent communication about those delays. In both cases, digging beneath the first complaint changed what the product should address.
Test the market, not your enthusiasm. Start with hypotheses about the problem, who experiences it, and how they solve it today. Interviewing a mix of buyers, users, prospects, and former customers can reveal motivations and root causes. Then check whether the relevant segment is large enough to support a product. The book calls that opportunity the Total Addressable Market, or TAM: the revenue available if the offering captured the entire market. A single client’s request is not proof of broad demand.
Problem discovery is a form of disciplined skepticism. Customers can describe frustration accurately while misidentifying its cause, and organizations can mistake the most visible complaint for the most valuable opportunity. Combining interviews with behavioral or market data helps distinguish what people say from what they do. The TAM question adds an important second filter: a real pain in a tiny segment may support a bespoke service, but not the investment required for a scalable product. Market size should not replace customer evidence, but it can prevent a locally compelling idea from becoming an expensive dead end.
Let customers and developers shape products before expensive code hardens
Make ideas tangible early. Co-creation means involving customers and people beyond the core product team in designing and developing an offer. It can begin with existing intellectual property, data, or documented service methods, then move through rough concepts and prototypes. Customer conversations are useful, but actual behavior is stronger evidence than stated enthusiasm. A sell-then-build test gauges demand before full development; a Concierge Test delivers the idea manually to a small group; Wizard of Oz Testing makes a service appear automated while people perform the work behind the scenes.
Learn without overbuilding. Zappos began by photographing shoes in a local store and buying a pair only after an online customer ordered it. That manual process tested whether people would buy shoes online before a complex retail operation existed. In development, designers and developers should hear the customer problem and product vision, not just receive a fixed feature list. Small user tests can then expose confusion and usability problems while changes are still manageable.
Early prototypes reduce the cost of being wrong by making assumptions visible before they become code, contracts, and internal commitments. The manual versions are particularly powerful because they test whether the underlying service has value, not whether a polished interface looks appealing. There is, however, a trust boundary: simulated automation should not mislead users about reliability, privacy, or what is actually being delivered. Good experiments keep the risk low for customers and make clear what is being tested, while giving the team enough contact with real use to learn.
If your product can replace your service, competitors can too
Examine the overlap. Leaders often fear a product will draw revenue away from higher-priced consulting. Armstrong’s cannibalization framework asks firms to compare the customers and needs served by the new offer with those served today, look for products that complement existing services, and consider whether a competitor could disrupt the business first. A tool aimed at smaller companies, for example, may open a market that cannot afford bespoke work rather than steal current clients.
Choose the risk deliberately. A market research firm found that much of its custom reporting could be automated and offered through a self-service dashboard. The shift worried leaders because it might replace a large share of existing work. Yet refusing to build it would leave the opportunity open to another provider. The book argues that product and service relationships can also work in both directions: a product may attract customers who later need expert help, or support clients already using services.
Cannibalization is not automatically a win. A cheaper product may attract new buyers, but it can also shift existing customers to a lower-revenue option or weaken the perceived value of expert work. The useful decision is not simply whether overlap exists, but whether the new offer improves the firm’s position across the whole customer relationship. This requires segment-level evidence and a credible account of what happens to service capacity, pricing, and customer outcomes. The strategic warning remains sharp: protection can preserve near-term revenue while allowing the underlying customer need to migrate elsewhere.
Price around customer value, then equip sales to sell differently
Give buyers useful choices. Tiered packages can serve customers with different budgets and needs, while a free entry level can let buyers experience a limited offer before upgrading. The book cautions against setting an immature product’s permanent price too low; an introductory discount should be identified as temporary. Messaging should also reach beyond features to the outcome customers want. A training product, for example, may sell not merely lessons but a way for an organization to build needed skills.
Change the sales motion. Selling a standardized product is not the same as selling a custom engagement. Product sales may depend more on clear demonstrations, repeatable collateral, and lead generation. Strategy Execution offered salespeople a 3 percent commission on consulting work and 6 percent on subscription sales to encourage the new focus. Sales teams also need to understand the customer problem, the product roadmap, and how a first purchase may connect to other offerings.
Packaging and incentives are not cosmetic details; they shape who buys, what they expect, and which internal behaviors become profitable. Tiering can reveal where customers see value, but too many options can make comparison harder. Similarly, a higher commission can redirect attention, yet it cannot compensate for a weak product or confused positioning. The most durable sales transition links incentives to customer fit and equips salespeople to explain the product’s specific use, limits, and path of improvement. Clear expectations are especially important when early versions are still changing.
Treat launch as the first measurement cycle, not the finish line
Usage reveals value. A Minimum Viable Product, or MVP, is a deliberately limited version that tests important assumptions in real use. It is not simply a cheaper final product. After launch, onboarding should help buyers and users reach value quickly, while usage data and customer conversations reveal where they struggle. One Metric that Matters, or OMTM, is the primary signal a team uses to judge whether customers are moving toward meaningful product use. For one offering, early attendance at a live event was linked to renewal, making attendance a useful signal.
Improve what evidence identifies. Teams should review product performance, customer feedback, costs, renewals, and the roadmap, then update their assumptions and priorities. Dyson’s vacuum business illustrates the persistence of iteration: its founder built 5,271 prototypes while learning from each version. That number is not a recommended target. The lesson is that an MVP creates value only when the team has the capacity to respond to what customers actually experience, including problems the initial design did not anticipate.
Launch changes the evidence available: teams move from forecasts and interviews toward observed behavior, retention, and support needs. That shift is only useful if someone is accountable for interpreting the signals and changing the product. A single headline metric can focus attention, but it can also distort behavior if teams optimize the signal rather than the customer outcome it represents. Pairing usage measures with qualitative feedback and business results helps reveal whether customers are succeeding, not merely clicking. Iteration is a capability, not a slogan; it needs people, budget, and decision-making authority.
Analysis
Productize is strongest when read as a guide to changing the operating system of a professional services firm, not as a recipe for turning expertise into software. Its central insight is that scalable products emerge when firms make knowledge repeatable, build new capabilities around that knowledge, and shift investment toward customer value that can serve more than one client. The product itself is only one part of the transition. Culture, incentives, sales, customer research, and governance determine whether it can survive beside a service business optimized for immediate custom revenue.
The book’s most useful discipline is its repeated demand for evidence before commitment. Start small, test real demand, and treat initial plans as revisable assumptions. This is especially important in firms where senior experts can mistake their own confidence for market validation. A client request may be a valuable clue, but it does not establish a segment, a price, or a repeatable need. Likewise, an attractive margin comparison does not guarantee that a particular product will scale profitably.
The deeper tension is between repeatability and responsiveness. Standardization makes delivery more efficient, but professional services often succeed because they adapt to context. The strongest product strategy therefore does not remove human judgment indiscriminately. It identifies what can be made consistent, what requires human support, and how the two reinforce each other. Products can make expertise accessible and services can help customers realize its value, but that relationship must be designed rather than assumed.
The practical test for leaders is not whether the organization has announced a product strategy. It is whether teams can spend protected time on it, learn from customers without punishment, decline custom work when it conflicts with the strategy, and improve the offer after launch. Without those conditions, productization remains a side project. With them, it becomes a credible path to broader reach and less dependence on selling expert hours one engagement at a time.
Review Summary
Productize receives mixed reviews, with an average rating of 3.92 out of 5. Readers appreciate its clear framework for product development and actionable insights for professional service firms looking to scale. Many find it useful for mid-market to enterprise companies, praising its emphasis on customer collaboration and innovation. However, some critics argue that the content is too generic, lacks specificity for small businesses, and doesn't provide enough guidance on identifying productization opportunities. Some view it as a marketing piece for the author's services, while others find it a valuable resource for product management.
Glossary
Productize Pathway
Iterative product development routeArmstrong’s approach for helping services firms develop scalable products through repeated learning and adjustment. It connects organizational readiness and investment decisions with customer problem discovery, collaborative design and development, market launch, and ongoing product improvement. The pathway is meant to be adapted over time rather than treated as a rigid, one-way sequence.
Innovation Ladder
Stages of product scalabilityA model for describing offerings that range from customized, people-intensive services to standardized service packages, standalone products, and ongoing products delivered through subscriptions. Moving upward generally increases the use of technology and the potential for scale, revenue visibility, and stronger margins. A firm does not need to pass through every stage.
Minimum Viable Product
Smallest useful market testA version of a product designed to test key assumptions with real users or buyers while limiting the cost of development. It includes enough functionality to test the product’s core value, but is not simply a reduced or cheap final product. Its purpose is to generate evidence that guides subsequent development.
Total Addressable Market
Maximum market revenue opportunityThe total revenue opportunity available if a product captured all customers in its defined market. It is estimated using the number of potential customers and the average price. In product planning, TAM helps assess whether a target segment is large enough to justify developing and maintaining a scalable offer.
3 C’s of Cannibalization
Assess product overlap and disruptionA framework for assessing whether a new product may displace existing services and how to respond. It examines overlap between current and prospective customer needs, opportunities to create complementary offerings, and the risk that competitors will disrupt the existing business. The framework supports informed tradeoffs rather than an assumption that existing revenue can be fully protected.
One Metric that Matters
Primary customer success signalA selected metric that receives priority among the many measures a product team may track. It should indicate whether customers are reaching meaningful value from the product. For example, early use of a particular feature or participation in an included event may signal stronger engagement or renewal likelihood, depending on the product.
Wizard of Oz Testing
Manually simulate automationA product test in which customers experience what appears to be an automated service, while people perform some or all of the work manually behind the scenes. This lets a team test demand and refine the experience before investing in full technical development. The test should avoid misleading customers about matters that affect trust or their use of the service.
Concierge Test
Manual early customer deliveryA test in which a small group of customers receives an early version of a proposed product through hands-on, manual service. The team observes what customers need, how they respond, and which parts of the experience create value. It can reveal whether the underlying offer works before the organization builds systems to deliver it at scale.
FAQ
1. What is "Productize: The Ultimate Guide to Turning Professional Services into Scalable Products" by Eisha Armstrong about?
- Transforming Services to Products: The book provides a comprehensive blueprint for professional services firms (consulting, marketing, training, etc.) to convert their expertise and offerings into scalable, often tech-enabled, products.
- Productization Framework: Eisha Armstrong introduces the Productize Pathway™, a step-by-step method tailored for service organizations to innovate, develop, and launch successful products.
- Real-World Examples: The book is filled with case studies, practical tools, and stories from leaders who have successfully navigated the productization journey.
- Avoiding Common Pitfalls: It highlights the seven most common mistakes organizations make when shifting from services to products and offers actionable solutions to avoid them.
2. Why should I read "Productize" by Eisha Armstrong?
- Growth and Scale: If you lead or work in a professional services firm and want to grow revenue without proportionally increasing costs, this book offers a proven roadmap.
- Competitive Advantage: The book addresses how to stay relevant and competitive in a market increasingly disrupted by digital-first and tech-enabled competitors.
- Practical Tools: Readers gain access to downloadable frameworks, templates, and diagnostic tools to apply the book’s concepts directly to their business.
- Cultural Transformation: It goes beyond product development, focusing on the leadership and cultural changes required for successful productization.
3. What are the key takeaways from "Productize" by Eisha Armstrong?
- Think Big, Start Small: Begin with a bold vision but use iterative, small-scale experiments to test and refine product ideas.
- Solve Urgent, Expensive Problems: Successful products address real, pressing, and costly customer problems, not just frequently mentioned annoyances.
- Be Fearless: Overcome internal resistance, especially fears of cannibalizing existing services, and embrace bold moves to innovate.
- Productization is a Journey: The transition requires new skills, organizational structures, and a test-and-learn mindset, not just process changes.
4. How does Eisha Armstrong define "productization" in "Productize"?
- Scalable, Packaged Offerings: Productization is turning customized, people-intensive services into scalable, often tech-enabled, products that can be packaged, named, and sold repeatedly.
- Innovation Ladder: Armstrong describes a progression from customized services to productized services, to products, and finally to products-as-a-service (e.g., SaaS, DaaS).
- Mix of IP, Tech, and Service: Every productized offering combines intellectual property, technology, and service in varying ratios depending on the business model.
- Recurring Revenue Focus: The goal is to create offerings that generate recurring revenue and higher profit margins compared to traditional services.
5. What is the Productize Pathway™ method in "Productize" by Eisha Armstrong?
- Six-Part Framework: The Productize Pathway™ includes: Create a Product-Friendly Culture, Align to Support Innovation, Define the Right Problem, Co-Design and Develop, Launch Boldly, and Manage & Iterate.
- Iterative, Customer-Centric: The method emphasizes continuous learning, rapid prototyping, and customer involvement at every stage.
- Avoids Common Mistakes: Each step is designed to help organizations sidestep the seven deadly productization mistakes outlined in the book.
- Action-Oriented Tools: The pathway is supported by practical tools and templates available for download to guide implementation.
6. What are the "Seven Deadly Productization Mistakes" described in "Productize"?
- Focusing on Processes Before People: Neglecting the cultural and behavioral changes needed for productization.
- Starting Too Big or Too Perfectly: Over-investing in untested ideas and delaying market feedback.
- Favoring Existing Business Over New Products: Under-resourcing new product initiatives due to short-term revenue focus.
- Not Solving an Urgent and Expensive Problem: Building products that don’t address real customer pain points.
- Designing and Developing in a Vacuum: Failing to involve customers and stakeholders in the design process.
- Starving Products Due to Fear of Cannibalization: Avoiding innovation that might disrupt current services.
- Stopping at the MVP: Not iterating and improving after the initial product launch.
7. How does "Productize" by Eisha Armstrong recommend creating a product-friendly culture?
- Vision and Leadership: Start with a clear, inspiring vision for productization, modeled and reinforced by leadership.
- Behavioral Change: Focus on changing behaviors across the organization, not just processes or structures.
- Skill Development: Hire or develop talent with product management, technology, and analytics skills, not just subject matter expertise.
- Cross-Functional Teams: Break down silos and encourage collaboration through agile, multi-disciplinary teams.
- Test-and-Learn Mindset: Foster a culture that values experimentation, rapid feedback, and continuous improvement.
8. What is the importance of solving "urgent and expensive problems" in "Productize"?
- Market Fit: Products that address urgent and expensive problems are more likely to be adopted and valued by customers.
- Avoiding Wasted Investment: Focusing on real pain points prevents building solutions that no one wants or needs.
- Customer Research: Armstrong advocates for hypothesis-driven research, customer interviews, and competitive analysis to identify these problems.
- Segmentation and Personas: Understanding which customer segments experience these problems ensures the product has a large enough market.
9. How does "Productize" by Eisha Armstrong suggest organizations should co-design and develop products?
- Co-Creation Approach: Involve customers, employees outside the core team, and developers early and often in ideation and prototyping.
- Rapid Prototyping: Use MVPs, concept testing, and pre-development market tests (like sell-then-build or Wizard of Oz) to validate ideas quickly.
- Leverage Existing Assets: Catalog and repurpose unique intellectual property, data, and processes as the foundation for new products.
- Iterative Development: Continuously solicit user feedback and refine the product through multiple iterations before and after launch.
10. What strategies does "Productize" recommend for launching and marketing new products, especially regarding cannibalization fears?
- Address Cannibalization Directly: Use the 3 C’s framework—Customers, Complementary, Christensen—to analyze and mitigate cannibalization risks.
- Tiered Pricing and Packaging: Offer multi-level pricing (e.g., Good-Better-Best, Freemium) to attract different customer segments and maximize value.
- Compelling Messaging: Focus on the ultimate benefit (“the product of the product’s product”) and tailor messages to different personas.
- Sales Enablement: Equip sales teams with the right tools, training, and incentives to sell new products, and communicate the vision repeatedly.
11. How does "Productize" by Eisha Armstrong advise organizations to manage and iterate on products post-launch?
- Customer Success Focus: Develop robust onboarding, usage measurement, and customer success processes to maximize renewals and upsells.
- Data-Driven Improvement: Monitor key usage metrics (like the “One Metric That Matters”) and gather qualitative feedback to guide enhancements.
- Regular Roadmap Updates: Maintain and update product roadmaps based on market feedback, performance data, and evolving business goals.
- Portfolio Management: Review the entire product portfolio regularly to allocate resources, spot cross-sell opportunities, and ensure strategic alignment.
12. What are the best quotes from "Productize" by Eisha Armstrong and what do they mean?
- “Think Big, Start Small.” – Encourages organizations to have ambitious goals but to begin with manageable, low-risk experiments.
- “If you are not embarrassed by the first version of your product, you’ve launched too late.” (Reid Hoffman, quoted) – Stresses the importance of launching early to gather real market feedback rather than waiting for perfection.
- “If you don’t cannibalize yourself, someone else will.” (Steve Jobs, quoted) – Highlights the necessity of self-disruption to stay competitive.
- “The most successful companies take a co-creation approach to both design and development.” – Underlines the value of involving customers and stakeholders throughout the product development process.
- “Productization is a critical part of the growth strategy for business services.” – Emphasizes that turning services into products is essential for scaling, improving margins, and increasing company valuation.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.