Introducing Timesheets: Where the Hours Went
A timesheet web app for freelancers and small studios — workspaces for clients, calendar-style time entry as the week happens, and a workspace that carries its invoice defaults straight into Invoicing. In beta, and the studio runs its own hours on it.
A client wanted an invoice on a Sunday night. I opened the week between me and that invoice and could not have said where a single hour had gone.
The problem
Time tracking fails at the entry, not the timer. Every tool can tick seconds. Then Friday comes, and the tool asks you to rebuild the week from memory: what you worked on, for whom, and how long. Reconstruction is the part I hate, so Timesheets is built to make entry cheap enough that Friday never needs a reconstruction.
What it is
Timesheets is a web app with two ideas and no ceremony.
Workspaces are clients. A workspace holds a client’s people and their hours. It also carries invoice defaults and a due-date duration, so what you tracked walks into Invoicing without a second re-typing session.
Time entry on a calendar. Drag out a block when the work happens, describe it, done. Entries autosave as you go. Teams share a workspace, and invitations go out by e-mail. Filterable reports keep the whole week one click away.
What it costs
- It is beta. We run our own hours on it, which is the test we trust most. Rough edges are still possible, and I would rather you know.
That is the list. The beta is the cost, and running on it is the mitigation.
Try it
Timesheets is up. Track the week as it happens — a block here, a block there — and see how the Friday reconstruction disappears.
If your hours end up on invoices anyway, pair it with Invoicing — tracked hours that cannot become invoices are just a hobby.
Technical Details: Meteor web app — workspaces, teams, and timesheet entries with autosave; workspace invitations by e-mail. Developed with OpenCode.