An assistant that already knows your projects.
The assistant works on the record your firm already keeps: projects, clients, proposals, invoices, permits, tasks and workload. It is an operations assistant, not a design tool.
For the question you would otherwise ask three people
Principals, project managers and office managers who need an answer about the firm's own operations without opening five screens to assemble it.
What it does, and how it is bounded
- Reads and drafts across the firm record: projects, clients, proposals, invoices, permits, tasks, meetings and workload.
- Permission-gated by construction: the model is never shown a capability the user's role does not have.
- Every action is re-checked server-side, so the boundary does not depend on the model behaving.
- Actions that change data are previewed and require confirmation before they run.
- Every read, preview and execution is written to an audit log tied to the conversation.
How to think about it
- Ask in plain language about work that already exists in Sitework.
- The assistant only reaches the parts of the record your role can reach.
- Anything that writes shows you the change first and waits for your confirmation.
- The action log keeps a record of what was read and what was done.
Frequently asked questions
What can the assistant see?
Answer: Only what the person asking can already see. Capabilities are filtered by the permissions of the user's role before the model is called, and each action is validated again on the server.