The first workspace went live on Argus this week, and the dashboard grew around it: an office for the agents, a Business review, a clearer Inbox, and access by department.

Highlights

• Office: every workspace now opens on an office floor. Each desk shows what its agent is doing, the Needs you card counts what waits for you, and Open inbox takes you there. Full screen shows the floor alone (Orhan)

• Inbox: each card says what approving does, such as Sends an e-mail or Posts on Slack, with a Why line and a What happens section. You can approve, edit, dismiss, put a card aside for later, or hand it to a colleague with Assign to. Anything that leaves the company asks you to confirm first (Orhan)

• Agents: one employee per department, each with its own duties and a name such as Atlas or Hermes. An agent's page shows its goals with the current value (Orhan)
• Reports: one readable report per agent run. Agents' summaries now live here, so the Inbox and Slack carry only actions (Orhan)
• Business review: the monthly and quarterly review numbers on one page, with targets, a Gaps tab that names what is missing, and Download deck for the QBR or MBR as a PowerPoint file (Orhan)

• Growth: the Overview page answers where growth comes from, starting with Revenue by channel (Orhan)
• Team: in Settings, give each person the departments they work in and a level for each: Sees, Decides or Manages. Admins can use See as to open the workspace as that person (Orhan)
• Metis: the knowledge page is now your company's brain. It shows what every agent knows and follows, and which questions are still running on safe defaults (Orhan)

Everything shipped this week

Agents and automation

• AnnounceKit live on Argus: AnnounceKit's agents moved to Argus in draft mode, with Argus's own customer records and the website as sources, so every outward step waits for approval (Orhan)
• Office floor: an office drawn in department zones where each desk shows its agent's real state, with a clock, a weather chip, full screen and a card for what needs you (Orhan)
• Office as the landing page: a workspace opens on the Office, the old Home page is gone, and a person with one workspace starts inside it (Orhan)
• 3D office and walk: a 3D version of the office and a walk across the floor for the general manager were built, with a switch between the flat and the 3D view (Orhan)
• One employee per department: agents are grouped as one virtual employee per department with its duties, named after mythological figures, and a duty can read its colleagues' last runs (Orhan)
• Agent goals: each agent can carry a goal with a baseline, a target and an owner, and its page shows the current value (Orhan)
• Reports page: one readable report per run with filters, and agents' summaries moved out of the Inbox and Slack (Orhan)
• Slack threads: an agent's posts in a channel now sit in one thread per agent, channel and week (Orhan)
• Workflows: nine templated loops that a general manager can read, tune and build from scratch in a workflow editor, with the story, the flow and the history (Orhan)
• Content pipeline: the marketing agents hand work to each other as cases, the general manager decides both approvals, and Argus never merges a change itself (Orhan)
• Weekly update and partner report: two new reporting duties that deliver a report with e-mail copies, and a monthly digest that compares periods (Orhan)
• Product loops: the feedback, release notes, roadmap and competitor duties read more sources and their four templates went live (Orhan)
• Sales flows: the ideal customer profile is drawn from paying customers, with lead research and campaigns that learn from results (Orhan)
• Overdue invoices: chasing became a sequence of reminders that carry the billing system's own payment link (Orhan)
• Jarvis: powers per person, approvals inside the conversation, a web reader and video, and a voice workspace with panes (Orhan)
• Company brain: Metis keeps answers, uploads, customer memories and an operating brief for the agents. The duty that maintains it is built, not switched on (Orhan)
• Fetch's first agents: a support agent and a product manager were hired for Fetch in draft mode, from a plan based on its tickets, code and tools (Orhan)
• Failed runs clear: a failed run leaves the list once the agent has run well again (Orhan)

Inbox and approvals

• What approving does: each approval says where it goes, how it is sent and why, in one layout per route and without internal ids (Orhan)
• Hand to a colleague: an approval can be assigned to someone else with a note, and notes from colleagues arrive as Inbox cards (Orhan)
• Personal list: the Inbox shows what waits on you, with Dismiss and a reminder for later (Orhan)
• Notification center: a full width Inbox with one tab group, icon actions with keys, filters by type and agent, and a confirm step before anything leaves the company (Orhan)
• Fewer cards: notes are kept apart from decisions, one digest per agent and topic a day, one card for a run's issues, stale drafts expire, and low-value hand-offs are grouped (Orhan)
• One waiting count: the number of things waiting on you is the same on every page (Orhan)

Support desk

• Answers from the code: the support agent can read the product's code through GitHub and search the knowledge base, which keeps its headings and links (Orhan)
• A draft for every ticket: the support agent can draft a reply to every ticket, mark the ones that need review and record hand-offs as taken (Orhan)
• Help center drafts: the knowledge base agent creates new Zendesk Guide articles as drafts only, and proposes articles for the gaps support found (Orhan)

Dashboards

• Business review: the review numbers as the first dashboard, drawn as charts and target rings, each with its status and gap, with finance's figures from the last closed month (Orhan)
• Business review speed: the page timed out on large workspaces. It now reads a stored copy that is kept fresh (Orhan)
• Review deck: the QBR or MBR pack downloads as a PowerPoint file in one click, with a forecast and a growth levers slide (Orhan)
• Growth by channel: eleven channels, a growth profile, question blocks on Growth, channel filters on Customers, and how each customer got here on its page (Orhan)
• Partner channels: Growth shows channel-partner metrics from the deals, and Fetch's partners were recorded from its import sheet (Orhan)
• Customer records: tags, categories, member notes, links between records of the same customer, and a setting for customer fields (Orhan)
• Honest dashboards: a dashboard with no data is locked instead of empty, empty tiles say Coming soon, illustrative blocks say Sample data (Orhan)
• Where a number comes from: a tip beside every number names its source and its last sync (Orhan)
• Pipeline and deals: the pipeline follows the CRM, a signed deal counts as won only once the customer has paid, and deals get a reliable open date (Orhan)
• Fetch's dashboards: Growth, Churn, Cash flow and Reconciliation were prepared for Fetch's demo, with its review cards as the data team reviewed them (Orhan)
• Plain words and phones: a wording pass on the office, inbox, workflow and agent pages, filters that fold on a phone, and one style of selects and tabs (Orhan)

Data and connections

• Integrations page: tools in use are shown in fitting categories, with a row per dashboard for what your tools feed (Orhan)
• Connections that need you: a connection whose key was rejected says so and waits for its owner instead of failing every sync (Orhan)
• Mailgun: each sending domain has its own key, with a separate one for outreach, and errors say Mailgun's own reason (Orhan)
• Fetch's warehouse: Fetch's Snowflake views are read through a reviewed mapping, its management accounts become the booked P&L, and its tickets come from Zendesk directly (Orhan)
• Warehouse sync: rows the warehouse dropped are removed, a changed mapping is read again, and a warehouse that delivers billing counts as billing (Orhan)
• Paddle fixes: an unsent Paddle transaction was counted as an open invoice and recurring discounts were missing from MRR. Both are fixed, and paid invoices carry their paid date (Orhan)
• Receivables: open receivables count only what was billed and is still owed (Orhan)
• AnnounceKit's review data: the 2026 budget and actuals were loaded and the pipeline was cleaned up for the quarterly review (Orhan)
• Time zones: changing a workspace's time zone recomputes its metric history (Orhan)
• Meetings and mail: internal participants no longer decide which customer a meeting or mail thread belongs to (Orhan)
• Code check: a read-only check lists the third-party tools a company's code uses, through its GitHub connection (Orhan)

Access and security

• Roles: an owner, a read-only Balio reviewer, a Balio data team role and a workspace member role, with roles kept as data (Orhan)
• Departments and levels: workspace access is given per department at three levels, least privilege by default, edited in one Team grid (Orhan)
• See as: a workspace admin can open the workspace as one of its seats for a limited time (Orhan)
• Only what you may use: pages, metrics, inbox actions and connections a person cannot use are hidden (Orhan)
• Sensitive figures: AI spend is shown to workspace admins and Balio only, and an account's billing in Customers sits behind a switch (Orhan)
• Privacy: a path to erase a person's data, retention rules, and no card data kept in billing records (Orhan)

Balio's side

• Workspace readiness: Foundry scores how ready each workspace is, from a workforce model of 29 roles and what each workflow needs (Orhan)
• New workspace in one step: creating a workspace takes one step and the rest moves to Getting started (Orhan)
• Workspace controls: tables for modules and data sets, hireable agents, a monthly limit and finance plans (Orhan)
• Health page: Foundry shows whether the runner is alive, and a sync is flagged stale after two hours (Orhan)
• Company-specific behaviour: an audit found where Argus behaved differently per company, and five packages turned those cases into settings (Orhan)

Platform and engineering

• Database changes: the schema is kept as a reviewable tree with safer change checks, and access checks are answered once per statement (Orhan)
• Tests: runtime tests run in isolation, a missing database call is a visible error, and the evals gained a second made-up company (Orhan)
• Diagnose tools: new read-only checks for support, revenue, approvals, the Business review, connections and Fetch's data (Orhan)
• Reload on a new release: an open tab reloads once when it asks for files of an older release (Orhan)