Launch
Stintt
Visit
Example Image

Stintt

Your calendar writes your timesheet. No timers, no agent.

Visit

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.

Example Image
Example Image
Example Image
Example Image
Example Image
Example Image

Features

  • Automatic timesheets: Reads your calendar read-only and turns the events into timesheet entries. No timers, no screenshots, no desktop agent.
  • AI categorisation: Sorts every event into meetings, focus, admin, breaks and time off, by client and project. Correct one and the rule sticks.
  • Approvals: Logged time lands in one workspace inbox. Managers approve, edit and approve, or send it back with a note. Auto-approve when review is overkill.
  • Invoicing from approved hours: Roll approved time into invoice line items, apply the tax treatment and export a PDF. Modern and India GST templates included.
  • Log time from chat: Telegram, Google Chat and in-app chat. Send "fixed login bug 2h" and it is logged. Ask "hours on Acme this week?" and it answers.
  • Exports and templates: Excel, CSV and PDF with six ready templates: Standard, Detailed, Daily, Client Billing, Simple and Grid.


Use Cases

  • Agencies billing by the hour: Turn the week's calendar into approved hours and an invoice line a client will accept, without rebuilding Friday from memory.
  • Consultants and freelancers: Get a finished, exportable timesheet per client from the meetings and focus blocks already on your calendar.
  • Managers chasing timesheets: Timezone-aware reminders before a sheet is late, and one inbox to approve or send back the week.
  • Teams that will not be watched: Automatic capture from read-only calendar access. No screenshots, no keystroke logging, nothing installed on anyone's laptop.
  • Capacity planning: See utilization, meeting load, focus time and capacity before the next sprint. Team views aggregate by default.


Comments

Reading the calendar read-only is a reassuring choice. How does the AI categorisation handle recurring events that are sometimes client work and sometimes internal, such as a weekly sync?

How does the AI categorisation handle calendar events with vague titles like "Catch up" or "Sync"? Does it ask you to confirm the client or project, or does it guess and let you correct it afterwards?

The read-only calendar angle is neat. For people who bill clients, how does it deal with back-to-back meetings that overrun, since the calendar end time rarely matches reality?

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?

custom-img
Small, focused tools for small businesse...

Building timesheets from read-only calendar access instead of timers or screenshots is a thoughtful tradeoff for teams that don't want to feel watched. How does the AI handle events that are ambiguous, like a generic "Sync" meeting that could belong to several clients?

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.

custom-img
Buiding with AI

Love it! Congrats on the launch.

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.

The read-only calendar angle is neat. For people who bill clients, how does it deal with back-to-back meetings that overrun, since the calendar end time rarely matches reality?

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?

custom-img
POSTIVA Founder

How do you handle changes to a calendar event after its week has been approved? Keeping approved billable hours frozen, while flagging the later calendar change for review, would help avoid an invoice changing unexpectedly.

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?

The approval-to-invoice flow looks useful for small agencies. When a manager adjusts an auto-generated entry, does the exported invoice retain a link to the calendar event or an edit history? That would help resolve billing questions later.

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.

custom-img
I build & lead the engineering behind AI...

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.

How is Stintt priced as a team grows? Harvest moved to charging for projects, clients and invoices this summer, and a lot of small agencies started looking around. A flat price that doesn't climb with every client you add would be a strong reason to switch.

Premium Products
Social Links

Comments

Reading the calendar read-only is a reassuring choice. How does the AI categorisation handle recurring events that are sometimes client work and sometimes internal, such as a weekly sync?

How does the AI categorisation handle calendar events with vague titles like "Catch up" or "Sync"? Does it ask you to confirm the client or project, or does it guess and let you correct it afterwards?

The read-only calendar angle is neat. For people who bill clients, how does it deal with back-to-back meetings that overrun, since the calendar end time rarely matches reality?

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?

custom-img
Small, focused tools for small businesse...

Building timesheets from read-only calendar access instead of timers or screenshots is a thoughtful tradeoff for teams that don't want to feel watched. How does the AI handle events that are ambiguous, like a generic "Sync" meeting that could belong to several clients?

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.

custom-img
Buiding with AI

Love it! Congrats on the launch.

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.

The read-only calendar angle is neat. For people who bill clients, how does it deal with back-to-back meetings that overrun, since the calendar end time rarely matches reality?

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?

custom-img
POSTIVA Founder

How do you handle changes to a calendar event after its week has been approved? Keeping approved billable hours frozen, while flagging the later calendar change for review, would help avoid an invoice changing unexpectedly.

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?

The approval-to-invoice flow looks useful for small agencies. When a manager adjusts an auto-generated entry, does the exported invoice retain a link to the calendar event or an edit history? That would help resolve billing questions later.

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.

custom-img
I build & lead the engineering behind AI...

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.

How is Stintt priced as a team grows? Harvest moved to charging for projects, clients and invoices this summer, and a lot of small agencies started looking around. A flat price that doesn't climb with every client you add would be a strong reason to switch.

Premium Products