Space Grotesk / Inter
- ▸ Launch post
- ▸ Pitch deck
- ▸ Landing page
FOR TEAMS &
AGENCIES!
Three clients, three brands, eight designers, one place for all of it. Here is how a small studio runs its week in PopCraft: shared files, a brand kit per client, your own plugins and agents, and a plan per team.
Home, signed in. Brightside Studio is picked in the sidebar, then New and File open the gallery, whose owner picker says the file will be made in Brightside Studio. Social is picked in the rail, showing its sizes and templates; whatever is used next is made in the team.
TEAM UP!
THE JOB
Paperplane has three clients and one Monday
Paperplane is an imaginary eight-person studio in Brooklyn. This month it has a software launch for Northwind Cloud, an opening for a bakery called Hearth & Crumb, and its own credentials deck, which has been “nearly done” since spring.
Every agency knows the weekly tax that comes with that. Files in three places. A brand guide PDF per client that nobody opens. Hex codes pasted into Slack. A client who replies to the wrong email thread with “can the logo be bigger”. And a final_FINAL_v3 that is not the one that got approved.
The point of running the studio in PopCraft is that the client, the brand and the work are all things the tool knows about. Not folders on a drive that happen to sit next to each other.
3
plans, chosen per team
6
example brand kits to start from
3
roles: edit, comment, view
1
year of history on Studio
THE ROSTER
One studio, three brands
Each client gets a project and a brand kit. These three kits start from examples that ship in the brand kit dialog, so you can try exactly this.
Hearth & Crumb
Kit from the “Café & bakery” example
Fraunces / Work Sans
- ▸ Menu
- ▸ Opening post
- ▸ Loyalty card
Paperplane (us)
Kit from the “Creative studio” example
Playfair Display / DM Sans
- ▸ Credentials deck
- ▸ Newsletter
- ▸ Case studies
MONDAY
Set the studio up once
- 1
A team for the studio
On Home, New team… in the sidebar. A personal space is a real team too, so nothing is ever loose. - 2
A project per client
Files live in projects inside a team, folders organise projects, and permissions can be set at any level. - 3
New file, in the right place
New makes the file where you are browsing, and the dialog says which owner it will be made in before you pick a template. - 4
Invite the client
Share by email with a role: edit, comment or view. Or set link access so anyone with the URL can open it.
Home, signed in. Brightside Studio is picked in the sidebar and its files show: the Spring launch post, the Q3 pitch deck and the Product trailer. Personal shows the files in the personal space instead.
A launch post in the editor, signed in. The Shapes panel’s Library section lists the media in the team’s files. The team is set to Brightside Studio and the type to Images, and one of the photos is clicked: it lands on the canvas, copied into this file.
TUESDAY
A brand kit per client
A brand kit is a client in a dialog: five colour roles, a heading and body font, logos, and text fields like name, tagline, website and email. Find it under ⋯ › Brand kit….
Apply to document and the file takes it. Colours land in brand/ variables, fonts on the text styles, and {{brand.name}} tokens in text fill in. Templates that bind brand slots arrive already wearing the client. Here the Pitch deck turns Paperplane orange in one click.
The Pitch deck template in Design. ⋯ › Brand kit… opens the brand kit dialog; the Creative studio example is added as a kit, showing its colours, fonts and text fields. Apply to document recolours the deck, sets its fonts and fills the company name.
SAME KIT, EVERY DELIVERABLE
Change the client, not the files
The money shot for an agency is not one file in a brand. It is every file in the same brand without anyone checking hex codes. The same Paperplane kit goes on the launch email, and a different client's kit goes on a launch post, in the same two clicks.
The SaaS launch announcement email in Design. ⋯ › Brand kit… and the Creative studio example, the same kit the pitch deck took, is added; Apply to document recolours the email in that brand, sets its fonts and fills the company name and address.
The launch post template in Design. ⋯ › Brand kit… and the Software product example is added; Apply to document recolours the post in that brand and sets its fonts.
WEDNESDAY
The client reviews, in the file
The Northwind landing page goes to the client with a comment role. They press C, click the hero, and write “Can we try a shorter headline?”. It is pinned to the design, it takes replies and @mentions, and it gets resolved when it is done. No screenshots in email threads.
Before it goes out, the designer names a version: Sent to client. Version history keeps automatic checkpoints too, and you can scrub back, restore a point or copy something out of it. When the client wants to see a bolder direction without losing the approved one, a branch is a copy you can merge back or throw away.
A landing page in Design. C picks the comment tool and a click on the hero places a comment: “Can we try a shorter headline?” is posted. The Comments panel opens on the right and Reply opens under it, “Trying three words now” is sent, and the thread is resolved with the tick.
A landing page in Design. The ⋯ menu opens Version history, which takes the right panel. Save current version is clicked, the version is named “Sent to client”, and Save adds it to the saved versions, ready to preview or restore later.
Live cursors, follow and Spotlight are on the multiplayer page.
THURSDAY
Your own tools, private to the studio
Every studio has its tricks. In PopCraft they can be tools the whole team has, without putting them in front of the world.
TEAM PLUGINS
CLICK!Install a plugin for your team workspace and everyone in it has it. Or send the file. Or publish it to the marketplace when you are ready to.
TEAM THEMES
SWISH!A theme pack restyles the editor itself. Make the studio's own, package it, and publish it for the team.
THE MARKET TAB
LOOK!Home's Market tab lists everything a team has published, with Edit for the people who manage it.
Signed in, in the editor. ⋯ → Manage plugins… opens the plugin manager, and Publish from file… sends the Panel Checklist widget’s package to the marketplace. The first version of a new plugin waits for review before it is listed.
The theme editor on the built-in PopCraft Dark, which is read-only. Duplicate makes an editable copy named Pop Sunset. Its accent token is changed to an orange, and every accent in the app — the selected tool, buttons, the selection — turns orange at once.
The details are on plugins & marketplace and themes.
FRIDAY
Agents that know how you work
The PopCraft agent pulls in skills, short instruction sheets, when a job matches one. Write your own: “brand-audit”, “export-checklist”, the way Paperplane names layers. In the desktop app they are markdown files in a folder, so you can keep them in a git repo and the whole team gets the same ones.
Outside the editor, the popcraft CLI and the REST API run the same commands on files, with a personal access token. A CI job can make the launch in three sizes, check a design, or publish the team's plugin. See agents & API.
A launch post in the editor. The agent panel opens and Manage lists the built-in skills, each an instruction sheet the agent pulls in when a job matches. One is opened and Duplicate makes an editable copy of it, with its name, when to use it and its instructions.
AND THE PLUMBING
Where the work goes next
A landing page that ships does not stop at the design. Connect the studio's own GitHub, Vercel, Neon or Supabase accounts, push a published site to a repository, or deploy it to a Vercel project you already have. The integrations page shows each one.
Home, signed in. The avatar opens the account menu and Personal access tokens lists the tokens there are. A new one is named “CI publish”, given a scope, and created; its secret is shown once, ready to copy into the service that calls the API.
Home, signed in. The avatar opens the account menu and Integrations is chosen. The dialog lists GitHub, Vercel, Neon and Supabase, each with what it is for. Connect is clicked on Neon, a token is pasted (shown as dots) and Connect checks it: the Neon account appears under Neon. The same is done for GitHub, and its account appears under GitHub.
THE OLD WAY
Six tools and a shared drive
| THE OLD WAY | IN POPCRAFT |
|---|---|
| A folder per client on a shared drive | A project per client in the team, with permissions at any level |
| A brand guide PDF nobody opens | A brand kit applied in one click |
| Feedback in email threads | Comments pinned to the design, with @mentions |
| final_FINAL_v3.fig | A named version: “Sent to client” |
| Scripts and plugins on one person’s laptop | Team plugins, themes and agent skills everyone has |
PLANS
A plan per team
Each team has its own plan, and so does your personal space. A studio can keep its own team on Studio and give a small client a Creator team of its own. Limits only stop you creating more: nothing is deleted or locked on a downgrade, and saves never fail because of a plan.
| Free | Creator | Studio | |
|---|---|---|---|
| Cloud files | 3 | 100 | Unlimited |
| Pages per file | 5 | 50 | 200 |
| Media storage | 250 MB | 10 GB | 100 GB |
| Version history | 7 days | 90 days | 1 year |
| Named versions per file | 3 | 50 | Unlimited |
| People per shared file | 2 | 10 | Unlimited |
| Published libraries | — | 5 | Unlimited |
| Workspace plugins | 3 | 20 | Unlimited |
| Team editors | 3 | 10 | 25 |
Every tool, brush, the pixel studio, export and the plugin platform are on every plan. Free's GIF and video exports carry a PopCraft watermark. AI is metered separately in credits, billed to the team that owns the file on screen, which makes per-client AI costs easy to see. Prices are on the pricing page.
TRY IT ON ONE CLIENT
Make the team. Apply the kit.
Make a team on Home, open the Pitch deck template in it, then ⋯ › Brand kit… and start from an example. That is a client deck in a brand in under a minute. The collaborating docs cover sharing, roles and history.
ASKED & ANSWERED
Questions, answered
Should each client be its own team?
Either works. One studio team with a project per client keeps everything in one place. A team per client gives that client its own plan, its own published items and its own AI billing, because AI usage is billed to the team that owns the file on screen.
Can clients see the files without editing them?
Yes. Share a file with a view or comment role, by email or by link access. Comments thread, take @mentions and resolve, so feedback lands on the design rather than in an email.
How do brand kits work across clients?
A brand kit holds a client’s colours, heading and body fonts, logos and text fields like name, tagline and website. Apply it to a file and templates that bind brand slots take it. Saved into a team, a kit is shared with that team; its owner or a team admin can change it.
Can we keep our own plugins private?
Yes. A plugin can be sent as a file, installed for your team workspace (the version must be approved), or published to the public marketplace. Plugins, theme packs and brush and shader packs published from the editor belong to the team you are working in.
What do the plans cost?
Each team has its own plan, Free, Creator or Studio, and so does your personal space. Prices are on the pricing page. The editor is not cut down on Free: the limits are on how much you keep in the cloud and how many people you keep it with.
Is there an enterprise plan or SSO?
Not today. Free, Creator and Studio are what is sold. Accounts sign in through Hypery.
KEEP EXPLORING
Goes great with
TEAM UP! YOUR TURN.
Shared files, brand kits, plugins and agents for every client. Free to start, in your browser or on your Mac.