How to Build a Product that Scales into a Company

About this video

Chris Gardner is a seasoned FinTech entrepreneur and now General Partner at Boston-based Underscore VC, where he invests in bold early-stage B2B software founders, boasting a stellar track record of co-founding Paydiant (acquired by PayPal) and leading multiple other exits at companies like ExtendMedia, m-Qube, and edocs

Many startups begin with a strong product idea, but few successfully turn that product into a scalable company. This talk explains the often-overlooked “product–company gap” and how founders must design not just the product, but also the go-to-market strategy, pricing, and distribution from the very beginning

Full Video at the end of page

Key takeaways

Core Insight (Plain English)

Many founders start with a product idea and assume that if the product is good enough, a company will naturally emerge. The argument here is that this assumption is wrong. A good product is only the starting point.

To build a real company, founders must deliberately design how the product will be sold, adopted, priced, and distributed. The gap between “a product people like” and “a scalable company” is what the speaker calls the product–company gap. Closing that gap requires thinking about go-to-market strategy, pricing models, distribution channels, and partnerships from the beginning—not after the product is built.

7 Practical Operator Lessons
(For SME Leaders)

1. Product-market fit is not enough

A product that people like or even pay for does not automatically become a company. Many startups reach early traction but stall because they never solve the operational side of scaling—sales, pricing, distribution, and on-boarding.

For operators, the question is not just “Does the product work?” but “Can this product scale into a repeatable business?”

2. Start with a minimum viable segment, not the entire market

Early-stage founders often aim too broadly. Instead of targeting the whole market, focus on one tight segment with a specific pain point.

The goal is to:

• Solve a very specific problem

• Sell repeatedly to similar customers

• Prove the model works before expanding

Once that narrow segment is dominated, expansion becomes easier and more credible to investors.

3. Talk to customers before building anything

One practical tactic: talk to hundreds of potential users before writing code.

This process reveals:

• Whether the problem is urgent

• How much customers would pay

• Which segment cares the most

The insight here is simple but often ignored: customer conversations are cheaper than product development mistakes.

4. Design the product for distribution, not just functionality

A scalable product is easy to adopt. Chris proposes a framework called SLIP:

• S – Simple to install and use

• L – Low initial cost

• I – Instant and ongoing value

• P – Plays well in the ecosystem

Products that meet these criteria spread faster because they reduce friction for customers trying something new.

5. Early pricing should reduce adoption friction

Pricing is not just a revenue decision—it is a growth decision.

Common approaches include:

• Free trials

• Freemium models

• Tiered pricing

These approaches lower the barrier to first adoption while still allowing upgrades as customers gain value from the product.

6. Partnerships can accelerate growth dramatically

A strategic partner can change the trajectory of a startup.
Examples include:

• Platform integrations

• Distribution partnerships

• Ecosystem positioning

Instead of building everything independently, smart founders design products that fit naturally into existing ecosystems.

7. Spending patterns flip as companies scale

Early startups spend mostly on engineering.
As companies mature, spending shifts heavily toward:

• Sales

• Marketing

• Customer success

In mature SaaS companies, around 40% of revenue may go to sales and marketing while only about 20% goes to product development. This reflects a reality operators eventually face: distribution often becomes more expensive than development.

Summary & Reflections

The ideas here are not particularly glamorous, but they reflect a practical truth about company building.

Many founders obsess over the product itself. Yet the examples in the talk suggest that successful companies treat product design and business design as the same problem. A technically impressive product can still fail if it is hard to deploy, expensive to adopt, or disconnected from existing ecosystems.

For SME operators—especially in Southeast Asia where markets are fragmented and distribution can be messy—the lesson is even more relevant. The winning product is often not the most advanced one. It is the one that fits naturally into how customers already work and buy.

Who should watch the full video

This video is particularly useful for:

• Startup founders moving from prototype to real revenue

• Product managers building SaaS or platform products

• ASEAN SME founders developing software or tech-enabled services

• Operators preparing to raise venture funding

Anyone transitioning from “building a product” to “building a company” will likely find the full talk useful.

Until next time,
The SME Signal editorial Team