Questions we get asked.

Firms that sell people's time and expertise: consultancies, agencies, software houses, studios and professional services teams. It fits best from about ten people, when the spreadsheet stops scaling, up to a few hundred.

Usually a timesheet tool, a planning spreadsheet, a folder of proposals that hold the budgets, and the workbook somebody builds at month-end to make them agree. It does not replace your accounts package; it feeds it.

No. Bitmap does not hold tasks, tickets or sprints. It holds the commercial shape of the work — budgets, people, time and money — and connects to Jira for the delivery detail where you want it.

No. Bitmap runs the part between delivery and the ledger: what can be invoiced, when, for how much, and what has been paid for but not yet delivered. The invoice itself lives in Xero or wherever you raise it.

A project carries budgets. The planner books people onto a budget; people log time against it; a payment schedule is priced from it; an invoice is raised from the schedule. Every report reads those same records, which is why the numbers agree.

The timesheet wins for the past and the plan for the future. When a person logs time on a day the planner had booked, the planned block gives way to the logged one, so nothing is counted twice.

From a fact table with one row per person per day: hours logged, billable and non-billable, leave, expected hours and the job role at the time. It updates as timesheets change, so the month is right on the first rather than the fifteenth.

The value of work you have invoiced but not yet delivered. Per project, Bitmap takes revenue recognised, converts it to time at the budgeted day rate, subtracts time used and planned, and values the balance. You can ask for it at any date.

Slack for notifications, Jira for estimates and work logs, and Xero for invoicing. Each is switched on per company from the integration settings. Everything else reaches Bitmap through its API.

You create a custom connection in Xero and enter its details in Bitmap. Bitmap then raises draft invoices in Xero against the right contact and account codes, and Xero tells Bitmap through a webhook when each is approved, paid, voided or deleted.

Yes. Everything the screens do is a JSON API behind the same login, with OAuth 2.0 scopes that mirror the permissions. The Google Slides add-on that puts live Bitmap charts in a board pack is built on it.

A person holds roles and a role is a set of permissions. A project manager sees their projects, an approver sees their people's timesheets, finance sees the invoices, and a platform admin sees the settings. Every screen and API call asks for a permission.

Yes. A contractor logs time and sees their own plan, and no more. Their day rate goes on the rate card like anybody else's, so budgets and utilisation count them correctly.

In Slack or by email, as each person chooses. Company events, such as an invoice being paid or a contract coming up for notice, post to a channel you pick. Overdue timesheets are chased in a conversation with the person and their approver.

Sign up and you get an empty company and a sign-in for yourself. Add clients, projects and people, or invite the team. Nothing is charged during the trial.

Clients, projects, budgets and staff can be entered by hand or created through the API. Talk to us about a larger migration; we have done it for ourselves.

In the United Kingdom, on infrastructure operated by The Curve, with nightly backups. Your company's data is separate from every other company's.

Bitmap is sold as a subscription. Start a free trial, and talk to us about pricing for the size of your team.