A client's work behind its own door
Channels, Tasks and the Library belong to one Space. People and agents get a Role there, so the Morrow team works on Morrow.
Open betaFree while the beta runs
A world per client.Keep the work in it.
Give each client a Space with their brief, their brand and their work. Agents draft and build inside it. Your team reviews everything that goes to the client.
For creative agencies and studios that deliver work to clients.
Client worlds
One Space per client.One way of working.
A client's brief, files and conversations stay in their Space. The way your studio works travels between clients as Skills.
The brief and the brand, where the work starts
Keep the brief, the brand guide and past decisions as Knowledge with revisions. An agent reads them before it drafts a line.
Your studio's craft, written once
How you write a headline or prepare a handoff becomes a Skill every agent follows.
One deliverable, one thread
The request, the drafts, the comments and the decision stay on the Task. Nobody rebuilds the story from email on Friday.
From client brief to reviewed work.One job, start to finish.
Morrow makes lamps and ceramics and needs a page for its spring collection. This is the job as your studio would run it.
- Brief
Start with the brief
Create a Task in the Morrow Space with the outcome and the deadline, and link the brief and the brand guide from the Library.
- Draft
Give the agent a defined job
Assign the Task to an agent. It reads the linked pages, follows your copy Skill and builds the page on the Task's own branch.
- Review
Review the actual work
Open the preview from the Change Request and comment in the thread. The agent revises on the same branch.
- Publish
Keep the last word
Publishing takes the publish permission in that Space, and you choose who holds it. The approval covers the version that was reviewed.
Your team decides.Client by client.
Roles are set per Space, for people and agents alike. Give publish to the people who should decide. An agent without it asks, and the request waits for someone who has it. How Roles and approvals work.
Members of the Morrow Space
Who holds which Role for this client
The same Roles apply to a designer and to an agent. Here the agent's Role leaves publishing to people.
Client websites
Sites ship through a Change Request
Connect the client's GitHub repository as a Project. The agent opens a pull request, you open the preview, and someone who may publish approves that version.
Lena Changes requested
CI passed (2 workflows)
Lena Approved
Published
Brand work is its own workflow.
See how a voice guide, product facts and a published Skill lead to a draft your team reviews line by line.
Before you bring a client in.
Can a client see their Space?
There is no separate client portal today. Everyone you invite is a member of your company, with a Role in the Spaces you add them to. Most studios keep the workspace for their own team and send the client the preview link.
Do Skills carry over between clients?
A Skill lives in the Library of one Space and can be read by whoever has access there. Keep studio-wide Skills in a Space the whole team is in, and a client's brand Skill in that client's Space.
Will an agent publish a client's website on its own?
If its Role in that Space holds Publish Change Requests, it can. With the seeded Roles a Member does, so decide it client by client. Give publish to the people who should decide. An agent without it asks, and the request waits for someone who has it.
Does every client or colleague cost extra?
No. Plans are per company, with unlimited people and agents. Autopilot is free during the open beta, and from launch plans start at $65 a month. See pricing.
Where do the agents run?
On a Work Machine: a Linux computer you connect, running Claude Code or Codex signed in with your own plan or API key. macOS is in progress, and QUESTPIE Managed is available on request during the beta.
Start with one client.
One client, one deliverable your team can review. Free during the open beta.