Features

Seventeen features. One record.

These are not modules that share a login. What somebody checks in on becomes what payroll pays, the hours they log become what a project cost, and the invoice you raise becomes the revenue that cost is set against. Follow any number far enough and you land on a person's actual day.

If you would rather see the jobs than the parts, start with the flows — enquiry to paid invoice, onboarding to exit, and daily plan to project profit.

Why one system

The join is the product.

Any of these features exists on its own elsewhere. What you cannot buy separately is the chain between them — and that chain is where every month-end reconciliation, every "which project actually made money", and every disputed deduction gets settled.

  • Attendance decides paid days Not a spreadsheet somebody retypes at month end.
  • Paid days decide the payslip Prorated from the month that actually happened.
  • The payslip is what a project cost Divided across the hours people logged to it.
  • The invoice is the revenue it is set against Recorded the moment it is issued.
  • And the leaver's laptop holds the settlement Because the register and payroll are the same system.
The company overview dashboard with profit, pipeline, capacity and what needs attention
The owner's overview. One sentence at the top, then what needs deciding.

Try all of it for thirty days

No card. Generate a full sample company in one click to see every screen with realistic data in it, then clear it and start with your own.