Product Line Extensions

Deciding when and how to extend a product line: the line map and extension thesis, cannibalisation and fence checks, new editions, tiers and add-ons, pilots and launch readiness, and the reviews that scale or stop them.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Product Line Extensions, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🧩 Product Management

Product Line Extensions

Planning new editions, tiers, add-ons or adjacent products that extend an existing product line into new segments or use cases.

  1. Current product line map with revenue by edition
  2. One-page extension thesis on why to extend now
  3. Adjacent segment candidate list
  4. Choosing between an edition, tier, add-on or new product
  5. Customer evidence file for the extension idea
  6. Success measures and kill criteria for the extension
  7. Cannibalisation risk assessment for the new offer
  8. Platform reuse audit for the extension
  9. Owning team and sponsor for the extension
  10. Extension idea intake and scoring log
  11. Attach rate and add-on uptake review
  12. Plan migration watch for cannibalisation
  13. Sales and success feedback loop on the new line
  14. Extension profit and loss tracking
  15. Quarterly product line coherence review
  16. Edition feature fence register
  17. Pilot customer check-ins for the extension
  18. Annual product line strategy review
  19. Target segment incumbent watch
  20. Lessons from successful and failed line extensions
  21. Fence design for a new edition beside existing ones
  22. Willingness-to-pay methods for a new segment
  23. Adjacency analysis methods
  24. Brand architecture for a growing product line
  25. Unit economics of editions and add-ons
  26. Entitlements and plan configuration for product managers
  27. Lite edition scope and limits for smaller customers
  28. Premium tier above the current top plan
  29. Paid add-on for a high-demand capability
  30. Vertical edition for one industry
  31. Unbundling a core feature into a standalone product
  32. Extension naming and SKU structure
  33. Bundle with the core or sell separately
  34. Go-to-market motion for the extension
  35. Upgrade and cross-sell paths between editions
  36. Extension business case review with leadership
  37. Pilot cohort launch for the new edition
  38. Sales and support enablement session on the new line
  39. Plan page and catalogue readiness for the extension
  40. Six-month extension review to scale, fix or stop
  41. Debut of the extension at an industry event
  42. Second product decision for a single-product founder
  43. Inheriting a sprawling product line as a new manager
  44. Running an extension with a small team beside the core
  45. Folding an acquired product into the line
  46. Moving downmarket from larger customers to small teams
  47. Extension for a new role inside existing accounts
  48. Three-year product line architecture plan
  49. Entitlements model for flexible editions and add-ons
  50. Edition mix and migration analysis across cohorts

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Current product line map with revenue by edition

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before adding anything to a product line, write down what the line already is: every edition, tier, add-on and standalone product, who buys each one and what share of revenue it brings.

First tasks

  • Export the list of active plans and add-ons from the billing system
  • Count customers and revenue on each plan, including legacy ones
  • Write the main buyer and use case beside every item
  • Mark overlaps and gaps on the map and share it with the product leads

One-page extension thesis on why to extend now

Line extensions often start as a sales request or a reaction to a competitor's announcement rather than a strategy. A one-page thesis that states the growth gap, the segment or use case in view, the evidence and why the core product cannot simply absorb the need forces the argument into the open before any engineering time is spent. It is also the document leadership will ask for first.

First tasks

  • Write the growth gap the extension would close in one sentence with a number
  • Name the segment or use case and why the current line misses it
  • Argue the case for improving the core product instead, in one paragraph
  • Send the draft thesis to one sceptical colleague for challenge

Adjacent segment candidate list

The segments closest to your current customers are where extensions usually succeed: a smaller or larger company size, a neighbouring industry, a different role in the same account or a new kind of use. Listing five to eight candidates and describing each by size, current workaround and distance from your core keeps the team from chasing the one segment a single loud prospect happens to represent.

First tasks

  • List the deal types sales loses or turns away most often
  • Describe each candidate segment's current workaround in a sentence
  • Score each candidate on distance from the core customer, one to five
  • Ask sales and customer success to correct the list before shortlisting

Make it yours.

Install Product Line Extensions, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.