The product is in release v2. Below is what each release contained, the links to ecosystem products being connected now and what was deliberately postponed.
Extensions, external participants and the ecosystem agent are available on a par with the core. Links that need work on neighbouring products are listed separately below and are not presented as ready.
Features for narrow segments plus access for the ecosystem AI agent.
Billing, portfolios and reporting built under the permissions of the reader.
The stage about scheduling, and about replacing manually entered rates with actual data.
Economics went into the first stage alongside the base. Distinguishing features are usually deferred, but without this one the product would not differ from free competitors.
These links are described in the specification but do not work end to end yet: some wait for work on neighbouring products. Until then the calculation runs on manual data.
The contract is described, but project dates and milestones do not appear in the participant calendar yet.
An act already keeps links to the bill in A3.Sales and the contract act in A3.Lawyer. Automatic transfer of bills, costs from A3.Accounting and payments from A3.Finance arrives together with them.
External assignment fields are read from the source, and edits wait in a queue. Writing back waits for the reference integration with A3.Lawyer.
Notifications go to the in-app feed, the A3.ID feed and email. Push for the installed mobile version is in progress.
Turning a feature down is a decision too, and it deserves an explanation rather than silence.
It eats budget and loses to the messengers the team uses anyway. Comments, mentions and the activity feed cover work in the context of a task.
Until the demand is confirmed. Automatic placement produces formally correct plans that no project manager accepts.
Email is covered, Telegram waits for demand: a bot needs its own registration at the customer and separate consent to forward task content.
After the first reference integration. A sandbox with no first consumer would serve an imaginary scenario.
Instructions, settings and contract details live in the knowledge base. The product scope by feature is collected in the catalogue.