Leave lives in chat messages.
A message to a team lead, forwarded to a manager, checked against a balance sheet that was last correct months ago.
CrewPacks · HR software
HR software that decides, not just stores.
CrewPacks runs attendance, leave, contracts and payroll in one system. It approves the routine requests on its own, so managers only see the ones that need a person. Built by Enegix, and used every day to run our own team.
The problem
Most HR software stores what you already knew.
Someone asked for leave. Someone was late. A contract is about to expire. A person still has to open it, read it, decide, and click.
Payroll is one person and a spreadsheet.
Copy last month's file, adjust for joiners, subtract unpaid leave. One wrong cell is somebody's rent.
Contracts take days of chasing.
Emailed, printed, signed, photographed, saved in a folder three people know about. Nobody notices the expiry date.
One system replaces all three — used by employees from their phone, run by admins from a web dashboard.
How it decides
Fixed rules decide on leave, not a language model.
Every request is checked the moment it is submitted, against the rules your company switches on.
Balance and limits
Enough balance for the leave type, inside the monthly limit, and no over-long run of consecutive days off.
Workload (optional, for teams on Jira)
Not assigned in an active sprint, and no open work in progress.
Notice and length
Submitted with enough notice, and no longer than your maximum single request.
Frequency
One request per week, unless you set it otherwise.
Every rule passes
Approved in seconds, and the approval chain is informed. Nobody has to act.
A rule fails
It goes to the next approver in your own approval chain, with the exact reason attached, not a vague “flagged for review”.
Every rule is optional and every limit is yours: switch rules on or off and set the numbers to match your policy. Emergency leave follows its own shorter path, and every decision is logged — when, for whom, which rule, which path.
Employment decisions have to be explainable and repeatable a year later. A fixed rule set can do that. A model that answers differently on Tuesday cannot.
Modules
All of it included — no module behind a surprise upgrade.
- AttendanceCheck in and out from the phone with location attached, several sessions a day, weekly summaries, HR corrections and reminders for sessions left open.
- Leave and days offRule-based automatic approval, balances per leave type, and a real approval chain when a rule fails.
- Short absencesFor the two hours at the bank: one date, one time range, the same chain — and requests expire if nobody decides in time.
- ContractsTemplates with variables filled in automatically, in-app and public signing, letterheaded PDF, attachments and expiry warnings.
- PayrollSalaries synced from contracts, monthly payroll runs, and access limited to the people who should see it.
- PayslipsGenerated from the payroll run and delivered inside the app. No email attachments.
- Bank detailsEmployees submit their own, with an approval step before anything reaches payroll.
- Company calendarWorking days, public holidays and company days off. Every other module counts against it.
- Company policyOne place for policy documents, with notifications on every update and a record of who read them.
- AnnouncementsCompany-wide or per department, delivered in the app and mirrored to Slack.
- Skills and certificationsEmployees manage their own, grouped by department, with a team-wide skills matrix.
- OnboardingChecklists with owners and dates, adjusted per role, with platform invites sent automatically.
- OffboardingThe last day handled the same way: access, handover, documents and final payroll.
- Performance reviewsReview cycles with the record behind them — attendance, activity and skills in one place.
- Employee of the MonthNominations and recognition, visible to the whole company in the app.
- Calendar and meetingsMeetings beside leave and working days, so availability is a single view.
- Developer activityOptional GitHub connection that turns real contribution into something a review can refer to.
Built around your local rules, not adapted to them.
Working days are configuration, not a constant.
Your working week, your holidays, your company days off — and every balance, report and payroll period counts against them.
Contracts that match local practice.
Your letterhead, your variables, and signing inside the app or through a secure public link.
Historical records are kept.
Employees are never hard-deleted, so payroll and contract history stays intact.
Labor-law details, built in.
Shift rosters, end-of-service indemnity, and residency and civil ID expiry alerts, alongside contracts.
Your company gets its own database.
Most platforms put every customer in one shared database and separate them with a column. CrewPacks gives each company its own — separate storage, separate sign-in, no shared tables. When a system holds salaries, national ID numbers and signed contracts, “logically separated” is not the same as separate.
Passwordless sign-in
A six-digit code to a work email on your approved domains. No passwords to leak or reuse.
Permissions enforced in the database
Not just hidden in the interface. A screen a role cannot see is data it cannot read.
Salary has its own permission
Separate from the rest of HR and off by default for everyone except the owner.
Roles are fully configurable
Start with Employee, Manager and Owner, then add your own.
Two surfaces, one system
A mobile app for every employee
iOS and Android. Check in, request leave, see the balance, read and sign the contract, open the payslip.
A web dashboard for the people who need one
Payroll, contracts, approvals, roles and permissions, reports. Dashboard access is itself a permission, so it only goes to the roles that need it.
Who it is for
- A working week that is not Monday to Friday, or your own working-day rules.
- A real approval chain, whatever shape your policy gives it.
- Payroll run by hand today, and you know it depends on one person.
- Leave, contracts and attendance still living in chat and spreadsheets.
We are the first customer
CrewPacks was built inside Enegix, for Enegix. It runs on our real payroll, our real contracts, and our real arguments about leave balances. Every rough edge was found by people who could walk over and complain about it.
Pricing
Priced per company, not per seat.
Hiring never costs you twice. We are setting prices together with our first companies instead of guessing. What is fixed is the model: a flat monthly rate for your company and your own database.
Early access pricing
For the first companies. Set up with you personally, pricing agreed together, and your feedback shapes the roadmap.
Standard
Your own database, hosted and managed by us. Every module, all employees.
Enterprise
Everything in Standard, running inside your own cloud account — your billing, your data location, your control over access.
Frequently asked questions
How does setup start?
The Enegix team sets up the first companies by hand: your database is created for you, your roles and approval chain are configured with you, and your data is moved across.
How long does setup take?
Days, not months. The slow part is your own decisions: who approves what, what counts as a working day, and how leave builds up.
What happens to our existing data?
Employees, balances and contracts are moved across during setup. History is kept.
What does CrewPacks do with payroll?
CrewPacks prepares payroll and issues payslips, ready for whoever files and pays today.
What if we outgrow CrewPacks?
Your data sits in a standard PostgreSQL database that belongs to you. Exporting it is a file, not a support ticket.
Thirty minutes, no slides.
If two of the three problems on this page describe your week, we should talk. We will run the leave engine against your actual leave policy.