What HR sees: which teams ran the close.

Six teams, 180 people. How many days each team ran the close, and how many joined on average. Never who. There is nothing here to manage.

The HR view · sample data · nothing here is real, and there is no backend

Sample data. This screen is a working demo, not a customer. Every number is invented, the buttons change the page but not a database, and reloading breaks it. It exists so you can judge the product without a call.

Northwind Logistics

6 teams · 180 people declared · billed monthly

Next invoice

₹8,994 + ₹1,619 GST

₹1,499 a team · 6 teams · 180 people

Teams

Teams with fewer than 10 people taking part are hidden from HR, plus the next-smallest.
Team Declared size Days run Sessions a day (avg) Trend Status
Engineering645 of 541Steady Running
Operations384 of 519Steady Running
Sales282 of 511Fading Fading
Customer success265 of 513Steady Running
Finance16Hidden · under 10 sessions this week Not shown
Design8Hidden · under 10 sessions this week Not shown

Add a team and type its size: the invoice updates (₹1,499 a team; size is only used for the "joined" share). Nothing is saved.

HR's line, as it was sent

Six weeks

  • Week 122of 30 team-days
  • Week 226of 30
  • Week 325of 30 · Sales 5/5
  • Week 423of 30
  • Week 524of 30
  • Week 621of 30 · Sales 2/5

What this screen will not do. It will not show you a person, a team under 10 taking part, a manager's breakdown, or a health outcome. Those are not missing features — the first two are the product, and the third does not exist.

Read the rule behind the grey rows: the under-10 rule and the full data map →