Work · Service desk · CRM · Invoicing · HR and payroll
One system for the work, the people and the money.
Most companies run projects in one tool, the service desk in another, the CRM in a third, invoices in a fourth and HR in a spreadsheet — then spend every month reconciling them. Ergira is one database, so a sprint’s capacity already knows who is on leave, an hour’s cost comes from what that person is actually paid, and an invoice posts itself to a real ledger.
The free plan is the whole product at a smaller scale. No card, no time limit, and nothing switched off.
Five things only one database can do
These are not integrations. They are queries — which is why no amount of connecting two products produces them.
Capacity from real absence
A sprint's capacity is scheduled hours minus public holidays minus approved leave, per person, as of its start date. Not a number somebody maintains by hand, and not an estimate — a fact, resolved from the leave ledger and the holiday calendars that are already there.
An hour's cost, derived
Every other tool asks you to type a cost rate, which goes stale at the first pay rise and then sits under every margin figure it produces. Here the base comes from effective-dated pay, the working pattern, the composed holiday calendars and the leave entitlement. You choose the overhead loading; the rest moves on its own.
A booking page that sees the diary
Approved leave and public holidays are gone from a client's booking page on the next read, with no sync step and no calendar integration to break. A standalone scheduler cannot do it: its business calendar is a list somebody typed once and will not maintain.
Work, tickets and money that reconcile
An hour recorded against a work item, a desk ticket or nothing at all becomes a charge with a client and a value. It draws down the client's contract, reaches an invoice, and the invoice posts itself to a double-entry ledger. One figure, not four systems disagreeing.
Several companies, one workspace
A holding company and its subsidiaries are separate employers with separate payrolls, separate numbering and separate filings — and one set of people moving between them. Each entity keeps its own books and its own rules; the group consolidates in a query. Most tools make you buy a second subscription and reconcile by hand.
Everything, on every plan
There is no feature-gating between tiers. Plans differ by how many legal entities you run and how many people may have a login — never by what works.
People and HR
- Records for everybody, whether or not they sign in
- Effective-dated engagements, pay and allowances
- Right to work, permits, dependants and credentials
- Onboarding and offboarding checklists
- Performance cycles, goals and peer feedback
Leave and attendance
- Policies that differ by jurisdiction as data, not code
- An insert-only ledger — corrections reverse, never edit
- Approval chains, delegation and escalation
- Overtime rules, including daily and seventh-day tiers
- Public holidays that compose: federal, state and company
Payroll
- Gross to net, per jurisdiction
- Employer and employee contributions
- Payslips, and an immutable snapshot per period
- Leave paid at the right band, from the ledger
- Retro corrections as deltas, never rewrites
Work management
- One backlog across every project, and sprints to match
- Board, list, table, calendar and timeline on one view spec
- Initiatives, milestones and a roadmap that draws only what it knows
- Burndown, cumulative flow, cycle time and workload
- Automation that cannot trigger itself
Service desk
- SLA clocks derived from an event log, on business hours
- Email at a support address, live chat and a customer portal
- A help centre published from your own document store
- Leave-aware assignment and satisfaction scoring
- Ticket merging that moves the conversation, not the clock
CRM
- Contacts, companies and deals — and deliberately no Lead
- Proposals on the same engine as employment contracts
- Hosted forms, booking links and click-to-dial
- Consent as a record with the wording that was shown
- Two-way sync with HubSpot
Invoicing and payment
- Sales invoices and bills in one model, gapless numbering
- Tax rates resolved most-specific-first, never guessed
- Pay online by card, and save a card for next time
- Reminders that stop after three, and recurring invoices
- Bills captured from a mailbox as drafts
Accounting
- Double-entry, with the invariants in the database
- Bank feeds, camt.053, MT940 and CSV
- Statements, year-end close, budgets and consolidation
- Fixed assets with a schedule an accountant can reproduce
- Filed into Xero or Zoho Books, if that is where the books are
Professional services
- Contracts with allowances: hours, money, tickets or unlimited
- A drawdown ledger, so what is left is always explainable
- Delivered, charged and cost — and the margin between them
- What the arrangement gave away, named rather than lost
- Rates scoped by client, project or person, and dated
Some things we deliberately do not do
A list of what a product will not do is more useful than another list of what it will.
We do not write your knowledge articles
You already have somewhere documents are written, reviewed and permissioned. What you do not have is a public help centre a customer can find. Authoring stays yours; publishing is ours.
We do not guess at a price or a rate
A tax rate scoped to another country, a billing rate agreed with another client, an exchange rate from a market feed — none is used as a fallback. Where nothing matches, nothing is suggested, because a plausible wrong number is the one that gets invoiced and then argued about.
We do not delete your records over a billing state
Downgrade and everything above the new limits becomes read-only. Nothing is removed. A system holding employment records cannot erase them because a card expired.
We do not keep call recordings or transcripts
They stay in your own telephony account. A transcript is the same personal data in a more exposing form, and holding a copy would quietly undo the decision that put the recording there.
Start on the free plan
One legal entity, five people, and every module. No card, no trial clock, and nothing that stops working after a fortnight.