Monday morning: your portfolio in 10 minutes
You open AG.it. Walked through the at-risk project “CRM rollout at Mercury Trade” — 60% done, the next payment of 1.5M ₽ for pilot-operation acceptance overdue.
Step screenshots show the detailed (expert) view. The live demo opens in the lightweight focus mode: the full toolset is one tap away — “expert” on the bottom dock or the F key.
The whole portfolio and the money on one screen
The portfolio canvas: 23 projects on one screen. Per project — a money bar (green secured · grey promised · orange at-risk), the next milestone ◆ and the computed finish ● on a shared time axis, the schedule slip. Groups by industry with live subtotals. Up top: “18 projects need attention · 24.3M ₽ at risk · 33 decisions”.
In 10 seconds you know where the money is and what's on fire — before the status meeting. At-risk projects are already flagged with the overdue figure.
Risks and decisions, quantified in money
“3 of 5 projects need attention · 4.5M ₽ · $4K at risk”. Problem cards on the left (expand on hover); a Risks & Blockers register and a “Waiting on you” list on the right.
A list of decisions instead of digging. Every risk is tied to money and a milestone — you see which action closes which payment.
What moved this week — across every project
A ready weekly review: where there was movement, what closed with confirmation, where it's quiet (the “no change” strip is always pinned at the bottom). The pending-decisions list, assembled automatically.
A weekly report with no manual roll-up. You walk into the meeting with the picture, not questions for the team.
Diagnosis at a glance: money at risk
The verdict, right in the header: “Money at risk — outcome not locked in”. The revenue path as a staircase of milestones. At the bottom: Revenue 0 ₽ · Backlog 3.3M ₽ · of which at risk 1.5M ₽.
You grasp the cause instantly: the pilot-operation milestone worth 1.5M ₽ is overdue and needs a signed act. And you see the options right there: cut scope, move the deadline, add help, accept.
The cash truth of the project
Inflows (plan) 3.3M ₽ · Received 0 ₽ · Deviation −1.5M ₽. A monthly inflow chart (plan vs actual) and a deviation table by milestone.
In black and white: not a single ruble is closed by an act yet, even though the project is 60% done. That's the cue to talk acceptance with the client — before quarter-end.
Trust in the status: changes backed by facts
The diff between two snapshots: what's achieved, what slipped, which signals arrived (e.g. “client scheduled acceptance for June 20”). Every change with an actual date.
The status is trustworthy — every change stands on a fact or a signal, not on “we think it's done”.
The critical path to the money
A goal graph by phase: Prep → Build → Verify → Launch. The “System accepted for pilot operation” milestone (1.5M ₽) is flagged at-risk on the critical path.
You see the exact node holding 1.5M ₽ and what unblocks it — you can push on that specifically, not “speed everything up”.
When is the finish — and which task holds it
A computed schedule: a verdict on top — “finish Sep 30, 2026 — on schedule” (or “slipped by +N days”, with the culprit). Bars are derived from facts — milestone plan dates ◆, task date windows, forecasts; every lane carries its source badge: “milestone · plan”, “from tasks · N”.
The familiar Gantt read — except it can't be drawn, only computed. A bar edge clicks through to the task that holds it: the schedule conversation is concrete from the first minute.
Rewind two weeks — and prove it
The portfolio as of June 24 — exactly as it was. On top, the slice map: the whole observation history, a tick per snapshot, ◆ on acceptance dates. Clicking a tick moves the whole portfolio to that date; a step takes about a second.
State is reproducible. You can rewind and show the client or the team exactly when and what slipped — no “did it really” argument.
The evidence: the acceptance log
History on the left: plan snapshots and acceptance confirmations with dates — “accepted, all milestone tasks complete”. The same log in a console view on the right.
An append-only audit trail: entries aren't edited — changes are added as a new event. Every accepted milestone = money, with a date and a basis. This is what separates AG.it from a task tracker.
Where does the data come from? First technical snapshot in ~10 minutes
Import a task snapshot from Jira / Excel (CSV or XLSX) — the system builds the state at once: progress, overdue, diff. The goal graph and money come later.
The main objection — “who is going to fill this in” — is gone. The first report lands on day one, no long rollout; the data comes from what the team already has.