This week the Balio team got its own side of Argus, with a Home page, a plan and trials for agents, and workspace dashboards can now be read one channel at a time.

Highlights

• Home: the Balio team's new landing page shows what needs Balio now across every workspace: broken tools, late tasks, trials ready to decide and security fixes. Tools and Agents list every tool and agent, and Search Foundry finds any of them (Orhan)

• Experiments: every agent on trial, measured against the weeks before it was switched on. A trial marked Ready to go live waits for a person to decide (Orhan)

• Planning: the Balio team's plan in six views: Cockpit, Workspaces, Timeline, Tasks, Review and Team. A workspace's Setup tab starts its plan from a template and a target go-live date (Orhan)
• Workspaces: one dashboard lists every workspace, each with its own admin page. The new Data map tab draws the tools a workspace uses and what flows between them (Orhan)
• Security: a console with a score, the checks that passed and the ones to fix or look at (Orhan)
• Channel filter: on Revenue, Success and Customers, pick a channel or a partner to see only the customers who came through it. Growth, Channels now draws revenue and customers by channel (Orhan)

• Team & hiring: 18 new duties to hire, among them renewals, MRR bridge, pull request review and board update. None switches on by itself, and each starts in draft (Orhan)
• Support: every workspace now runs the same support flow. The agent can leave its suggested reply as an internal note on the ticket, and ticket categories come from your own tickets (Orhan)
• Logs: Reports is now Logs under Agents, for admins. Tone and agent rules moved from Settings to Metis (Orhan)

Everything shipped this week

Agents and automation

• Experiments: an agent switched on in draft now runs as a trial, measured against the weeks before it, with a board, a read-out per trial, a check that says when it is ready to go live, and a way to start a trial by hand (Orhan)
• Hireable-only duties: a plan for 18 new duties, and a rule that a new duty is offered in Team & hiring but never switched on by a hire, so adding one changes nothing until a person turns it on (Orhan)
• Customer health duties: support health check, churn intake, renewals and expansion signals can be hired; built, not switched on (Orhan)
• Finance close duties: MRR bridge, cash review and past-due review can be hired; built, not switched on (Orhan)
• Growth strategy duties: a competitor scorecard, a growth report and an outbound strategy among them can be hired; built, not switched on (Orhan)
• Engineering desk duties: pull request review (quiet on weekends), weekly code review, engineering report and QA test plan can be hired; built, not switched on (Orhan)
• Operations and executive duties: sync health, workforce review and board update can be hired; built, not switched on (Orhan)
• Agent page and Logs: the agent page has one header with an action bar and each duty's status as plain labels, and Reports became Logs under Agents, for admins (Orhan)
• Agent runner: the runner now stops cleanly when a new version is deployed, and the data sync is no longer listed as an agent (Orhan)

Support desk

• One support flow: every workspace runs the same support flow, stage by stage, instead of a setup of its own (Orhan)
• Desk notes: the agent can leave its suggested reply as an internal note on the ticket, written as a named teammate, reading the whole ticket and building on the team's answer; switched on for Fetch and AnnounceKit (Orhan)
• Loop builder: steps are numbered, a stage can take any of the desk's duties or "No one yet (plan only)", and missing items are named (Orhan)
• Ticket categories: support categories are now derived from a workspace's own tickets, never typed in by hand; two changes to the code the agents read were held back until the general manager approves them (Orhan)

Dashboards

• Channel filter: Revenue, Success and Customers can be filtered to one channel or one partner, the choice is remembered between those pages, and the page keeps the last numbers on screen while a new filter loads (Orhan)
• Growth, Channels: the page draws revenue and customers by channel with partners, and the coverage strip moved off the dashboards into an information button for admins (Orhan)
• Shared bills: a bill recorded as shared between partners is split across them in the Growth numbers, first used for Fetch (Orhan)
• Billed through a partner: Fetch's hotels count as its customers and the systems that bill them as billing partners, with a badge on the customer's page (Orhan)
• Faster Growth pages: the content block was reading far more search data than it needed, which made the page slow; it now reads only its own pages (Orhan)
• Faster Revenue pages: the Revenue read and the nightly metrics were slow on large accounts; both were reworked after timing every dashboard read in production (Orhan)
• Settings: tone, hand-offs, agent rules, customer fields and the growth profile are now set in Metis only, not twice (Orhan)
• Team table: the actions fit on one line and long department names wrap inside their column (Orhan)
• Sidebar: the "new" badge beside dashboards is gone (Orhan)

Data and connections

• Empty warehouse: a warehouse connection that imports nothing used to show as healthy; it is now flagged (Orhan)

Access and security

• Sign-in: after Continue with Google some people landed on "You are not signed in"; that detour is fixed, and a refused sign-in now shows its reason (Orhan)
• Security console: a page for Balio admins with a score and every check, including that sign-in is Google only (Orhan)
• Weekly security check: a routine that scans the code and audits the database without changing anything, and feeds the console (Orhan)
• Read-only login for the data engineer: a database login that can read and cannot change anything (Orhan)
• The data team reaches the plan: the data team can open and work Planning and a workspace's setup steps, and nothing else on Balio's side (Orhan)

Balio's side

• Workspaces: one dashboard for every workspace with first and last seen for its people, and a simpler admin page per workspace (Orhan)
• Planning: the Balio team's one plan to the end of the year, with workspaces as projects, checklists read live from each workspace's data, a week and month calendar and a timeline with milestones (Orhan)
• Setup guide: a workspace's Setup tab plans every step from kickoff to go-live from a template, opens the next steps as earlier ones close, and starts when the workspace is created (Orhan)
• Planning cockpit: one lane per role with what is ready, late and waiting on someone, the week's load, a weekly review and a team view (Orhan)
• Four setup roles: setup steps are owned by chief of staff, forward deployed engineer, data engineer and product lead (Orhan)
• Planning opens faster: the page was slow to appear; it now shows at once and fills in the live facts after (Orhan)
• Home and search: a Home page with what needs Balio now, a new sidebar with counts, tabs on every workspace's admin page, and search across workspaces, tools and agents (Orhan)
• Tools and Agents: a page for every tool with where it is connected and whether it works, a page for every agent across workspaces, and a Tools tab on each workspace (Orhan)
• Tool watch: a broken tool opens a task on the plan for the right role and closes it when the tool works again (Orhan)
• Data map: a drawing of each workspace's tools and what flows between them, suggested from its connections and editable; it changes no connection (Orhan)
• Team photos: profile photos for the Balio team on Planning (Orhan)

Platform and engineering

• Database load: the busiest lookups got indexes, the business review refreshes only when it is out of date and the upkeep runs once a minute, measured before and after on production (Orhan)
• Schema snapshot: the stored picture of the database no longer changes with the version of the tool that writes it (Orhan)
• Local test database: one script starts the local database the test suite needs (Orhan)
• Test fixes: three tests that failed for reasons unrelated to the product were fixed, among them a baseline check that broke on a database without Fetch (Orhan)
• Diagnose tools: read-only reports for the last applied database changes, the support desk's notes, why a company's code cannot be read, and the setup audit (Orhan)