The feed
One thread per customer, or per project if you like, for summaries, decisions, questions, files and inline images. People reply, edits keep a record of what changed, and “new” marks follow what each reader has already seen.
Features
Your clients see the progress, without asking for it.
Your clients sign in to file requests, comment on items and documents, and see in their overview how far the work has got. Your team works on the same board and decides, item by item, what the client gets to see.
- Where things stand is there for the client to look up
- The spec and the feedback on it sit on the same page
- Hours are logged while the work happens, not afterwards
Muster GmbHOverview · Feed · DocumentsClient view
In progress
SEPA direct debit
Invoice PDF export
Feed
Jonas B.Update
Checkout is on staging — please try a SEPA order.
Boards
Portal RelaunchInfrastructureRecent documents
📄 Checkout — brief📄 Mandate texts01 · How it works
Three steps, all in one place.
Every request, every hour and every comment hangs off the same work item. Nothing is copied from an email onto the board, or from the board into a report.
- 1
They ask
Your client files the request themselves, with a title, details, the project and a priority. It lands on the board as a work item that records who asked, and nobody types it up again.
Request work · Muster GmbHPDF invoice exportPortal Relaunch▾High▾Request work - 2
You do the work
You work on your board, with the spec beside you and the timer running on the item. Your internal estimate and time notes stay on your side.
Portal Relaunch · boardRequestedIn progressPORTAL-147PDF invoice export00:47:12 - 3
They see the progress
Their overview updates as the card moves, so they can check where things stand at any time.
Muster GmbH · overviewPDF invoice exportPORTAL-147We’re on itStarted today — you’ll get it for review.
02 · What it solves
The everyday problems AgencyOS addresses
Each section describes a problem that comes up regularly in client work, and the part of AgencyOS meant to handle it.
01 · Board & work items
The problem
Your work is spread across five tools, three naming schemes and somebody’s inbox.
Every customer’s work on one board.
Each project keeps its own columns, and each column maps to one of seven shared stages. So one board shows what’s in progress for every customer, while each client reads it in their own words.
- Clients file requests themselves, with who asked and when
- The estimate you share and the one you expect, side by side
All work3 customers · grouped by stage
Backlog
PORTAL-151Muster GmbH
NORD-12Nordlicht
In progress
PORTAL-142Muster GmbH
OCK-7Studio Ocker
Review
NORD-9Nordlicht
Your side
PORTAL-142SEPA direct debit
Internal
10.0 h
Quoted to client
8.0 h
Tracked
9.4 h
Their side
PORTAL-142SEPA direct debit
Estimated effort8.0 h
Internal estimate and hours: not sent02 · Time tracking
The problem
It’s Friday afternoon, and you’re rebuilding the week from calendar entries and memory.
Hours are logged where the work happens.
Start the timer on the card you’re working on. It runs on the server, survives a closed laptop and books every minute to the right customer without you having to think about it.
- Type 90m, 1.5 or 9–11:30, and all of them work
- Your week against your target, at a glance
01:24:07
PORTAL-142 · SEPA direct debit
Switched — earlier entry savedNORD-12 · 0:42Undo
My weekW40
| Mon | Tue | Wed | Thu | Fri | |
|---|---|---|---|---|---|
| PORTAL-142 | 3.0 | 2.5 | · | 1.5 | · |
| NORD-9 | · | 4.0 | 3.5 | · | 2.0 |
| OPS-22 | 1.0 | · | 1.0 | · | 0.5 |
| Muster GmbH | · | · | 2.5 | 4.0 | 2.0 |
Logged 28.5 of 32.0 h81% billable
03 · Documents
The problem
The spec is in one doc, the feedback in an email and the final version nowhere.
Specs and feedback on the same page.
Write briefs, specs and meeting notes right next to the work they describe. Your client comments on the exact sentence they mean, and you can see who has actually read the page.
- Tables, images and diagrams, formatted as you type
- Share by link and see who read it, or keep it internal
Muster GmbH / Portal RelaunchShared with client
Checkout — technical brief
SEPA direct debit replaces invoice payment for new customers. Existing mandates stay as they are, and the checkout only asks new customers.
StepOwner
Mandate wordingMuster GmbH
Anna MeierClient
Does that include the B2B accounts?
Jonas B.Client
Yes — they keep invoice payment.
Jonas B.Internal
Check with legal before we promise more.
Public linkagencyoshq.de/s/…k3f9
Seen by
Anna Meieranna@muster.de4 opens · 2 h ago
Tim Kraustim@muster.de1 opens · yesterday
Lea Wolflea@agentur-wolf.de2 opens · 3 days ago
04 · Status overview
The problem
“Where are we with the checkout?” It’s the third email this week.
Clients see where things stand without asking.
Every customer gets one page with the work in progress, the latest updates and new documents. It’s the first thing your client sees when they sign in, and it comes from the work itself rather than from a report someone writes.
- Progress for the client, the month’s hours for you
- Post updates right from the page
Muster GmbHOverview · Feed · DocumentsClient view
In progress
SEPA direct debit
Invoice PDF export
Feed
Jonas B.Update
Checkout is on staging — please try a SEPA order.
Boards
Portal RelaunchInfrastructureRecent documents
📄 Checkout — brief📄 Mandate texts05 · Privacy by design
The problem
One wrong click, and the client reads what you wrote about them.
You decide what the client sees.
Every item, comment, update and page is either shared or internal. Anything internal never reaches the client’s browser at all, so there is nothing on their screen to stumble across.
- Sensible defaults mean that most of the time nobody has to decide
- Time entries and internal estimates never reach a client
| What | Starts as | |
|---|---|---|
| Work item | project default | SharedInternal |
| Comment | last used on the item | SharedInternal |
| Feed entry | shared | SharedInternal |
| Document | internal | SharedInternal |
| Time entry | always internal | Internal |
GET/work-items/ops-22
What the client receives404 · the same answer as for an item that never existed
06 · Pin — the feedback widgetIn preparation
The problem
A screenshot with a red circle and three words: “this is broken”.
Bug reports that know the page and the element.
Pin is planned as a widget that lets your client mark a problem right on their own website and write one sentence. The report is meant to carry the page, the element and the browser, and arrive in an inbox instead of an email thread. Today, Pin can only be set up per project.
- Accepted reports are planned to become work items
- Only on sites you allow, only for people you invited
shop.muster.de/checkout
Pay with SEPA1
button.pay-sepa
Nothing happens on the second click — I expected the mandate form.
SendPin inbox · Portal Relaunch
PIN-318New3 similar in 24 h
Nothing happens on the second click
Anna Meier·/checkout·Firefox 141
POST /api/mandate → 422
Accept as work itemDecline
03 · Coming next
What’s planned next.
Intake forms are planned and not in the product yet. We show them here so you can tell us whether they would help. Pin, shown further up, is also only in preparation. Both are marked wherever they appear on this site.
Intake formsPlanned
Your own forms, landing on the board as work items.
You’ll design the form your intake really needs, choose a template for what it creates, and every submission will arrive as a work item with the answers already in it.
Read the plan →Enquiry · Haus am SeePlanned · preview
NameText
EmailEmail
PhoneText
Financing confirmed?Yes / No
Preferred viewing dayDate
+ Field
CreatesEnquiry template
04 · And around it
Everything else a client relationship needs.
The smaller features that sit around the ones above.
Email an entry
Send a feed entry to the people it concerns, even someone without an account. Each recipient gets their own email, replies come straight back to you, and the entry remembers who it went to.
Drafts that follow you
Unsent replies, comments and descriptions are saved on the server. Close the laptop, pick up your phone and carry on where you left off.
People and roles
Five roles: Owner, Employee, Freelancer, Client admin and Client member. Narrow employees, freelancers and client members to named projects. The owner invites people by link and deactivates someone in one step.
Agents and MCP
Give an AI agent its own token, limited to the projects you choose. Through the MCP server it can create, update and move work items, comment, attach files, post to the feed and write documents. It never reaches people, invites, tokens or time entries, never removes a file, and can never widen its own access.
Sign in without a password
A password or a single-use link by email, offered side by side. A client who opens the portal four times a year never has to remember anything.
Three languages
The whole interface comes in English, German and French, and each reader picks their own. Emails such as invitations are sent in English only for now. Light, dark and high-contrast appearances are included too.
A record of every change
Visibility switches, edits, invites, deactivations and shared links are all written to an internal audit log. There’s no view or export of it in the app yet.
See it with your own customers in it.
We’ll set up your workspace with you and move your current projects over before the first call ends.