Saved-time dashboard

A rough, workroom-level estimate of hours you didn't spend writing from scratch.

The 30-second version

The Insights page (/insights) shows total estimated hours saved across all completed workrooms in your workspace, plus a count of workrooms behind the number. The estimate is based on a per-workroom heuristic computed at completion. The number is best read as a workspace-level lifetime total.

Why this matters

Agency leadership wants a number to point at when justifying tooling spend. AtelyaOS gives you a workspace-level number — not a marketing claim — based on your actual completed workrooms. The estimate is heuristic, not a stopwatch. It's good enough for "we shipped 40 deliverables this quarter and saved an estimated 60 hours" and not good enough for individual-performance reviews.

How it works

Where the dashboard lives

Sidebar → Insights. The page shows:

• Total estimated hours saved — sum across every completed workroom.
• Workroom count — how many completed workrooms feed the total.
• A breakdown view with per-workroom estimates.

[SCREENSHOT: insights page showing total hours and workroom count]

How the estimate is computed

Each workroom, on completion, runs a small estimator that assigns it an "estimated hours saved" value. The estimator considers the deliverable size, agent type, and number of revisions. The computed value is stored on the workroom and rolled up into the workspace total.

The estimate is lifetime — it sums across every completed workroom in the workspace. There is no calendar-month view today. To approximate "this month", filter the breakdown by completion date.

The estimate is per workspace, not per user.

Who sees it

Any workspace member can read the Insights page. Owners and admins can additionally export a CSV of per-workroom estimates for their own analysis.

The dashboard is currently available to every plan in the app. Marketing copy in the pricing matrix mentions "Saved-time stats" on Starter and "Saved-time dashboard" on Pro — that distinction is presentational and not enforced as a hard plan gate today.

What the estimate is not

• It's not a stopwatch. It's a heuristic based on deliverable characteristics.
• It's not a per-user productivity metric. The workspace total doesn't break down by who created the workroom.
• It's not a revenue figure. Convert to dollars yourself if you want one.

Using the number

What the saved-time number is genuinely useful for:

• A line item in your monthly partner update: "AtelyaOS shipped 28 deliverables, ~40 estimated hours saved."
• A quick "is the team using it?" check — if the number isn't growing, the team isn't using AtelyaOS.
• A trend over quarters when you can pull two CSV exports.

What it's not useful for:

• Individual performance review.
• Hard ROI calculations.
• Comparing across workspaces.

Common pitfalls

• Using it as a per-user metric. The total is workspace-level. Don't try to rank writers off it.
• Reading it as exact. The heuristic is good for orders of magnitude, not minutes.
• Forgetting to look. The number is most useful as a trend, but only if you check it regularly.
• Ignoring workrooms in the count. A high "hours saved" number with a low workroom count means a few large deliverables; a low hours-saved with high count means many short pieces. Both are useful, in different ways.

What's next

• Pricing plans — what each tier includes.
• Team collaboration — context for who created what.
• Workrooms — the unit the estimate is computed on.