---
title: "Framer | Skills We Assign For | Azendo"
description: "Framer for high-fidelity prototypes and sites — motion, publishing, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/framer/"
---

[Skills](https://azendo.co/skills/) Design and research 

# Framer.

Framer is a design and publishing tool combining interface design with real interaction, animation and the ability to publish production websites directly from the design canvas.

## Where Framer fits on a long engagement.

Framer is strongest where motion and interaction are the design rather than decoration on it. Scroll behaviour, transitions and gesture-driven interaction are things a static mockup cannot communicate and a Framer prototype can, which matters when the feel is what is being decided.

Publishing directly is genuinely useful for marketing sites and landing pages, where the design and the site are the same artefact. For application work it is prototyping rather than production, and treating it as the latter creates a surface nobody else can maintain.

## What an assigned team does with Framer.

Knowing which of those a project is matters. A marketing site published from Framer is a reasonable decision; an application surface built there becomes a dependency on one tool and one person's access.

Making that boundary explicit at the start is a scoping decision, and what it covers is set out in [how the monthly fee is built](https://azendo.co/pricing/).

## What we use Framer for.

* Motion communicated rather than described Prototypes where the feel is what stakeholders are deciding on.
* Marketing sites published directly Design and site as one artefact where that is the right model.
* A stated boundary against production Application surfaces built in the codebase rather than the design tool.

## How Framer capacity is assigned.

Prototyping capacity is assigned inside design work, with the line between prototype and production stated explicitly at scoping.

## Service lines it sits in

* [UX/UI design](https://azendo.co/services/ux-ui-design/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in design and research

* [Storybook — skill we assign for](https://azendo.co/skills/storybook/)
* [Maze — skill we assign for](https://azendo.co/skills/maze/)
* [Hotjar — skill we assign for](https://azendo.co/skills/hotjar/)
* [usability testing — skill we assign for](https://azendo.co/skills/usability-testing/)
* [design systems — skill we assign for](https://azendo.co/skills/design-systems/)
* [design tokens — skill we assign for](https://azendo.co/skills/design-tokens/)
* [component libraries — skill we assign for](https://azendo.co/skills/component-libraries/)
* [Figma Dev Mode — skill we assign for](https://azendo.co/skills/figma-dev-mode/)

## Tell us what your roadmap needs Framer for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)