Integrations with tools you already use
RabbitWork browser extension: hours, cost, budget, and margin without switching apps.
Trello Time TrackingKeep cards in Trello and turn their hours into timesheets, billable value, cost, budget, and margin with the RabbitWork extension.
Chrome Extension Time TrackingLog hours on any Chrome tab with the RabbitWork extension and track timesheets, cost, budget, and margin in Rabbiit.
Rabbiit APIRead and write time entries, projects, and reports from another system. Call the API when you need the data, and use webhooks when Rabbiit should notify you.Everything the product does on one page — with real app screenshots. Scroll, see the screen, and understand the day-to-day benefit for your team.
Each person’s week sits in one grid: days across the top, projects down the side, and the total at the end. At a glance you can see who hasn’t logged anything yet, which client took up the team’s time, and which day is short. Because people see their own total while the week is still open, they fix it right away instead of trying to remember on Friday what they did on Tuesday. Whoever approves or bills starts with a complete week.
Some people start a timer when they pick up a task. Others log everything at the end of the day. Rabbiit works both ways: the timer starts with one click, and a manual entry takes a project, an activity, a duration, and a description. Both end up in the same history, so reports and invoices count hours the same way. The description is there for when the client asks what those four hours were spent on.
At the end of the week, people review what they logged and send it to their manager. From then on, both sides see the same status on the timesheet: submitted, approved, or rejected. If something is off, the week comes back with a comment saying what to fix, and the person corrects it right there. Nobody has to ask in Slack whether hours were sent, and the manager doesn’t find the gap on invoicing day.
Every week sent to you shows up in one queue, with the person, the period, and the total hours. If a number looks odd, you open the week and see the same entries as the timesheet. You can approve everything at once when it checks out, or reject just the week with a problem and leave a comment. With a large team, that saves you from opening timesheets one by one. Once approved, the week is ready to be invoiced.
On the Projects screen, each row shows the client, the budget, and a bar with how much has been used so far, in hours or in money. You see the whole portfolio at once and quickly spot the project that is getting close to its limit. The bar moves as the team logs time, so it reflects this week, not the last report someone put together. That way, the scope conversation with the client happens while there is still budget left to negotiate.
The project has a default rate, but each member can have their own. A senior can bill at one rate, a junior at another, and someone who only joins internal meetings can be non-billable on that project. Each entry is priced at the rate of the person who did the work. If a rate changes mid-contract, you choose when it takes effect, and hours that were already invoiced keep their original value.
Project activities can also be viewed as a board, with a column for each stage and a color for each column. Dragging a card changes its status, and it stays the same activity the team logs time against. So there’s no need to keep the board in one tool and time tracking in another. In a status meeting, you can see right away what has been sitting in the same column for days and who owns it.
Inside a project, work is split into activities, each with an owner and a due date. When people log time, they pick the activity, so the hours are tied to what they actually delivered. The team knows what’s theirs this week, and the manager can see where the project’s effort is going. A large activity can have subactivities, which helps break a big scope into pieces that fit into a week of work.
Each activity can have an hour estimate. As the team logs time, actual hours show up next to the estimate, and the parent activity adds up the estimates of its subactivities. That lets you notice early when part of the project is taking longer than planned. There’s still time to revisit scope, move someone to a different task, or give the client a heads-up before the gap only shows up in the month’s margin.
Each person has a work schedule on file, with the days and hours they’re expected to work. The dashboard compares that schedule with what they logged in the period. You can see who came in under, who went over, and who logged time on a holiday or during vacation. It’s a quick way to find holes in timesheets before closing the month and to notice someone who has been overloaded for several weeks in a row.
At the end of the month, contractors and freelancers get paid for the hours they worked. Once each person’s hourly cost is on their record, Rabbiit does that math for you: the summary shows one row per person, with their hours for the month and what those hours cost. You can check the amount before paying, without adding up spreadsheets or asking anyone to send their own log. If you need the detail, open the row to see which projects the hours went to. Salaried employees stay on your regular payroll.
In the detailed report, you mark the entries that have already gone out on an invoice. They then show as billed and aren’t recalculated if a rate changes later. Whatever isn’t marked is what you still need to bill. At month-end, filter a client’s unbilled entries to put together the next invoice, without billing the same hour twice or leaving one out. Finance and the project manager look at the same list, so there’s no separate sheet to reconcile.
It works like a pivot table inside Rabbiit. You pick up to five groupings, such as client, project, and person, and turn on the columns you want: hours, percentages, cost, billable amount, margin, or budget. The chart follows the table. When someone asks how much a client used last quarter, broken down by project, the answer takes a few clicks and is ready to export. Click any total to see the entries that make it up.
The detailed report lists every entry with the date, person, project, activity, duration, and description. Filters narrow it down by client, period, team, or custom field. It’s the report you send when a client wants to understand an invoice, and the one you use internally to catch time logged to the wrong project. Clicking any total in another report takes you to the lines behind that number.
This is one way to set up the summary around time alone. The chart shows total hours by client and by project, and the table separates billable from non-billable. The percentages show how much each client weighs in the month and how much each project weighs within its client. It works well in a monthly review, when the question is where the team’s time went and whether that matches what was sold.
Here the summary is about money: internal cost, billable amount, and margin side by side, with hours in the table for context. The chart makes it clear which clients carry the results and which ones take a lot of time for little margin. That makes it easier to decide where to renegotiate price, where to cut scope, and which accounts deserve more attention from sales in the coming months.
This version of the summary puts the billable amount next to its billing status. The chart separates what has already been invoiced from what is still pending, by client or by project, and the table shows the margin for each. At month-end, this is where you check that all delivered work turned into an invoice. Whatever shows as pending is what needs to go on the next one.
Teams group people who work together, such as a squad, a department, or an office. Once created, they show up as a filter in reports, so each manager can follow their own group without picking names every time. It also makes it easier to compare one area’s workload with another’s and see how each is doing. When someone changes teams, you just move them on the Teams screen.
You choose who gets reminders and how often: daily, weekly, or monthly. The email goes out automatically to anyone who logged less than their capacity for the period, and you can add your own highlighted message. The manager doesn’t have to message each person, and every reminder is recorded in the approval history. The week arrives more complete for whoever approves it.
Under Settings, the Integrations screen covers both the API and webhooks. The API management tab shows how many requests the account has made today, how many are left, and when the limit renews. The cap applies to the whole account, not to each person. Each integration uses a token created under My Tokens, with the permissions of whoever generated it, and the other system pulls time entries, projects, and reports when it needs them. On the Webhooks tab it works the other way: you register a URL, pick the events, and Rabbiit notifies that URL on its own when an entry, a project, or a client changes.
Some hours repeat every week: a fixed package a client pays for, on-call time, a cost split between departments. With automation, you create a rule that says who, on which project, how many hours, and at what time it runs. The hours show up on the timesheet by themselves, and people only adjust them when the week was different. Rules never log time in the future, and the week still goes through approval as usual.