Features
Three organizations, one system
AROS is not a chat window with tools attached. It is a revenue organization, a quality organization and a discovery organization that share one company brain and one safety model.
The revenue organization
22 specialized agents that plan, produce, qualify and prepare outreach — each with one job and explicit permissions.
- Objective in a sentence → an agent pipeline built only from agents that exist
- Every agent reads the Company Brain — and your Organization DNA, once it is set — before writing a word
- Cheap↔advanced model routing with a cost ledger and a hard daily/monthly budget cutoff (with a live AI provider configured)
- Daily, weekly and monthly loops that run on a schedule; the quarterly strategic review is built but not on a schedule yet
The quality organization
25 virtual humans driving a real headless Chromium through your applications, on a cadence.
- Real browser runs — not mocked HTTP — against login, critical workflows and access control
- Defects deduplicate by signature; filing one to GitHub is a person's click, through the approval gateway (simulated until GitHub is connected)
- Private-network and cloud-metadata targets are refused by default (an SSRF guard)
- A product cannot be recorded as launched or scaling without a QA certificate that actually passed
The discovery organization
What to build next, decided from evidence rather than enthusiasm.
- Recorded market signals and internal mining feed a scored opportunity board (17 dimensions)
- Confidence is computed from the evidence and can never be set by hand
- A discovered opportunity must cite the signals it came from or it is discarded unwritten
- Eight validation gates stand between an idea and a development brief
Autonomy with a hand on the brake
Every external action an agent requests passes the same three checks, in the same order, whichever agent raised it. Sends through the communications engine and spend through the ad governor run through their own gated engines, with approval, stop rules and budgets of their own.
- · Autonomy level L0–L4, set per agent
- · Risk class LOW → CRITICAL, set per capability
- · A global kill switch that stops autonomous external action, re-checked at execution time — not at queue time
- · Append-only audit, with secrets redacted systemically rather than per call site
What the console includes
Command Center
One screen for what the system did, what it wants to do, and what it is waiting on.
Approvals
External actions the policy engine will not take alone route to the role that should decide them.
Leads & pipeline
Qualification from HOT to DISQUALIFIED by a deterministic scoring model, with the score shown beside the band.
Prospect intelligence
Attributable signals, product matches that must cite them, explainable priority.
Revenue execution
An 11-step commercial lifecycle with per-product configurable workflows.
Content factory
Planned against the funnel, drafted in your brand voice once Organization DNA is set, and held in review until a person approves it.
Social & community
Drafted per channel into review on a schedule, with replies proposed for a person to send. Nothing publishes until a channel is connected.
Business profiles
Reusable business identity with classification bounded by where the fact came from.
Communications engine
Products own the identity; AROS operates the governed engine and the stop rules. Messages are held as not connected until a channel is.
Authentication center
Policy and tracking for sign-in challenges on accounts you authorise; no platform login is connected yet. It never stores a one-time code.
Plans & metering
Per-tenant quotas and QA concurrency caps, so one tenant cannot starve another.
Audit & rollback
Append-only: no screen edits or deletes an entry. Every action, decision and AI cost is recorded; secrets are redacted before they are written.
And what it does not do yet
A revenue number that has not been measured is shown as unmeasured, never as zero. The same rule applies to this page.
Answer-engine (AEO) visibility
Reported as UNMEASURED rather than implied. No such subsystem exists yet.
Measured revenue
Revenue counts as measured only when a product reports its customers' payments to AROS. Until one does, that product's revenue reads UNMEASURED, never zero; CRM-recorded MRR is labelled as recorded, and CAC as an estimate.
Authorised data sources (GST/MCA)
Not integrated. VERIFIED means a human recorded a document they checked.
Self-serve signup
Onboarding is key-gated by design; a company is provisioned deliberately.
Connected channels
Connector code exists for GitHub, Gmail, WhatsApp, LinkedIn, Meta, X, Google Ads and others, but each runs as a labelled simulation until a company connects it. Nothing is published, sent or spent through a channel that is not connected.
Live messaging and online payment
Governed email and WhatsApp sends, one-time codes and online payment run through SnxwFairies' central Core AI service. Where it is not configured, WhatsApp is unavailable, governed messages are held, and no "Pay now" is offered.
See it against your own objective
Tell us what your revenue motion looks like and we will walk you through what AROS would do with it.
Talk to us