The first week of Argus: one workspace per company, where agents do the routine work, people approve what goes out, and the company's numbers sit on one set of dashboards.

Highlights

• Agents: your agents sit on a floor by department, with what each is doing and what needs you. Org chart shows who reports to whom. Hire agents lists 17 agents across Sales, Customer Success, Finance, Marketing and Product. A hired agent starts in draft and sends nothing on its own. (Orhan)

• Inbox: every e-mail, reply or post an agent wants to send waits here. Read it, then Approve, Edit or Skip. Filter by type or by agent. (Orhan)

• Jarvis: ask a question about your company and get the answer with its numbers. Open it from the sidebar or with Ctrl K on any page. Once connected, it also answers in Slack and Telegram. (Orhan)
• Home: the main numbers, your calendar today, mail awaiting your reply, your tasks and the morning brief. (Orhan)
• Dashboards: Revenue, Customers, Success, Growth, Marketing, Product, Cost and Monthly review, filled from your connected tools. (Orhan)

• Customers: one record per account with billing, product use and support together. Review matches lists possible duplicates for you to confirm. (Orhan)
• Board: a product board under Product that takes in Linear issues. Send to Linear waits for your approval first. (Orhan)
• Integrations: connect billing, support, analytics and other tools. A tool syncs when you connect it, then every hour. (Orhan)
• Knowledge: the help articles, website pages and company notes your agents read before they answer. (Orhan)

Everything shipped this week

Agents and automation

• Agents floor: a page that shows every agent at a desk in its department, what it is doing now and what waits for you (Orhan)
• Departments, Org chart and hiring: agents have roles and departments, you can hire into an open seat or let an agent go, and department heads send their reports up to the general manager (Orhan)
• A roster of 17 agents: agents for support, collections, sales, customer success, marketing, product and finance, all written to one standard that says what each reads, what it may decide and when it hands over to a person (Orhan)
• Hire agents: a catalogue where each agent card shows the tools it needs, its tasks and its monthly cost, with one button to hire it in draft (Orhan)
• How it works: each agent's page draws its work as a flow, from what starts it to what it reads, decides and sends (Orhan)
• Tell the agent and sources consulted: you can leave an instruction for an agent, and each run lists the sources the agent read before it answered (Orhan)
• Autonomy levels: each agent has a level that sets what it may send without asking, with a record of every change and a weekly scorecard (Orhan)
• Company memory and hand-offs: agents share what they learn, pass work to each other, and a Team manager agent reviews their reports and proposes improvements (Orhan)
• Six routine agents for any company: six more agents that do not depend on one company's setup, with a table that shows what each still needs before it can start (Orhan)
• Jarvis: an assistant for the general manager that answers questions about the company from its data, on its own page and from a Ctrl K bar on every page (Orhan)
• Jarvis memory and web search: Jarvis remembers what you ask it to keep, forgets on request, and can search the web and list its sources (Orhan)
• Jarvis in Slack: a direct message or a mention of Argus in Slack gets Jarvis's answer in the same thread (Orhan)
• Jarvis in Telegram: link your Telegram account in Settings and ask Jarvis there, by text or by voice note, and approve items from the chat (Orhan)
• Jarvis voice: hold to talk to Jarvis and hear the answer, with a voice mode that works over any company page (Orhan)
• Jarvis calendar and mail actions: Jarvis can prepare a calendar event or an e-mail for you, and it goes out only after you approve it (Orhan)
• Jarvis watch and settings: Jarvis checks the company every hour and nudges you about what needs attention, within the permissions and standing orders you set in Settings (Orhan)
• Morning brief per person: the morning brief now goes to each recipient as a direct message with their own day, next to the channel post (Orhan)
• Agents on the company's own AI key: each company's agents run on that company's key, and Argus can now route work to several AI providers and to cheaper models where they do (Orhan)
• Agent reply fixes: replies signed with a team name are no longer rejected, and a reply that was cut off at the length limit is asked for again in smaller pieces (Orhan)
• Health score fixes: the health agent scores every paying account in one pass and no longer marks an account at risk only because its product use is not tracked (Orhan)
• Event triggers: the groundwork for agents that start when something happens, such as a new case, and not only on a schedule (Orhan)
• Agent test cases: every agent has a set of written cases it must pass, including refusals, spending limits and attempts to mislead it (Orhan)

Inbox and approvals

• Inbox: everything an agent wants to send waits in one list in plain language, with Approve, Edit and Skip and filters by type and agent (Orhan)
• Approved actions go out through your own tools: an approved e-mail, reply or post is sent from the company's own mailbox, help desk or chat (Orhan)
• Nothing live by default: a newly hired agent only drafts until someone switches it to live (Orhan)
• Each send goes out once: an approved item can no longer be sent twice, and each company has its own send queue so one busy company does not delay another (Orhan)
• Sender roles: agents send as billing, success, outreach or internal, each from the address you set (Orhan)
• Agents' own e-mails go to known people: an agent's reports go only to people listed for the workspace, and Settings has a list of who receives them (Orhan)

Support desk

• Support desk agent: the support agent now looks up the customer and the help articles before it drafts, and hands over to a person when the topic is outside what it may decide (Orhan)
• People and escalation: Settings lists your people, which topics go to whom, and the rules a reply must follow (Orhan)

Dashboards

• Home: a first page with the headline numbers, today's calendar, mail awaiting your reply, your tasks, free days and the morning brief (Orhan)
• Dashboards on real data: Revenue, Success, Growth, Marketing, Product, Cost and Monthly review read from the connected tools, in the company's reporting currency, and a block with no data says so (Orhan)
• Customers and the customer page: a list of every account by segment, and one page per customer with overview, billing, product use, support and contacts (Orhan)
• Review matches: records of the same customer from different tools are joined into one account, and uncertain matches wait for a person to confirm (Orhan)
• Product board: a board per company that takes in Linear issues and GitHub pull requests, shows agent suggestions, and sends a card to Linear after approval (Orhan)
• Pipeline board and Funnels: two working pages under Growth for deals by stage and for conversion step by step (Orhan)
• Cost and Monthly review books: Cost gains an Invoiced page and Monthly review an Actuals page, and a general manager can edit the books, budget and vendor terms (Orhan)
• Agent results on pages: what agents produce, such as health tiers, the roadmap check, release notes, competitor notes and outbound drafts, appears on the matching dashboard page (Orhan)
• Churn, sign-ups and traffic detail: churn cases with reasons, live sign-ups with their channel, search position, countries and visits sent by AI assistants (Orhan)
• Meetings matched to customers: calendar and meeting-note entries are matched to customers by the attendees' e-mail addresses (Orhan)
• Faster pages: dashboards load card by card and the heavy reads were rewritten, so pages open quickly on a full company's data (Orhan)
• Honest charts: a chart no longer drops at its right end because the current period is not over, and axes use even steps (Orhan)
• One sidebar, dark mode and the Argus look: the product was renamed from Cockpit to Argus, with a new logo, one left sidebar, a theme switch, plain wording and a layout that works on a phone (Orhan)

Data and connections

• Integrations: a page to connect each tool with a key, a sign-in or a ready-made preset, and to change a connected tool's settings later (Orhan)
• New connections: Stripe, Paddle, Paddle Classic, Zendesk, Intercom, Xero, HubSpot, Mixpanel, Google Search Console, Google Analytics, Gmail, Linear, GitHub, AWS, Mailgun and AnnounceKit can be read (Orhan)
• Add to Slack: Slack connects through one Argus app, and the install screen picks the channel agents post to (Orhan)
• Sync on connect, then hourly: a tool syncs the moment it is connected and every hour after, and one failing or slow tool no longer stops the others (Orhan)
• Knowledge: help center articles, website pages and company notes are collected into one searchable library that agents read (Orhan)
• One data model and one set of metrics: every tool's records are stored in one shape, and each metric is computed one way for every company (Orhan)
• A data warehouse as a source: a company can connect its warehouse, Snowflake first, and have revenue read from it (Orhan)
• Monthly revenue corrected: a subscription moved between two billing systems counted twice, discounts were ignored, and past months used today's prices. All three are fixed for Paddle and Stripe (Orhan)
• AnnounceKit's history brought over: the customers, billing and agent history of the old AnnounceKit admin were imported into Argus, with an import that resumes after a dropped connection (Orhan)

Access and security

• General managers run their own workspace: a workspace admin can hire agents, configure them, switch them to live and pause them without Balio's help (Orhan)
• Invite your team and Preferences: a general manager invites their own people, and Settings has a Preferences tab (Orhan)
• Personal mail and calendar stay personal: rows from a person's own mailbox and calendar are visible to that person only (Orhan)
• Security review and fixes: four audits of security, company separation, code and readiness were written, and the first findings were fixed, among them connections that could be pointed at another address (Orhan)
• Privacy policy and About pages: two public pages that Google requires before a company can connect its Google account (Orhan)

Balio's side

• Foundry desk: Balio's page for requests from workspaces. A request for a team of agents is answered with one action that installs it in draft (Orhan)
• Modules: every dashboard and feature can be switched off for a workspace from Foundry (Orhan)
• Onboarding and company profile: a setup wizard for a new workspace, a Settings page, and one company profile that agents and pages read (Orhan)
• Demo company: a sample company named Ground Zero for showing the product, kept out of the portfolio numbers and never run by the scheduler (Orhan)

Platform and engineering

• The agent runner: the service that runs agents and syncs moved to Cloudflare, with separate lanes for support and scheduled work so a busy company does not hold up the rest (Orhan)
• Staging and production releases: the dashboard is deployed as its own service, with a written guide for staging and production (Orhan)
• Tests before every release: a release now waits for the full test run to pass, and database changes are checked for order and safety first (Orhan)
• Read-only diagnose tool: a way to run a read-only question against production data, with ready reports on revenue, connections, agents and page speed (Orhan)
• Simulated tools for testing: stand-ins for billing, support, chat and help center tools, so agents are tested end to end without touching a real account (Orhan)