Run the studio
without living in status meetings.
You are the person who has to know where nine projects are without asking nine people. Workroom keeps the plan, the approvals, the procurement and the hours on the same records the team is already working in — so the Friday review is fifteen minutes of decisions rather than three hours of reconstruction.
A set is a job, not a person. Hire a second sourcing assistant and they start with the same 46 on their first morning.
What you can hand over is a list, not a leap of faith.
Trusted by the studios doing the work
The install date is a promise. Treat it like one.
Every project carries a live install-readiness score, worked out hourly from what you have actually ordered: delivered, on track, or at risk. You never have to look at it — when it crosses a band you chose, an automation tells you, with the at-risk count and the install date already in the message.
That is the difference between telling a client in September that November is tight, and telling them in November that it moved.
(Delivered + On track) ÷ total ordered × 100 = (12 + 3) ÷ 20
Friday review in fifteen minutes, not three hours
The job is not knowing everything. It is knowing which three things need you this week, and being able to see that without calling a meeting to find out.
- Portfolio across every project — phases and overlaps on one timeline, so the crunch in October is visible in July rather than discovered in it.
- Approvals that move the record — a client approves a product in Comms and the item changes. No screenshots, no chasing a decision that was already made.
- Exceptions that raise themselves — a shipment gone quiet, a lead time that drifted, an allowance specified over. You hear once, early, and only about the ones that matter.
See who is drowning before they tell you
Utilization reads the same tasks and time your team already logs, by person and by week. It is how you find out that one designer is at 88% for three weeks running while another has room — while you can still move something, rather than at the exit interview.
It is also the honest answer when the principal asks whether the studio can take another project in November.
Team avg 74% · 118h planned
“I used to find out a project had drifted in a status meeting. Now I find out on the day it drifts, from the same record the team is working in.”
Directing the studio, specifically answered
My designers will not update another system.
They are not updating a second one. The plan, the products, the purchase orders and the hours are the same records they already work in — the difference is that the gantt, the kanban and the portfolio all read from them, so nothing has to be rebuilt for a review. If a task moves in one view it has moved in all five.
How do I see everything without a meeting?
Portfolio view puts every project on one timeline with its phases. Utilization shows the team's load underneath it. Between them you can see which projects are tight and who is carrying them, which is most of what a status meeting was for.
What happens when a delivery slips?
The item's dates move, the hourly install-readiness recalculation picks it up, anything dependent on it is flagged, and a review task opens with the recalculated date and a drafted client update already assembled. You review and send.
Can I keep the client out of the internal detail?
Yes. Clients see selections, approvals, documents and the financials you choose to share. The schedule, the margin and the internal notes stay yours. Client collaboration →
Does this replace our task tool?
For most studios, yes — because a task tool cannot know that a sofa was acknowledged four weeks late or that six drapery items are blocked behind a field measure. Asana and Trello integrations are on the roadmap for teams that want to keep both.
Bring us your Friday review.
Tell us what you currently have to open to run it, and we will show you the same review from one screen on the call.