Your team plans the work for every customer in AgencyOS and tracks time against it. In the same application, your clients submit requests, answer questions, comment on documents and follow progress. You decide, item by item, what stays internal.
Call your columns whatever you like. Underneath, every one of them maps to one of seven shared stages.
Each one is checked automatically before anything we ship goes live.
It runs on our server, one per person, so a reload, a crash or a second device can’t lose it.
Charging for client logins would work against the whole idea. You pay for your own team.
Every project names its columns differently, yet “Requested”, “Ideas” and “Inbox” all belong to Backlog. That shared stage is what lets one board hold three customers at once.
Your team and your client look at the same item at the same moment, and each sees what they need. Your team gets the internal estimate, the tracked hours, the time notes and the internal items. Your client gets their request in their own words and the estimate you shared with them.
Sandbox keys took 3 h — worth quoting higher next time.
Jonas is on it. You’ll get it for review before it ships.
They see the 8.0 h estimate you shared and nothing else. The 10.0 h you actually expect and the 9.4 h already tracked stay with you.
The estimate you share is the only number the client sees. Your internal estimate, tracked hours, time notes and internal items are never sent to their browser in the first place, so there is nothing on their screen to hide.
Privacy by design →AgencyOS isn’t a suite. It covers the work an agency does with its clients every day: planning, time, documents and communication.
All features →Seven fixed stages sit underneath whatever you call things. That’s how one board pulls in work from every customer, while each client sees their project under the column names you set for them.
One per person, running on the server. Forgot to start it? Type 1.5, 90m or 9–11:30. Every hour lands on a work item or a customer, so nobody wonders where it belongs.
Pages on a customer, a project or a work item, with tables, images, diagrams and comments on any passage. They stay internal until you share them.
Existing mandates stay as they are. · 2 comments
Each customer gets one page showing what’s in progress, the latest feed entries and the newest documents. Your client lands there when they sign in, and your team also sees the month’s hours on the same page.
Summaries, decisions and questions sit next to the work they’re about, along with files, inline images and internal notes your client never sees.
Checkout first. Anna sends the mandate wording by Friday.
Every item, comment, entry and page is either shared or internal. The rule lives in the database itself, so a screen that forgets to filter shows nothing at all rather than a leak.
We built client access before anything else. Every record in the database carries its own rule about who may read it, and anyone not explicitly allowed sees nothing. Nothing new goes live without such a rule.
The access model →| No client ever receives | Why it stays with you |
|---|---|
| Your time entries and notes | How long things took, and why |
| Your internal estimate | What you actually expect it to take. Clients only see the estimate you shared. |
| Internal notes and pages | What you say about them among yourselves |
| Internal items and comments | Nothing on their side so much as confirms they exist |
| Anything belonging to another customer | It appears in none of the lists they open |
There’s no big rollout. Start with a single customer; you will usually notice the difference in three areas.
The overview shows what’s in progress, what was decided and what was shared. Your client can look there instead of waiting for a weekly summary, and you can still email an important feed entry when it matters.
Every request records who asked and when, the estimate you shared sits on the item it belongs to, and every hour on the work it was spent on. When scope is questioned, you can look it up instead of reconstructing it.
Hours were logged against items while the work happened, so nobody has to rebuild a week from calendar entries and memory. AgencyOS doesn’t send invoices; export an item’s time entries as CSV and take them into your accounting.
We’ll set up your workspace with you and move your current projects over. Then invite one of your clients and see whether it fits the way you work.