Should you build core capabilities yourself, or leverage third-party tools and platforms?
Experts
If it's core to your product, build it yourself. Third-party dependencies create risk, limit differentiation, and add complexity. Own your stack, own your destiny.
Don't reinvent the wheel. Use best-in-class tools for non-core functions so you can focus engineering on what actually differentiates your product.
The AI-native startup: 5 products, 7-figure revenue, 100% AI-written code. | Dan Shipper (Every)
Their editorial arm uses AI to publish better work faster, and they even have a person whose entire job is to help every employee at the company become more efficient using the latest AI workflows.
One is, there are a lot of expensive services that rich people and big companies are paid for right now, so in-house counsel or call center or whatever. And what cheap intelligence does is it makes those kinds of things affordable for small companies and individuals. So it stimulates demand.
The ultimate guide to founder-led sales | Jen Abel (co-founder of JJELLYFISH)
It's interesting how similar this is to product building, where there's this idea that a founder top down can tell the team what to build, and it's this very waterfall cycle.
So I've seen, hey, can you come in and actually help me pitch this, design a custom pitch to my boss as to why we should do this today? And we literally got paid to build a sales pitch.
Lessons from scaling Ramp | Sri Batchu (Ramp, Instacart, Opendoor)
Eric, our CEO, has publicly talked about this. I think we as a company are very thoughtful about what we build in-house versus what we buy externally. I think a lot of engineering teams are often excited about building things in-house where there's off the shelf products that could basically work externally. And Ramp has historically been good at not falling into that trap.
I think what we've done differently is we've really focused on making all of those investments very much driven by technology and data. And so one example that I'll give you is that our sales teams are actually incredibly efficient by any metric that we look at and we obviously benchmark them.
Building a magical AI code editor used by over 1m developers in 4 months: Inside Windsurf
One of the key pieces that we recognized was, with this new paradigm with AI, AI was probably going to write well over 90% of the software, in which case the role of a developer and what they're doing in the IDE is maybe reviewing code. Maybe it's actually a little bit different than what it is in the past. And we'll see this very soon with Windsurf.
And this is the fundamental premise on why we built the product. We thought we were going to get limited a ton if we had very, very basic UI out there. And I'll give you even a simple example here. We have this auto-complete product that completes a handful of lines of code.
How to drive word of mouth | Nilan Peiris (CPO of Wise)
Yeah. I think we might've been in this weird temporary phase where, for a while, it was so hard to build product that you mostly just had to be really good at building product and it maybe didn't matter if you had an intimate understanding of a specific customer.
Here's a puzzle for you. What do OpenAI, Cursor, Perplexity, Vercel, Plaid, and hundreds of other winning companies have in common? The answer is they're all powered by today's sponsor, WorkOS. If you're building software for enterprises, you've probably felt the pain of integrating single sign-on, SCIM, RBAC, audit logs, and other features required by big customers.
The ultimate guide to Martech | Austin Hay (Reforge, Ramp, Runway)
Yeah, because they're afraid. There are mutual benefits is a better way of saying it, if you build a tool custom to yourself when you've bought a tool because the vendor at that point is committed to you and they want you to be successful, so you often can get accelerated outcomes if you build on top of a third party than if you just build it yourself.
This comes up all the time, by the way, I talk to businesses every year that have this problem of we have a growth team, we're growing pretty fast. We have a guy that we hired, usually an engineer who stood up all these tools for us.
How marketplaces win: Liquidity, growth levers, quality, more | Benjamin Lauzier (Lyft, Thumbtack)
But building these integrations in-house cost an average of three months of engineering, according to the 2024 State of Integration survey, which results in difficult roadmap tradeoffs. This is why engineering teams at Copy.ai, AI21, and over 100 other B2B SaaS companies use Paragon so they can focus their efforts on core product features, not integrations. The result?
Awesome. Okay, so let's come back to that, because that's a really important topic and it's something that every marketplace trends towards or thinks about is just like we're going to control the supply, we're going to manage it, we're going to maybe own it in the future, but let's get back to that. So, you work with a ton of marketplaces, you've built a bunch of marketplaces.
He saved OpenAI, invented the “Like” button, and built Google Maps: Bret Taylor (Sierra)
Today, my guest is Bret Taylor. Bret is an absolute legendary builder and founder. He co-created Google Maps at Google. He co-founded the social network, FriendFeed invented the like button and the real-time newsfeed, which he sold to Facebook. He then became CTO at Facebook. He then started a productivity company called Quip, which he sold to Salesforce for $750 million.
There's also things like open source, but I think I'm a huge believer in the confluence of technology and capitalism to produce just incredible outcomes for customers.
Finding hidden growth opportunities in your product | Albert Cheng (Duolingo, Grammarly, Chess.com)
Head on over to lennysnewsletter.com and click Product Pass. With that, I bring you Albert Chain, my podcast guest tonight love talking about craft and taste and agency and product market fit. You know what we don't love talking about? SOC 2. That's where Vanta comes in.
So I just encourage taking that first step, just run an A/B test, find a third-party tool or something that you can integrate quickly or even just work with your engineers to spin something up. Just get in the practice of crawl then walk then run type of thing.
How to measure AI developer productivity in 2025 | Nicole Forsgren
See what over 200,000 entrepreneurs love about Mercury. Visit mercury.com to apply online in 10 minutes. Mercury is a FinTech, not a bank. Banking services are provided through Mercury's FDIC-insured partner banks. For more details, check out the show notes. Here's a puzzle for you.
DORA 4, there are four key metrics. There's two speed metrics, deployment frequency and lead time. So code commit to code deploy. There's stability metrics, MTTR and change fail rate. If those are used to assess the speed of the pipeline and the general performance of the pipeline, that's great. If you're trying to use those to understand...
The art of building legendary brands | Arielle Jackson (Google, Square, First Round Capital)
Embedding banking into your product, not only adds differentiation, but also helps you acquire, retain and monetize your customers. Unit is the market leader in banking as a service combining multiple bank partners with a developer friendly API to empower companies of all sizes to launch accounts, cards, payments, and lending in just a few weeks.
Frameworks for product differentiation, team building, and first principles thinking | Ayo Omojola
Because I just find... I'm sure you see this in B2B, this is so much... There's just so much leverage in knowing the person in the place who actually has their finger on the button, versus trying to network your way in, and people don't want to spend their social capital introducing you to this department, or they've just got like 19 other things going on.
235 votes cast
1 comment · Share your perspective
We built our own auth system. Biggest mistake ever. Use Auth0 or Clerk and spend your engineering time on what makes you unique.