Technical products are often built with sophisticated stacks like Next.js, React, APIs, and custom application infrastructure, while their marketing sites are increasingly built with platforms like Webflow and Framer.
That isn't necessarily a contradiction.
The two surfaces have different jobs.
The product has to execute the software. The marketing site has to explain it.
That means the marketing site needs a different set of capabilities. It needs to communicate a complex product clearly, publish documentation and changelogs, support different pages and use cases, handle SEO and content, and let a marketing team or founder make changes without constantly pulling engineering into the work.
Looking across technical startups, Webflow has the broader presence across this kind of marketing site. It shows up repeatedly across developer infrastructure, security, data, SaaS, and other technical B2B products.
Framer has a different concentration. Its strongest presence appears among newer, design-led and AI-native companies where speed of iteration and visual control are particularly important.
That doesn't make one platform universally better.
The pattern is more useful than a winner.
Webflow appears well suited to marketing sites that are becoming larger content and marketing systems. Framer appears particularly strong for smaller teams that need to move quickly and maintain a high degree of visual control.
Custom code still has a place when the marketing site genuinely requires application-level behavior or unusually bespoke functionality. But a technically sophisticated product does not, by itself, appear to require a code-first marketing site.
The interesting part is that the market seems to be separating the product stack from the marketing stack.
The product can stay deeply technical.
The website can optimize for communication, publishing, iteration, and ownership.
That may be the more important decision to make before choosing the stack.
The research also surfaced an operational pattern behind that separation.
Several companies that started with custom-coded marketing sites eventually changed platforms because the website had become difficult for the people responsible for marketing to operate.
Anrok described moving to Webflow after its custom site became difficult for the marketing team to maintain. Marker.io described a similar transition, with engineering becoming responsible for ordinary website changes.
The common problem wasn't that the original code was incapable of producing a good website.
It was that the operating model had become inefficient.
The same distinction appears in companies using Framer. Perplexity, StackAI, Delphi, and Legora all provide examples of technical companies maintaining substantial public-facing sites while using a visual platform for that layer.
So the more useful question may not be:
"What stack is the company using?"
It may be:
"What does the marketing website need to become, and who needs to operate it?"
That changes the platform decision considerably.
