A marketing team ships without a developer
Technology
Framer is a design tool that is also the CMS and also the host. The bundling is the whole proposition: content changes happen in the browser, deployment is one click, and nobody waits on an engineer to publish a page. The trade is that you rent the runtime and always will.
We built Meritech Capital's site in Framer. Meritech has led two funding rounds for the company, most recently a $100M Series D that valued it at $2B, so the platform did not need selling. What it needed was a component structure that survives another hundred pages.
The build
What Framer is genuinely good at, and where the ceiling is
- Reusable components, or it stops scaling
Dragging sections onto a canvas produces a site that gets harder to change with every page added. Meritech's is assembled from reusable Framer components instead, so a brand change happens once. The platform allows both approaches, and only one of them is still maintainable a year in.
- Code overrides are the honest ceiling test
Custom components and code overrides let a developer go past the templates, and that is the test of whether Framer fits. If what you need lives inside a component, build it there. If it needs a server, an auth session, or your own data layer, it belongs elsewhere.
- Leaving means rebuilding, so decide early
Editor, CMS, and hosting are one product, and there is no copy of this site sitting in a repository you own. Moving off Framer later is a rebuild, not a migration. For a portfolio site answering to a marketing team that is a fine trade. For an application surface it is not.
