# For agencies

> Design a client site once and keep it that way. Clients edit plain forms, an assistant drafts pages from your components, and it’s free on every site.

## Design it once. It stays designed.

However long the client has the keys.

[Get started](https://lettern.org/download)

[See examples](https://lettern.org/examples)

![A skincare shop’s home page open in the builder.]()

Skincare shop

![An art venue’s home page open in the builder.]()

Cultural venue

![An architect’s home page open in the builder.]()

Architect

![A magazine’s home page open in the builder.]()

Magazine

![An illustrator’s home page open in the builder.]()

Illustrator

## Everyone on the job gets the right screen.

Nobody can reach what isn’t theirs.

Users and roles

### Designers

### Type, colour and motion, on the real page.

Every value is a token, so the next page starts on brand.

![The design screen: a restaurant’s colours beside a live preview of its site.]()

![The design screen: a restaurant’s colours beside a live preview of its site.]()

### Developers

### Templates, fields and roles, in git.

Design and content are plain files. Review them like code.

config/roles.yaml

```yaml
roles:
  client:
    label: Restaurant team
    description: Changes dishes, prices and photos.
    permissions:
      - admin.access
      - entries.dishes.view
      - entries.dishes.edit
      - entries.dishes.publish
      - media.view
      - media.upload
```

### Project leads

### Comments where the work is.

Threads on the page, and @mentions that send an email.

![A question and its answer in the comments panel beside a restaurant’s home page.]()

### Clients

### A form with their words on it.

Dishes, prices and photos. Everything else stays out of sight.

![One dish as the restaurant’s team sees it: a short form with price, course, description and allergens.]()

![One dish as the restaurant’s team sees it: a short form with price, course, description and allergens.]()

### The assistant

### A first draft, from your own components.

It works in draft and waits. You publish.

Spring landing page

Add a landing page for the spring menu, using our hero and menu components.

List Components

6 found

Create Entry

Spring menu

Done. **Spring menu** is saved as a draft, built from your hero and menu components. Nobody sees it until you publish.

## The requests that fill your week.

Most of them no longer need you.

### “Can you change the opening hours?”

Client

They do it, in a form. Your layout isn’t in reach.

### “We need a page for the spring campaign.”

Assistant

It builds a draft from your components. You publish.

### “Can we have that in German too?”

Assistant

It translates the page into a draft to review.

### “Can the brand colour be warmer?”

Designer

One token. Every page follows.

### “Who changed the home page?”

Anyone

The audit log says who and when, and if an agent did it.

### “We want to sell online.”

Commerce

Checkout, invoices and EU VAT, from the store.

## Keep the budget for the work.

Free on every client site, with no seats.

See it on GitHub

### On the host they already have

Any PHP host will do, so there’s no platform bill to explain.

Requirements

### Plugins when a job needs them

The store has paid extras for bigger jobs, starting with Commerce.

Commerce

### Get listed

Studios that build with it can get listed on our partners page.

Partners

## Put your next client on it.

[Get started](https://lettern.org/download)

![A magazine’s home page open in the builder.]()

---
Source: https://lettern.org/for/agencies · Updated 2026-10-30