What Ergira is

Ergira is a work-management product with an HR system at its core and a CRM beside them. All three share one database, which is the point: sprint capacity is scheduled hours minus public holidays minus approved leave per person, and a client picking a slot on a colleague's booking page is never offered a day that colleague is on leave. Neither question can be answered by separate products talking over an integration.

Who it is for

Organisations of ten to a few hundred people who employ across more than one country — agencies, software companies, groups with a holding entity and operating subsidiaries. The design assumes several legal entities and several jurisdictions from the beginning rather than treating them as an enterprise upgrade.

Three decisions that shape everything else

Sprints and backlog order are organisation-wide

An agency runs one cadence across many client projects. A sprint collects work from any project, and the project board is the organisation board with one filter applied. This is why the backlog interleaves projects into a single order.

HR lives beside the work

Leave, engagements, working patterns and holidays are in the same database as the issues and sprints. Capacity, absence cover and cost per project all fall out of that rather than being estimated.

The customers are there too

Contacts, companies and deals sit beside the delivery work rather than in a separate system, so the client on a project is the client in the pipeline. It is also why a booking page can skip the days its host is away — the leave is a join rather than another vendor's database.

What it deliberately is not

Ergira records what somebody is entitled to. It does not calculate or file payroll, adjudicate insurance claims, or run recruitment. On the customer side it is a CRM and not a marketing platform: no bulk sending, no landing pages, no ad management. Those boundaries are described in Payroll handoff and what is not built, and they are architectural rather than a matter of time.