Stintt reads your calendar read-only and writes the timesheet for you, sorted by AI and ready to export to Excel, CSV or PDF. Managers approve the week and turn approved hours into invoices. No timers, no screenshots, no desktop agent.

Hi Fazier, I'm Ritik and I built Stintt. It started with Friday afternoons spent trying to remember what I did on Tuesday, and then billing a client based on that guess. Every automatic tracker I tried fixed it by installing an agent and taking screenshots, and my team hated being watched. Stintt reads your calendar instead. The access is read-only, so it can never edit or delete an event. Connect Google Calendar and your events become a draft timesheet, sorted into meetings, focus, admin and breaks. A manager approves the week, approved hours become invoice line items, and anything that never made it onto the calendar can be logged from Telegram or Google Chat ("fixed login bug 2h"). Where it stops today: the team roll-up, approvals and invoicing run on Google Calendar. Teams, Jira, ClickUp and Asana cover your own timesheet and export. There is no Slack bot, and Stintt does not send invoices for you. You export the PDF and send it yourself. Free tier, no card. I would especially like to hear where the categorisation gets your week wrong.
Reading the calendar read-only and turning events into timesheet entries is a nice way to avoid the usual timer fatigue. I like that corrections turn into sticky rules for the AI categorisation. How does it handle calendar events that are padded or don't reflect real work, like a meeting that ran 20 minutes short?
The read-only calendar approach is a smart answer to timer and screenshot fatigue. I'd be curious how the categorisation handles recurring client meetings that span two projects: does correcting one event update the rule for the whole series? The approve-then-invoice flow would suit small agencies and freelancers billing hourly.
Logging from Telegram is the part I'd use most: half my client calls never make it onto the calendar. One question about overlaps: if Tuesday 14:00-16:00 is a planned focus block, but I send "Acme call 1h" for the same afternoon, does the chat entry replace part of the block, or do both stay and the day ends up with 3 hours? For invoicing, I'd want the chat entry to win and the focus block to shrink.
Building timesheets from read-only calendar events instead of timers is a nice way to avoid tracking fatigue. When AI categorisation gets an event wrong and I correct it, does the rule apply to recurring events with the same title, and can the approved hours be split across several clients on one invoice?
Turning calendar events into a timesheet without timers or screenshots is the right way round: people will not be watched, and the data already exists. Logging time from Telegram with "fixed login bug 2h" is a nice detail. How do you handle a meeting that covers two clients: can one event be split between projects?
As a two-person team billing partner work, the timer is exactly the part we forget. Reading the calendar read-only is a smart trust move. Question: how does it handle a block like “Partner calls” that covers three clients? Can I split one event across projects, or do I have to split it in the calendar first? Corrections that stick as rules sound like the real time-saver.
Timesheets are one of those admin tasks that should be invisible. Pulling from calendar events instead of manual tracking is genius - no more forgetting to start/stop timers. The accuracy improvement vs manual entry has to be massive. Curious how it handles overlapping events or back-to-back meetings where focus time is unclear.

Hi Fazier, I'm Ritik and I built Stintt. It started with Friday afternoons spent trying to remember what I did on Tuesday, and then billing a client based on that guess. Every automatic tracker I tried fixed it by installing an agent and taking screenshots, and my team hated being watched. Stintt reads your calendar instead. The access is read-only, so it can never edit or delete an event. Connect Google Calendar and your events become a draft timesheet, sorted into meetings, focus, admin and breaks. A manager approves the week, approved hours become invoice line items, and anything that never made it onto the calendar can be logged from Telegram or Google Chat ("fixed login bug 2h"). Where it stops today: the team roll-up, approvals and invoicing run on Google Calendar. Teams, Jira, ClickUp and Asana cover your own timesheet and export. There is no Slack bot, and Stintt does not send invoices for you. You export the PDF and send it yourself. Free tier, no card. I would especially like to hear where the categorisation gets your week wrong.
Reading the calendar read-only and turning events into timesheet entries is a nice way to avoid the usual timer fatigue. I like that corrections turn into sticky rules for the AI categorisation. How does it handle calendar events that are padded or don't reflect real work, like a meeting that ran 20 minutes short?
The read-only calendar approach is a smart answer to timer and screenshot fatigue. I'd be curious how the categorisation handles recurring client meetings that span two projects: does correcting one event update the rule for the whole series? The approve-then-invoice flow would suit small agencies and freelancers billing hourly.
Logging from Telegram is the part I'd use most: half my client calls never make it onto the calendar. One question about overlaps: if Tuesday 14:00-16:00 is a planned focus block, but I send "Acme call 1h" for the same afternoon, does the chat entry replace part of the block, or do both stay and the day ends up with 3 hours? For invoicing, I'd want the chat entry to win and the focus block to shrink.
Building timesheets from read-only calendar events instead of timers is a nice way to avoid tracking fatigue. When AI categorisation gets an event wrong and I correct it, does the rule apply to recurring events with the same title, and can the approved hours be split across several clients on one invoice?
Turning calendar events into a timesheet without timers or screenshots is the right way round: people will not be watched, and the data already exists. Logging time from Telegram with "fixed login bug 2h" is a nice detail. How do you handle a meeting that covers two clients: can one event be split between projects?
As a two-person team billing partner work, the timer is exactly the part we forget. Reading the calendar read-only is a smart trust move. Question: how does it handle a block like “Partner calls” that covers three clients? Can I split one event across projects, or do I have to split it in the calendar first? Corrections that stick as rules sound like the real time-saver.
Timesheets are one of those admin tasks that should be invisible. Pulling from calendar events instead of manual tracking is genius - no more forgetting to start/stop timers. The accuracy improvement vs manual entry has to be massive. Curious how it handles overlapping events or back-to-back meetings where focus time is unclear.
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved