Projects
Status, phase, room, what's approved and what's still sourcing.
"Summarize the Ashford Residence project."Walter answers from your projects, invoices, contacts and timelogs — the records your team already keeps — and it's been trained on the things a designer is expected to know: codes, clearances, standard dimensions, how the trade works. It will also tell you plainly what it can't do.
I read across your studio — projects, invoices, contacts, and timelogs — to help you find, summarize, and update things fast.
Walter is AI. It is right far more often than it is wrong, and it can still be confidently wrong — check anything load-bearing against the source.
Trusted by the studios doing the work
Most AI in this category is a general model with your logo on it. Walter is pointed at four kinds of record and nothing else — which is why its answers are specific enough to act on, and why it can be wrong in ways you can check.
Status, phase, room, what's approved and what's still sourcing.
"Summarize the Ashford Residence project."What's been sent, what's been paid, what's sitting unbilled.
"What invoices are unpaid?"Clients, vendors and reps, with the trade discount and the history attached.
"Who's the rep at Stark?"Hours by person, project and phase, billable and not.
"How many hours did we log this week?"Walter carries trade knowledge as well as your records — codes and clearances, standard furniture dimensions, how the sequence of a job normally runs. So "will a 96-inch sofa work in that room" is a question it can take a view on, not just a question about your data.
That knowledge comes from training, not from your project. Treat it the way you'd treat a well-read colleague's opinion — useful, usually right, and worth confirming before it reaches a client or an inspector.
Three of the prompts Walter offers are things to find out. The fourth — "add a note to my newest project saying client approved the sofa" — is a thing to do. That's the difference between a search box and an assistant: you can hand it the sentence you'd have typed into the project yourself.
Which projects are over their estimated hours?
Robin Residence is 54.1 hours over estimate. Most of the overage is in design development. Zapata Residence is 7.4 hours over in procurement.
Add a note to Robin Residence saying the client approved the sofa.
Added to Robin Residence.
Walter's own opening screen says it: billing, bugs and account issues aren't its job, and it points you at a person instead. We'd rather it declined clearly than guessed confidently — a wrong answer about an invoice is worse than no answer, because you'd act on it.
Those go to the success team, who are people, and who can actually change something.
An assistant is only useful in a system where the records already talk to each other. Walter isn't doing the connecting — the platform did that. Walter is what it looks like when you can finally ask.
"Which projects are over their estimated hours" is only answerable because timelogs and estimates sit on the same project.
Unpaid isn't a list of documents — it's a list of clients and jobs, because that's how the invoice was built.
A vendor's discount, their POs and their reps are one record, so a question about them has somewhere to land.
Asking is half of it. Walter writing a note onto the project is what stops the answer dying in a chat window.
The thread you started on Tuesday is still there on Friday, under its own name in the sidebar.
Walter reads your studio's records and no one else's, and your data never trains a model for another firm.
Every studio has a voice, and clients can tell when it slips. A draft that says “reach out” when you always say “connect” is not wrong, it is just somebody else — and rewriting it takes longer than writing it would have.
Describe the voice once, in a sentence. Add the word swaps you actually care about. From then on every draft Walter writes — replies, rewrites, email summaries — honours them, and confirmation stays on by default so nothing is committed without you seeing it first.
Word swaps Walter always honours.
Walter can only see data inside your own workspace.
Two things. Your studio's own records — projects, invoices, contacts and timelogs — and general design knowledge it was trained on, such as codes, clearances and standard furniture dimensions. Answers about your firm come from your data; answers about the trade come from training, and both are worth verifying before you act on them.
Treat it as a well-read assistant, not an authority. Walter is right far more often than it's wrong, and it is still AI — it can state something incorrect with complete confidence. Anything load-bearing — a code requirement, a clearance, a number going to a client — should be checked against the source before you rely on it.
Both. Adding a note to a project is one of the four suggestions it offers on the opening screen. Treat anything that changes a record the way you'd treat a junior's work — useful, fast, and worth a glance before you rely on it.
Because it would be guessing, and a confident wrong answer about your account is worse than no answer. Walter says so on its own opening screen and points you at the success team, who can actually change something.
No. Walter analyzes your firm's own records to serve your account only. Your data is never used to train models for other customers and never crosses between accounts. More on security and trust.
Anyone with access to the records in question. Walter respects the same permissions the rest of Workroom does — it can't surface a margin to someone who isn't allowed to see margins.
The demo works best when you ask Walter a question you actually can't answer today — about your hours, your unbilled work, or a client you haven't looked at in a month.