Planhat scaled a Framer website by starting with an in-house redesign, then turning the work into a system that more people could use. A six-month first version gave the team a foundation. New design, brand, and motion contributors could then improve the site without sending every decision through a separate production handoff.
Start with a website redesign that has an owner
Planhat had always had a website because a company needs one. The site did not yet have a clear owner or a strong connection to the brand and product. Alberto received a mandate from the co-founders to reimagine both.
That mandate changed the work. Instead of waiting for a large web team or an outside agency, Alberto built the first version himself. Within six months, Planhat had a V1 website built completely in-house with Framer.
The first version did not need to solve every future requirement. It needed to create a working base that the team could inspect, improve, and extend. A clear owner made that possible.
Bring more people into the same Framer website
After the first launch, Planhat faced a familiar scaling problem. The company needed more creative capacity, but adding people can also add more handoffs. Alberto brought in Shaked, an experienced web designer, to help the team move forward.
Shaked describes the core frustration clearly: a designer can create something strong and then watch the final implementation lose the details that made it work. Framer gave the team a way to keep more of those decisions in the website itself.
Access alone was not the change. Planhat gave contributors a shared environment where they could see the system, make a change, and review the result in context.
Build infrastructure, not another one-off page
The Planhat team uses Framer to create infrastructure that other people can use. That includes the visual rules of the website, the way pages connect, and the details that keep the brand consistent as more contributors join.
This is where a design system becomes useful. A system does not remove creative judgment. It gives the team a common starting point for type, spacing, color, components, and motion. Contributors can work on the part they understand without rebuilding the whole site around each new idea.
The team also points to interconnectivity as a reason it can scale. A change in one place can support work in another because the pieces live in the same Framer project. The system carries context that a handoff document often loses.
Why a Framer website became Planhat’s source of truth
The video describes Framer as Planhat’s go-to-market source of truth. The product, positioning, and messaging all need to stay aligned, and the website is where those decisions become visible to customers.
Framer is our go-to-market source of truth.
That work is shared across disciplines. Shaked acts as the website’s lead designer and architect. Claudio, the brand designer, can contribute a small systematic decision, such as a border radius. Dan, the motion designer, can build an asset that gets embedded directly into the site.
The result is a shorter path from decision to outcome. The team can make a brand adjustment, test it in the real website, and keep moving without waiting for a separate implementation cycle.
Scale complexity without losing the craft
Planhat is now a larger enterprise with offices in London, Los Angeles, Stockholm, and elsewhere. The company is growing quickly, but the video describes its teams as small, focused, and made up of people who care deeply about their craft.
That combination creates a specific requirement for the website. It must support complex work without making every contributor become a specialist in the entire stack. The team says Framer makes complex things intuitive to build, so people can focus on the quality of the decision in front of them.
This is a useful distinction for an enterprise website. Scale does not only mean more pages or more people. It means more inputs, more updates, and more chances for the brand to drift. A shared Framer website gives those inputs a common place to land.
What teams can take from Planhat
Planhat’s workflow offers five practical lessons for teams scaling a website:
Give the redesign a clear owner. One person can create the first version and set a quality bar before the team expands.
Ship a usable V1. The first release creates something concrete to test, improve, and build on.
Hire for capacity, not more handoffs. Add people who can work inside the same system and see their decisions in context.
Turn repeated decisions into infrastructure. Components, styles, and patterns help contributors move faster while keeping the brand coherent.
Make the website part of go-to-market. Product, brand, content, and motion should be able to reach the live experience without a long translation layer.
The main lesson is simple: Planhat did not scale its website by separating creative work from production. It built the first version in-house, brought more specialists into the same Framer project, and made the system easier for the whole company to use.
Watch the full Planhat story on YouTube, explore Framer for startups, or learn more about Framer CMS.
