Email API
Calendar API
Contacts API 
Scheduler
Notetaker API
Google email & calendar integration
Outlook email & calendar integration
IMAP integration
Calendar management
Embedded contextual email
Scheduling automation
Automated outreach
Expense management
Customer relationship management
Applicant tracking system
Communications platform
Marketplaces
Document management
Docs
SDKs
Tutorials
API status
Changelog
Support
Blog
Events
Guides
Inspiration gallery
Partners
Build vs. buy
Customer stories
Security & Compliance
Why Nylas
Newsroom
Jump to section
Jump to section
Over the past few months on the Platform Builders podcast, I’ve had the chance to sit down with leaders behind some of the most innovative platforms in SaaS, from CRMs and customer success tools to AI-native business builders. What struck me wasn’t just the technical nitty-gritty behind their platforms, but the patterns… the shared philosophies, missteps, and breakthroughs that came up again and again.
There’s a clear through-line: The people building software that others build their future on recognize that adaptability starts in the architecture.
Here are five things I’ve learned from them.
1. Point Solutions Die. Platforms Evolve.
Ben Rubin (CPO at Verify) put it perfectly: “The moat is the platform. In a world where point solutions get wiped out overnight, you have to own the rails.”
Across all five conversations, this theme kept resurfacing: Platform builders aren’t just solving a problem, they’re building more surface area for others to innovate. That means prioritizing extensibility, not just features. APIs, SDKs, and partner ecosystems are no longer nice-to-haves. They are existential. The further away you get from tablestakes infrastructure and deeper into your customer’s pain points… the safer your castle will be.
2. Customer Context is the New Differentiator
Jamie Davidson, CEO at Vitally, made a sharp observation: “Everyone has customer data. The difference is in what you can do with it.”
To me, this is all about fewer tabs and better timing. The best platforms aren’t just centralizing data. They’re contextualizing it. They’re making it more accessible and easier to act on in one interface. Especially in customer-facing tools, surfacing the right insight at the right time is where value gets created. It’s not about more dashboards, and it’s definitely not about more tabs.
3. Don’t Underestimate Product Velocity as a Strategy
Ray Zhou (co-founder of Affinity) talked about how they were able to outpace much bigger competitors by moving faster, even when their infrastructure wasn’t perfect:
“Sometimes the biggest advantage you have is being willing to ship before you’re totally ready.”
Most leaders acknowledged that perfect architecture can slow you down, and that product-led growth often demands shipping with uncertainty. It’s a muscle, not a risk — it’s important to recognize the difference. Teams that win are teams that launch quickly and iterate even faster.
4. AI Shouldn’t Feel Smart — It Should Feel Human
Justin Belobaba emphasized that AI isn’t magic when it’s obvious:
“Good AI disappears. Bad AI asks you to explain yourself.”
This reflects a broader learning: Successful AI integration is subtle. It anticipates, simplifies, and disappears into the background. From notetaking to pipeline building, AI isn’t about adding smarts; it’s about reducing friction. The more customers feel the AI in your product, the less they associate the value received with what you’ve built.
AI should not be the star — your product should be.
5. APIs Aren’t Just a Distribution Model — They’re a Trust Contract
When I asked Brad Rigby from Kanopy what’s changed most about how they think about integrations, he said:
“It’s no longer enough to offer a connection. It has to be durable, observable, and trustworthy.”
In other words, APIs aren’t just plumbing. They’re promises. And for platforms, the quality of those promises can define your growth.
TL;DR
Whether you’re building a developer tool, a vertical SaaS platform, or the next AI-powered workspace, here’s what I’d tell any product leader:
- Think platform-first, even if you’re starting as a tool.
- Design with context, not just access.
- Embrace speed as a competitive weapon.
- Let AI reduce user effort, not increase complexity.
- Treat your API like a product, not just a feature.
If you want to hear these stories directly from the source, check out the latest episodes of Platform Builders.
Let’s keep building.
— Christine
