How Startups Can Design Better Products by Building Inside Bigger Ecosystems
- Stephanie Roulic
- 6 hours ago
- 4 min read
At Startup Boston Week, a panel of product leaders and founders unpacked a question many startups eventually face: should you build everything yourself, or plug into someone else’s platform?
Moderated by John Zilch (Product, Breakthrough Ventures), the session featured Ada Glover, Chief Product Officer of Zeus Health, Izzat Jarudi, Co-Founder and CEO of Edify, and Jennifer Bullard, Founder of Yes Yes No. Together, they explored how founders can use platforms, partnerships, and ecosystems to move faster, reach customers sooner, and avoid costly product mistakes.
For early-stage founders, the topic could not be more relevant. Whether you are integrating with Salesforce, building on Apple’s iOS ecosystem, or using Google’s developer stack, most modern startups rely on outside infrastructure in some way. The challenge is knowing when that dependency accelerates growth and when it becomes a liability.
What Is a Platform, Really?
Jarudi described a platform as both a building block and a gateway.
Instead of creating every feature from scratch, startups can use existing tools and infrastructure to solve core problems faster. Mobile operating systems, analytics layers, authentication systems, and messaging tools all fall into that category.
But platforms also offer access to users, partners, and existing workflows.
That second point matters. It is one thing to build a strong product. It is another to place that product where customers already spend time.
Bullard explained that many integrations succeed because they reduce friction. If users can access your product inside the software they already use, they do not need to stop what they are doing, switch tabs, learn a new workflow, or retrain teams.
Why Ecosystems Can Create More Value Than Solo Products
Glover offered one of the session’s strongest lines: “One plus one might equal three.”
Her point was simple. When multiple participants interact inside the same ecosystem, the total value can grow faster than any one company could create alone.
She used a healthcare example from Snowflake, where shared infrastructure helps organizations combine multiple data sources and uncover stronger insights. For startups, ecosystems can create similar leverage:
Faster product development
Easier integrations
Immediate access to existing customer bases
Stronger data sharing opportunities
More seamless user experiences
For founders trying to do more with limited resources, that kind of leverage is hard to ignore.
The Build vs. Buy Decision Every Startup Faces
Eventually, every founder asks the same question: should we build this ourselves or use something off the shelf?
Glover broke the decision into two categories: speed and differentiation.
If the feature is standard, like login systems or basic infrastructure, it often makes sense to buy or integrate. There is little competitive advantage in reinventing a common tool.
But if the feature directly creates unique customer value, that may be worth owning internally.
She gave the example of permissions management at Zeus Health. While authentication could rely on common tools, permissions were core to the company’s differentiated model, so they chose to build.
For founders, that is the real test:
Does this feature make us different, or just functional?
If it only makes you functional, consider buying.
The Hidden Risks of Building on Someone Else’s Platform
While ecosystems can unlock growth, they come with tradeoffs.
Platforms can change pricing, rules, APIs, user permissions, or technical requirements with little warning. Jarudi shared examples from mobile ecosystems where policy shifts around location data disrupted products that depended on that access.
For startups, this creates real risk:
Revenue share fees
Product limitations
Sudden policy changes
Slow partner support
Customer issues you cannot directly control
Glover also warned that many partnerships look stronger on paper than in practice. Just because a platform signs a partnership agreement does not mean their sales team will actively promote you or help drive adoption.
How to Think Like a Platform Yourself
The panel also flipped the conversation: what if your startup becomes the platform?
Bullard noted that many great platforms start by solving one narrow problem extremely well. Amazon began with books. The iPhone evolved from the iPod.
The lesson for founders: start small, earn trust, then expand.
Rather than launching an “ecosystem” too early, focus first on becoming indispensable in one workflow. Once customers trust you, adjacent opportunities become easier to add.
How to Measure If It’s Actually Working
A platform strategy only matters if it creates measurable results.
The panel recommended tracking:
Pipeline growth from partnerships
Faster product development cycles
User satisfaction
Adoption rates
Completion rates for key tasks
Reduced time-to-value for customers
Bullard emphasized usability testing as one of the clearest signals. If users complete tasks faster and with less friction after an integration, you are likely creating real value.
Final Takeaway for Founders
The best startups do not always build more. Often, they build smarter.
Sometimes that means plugging into a larger ecosystem to move faster. Sometimes it means owning the product layers that truly differentiate you. And sometimes it means becoming the platform others want to build on.
The key is understanding where leverage lives and where dependency begins.
In startup product strategy, success is rarely about building everything yourself. It is about knowing what not to build.
