For teams leaving spreadsheets behind.
- Employee directory and records
- Attendance basics and leave workflows
- Admin workspace access
- Core HR structure for smaller teams
Choose the package that fits your current team size and process complexity. Final pricing can be shaped around rollout scope, support level, implementation needs, and how many workflows you want to bring online first.
The best plan is usually based on process complexity, number of reviewers, data migration needs, and how many workflows you want to bring online first.
This keeps pricing conversations practical. Instead of forcing a flat package, My HR can be matched to the rollout size and support depth your team actually needs.
Setup can include demo-ready workspace content, role mapping, portal guidance, and the first data load so the system feels alive on day one.
Public pages stay public, login paths stay separate, and operational routes remain hidden behind clean navigation and role-aware access.
Best when a team is replacing basic spreadsheets and wants one central place for employee data, attendance basics, and leave workflows.
Best when daily HR operations already need clearer approvals, payroll support coordination, reporting, and stronger process visibility.
Best when rollout needs custom workflow mapping, broader structure, staged implementation, or heavier migration support.
Teams do not need a perfect brief before reaching out. Still, quotes become more useful when a few rollout basics are already visible.
Share your team size, current pain point, approval complexity, and which part of HR needs the most improvement first. That is usually enough to begin a useful pricing discussion.
Quotes take longer when the first request does not mention branch count, approval layers, payroll-related dependencies, or whether the workspace needs custom policy behavior.
These answers help teams understand how rollout scope, support needs, and implementation depth usually affect pricing decisions.
Pricing is shaped around team size, workflow scope, setup effort, and the level of rollout support your company needs.
Yes. Many companies start with a smaller scope first, then expand into more modules or more advanced workflow support after the first rollout is stable.
Yes. Demo-ready setup, migration help, policy alignment, and custom workflow preparation can all affect the final package recommendation.
Yes. If your workspace needs policy-specific behavior, extra approval logic, or more tailored rollout preparation, that can affect the recommended package.
No. Many teams ask for pricing while they are still deciding where to start. We can recommend a smaller first rollout and leave room to expand later.
Tell us your team size, approval structure, and the part of HR that needs the most improvement first. We can recommend the best fit.
Best if your team size, branch count, or policy complexity is already roughly visible.