Who built PeopleMuster, and who runs on it?
PeopleMuster was built by Hashlogics, a software house that runs its own people and client projects on it every working day. Attendance, leave, timesheets, the capacity plan, client projects and meeting imports all run in production there. Each module was shaped by a team living with the problem it solves.
Products built for a buyer tend to look good in a demo. Products built for daily use tend to handle the awkward Tuesday.
PeopleMuster is the second kind. Its builders run a real company on it, with real arguments about a missed punch and a late timesheet.
The origin shows in the details. Client cards show each client's local time, because offshore delivery means meeting across time zones. Projects warn when nobody has met about them in a while. The capacity grid already knows who is on leave.
The operations side came from the same place. A device register because laptops go missing. SOP checklists because offboarding steps get dropped. An internal helpdesk because HR questions were lost in chat.
Conventions are settings, not fixtures. Leave types, quotas, shifts, holidays and project health scoring are all configured per company.
The interface can even carry your own name. Our own instance runs under its own brand throughout.
Related questions
Why would a software house build HR software?
Because it needed HR and project delivery in one place, with approved leave flowing straight into the capacity plan.
Is it used in production?
Yes. Hashlogics runs attendance, leave, timesheets and client projects on it every working day.
Can the product carry our own name?
Yes. The name your team sees is configurable per customer.