Elisabeth SaehrProduct designer, Lausanne
CopyDash · own product · 2026

Clients write on the real page. The layout holds.

CopyDash lets agencies and their clients write website copy directly on the approved design, within each field’s limit, with an AI that suggests and never overwrites. I interviewed the project managers, designed the product and its design system, and built it alone.

In development, with a pilot agency
Role
Solo: research, product, UX/UI, design system, front and back end
Timeline
Mar 2026, market review and first mock-ups · Jun–Jul, interviews → building since
Platform
Web app for agencies, their teams and their clients
Research
3 interviews with agency project managers · market review
The designed interaction. The client’s paragraph is too long for the layout. They ask for a shorter version, the suggestion stays within the limit, and the page only changes once they apply it. Demo copy. Recreated from the product for this page.

In 30 seconds

3 of 3project managers I interviewed see clients change the copy after the layout is done.
1place for the copy, the feedback and the approval, instead of Word files, Sheets and email.
4page statuses, each one saying whose turn it is: the agency’s or the client’s.
÷2time spent moving copy between the design and documents, at least.Hypothesis, to test
Problem

Clients write their copy in Word, away from the design. It arrives late, too long or too short, and the layout gets reworked, round after round.

What I did

Interviewed three agency project managers, reframed the product around the copy’s whole life, designed a multi-brand system, and built the app with AI suggestions inside each field’s limit.

Where it stands

A working web app, in development with a pilot agency. No usage figures yet. The AI flows were prototyped with a live model; the build uses a stand-in until a model is wired.

The problem

I lived this problem as a web project manager

Before CopyDash, I was a web project manager and a freelance UX/UI designer. On every project, the content ran on its own track, apart from design and development. The design got approved, and then the real copy arrived: in a brief, a Google Doc, a spreadsheet, an email. Never quite the length the layout was drawn for.

  1. 01Client drafts copyOften placeholder, incomplete
  2. 02Wireframes and designDrawn for a length nobody has fixed
  3. 03PM copies text into a documentBy hand, from Figma or a PDF
  4. 04Client edits the documentWithout seeing the page
  5. 05Layout adjustmentThe copy doesn’t fit. The design moves.
  6. 06ApprovalIs this the final version?
  7. 07Prototype to developersWeeks after design approval
The copy’s journey today, as I mapped it from my own projects and the interviews. Step 5 is where time goes, and it comes back every time the client changes the copy.

Clients don’t see how long their copy is until it sits in the final layout. By then, every change costs a designer.

Tools like Content Snare collect content through forms, apart from the design. They fix the chasing, not the fit. I wanted the client to write where the copy will live, and to see the limit before breaking it.

Research · interviews

Three project managers, one problem I hadn’t framed

Video calls in June and July 2026 with three project managers who run website and app projects with clients. I asked how copy is collected, reviewed, approved and handed off, and where it hurts. I showed the third one an early version of the idea. The lines below come from my interview notes, not word-for-word quotes.

A
Project manager AApp and website projects

Her clients used colours: yellow for draft copy for the prototype, green for copy approved for development.

The status idea, before I had drawn any status.
B
Project manager BWebsite projects, often multilingual

Giving clients access to Figma is too risky: they could change more than the text. And French takes more space than English.

Ruled out the shortcut. Added translation to the list.
C
Project manager CAgency, websites and apps

One large copy change once meant a full redesign, billed again. Rare, when expectations are set early.

Saw the idea as a fit for a premium agency.
What they describedABC
Clients change the copy after the layout is done3/3
Copy lives in Word, Docs or Sheets, away from the design3/3
Clients can’t picture how much text fits2/3
Draft and approved copy get mixed up2/3
Clients shouldn’t get the design file2/3
The PM moves copy by hand between design and documents1/3
Translations change the length1/3
What it changed
Collecting contentThe copy’s whole life

I set out to build a collection tool. None of them struggled to get the first draft. They struggled with what happens after: copy that changes once the layout exists, versions nobody is sure about, text moved by hand from one tool to the next.

Three interviews is a signal, not proof. It was enough to change what I designed first.

From research to product

Two goals, two people, one page passed between them

Goal one: let clients write and update their final copy inside the design’s limits, without breaking the layout. Goal two: give each side its own space, a dashboard for the agency across all its projects, a focused workspace for the client. Then I drew how a page travels between them.

The copy’s lifecycle. The status always says whose turn it is. Everyone on the project gets an email when it changes.
Key decisions

Four choices that shaped the product

Each one answers something I heard in the interviews, and each one turned down a simpler option.

Decision 1

Edit on the page itself, not next to a picture of it.

Chose
The client clicks the text on the real design and types in place. The design comes in as a PDF, or straight from Figma through its API, so only the text can change. A plain list of fields remains for pages without a design.
Rejected
My second design: a form beside a picture of the page. And the obvious shortcut, sharing the Figma file with the client.
Because
Two managers said clients can’t picture their copy until it sits in the design; the third saw editing in the layout as the strongest part of the idea. Two said Figma access is too risky. Beside the page, the client still has to imagine the result; on the page, they see it.
Second design · form beside the page
Earlier CopyDash design: a small picture of the client’s page on the left and a column of text fields on the right, one of them 60 characters over a 45 limit.
Now · edit in place
The Foundation
Title · H126 / 40Where nature finds its voice

Nature Renaissance is a Geneva foundation protecting Alpine biodiversity and teaching the next generation to care for it.

Our projects

The form version already counted characters, but the client still wrote blind: 60 / 45, with no idea which part of the page would break.

Decision 2

Show the limit before it’s broken.

Chose
Every field carries the limit of the space it was designed for, with a meter that turns amber near the end and red past it. The page preview flags the paragraph that no longer fits.
Rejected
Writing guidelines in a brief, checked by the designer once the client is done. That is step 5 of today’s journey.
Because
Two of the three managers said clients can’t picture how much text fits. The third already gives clients character guidelines, and late changes are rare there. A visible limit turns a rework into a choice of words.
Section title
Projects that protect the Alps
29/ 40
Button label
Support our projects
20/ 21
Almost at the limit of the button.
About · body text
Nature Renaissance is a charitable foundation based in Geneva, rooted in a deep commitment to environmental conservation, biodiversity and education.
149/ 130
The highlighted part won’t fit the layout.
Decision 3

The AI suggests. The client decides.

Chose
AI actions on each field (improve, shorten, friendlier, SEO, more formal, translate) whose suggestions stay inside the field’s limit and appear beside the client’s text, with Apply and Keep mine. A whole page can also be pre-filled from a PDF, as a first draft to edit.
Rejected
An AI that rewrites the text in place, and free-length suggestions that someone trims afterwards.
Because
The client signs off on their words, so they keep the last say. And a suggestion that breaks the layout brings back the very problem CopyDash exists to remove.
1 · Idle
Nature Renaissance is a charitable foundation based in Geneva…
✦ AI
2 · Thinking
AI
3 · Suggestion ✓ fits
Nature Renaissance is a Geneva foundation protecting Alpine biodiversity…
Keep mineApply
4 · Applied
Nature Renaissance is a Geneva foundation protecting Alpine biodiversity…
Previous version in the history
5 · Kept mine
Nature Renaissance is a charitable foundation based in Geneva…
Nothing changed
6 · Error
Couldn’t write a suggestion. Your text is unchanged. Try again.
Whole page: designed · Per field: next

Six states, designed before any model was wired. The error state exists for the whole-page fill; the per-field one is on my list.

Decision 4

A status says whose turn it is.

Chose
Four statuses that each mean a turn: Draft and Pending review for the agency, In progress for the client, then Completed. When a page comes back, every text changed in the last round shows who changed it and what it said before.
Rejected
New names I tried (With client, To review, Approved), which read well but broke the habits agencies already have. And a review banner across the top of the page, which got in the way of the copy.
Because
Project manager A’s clients had invented yellow and green on their own. Project manager C sets a draft round, then a deadline for final copy. People already think in turns; the tool just has to say whose.
DraftAgency sets up
In progressClient’s turn
Pending reviewAgency’s turn
CompletedReady for devs
About · body textChanged this round
CLChanged by the client · before:
Nature Renaissance is a charitable foundation based in Geneva, rooted in a deep commitment to environmental conservation, biodiversity and education. Nature Renaissance is a Geneva foundation protecting Alpine biodiversity and teaching the next generation to care for it.
The client changed Homepage to Pending review
Sent to everyone on the project, except the person who made the change
What didn’t work

I designed for an agency and its client. The business model said otherwise.

My first model had two roles: the agency’s project manager and the client. It matched my own experience and the interviews. But when I worked out who would pay for CopyDash, two roles boxed it in: only agencies would buy it, and a marketing team writing its own site had no place in it.

So I rebuilt the model around workspaces, with three roles: admins on the agency or team side who run the account and the projects, editors (the clients) who write the copy on the pages they’re invited to, and viewers who can follow and read without changing anything. That meant reworking the database, permissions, invitations and onboarding, well into the build.

First model
PM
Project managerThe agency, does everything
CL
ClientFills in the copy
Agencies only
Now
WorkspacePlan limits per workspace
AD
AdminOwns the account, all projects, the team, the branding
ED
Editor · the clientWrites the copy on the pages they’re invited to. Creates nothing.
VW
ViewerFollows the project and reads the copy, without editing
AgenciesFreelancersIn-house marketing teams
From two roles to three. The same product, open to teams that aren’t agencies.
What I’d do differently

Think about the business model much earlier. Who pays, and who else could use it, shapes the roles, the permissions, the onboarding: the whole product.

Building for scale

One set of components, any agency’s brand

If CopyDash is sold to other agencies, each client portal has to look like the agency, not like CopyDash. I built the design system in Figma on a shadcn base, with brand decisions kept apart from the components: switching a brand changes the tokens, not a single component.

PrimitiveSemanticComponent
violet-600→primary→button / bg
violet-50→primary-subtle→ai-chip / bg
violet-900→primary-darkest→ai-chip / text
red-500→danger→meter / over

Brand B maps primary to its own teal and swaps the typeface. Buttons, fields, meters and statuses follow on their own. Components carry their variants, states and specs for the hand-off to code.

Brand AViolet · Geist
Submit for reviewSave draft✦ AI
Title · H1
Where nature finds its voice
26/ 40
Brand BTeal · serif
Submit for reviewSave draft✦ AI
Title · H1
Where nature finds its voice
26/ 40
How I built it

Figma first, then a prototype that talked to a real model

I designed the screens and the design system myself in Figma first. Then I built the app with AI as my coding partner, deciding each feature and checking each screen against the design.

1 · FigmaMock-ups and design system

Market review, user stories for both roles, user flows, then the screens and a multi-brand system.

2 · PrototypeAI flows with a live model

The suggestion and whole-page flows called a real model, so I could design around real answers: too long, wrong tone, slow.

3 · ProductA working web app

Accounts, workspaces, PDF and Figma import, the editor, reviews, emails, export. The AI sits behind one integration point, on a stand-in for now.

  1. Market and user storiesWhat exists, what each role needs
  2. First commitAfter the first Figma screens
  3. 3 interviewsCollection becomes lifecycle
  4. The build picks upPDF and Figma import, the editor on the real page
  5. Workspaces and roles liveAdmin, editor, viewer; invitations; onboarding
  6. Reviews by turns · pilot“What changed”, status emails, a first agency

What I decided

  • What the AI may do: suggest within the limit, never write over the client.
  • When not to wire a model yet. The whole AI experience, loading and errors included, runs on a stand-in so it could be built and tested before paying for a model.
  • The words: statuses agencies already use, “Keep mine” rather than “Reject”.
  • The roles, once the business model changed.

Where I listened to the research

  • Figma through its API, not shared files: project manager B’s worry about clients changing more than text.
  • Paragraphs, not lines. B warned that editing a PDF tends to go line by line. Reading the PDF’s layout to rebuild real paragraphs became its own piece of work.
  • Draft versus approved, from A’s yellow and green.
  • Export for developers, because the copy’s life ends in code.
Where it stands

Built, not measured yet

CopyDash is in development with a pilot agency. Nobody outside the project has used the AI flows yet, so I won’t claim any results. This is what I’ll measure with the pilot:

÷2time spent moving copy between design and documentsHypothesis
Daysfrom a page’s creation to Completed, compared with the agency’s current projectsMain measure
Roundsof back and forth per page before it’s approvedTo track
What’s next

Ranked by what the research left open

  1. Test with the pilot agency and its clientsThe first test of the AI flows with real users
  2. Wire a real language modelThe integration point is ready
  3. An error state for each field’s suggestionDesigned for the whole page only
  4. Layouts that account for translationProject manager B: French takes more space
  5. Beyond websites: marketing emailsRaised by project manager C
What I learned

Three lessons

The need wasn’t editing. It was editing with context and limits.

Clients can already type in Word. What they lacked was seeing the page, and a frame that lets them change words without breaking it.

The business model is a design input.

It decided the roles, the permissions and the onboarding. I treated it as a later question and paid for it in rework.

A limit is what makes an AI suggestion useful.

A free suggestion is one more thing to check. One that fits the space and waits for a yes is something a client can act on.

CopyDash · 2026 · Product visuals redrawn from the app with demo copy. Interview lines are from my notes, not quotes. Next: Medair →