Engineering · May 8, 2025 · 7 min read
WhywestandardisedonNext.jsforeveryproduct
After building 40+ platforms on every stack imaginable, we now start almost every engagement in Next.js. Here’s why.
D
David Ochoa
CTO
Framework choice is one of the most expensive decisions a team makes and one of the hardest to reverse. After enough scars, we now default to Next.js on almost every engagement.
One mental model, front to back
Server components + route handlers cover 85% of what teams historically split across two codebases. Fewer moving parts, fewer context switches, faster people.
The performance ceiling is higher than most stacks’ floor
Between streaming, PPR, and image/font pipelines, well-built Next.js apps land in the top 5% of Lighthouse scores with very little extra work.
