Why has Figma acquired the CMS Payload?

Although the content management system (CMS) market is very saturated, Payload had managed to differentiate itself. It had done so thanks to being open source, something unusual in the industry, and above all, thanks to having a different approach from the rest of the managers. Its CEO, James Mikrut, explained it:  

“We are a kind of hybrid between a CMS and an app framework”. 

But it's not just that. Payload has managed to captivate the technical community thanks to: 

• Being flexible and extensible, with a hybrid architecture that does not strictly follow the headless model. 
• Offering superior performance thanks to its local API, which reduces latency. 
• Allowing content modeling directly in code, which facilitates control, integration, and versioning. 

Its differentiation and clear value proposition have led them to work for large companies and institutions, such as Microsoft, Bugatti, or even for the United States Air Force. 

Figma wants to close the gap between design and implementation 

To understand why Figma has decided to acquire Payload, one must look beyond the CMS as a content tool. The key lies in the barriers between design and implementation. 

The gap between design and code has been around for many years. Designers create in Figma, then developers recreate in code, and then content teams struggle to maintain it all. And historically, some CMS had tended to make it worse. 

Now, the integration between both platforms will allow directly connecting the components designed in Figma with the real data and functionalities that will be used in production. 

In addition, this acquisition aligns with the launch of Figma Sites, a new functionality that will allow creating functional websites directly from the design environment. 

AI, one of the underlying reasons 

Figma's decision may also be influenced by the rise of AI. LLMs are starting to generate complete interfaces without human intervention, which threatens the role of design tools.  

Figma is aware of this, and this new move aims to anticipate that scenario. It no longer settles for being a design tool: it wants to become the platform where all stages occur, from the idea to the final publication. 

And now, what will happen to Payload?

Although the collaboration between the two platforms is promising, acquisitions always cause some uncertainty among users. To reassure his audience, James Mikrut clarified:

• Payload remains open source.
• The commitment to creating the best possible developer experience remains high.
• The focus remains on the community.
• The current team will continue to manage Payload.

On the other hand, these are the main new features:

• There's a greater variety of resources.
• Payload can tackle much bigger challenges.
• They'll integrate design systems "like no other CMS can."

What is Figma really looking for? 

 Is it targeting the startup market like Webflow and Framer? Or is it looking to compete with enterprise CMSs like Adobe or Sitecore? Will it continue to coexist with open source solutions like WordPress?

For now, what's clear is that this acquisition marks a profound change. Figma aims to lead the future of design, but also of development and publishing.

Infinitum Digital, experts in digital experiences 

At Infinitum Digital, we accompany our clients throughout the process of creating digital experiences: from strategic consulting and solution design, to technical implementation and continuous growth. 

If you need a partner who understands the current digital landscape from start to finish, do not hesitate to contact us.