Analytics
DevSpec keeps two kinds of analytics, in two places, for two audiences.
Project intelligence
Every member of a project, whatever their role, can open Analytics in the project sidebar. It does not show totals for their own sake. Each panel opens with a sentence that states what changed in the period you pick (7 days to all time), and the numbers underneath explain the sentence.
- How long work waits. The typical time from an item being created to being picked up, implemented and verified, compared with the previous period, and how long the slowest tenth took.
- Where effort went. The share of implemented work that served each goal and each feature, against last period, and how much had nothing attached.
- How work originates. Whether new work was planned in a session first, created by a coding agent, or found after the fact from commits and deployments, and how that mix is shifting week by week.
Beneath the period, the project as it stands: conversations, knowledge and active people since the project connected, where open work is sitting (how much is waiting at each stage and for how long), and knowledge health: recorded decisions that carry a stale or contradictory flag, and discussion points that have been open for more than a month.
There is no money on this page for anyone.
Across the organization
Settings → Organization → Analytics shows the same signals for every project the organization owns, one row per project, so you can see which project is waiting longest, where effort is going and whose knowledge needs attention. Any member of the organization can read it.
Spend
Organization owners and admins manage money under Settings → Billing → Spend. It leads with the current calendar month:
- Balance, spent so far and expected this month as a range. The forecast is built weekday by weekday from the last four weeks, so a quiet weekend does not read as a slowing project. It appears once there are two weeks of usage.
- Runway at that rate, and the day the balance would reach zero.
- The auto top-up rule as one sentence, and the day the next top-up would fall due.
Below that, the period you choose: the last 30 or 90 days, any calendar month, or a custom range. You see what changed against the previous period of the same length, then spend by kind of work, by project, by session and by connected agent. The per-project figures for any period can be downloaded as a CSV that matches the page to the cent, for attaching to an invoice.
Money appears nowhere else in the product: not on a project's analytics page, not in a session, not on an agent.