Product — Part 1: From Expertise to a Product Ecosystem

Designing Products That Create Outcomes, Build Trust and Scale a Business

Introduction

You have already built the foundations.

You understand:

Concept — what business you are building.
Audience — who you are building it for.
Offer — what you are offering.
Sales — how you convert opportunity into revenue.
Pitch — how you communicate your vision.
Publish — how you turn your knowledge into public value.

Now we arrive at:

PRODUCT

This is where your expertise becomes:

a structured mechanism for creating transformation.

A Founder often thinks a product is:

“What I sell.”

But a sophisticated Founder thinks differently.

A product is:

a designed experience that moves someone from their current state to a desired outcome.

That distinction changes everything.

Learning Objectives

By the end of this module, you will be able to:

Define what a product actually is.
Understand why customers buy outcomes rather than inputs.
Understand the Product Ecosystem.
Distinguish between a Gift, Product for Prospects, Core Product and Product for Clients.
Design a Product for Prospects.
Use products to build trust.
Create a bridge between free attention and paid commitment.
Understand why product ecosystems outperform isolated products.
Identify opportunities for productisation.
Begin designing a scalable and profitable product ecosystem.

1. What Is a Product?

Let's begin with a deceptively simple question:

What is a product?

At first glance, the answer seems obvious.

A product is:

something you sell.

But this definition is incomplete.

Consider three bottles of sparkling wine.

One may cost:

£15.

Another:

£40.

Another:

£150.

They may all contain grapes.

They may all go through broadly similar production processes.

Yet people willingly pay dramatically different prices.

Why?

Because:

the physical contents are not the entire product.

The product includes the:

experience,
meaning,
positioning,
story,
status,
context,
expectation,
transformation.

The source uses the contrast between different sparkling wines to demonstrate that customers are purchasing very different outcomes, even when the underlying physical substance may be similar.

2. People Don't Buy the Thing

People rarely buy:

the thing itself.

They buy:

what the thing does for them.

A customer buying a luxury bottle may be buying:

status.

Another may be buying:

celebration.

Another may be buying:

social enjoyment.

The physical product is only:

the mechanism.

The desired experience is:

the product's real value.

3. Product = Outcome + Experience

A useful way to think about a product is:

Product = Mechanism + Experience + Outcome

The mechanism is:

what you deliver.

The experience is:

how the customer goes through the journey.

The outcome is:

what the customer ultimately gets.

And the further up the value chain you go:

the more important the outcome becomes.

4. Stop Selling the Mechanism

This principle is especially important for service businesses.

A coach might say:

“I sell coaching.”

A consultant might say:

“I provide consulting.”

A software company might say:

“We sell SaaS.”

A designer might say:

“I run design sprints.”

These describe:

the mechanism.

But the customer is thinking:

“What will this do for me?”

5. Sell the Outcome

Imagine someone wants to build a better leadership team.

They may think they need:

a coach.

But what they really want is:

great people on the team,
better leadership,
less operational dependence,
more freedom,
better performance.

The coach is:

the vehicle.

The desired future is:

the product in the customer's mind.

The source makes this distinction explicitly: people don't ultimately hire a coach because they want “coaching”; they choose the intervention because they believe it will reliably deliver the outcome they want.

6. The Magic-Wand Test

Ask your customer:

“If I could wave a magic wand and give you exactly what you wanted, what would your life or business look like?”

Do not immediately ask:

“What service would you buy?”

Ask:

“What outcome would you want?”

This reveals the actual value.

7. The Outcome Conversation

A powerful sequence is:

What do you want?

↓

Why do you want it?

↓

What is stopping you?

↓

What would change if you achieved it?

↓

What would that mean for you?

This takes you from:

surface-level requirement

to:

deep customer motivation.

8. Product Is Transformation

A strong product moves someone:

FROM

their current reality,

TO

their desired reality.

Therefore:

Product = Transformation

For example:

FROM

Overworked Founder

↓

Founder leading a capable team with freedom and control.

Or:

FROM

Unclear business model

↓

Clear, scalable, profitable business model.

9. The Product Ecosystem

One of the most important concepts in this module is:

The Product Ecosystem

A profitable business rarely depends on one isolated product.

Instead, it can contain several connected products.

A useful four-stage ecosystem is:

1. Gift

Creates attention and familiarity.

↓

2. Product for Prospects

Builds trust and commitment.

↓

3. Core Product

Solves the problem and delivers the primary outcome.

↓

4. Product for Clients

Maintains standards and creates continued improvement.

The source explicitly describes these four components and their different roles.

10. The Four Products

Think of the ecosystem as a journey:

Product	Primary Purpose
Gift	Attract attention
Product for Prospects	Build trust
Core Product	Deliver the outcome
Product for Clients	Maintain and improve results

Each product has:

a different job.

Confusing those jobs creates weak product design.

11. Product 1 — The Gift

A Gift is something your Audience can consume freely.

Examples include:

articles,
podcasts,
videos,
checklists,
guides,
useful resources,
educational content.

The purpose is:

give value before asking for commitment.

12. The Gift Builds Familiarity

The Gift allows people to think:

“I like this person's thinking.”

Then:

“They understand this problem.”

Then:

“I want to learn more.”

The Gift creates:

familiarity.

And familiarity creates the possibility of:

trust.

13. Your Published Content Can Be the Gift

This connects directly to the previous module:

Publish

Your content doesn't have to be a separate system from your product system.

Your:

YouTube videos,
podcast,
articles,
social posts,
interviews

can function as:

Gifts.

The source gives the example of freely available podcasts, books and other content serving as Gifts that allow people to discover and understand the creator.

14. Don't Overcomplicate the Gift

A Gift doesn't need to be:

a 200-page PDF.

It could be:

a 10-minute video.

Or:

a podcast episode.

Or:

a useful checklist.

Or simply:

an insightful article.

The question is:

Does this give the Audience something genuinely useful?

15. Product 2 — The Product for Prospects

Now we move one step deeper.

The Product for Prospects is not merely:

free content.

It is designed to create:

trust + commitment + momentum.

Its purpose is to move someone from:

“I'm interested.”

toward:

“I want to explore working with you.”

16. The Commitment Ladder

Customers rarely jump instantly from:

No

to:

Yes, I'll buy your main product.

There is usually a sequence.

No

↓

Curiosity

↓

Interest

↓

Engagement

↓

Trust

↓

Commitment

↓

Purchase

The Product for Prospects helps:

bridge the gap.

The source describes this explicitly as creating a series of smaller steps that bridge the gap between “no” and “yes.”

17. The Product for Prospects Builds Trust

A Gift says:

“Here is something useful.”

A Product for Prospects says:

“Let's experience something useful together.”

That difference matters.

The prospect may:

complete an assessment,
attend a workshop,
read a book,
use a diagnostic,
experience a small service,
receive a quick win.

Now they have:

evidence of your capability.

18. Examples of Products for Prospects

Common examples include:

Scorecards

The customer evaluates their current position.

Assessments

They discover gaps or opportunities.

Workshops

They experience your thinking and methodology.

Books

They consume a structured body of your expertise.

Introductory Services

They experience a smaller part of your solution.

The source identifies scorecards, assessments, books, workshops and basic services as examples.

19. Quick Wins

An excellent Product for Prospects should ideally create:

a quick win.

The prospect should think:

“That was useful.”

Better:

“I already got value from this.”

Even better:

“If this is what I got from the first step, imagine what the full solution could do.”

20. The Demonstration Principle

Don't merely tell people:

“I'm good at this.”

Let them experience:

what it feels like to work with you.

Your Product for Prospects becomes:

a demonstration of the core product.

It gives the prospect evidence.

21. The Bridge Principle

Think of the Product for Prospects as a bridge:

PROSPECT

“I'm not sure.”

↓

PRODUCT FOR PROSPECTS

“Let me experience this.”

↓

TRUST

“This person understands me.”

↓

CORE PRODUCT

“I'm ready to commit.”

The bridge reduces:

perceived risk.

22. Product 3 — The Core Product

The Core Product is where the primary transformation happens.

Its purpose is:

solve the problem or deliver the desired outcome.

This is the product most Founders instinctively focus on.

And it is important.

But:

it does not exist in isolation.

23. The Core Product Is the Main Transformation

The Core Product should answer:

What meaningful outcome will the customer achieve?

It should also define:

what happens,
how it happens,
how long it takes,
what is included,
what support exists,
what the customer must do,
what success looks like.

The product should be:

deliberately designed.

24. Product 4 — Product for Clients

The journey doesn't necessarily end after the initial transformation.

A Product for Clients can:

maintain standards,
prevent regression,
provide ongoing support,
improve performance,
introduce new capabilities,
create continuous improvement.

The source describes this fourth layer as maintaining standards over time or improving results beyond the initial outcome.

25. The Full Product Journey

The ecosystem therefore becomes:

DISCOVER

Gift

↓

TRUST

Product for Prospects

↓

TRANSFORM

Core Product

↓

CONTINUE

Product for Clients

This is a complete customer lifecycle.

26. Why Ecosystems Matter

A common mistake is asking:

“What is my product?”

A better question is:

“What is my product ecosystem?”

Because a business becomes more powerful when products:

feed one another.

For example:

Book

↓

Scorecard

↓

Workshop

↓

Core Programme

↓

Advanced Programme

The individual products make sense because:

the ecosystem makes sense.

27. Don't Evaluate Products in Isolation

One product might intentionally:

make little or no money.

Another may be:

free.

Another may be:

highly profitable.

Another may exist mainly to:

retain customers.

That doesn't mean the ecosystem is broken.

The correct question is:

“How does this product contribute to the entire customer journey?”

28. The Ecosystem Effect

Consider a business with:

books,
scorecards,
workshops,
programmes,
coaching,
consulting.

If you examine each independently, some may appear:

unprofitable.

But together they may create:

a highly profitable system.

The source emphasises that the economic value can emerge from the ecosystem, rather than any single product operating independently.

29. The Apple Lesson

A useful productisation principle is:

Simplify the core.

When Steve Jobs returned to Apple, the company had an enormous number of products.

The strategy was simplified around:

consumer vs professional,
desktop vs laptop.

This created:

a clear core product architecture.

The lesson:

Product ecosystems do not mean endless products.

They mean:

connected products with clear roles.

30. Product Ecosystem ≠ Product Catalogue

A catalogue says:

“Here are 27 things we sell.”

An ecosystem says:

“Here is the journey we take you on.”

That distinction is enormous.

Customers don't want:

more products.

They want:

a clearer path to their desired outcome.

31. Start With the Customer Journey

Don't start by asking:

“What product should I create?”

Start with:

“What journey does my customer need to go through?”

Map:

Where are they now?

↓

What do they need to understand?

↓

What do they need to experience?

↓

What transformation do they need?

↓

What support do they need afterwards?

Then design the products around:

that journey.

32. Product Architecture

Your product ecosystem should have:

Entry

How do people discover you?

Engagement

How do they experience you?

Transformation

How do they achieve the main outcome?

Continuity

How do they maintain and improve the result?

This is:

product architecture.

33. The Role of Publishing

This connects directly to:

PUBLISH

Your content creates:

awareness.

Your Gift creates:

value.

Your Product for Prospects creates:

commitment.

Your Core Product creates:

transformation.

Your Product for Clients creates:

continuity.

Therefore:

Publish feeds Product.

34. Content → Product

Your content can reveal:

what people care about.

Their questions reveal:

what they don't understand.

Their problems reveal:

what needs solving.

Their behaviour reveals:

what they will commit to.

Your best content can therefore become:

product research.

35. Build From Real Problems

Your product should emerge from:

real customer problems.

Not:

“I think this would be cool.”

Instead:

“I've repeatedly seen this problem.”

Then:

“I've repeatedly solved it.”

Then:

“I can now package the solution.”

That is:

productisation.

36. Productisation

Productisation means taking something that may currently be:

customised,

inconsistent,

dependent on you,

and turning it into:

a repeatable solution.

The transformation is:

Expertise

↓

Method

↓

Process

↓

Package

↓

Product

37. The Method Is the Backbone

You already developed your methodology during:

Publish.

Now Product asks:

How do we package that methodology into an experience?

For example:

Methodology

Concept → Audience → Offer → Sales

can become:

a startup programme.

And:

Pitch → Publish → Product → Profile → Partnership

can become:

a Creator Founder programme.

38. The Product Is More Than a Service

A product may contain:

software,
videos,
documents,
coaching,
community,
workshops,
templates,
assessments,
implementation,
support.

These are:

components.

The product is:

the complete transformation created by combining them.

The source illustrates this by explaining that coaching, software, videos and internal documents can all be components of one larger outcome-focused product.

39. The Full and Remarkable Solution

A powerful product is not necessarily:

one service.

It can be:

A Full and Remarkable Solution

Meaning:

everything necessary to reliably move the customer toward the desired outcome.

This could include:

education,
implementation,
accountability,
community,
tools,
coaching,
technology.

40. Do It Yourself → Do It With You → Do It For You

Products can sit along a spectrum.

Do It Yourself

The customer does most of the work.

Examples:

book,
course,
templates.

Do It With You

You work together.

Examples:

group programme,
coaching,
workshops.

Do It For You

You execute the work.

Examples:

consulting,
implementation,
managed service.

A sophisticated ecosystem may contain:

all three.

41. The Product Spectrum

The three models can be represented as:

DIY

→

DWY

→

DFY

The further you move toward:

Do It For You

the more implementation responsibility you take.

The further toward:

Do It Yourself

the more responsibility sits with the customer.

The right mix depends on:

the outcome, Audience and economics.

42. Group Does Not Mean Inferior

A common mistake is thinking:

one-to-one = premium

and:

group = cheap.

Not necessarily.

A group can provide:

peer learning,
community,
accountability,
shared experience,
multiple perspectives.

Sometimes:

the group itself is part of the value.

The product should therefore be designed around:

the best way to create the outcome.

43. Design the Delivery Around the Outcome

Ask:

What must happen for the customer to succeed?

Then determine:

What delivery mechanism creates that result most reliably?

Not:

“What delivery model do I personally prefer?”

The customer outcome comes first.

44. The Product Design Questions

For your Core Product, answer:

Outcome

What will they achieve?

Duration

How long will the journey take?

Inclusions

What is included?

Structure

How does the experience work?

Support

What help do they receive?

Pricing

What is the economic exchange?

The source explicitly uses these categories when designing the Core Product.

45. Outcome Before Price

Don't begin with:

“How much should I charge?”

Begin with:

“What outcome am I creating?”

Then consider:

How valuable is that outcome?

How reliably can I deliver it?

How much effort is required?

What alternatives does the customer have?

What is the cost of not solving the problem?

Price becomes:

an output of product design.

46. Product Options

Once your core product is understood, you may offer:

two or three options.

Why?

Because one option creates a binary decision:

Yes / No

Multiple suitable options create:

Which one is right for me?

The source recommends more than one but no more than three purchase options, such as different durations or package levels.

More choices do not automatically create more value.

A strong product ecosystem may contain many products across the customer lifecycle.

But the customer should encounter:

clarity.

At each stage:

What is the next best step?

48. Product for Prospects: The First Commitment

The Product for Prospects is particularly important because it creates:

the first meaningful commitment.

The commitment might be:

attending a workshop,
completing a scorecard,
booking an assessment,
reading a book,
trying a small service.

It is not necessarily the final purchase.

It is:

the next step.

49. The Commitment Ladder

A useful model:

FREE CONTENT

↓

GIFT

↓

PRODUCT FOR PROSPECTS

↓

SALES CONVERSATION

↓

CORE PRODUCT

↓

PRODUCT FOR CLIENTS

Every step increases:

commitment.

50. The Product for Prospects Should Create Momentum

A good Product for Prospects should make the next step feel:

natural.

After the workshop:

“Let's discuss your situation.”

After the scorecard:

“Let's review your results.”

After the assessment:

“Let's design your solution.”

The transition should feel like:

the next logical step.

51. Don't Give Away the Whole Core Product

There is an important distinction between:

demonstrating your capability

and:

delivering the entire transformation for free.

The Product for Prospects should give:

insight + quick wins + trust.

The Core Product delivers:

the complete transformation.

52. Demonstrate the Method

A powerful Product for Prospects can let someone experience:

one part of your methodology.

For example:

Scorecard

Diagnose the problem.

Workshop

Understand the solution.

Core Product

Implement the solution.

This creates a logical progression.

53. Product for Prospects as a Filter

A good Product for Prospects doesn't just:

attract people.

It also:

filters people.

If someone completes your scorecard and loves your workshop:

they are more likely to be a fit.

If they don't resonate:

you've saved everyone's time.

This improves:

sales efficiency.

54. The Ideal Prospect Journey

Imagine:

“I've heard about you.”

↓

“I'll consume some content.”

↓

“I'll take the scorecard.”

↓

“I'll attend the workshop.”

↓

“I'll speak with you.”

↓

“I'll buy the core product.”

This is much easier than asking someone to go directly from:

stranger

to:

high-ticket buyer.

55. Product for Prospects + Sales

The Product for Prospects prepares the prospect for:

Sales.

By the time the sales conversation happens, they should already understand:

the problem,
the importance,
your perspective,
your methodology,
some of your credibility.

The sales conversation can therefore focus on:

their specific situation.

56. Create Transparency Around Capacity

If your Core Product has limited delivery capacity, your Product for Prospects can help make that transparent.

For example:

Many people may consume the scorecard.

But:

only a smaller number can enter the Core Product.

This creates a legitimate distinction between:

demand

and:

delivery capacity.

57. Ethical Urgency

Urgency should come from:

real constraints.

Examples:

limited places,
limited delivery capacity,
fixed programme start dates,
genuine implementation constraints.

Do not manufacture fake scarcity.

The source specifically frames limited capacity as a way to protect the quality of the outcome delivered, while transparently explaining the difference between demand and available capacity.

58. Product Ecosystem and Scalability

A well-designed ecosystem can help a business become:

more scalable.

Instead of:

Founder does everything for everyone.

You create:

self-serve assets,
group experiences,
technology,
standardised processes,
recurring products,
client success systems.

This reduces dependence on:

Founder time.

59. From Founder Dependency to Product Dependency

The goal is not:

“How can I work harder?”

It is:

“How can the product create the outcome more reliably without requiring all of my personal time?”

That is the beginning of:

scalable expertise.

60. Product Ecosystem and Business Value

When your ecosystem is deliberately designed, you can create:

scalability,
repeatability,
profitability,
stronger customer journeys,
better conversion,
recurring revenue,
intellectual property,
greater business value.

The source describes the deliberate development of a product ecosystem over time as a route toward a business that is more saleable, scalable and less dependent on any one individual.

61. The Product Flywheel

Your complete system now looks like:

PUBLISH

↓

Create awareness

↓

GIFT

↓

Create value

↓

PRODUCT FOR PROSPECTS

↓

Create trust and commitment

↓

SALES

↓

Create the right customer relationship

↓

CORE PRODUCT

↓

Create transformation

↓

PRODUCT FOR CLIENTS

↓

Create continuity

↓

PUBLISH

↓

Create more awareness.

The system compounds.

62. Product Is a System, Not an Object

The most important conceptual shift in this module is:

Stop thinking about products as objects.

Think of them as:

systems for creating outcomes.

A product is not:

a course.

It is:

the transformation the course enables.

A product is not:

coaching.

It is:

the result created through the coaching experience.

A product is not:

software.

It is:

the job the software enables the customer to accomplish.

63. The Product Formula

Remember:

CURRENT STATE

↓

PROBLEM

↓

METHOD

↓

EXPERIENCE

↓

OUTCOME

↓

TRANSFORMATION

That is the heart of product design.

64. Product Design Exercise — Part 1

Complete the following.

My Audience

Their Current State

Their Biggest Problem

Their Desired Outcome

What Would Their Life/Business Look Like After Achieving It?

What Is Preventing Them From Getting There?

65. Product Ecosystem Exercise

Now design the four layers.

1. Gift

What can people freely consume?

2. Product for Prospects

What can they experience to build trust?

3. Core Product

What creates the primary transformation?

4. Product for Clients

What maintains or improves the result?

66. Product Journey Exercise

Draw your customer's journey:

Current State

↓

Desired Outcome

Now ask:

What product belongs at each stage?

67. Outcome Exercise

Complete this sentence:

“My customer isn't really buying ____________. They are buying ____________.”

Examples:

“They aren't buying coaching. They are buying leadership freedom.”

“They aren't buying software. They are buying operational efficiency.”

“They aren't buying consulting. They are buying a future-proof business.”

This exercise often reveals:

the real product.

68. Productisation Exercise

Take something you currently deliver manually.

Ask:

What do I repeatedly do?

What steps do I repeatedly follow?

What principles guide those steps?

What could be standardised?

What could become a template?

What could become software?

What could become training?

What could become part of a product?

69. Product Quality Checklist

A strong product should answer:

70. Product Ecosystem Checklist

You should also know:

71. The Founder Product Test

Ask yourself:

If I disappeared for 30 days, could my product still create value?

If the answer is:

No

ask:

What part depends unnecessarily on me?

Then ask:

Can I turn that knowledge into a process, system, asset, technology or team capability?

This is the beginning of:

product-led scalability.

72. The Product Ecosystem Test

Now ask:

If someone discovers me today, what happens next?

Can they:

Discover my content?
Consume a Gift?
Take a meaningful next step?
Experience my methodology?
Enter a sales conversation?
Buy the Core Product?
Continue with me afterwards?

If the answer is yes:

you have the beginnings of a Product Ecosystem.

73. The Bigger Picture

Think back to where we started.

You built:

a profitable startup.

Now you are building:

a profitable startup Founder.

The difference is leverage.

A Founder who only sells:

time

has limited capacity.

A Founder who packages:

knowledge

can scale expertise.

A Founder who builds:

products

can scale transformation.

A Founder who builds:

a product ecosystem

can scale the business.

74. Product Is Where Knowledge Becomes Leverage

Your journey is now:

EXPERIENCE

↓

KNOWLEDGE

↓

CONTENT

↓

TRUST

↓

PRODUCT

↓

TRANSFORMATION

↓

REVENUE

↓

ASSETS

↓

SCALE

This is the Creator Founder model.

75. Part 1 Conclusion

In this first part of Product, you learned the most important conceptual shift:

Your product is not what you deliver.

It is:

the outcome and transformation your customer experiences because of what you deliver.

You also learned that one product rarely needs to carry the entire business.

Instead, build:

A PRODUCT ECOSYSTEM

with:

Gift

Create awareness.

Product for Prospects

Create trust and commitment.

Core Product

Create transformation.

Product for Clients

Create continuity and improvement.

Together they create:

a customer journey.

And that customer journey creates:

a business system.

PRODUCT — PART 1 COMPLETE

From Expertise → Product → Transformation → Ecosystem

You now understand:

what a product is,

why outcomes matter,

how products fit together,

why the ecosystem matters,

and:

how Product connects with Publish and Sales.

But we have not yet finished Product.

The next part goes deeper into:

designing the Core Product itself.

That means turning your methodology into a Full and Remarkable Solution, defining its structure, inclusions, delivery, pricing, options and client journey — and ultimately designing a product that can deliver the promised outcome reliably, repeatedly and profitably.