Read-only tourEvery screen is captured from the running system. Look round freely; nothing you type is saved.Back to ayushmutha.in

A WORKING DEMO · NOT A VIDEO

Pick a seat, and the software changes.

This is a timesheet built for a thirty-eight person accountancy practice that was running on one shared spreadsheet. Everything in it is invented: the firm, the staff, and all 512 clients. No real data has ever been near it.

The interesting part is not the form. It is that three people open the same system and see three different things. Choose one and you are straight in; no password, nothing to fill in.

An employee

Logs their own week. Picks a client from a list of 512 and an assignment type, and the day totals as they type.

  • Their own week, and nobody else's
  • Their leave balance and requests
  • A week that locks on schedule

A team lead

Everything an employee has, plus the people who report to them, and only those people.

  • Their reports' weeks, with drill-down
  • Leave requests waiting on their decision
  • Team reports scoped to their line

An administrator

The firm-wide view: reports by month and by person, the master data, and the locking controls.

  • Every person's time, pivoted by month
  • Master data · clients, groups, types, holidays
  • Period locking, and deliberate unlocks

The payroll operator

A second module behind a second sign-in. Six months of invented pay: five closed, one open with the cases that need a person to look.

  • The month as one figure, with its arithmetic
  • One person's pay, leave and balances carried between months
  • Leave pulled from the timesheet, and where it was overruled

What this was built to fix

Their spreadsheet carried a 500-item client dropdown and a second, separate 500-item client group dropdown, with nothing linking the two, so the instructions asked every person to hand-check that the two agreed, on every row they typed. Job costing was being built on data nobody could trust. Open Master data as the administrator to see what replaced it.

This instance takes writes. Anything you add or change is fine; it is reset on a schedule, and it is not connected to anyone's real system.

Prefer the front door? instead.