Customer story5 min read

From Figma to Elementor: a shared starting point at 500 Designs

Mauro Carrera De Franceschi explains how Skelementor component references help 500 Designs carry design decisions from Figma into Elementor.

Skelementor customer story featuring Mauro Carrera De Franceschi

At 500 Designs, a handoff can begin with a specific instruction: use Hero 39, then apply the styles. For Mauro Carrera De Franceschi, the agency's Web Development Manager, that reference captures the value of Skelementor. Designers and developers can discuss the same starting structure before implementation begins. The finished website can still have custom styling, animation, and interactions. What changes is how much of the underlying structure the team needs to explain or reconstruct along the way.

Custom websites pass through several hands

500 Designs works across industries and markets, with separate responsibilities for UI, UX, development, and quality assurance. In the interview, Mauro described managing a development team of 25 people, including QA. A useful improvement therefore has to travel beyond one person's editor. A design decision needs to remain understandable when another team starts building it.

Mauro also described an emphasis on scalable websites that clients can manage after launch. Skelementor fits inside that wider agency process. Its role is to provide a foundation for the interface, while the agency continues to make the design and implementation decisions required by each client.

A design needed an implementation reference

Before adopting that shared foundation, the UI and UX team needed to understand what could be built in Elementor. The agency works with multiple technologies, so that understanding could not simply be assumed. Designers could look for references in different places, but those references did not necessarily tell the development team which existing structure to start from.

Mauro's account of the difficulty is practical: a component shown in Figma still needs to become a working component in the website. When the design starts with a known Skelementor section, the reference already carries part of that implementation decision. The developers can identify the structure instead of treating every section as an entirely new construction task.

That does not mean the library defines everything Elementor can do. In this workflow, it gives the teams a visible set of available starting points around which they can plan their own work.

From a Figma reference to Hero 39

Mauro first encountered Skelementor through the Elementor community and videos showing how other builders used it. He bought a lifetime license and began bringing it into the agency's workflow. He also contacted the Skelementor team about access to a Figma kit, because he wanted the UI and UX department to work from the components as well as the developers.

The process begins with the design team reviewing the library and choosing components that can support the interface they have in mind. The section provides a baseline. Designers can then decide how the content, visual treatment, animation, or interaction should behave for that particular website. Those decisions remain part of the agency's work.

The handoff becomes more specific when the design includes the component reference. Mauro gave Hero 39 as an example: developers can retrieve that hero and apply the required styles. They receive a connection between the visual design and an existing structure, rather than only a generic shape in a design file. The reference helps both sides talk about the same thing.

According to Mauro, Skelementor had become the starting foundation for pretty much all of the agency's designs at the time of the interview. That includes work with custom CSS, animation, and interactive behavior. The library supplies a starting structure; the team builds the client-specific experience around it.

There is still a gap Mauro would like to close. He wants client styles and variables established in Figma to transfer into Elementor alongside the components. He described that synchronization as a desired next step. The current benefit comes from the shared component references, while styling and further implementation still require the team's attention.

“we need the hero 39 and then apply the styles to it.”

Mauro Carrera De Franceschi

The gain extends across the handoff

Mauro sees benefits on both sides of the process. Designers have a clearer reference for the structures they can use, and developers have less reason to rebuild those structures from zero. In his account, the improvement comes from connecting stages of work that previously required more interpretation, research, or construction.

Mauro offered a rough, high-level estimate of a 25–30% reduction in time. He also explained why it was difficult to isolate: more than one department benefits, and the work within each phase varies. That was a broad retrospective assessment of the agency's experience. The time required still depends on the project and the custom behavior the team needs to develop.

The more concrete evidence is the handoff itself. A designer can name a component, and a developer can start with that component. That is a specific change another agency can examine in its own workflow, even if its eventual time savings differ.

Custom behavior remains a separate consideration. Mauro noted that designers still need to imagine how a section should behave, and the team continues to implement those decisions. He described Skelementor as the foundation underneath that work. Choosing a known structure lets the agency concentrate its design and development effort on how the component should look, react, and fit the website.

Make the starting structure visible

For agencies with separate design and development teams, Mauro's experience suggests a useful place to start: examine what information survives the handoff. A component reference can connect a visual decision to a structure that the next person can actually retrieve and use.

The detail worth borrowing is the named starting point. Choose the foundation while designing, carry its reference into the handoff, and make the remaining customization clear. That gives both teams a common basis for the work while leaving space for the client's visual identity and interactions. At 500 Designs, Skelementor became useful because the reference was part of the working process, from the design file through to implementation.

GET STARTED

Speed up your workflow in Elementor page builder now

Join thousands of professionals who are already building stunning websites faster & more effortlessly with Skelementor.

Create Free Account