Developer Experience Drives Platform Adoption
Diving deeper into
Jason Lengstorf, VP of Developer Experience at Netlify, on Jamstack's anti-monolith approach
that developer experience so good that the developers advocate for it within the company -- that’s your best sales motion.
Analyzed 5 sources
Reviewing context
The real product is not hosting, it is an easier way for developers to get work live without waiting on infra teams. Netlify and Vercel win when a frontend engineer can connect a Git repo, see preview builds for every change, deploy only the files that changed, and add serverless functions without stitching together AWS services by hand. That creates internal pull from the people building the site every day.
-
This is classic bottom up adoption. Teams often start with a docs site, landing page, or prototype where speed matters more than perfect standardization. Once developers show that deploys go from hours to minutes and previews make review easier, managers approve spend because the workflow is visibly faster.
-
The comparison is Heroku for modern frontend apps. The underlying compute and CDN are mostly commodity cloud pieces, but the value sits in opinionated defaults and polished workflow. Several interviews describe AWS as fully capable but painful, while Netlify and Vercel package the same building blocks into a tool developers actually enjoy using.
-
There is a clear limit to this sales motion. It is strongest for startups, prototypes, marketing sites, ecommerce frontends, and small teams inside large companies. At very large scale, enterprises often rebuild on their own cloud stack to lower bandwidth costs or fit internal security and edge requirements.
This motion points toward a bigger platform play. The companies that keep winning will be the ones that turn developer love into broader team adoption by adding security, collaboration, and enterprise controls, while keeping the original fast path that made engineers push for the tool in the first place.