Workspace onboarding
BacklogMediumMB
All use cases
use case
Marketing and content
From brief to publishing, with the asset and the decision side by side.
Content teams lose time searching: where the approved brief is, which version of the artwork counts, what already went out. muriki keeps the campaign, the assets and the agreements in one place, with the calendar showing what ships and when.
Get accesscampanha de lançamento3 peças na semana
Próximos 30 dias a partir de ago 3
segunda-feira, ago 3
1 eventoterça-feira, ago 4
1 eventoAmanhã
1 eventowhat changes in your campaign
The right version of the asset, without hunting in three places.
None of this is mandatory: each team takes what makes sense and ignores the rest. The module that delivers each item is marked — today only focus is standing.
work comes in here
01
Before the campaign ships
Editorial calendar
focusSee the whole month before you promise that post for Friday.
Campaign as a project
projectsEvery asset of a launch in one place — nobody asks “did it go out?” again.
Recurring schedule
focusWhat repeats every week shows up on its own. Your energy goes to what's new.
Próximos 30 dias a partir de ago 3
segunda-feira, ago 3
1 eventoterça-feira, ago 4
1 eventoAmanhã
1 evento02
While the asset is made
Briefs that don't get lost
docsThe approved brief sits on the asset. Nobody produces the wrong version again.
Visual board of assets
canvasThe artwork side by side, with each status right under it.
Review with a deadline
projectsApproval with an owner and a date. Nothing dies waiting to be remembered.
Backlog12
Search by subject
BacklogLowGT
This cycle5
Ship the early access
To doHighGT
Calendar MCP server
To doUrgentAL
In progress2
Offline sync with Yjs
In progressUrgentGT
Team invite by link
BlockedHighMB
Done8
The focus timeline
DoneMediumAL
03
When it is time to publish
Checklist per channel
focusEach channel with its own list. Nothing ships with a piece missing.
History of what shipped
docsProve what was published and when, without scrolling six months of chat.
Decision: CRDT on the client
The document is the local source of truth. The migration is being handled inMUR-25Offline sync with Yjs— when it closes, the paragraph below stops being true.
architecturedecided on Jul 28
and leaves here
What is ready lands where the team already is, with nobody copying links or telling people by hand.
- Slackthe approved asset pings the team right away
- Drivethe final file lands where it always lands
- Emailthe client receives what went live
with the agent
What it does for a content team
- The planning meeting becomes the week's tasks, each with channel, owner and date.
- An approved screen in Figma shows up on the board with the frame link and current status.
- “How did the August campaign go?” returns what shipped, what slipped and what got dropped.
day to day
How the team uses it
- monday
The week's plan becomes tasks with publishing dates and owners.
- during
Brief, artwork and review stay tied to the same asset.
- end of month
The calendar shows what actually shipped, not what was planned.
Is your team in the next wave?
Access opens in waves, as the modules become ready. People on the list go first.