
This explainer is for Australian operations leads, HR and facilities managers, and IT leaders who have been asked to "do what IT does" for the rest of the organisation. It covers what ESM is, how it works, how it differs from ITSM and HR service delivery, what the main platforms cost, and the signs you need it. ESM is sometimes also short for enterprise security management; this post is about enterprise service management only.
What does enterprise service management mean?
Atlassian's ESM guide defines it as "the practice of applying IT service management (ITSM) principles" to the services other departments deliver, so that business teams "handle demand as consistently as IT does". The same guide credits the analyst firm Forrester with coining the term, and quotes Forrester's definition: extending ITSM capabilities beyond technology services and managing service demand and supply "through a common platform, portal, and service catalog".
In plain terms, every internal team already provides services. HR answers leave and payroll questions, facilities fixes broken doors, legal reviews contracts, finance sets up suppliers. ESM gives each of those services a name, a request form, an owner and a target time, and puts them all behind one front door. If you are new to the IT side of this, start with our explainer on what ITSM is.
How does ESM work?
An ESM set-up has six parts, and most platforms build them the same way:
- A service catalogue and portal. One place where staff see every service on offer, by team, and raise a request. Atlassian's pricing page lists email, Microsoft Teams, Slack, an embedded widget and a portal as request channels for Jira Service Management.
- Request types and forms. Each service asks only for the details that team needs: a start date and role for a new starter, a building and floor for a maintenance fault.
- Workflows and approvals. The steps a request goes through, including who approves it, for example a manager for a purchase request.
- Queues and service levels. Requests land in the owning team's queue with a target response and resolution time.
- A knowledge base. Answers to common questions, suggested while people type, so the leave policy question never becomes a ticket.
- Automation across teams. One request creates linked tasks for several teams, which is where ESM pays off most.
The part that decides whether ESM works is the data each team's requests depend on. A service portal that can't see the HR system, the identity directory or the finance system turns into a smarter inbox, with agents retyping details between systems. This table is the integration view we use when scoping ESM for a business team:
| Team | Typical requests | Systems the requests need data from | First measure to track |
|---|---|---|---|
| HR | Policy questions, employment letters, new starters, leavers | HR information system (for example Workday), payroll, identity directory | Share of questions answered by the knowledge base |
| Facilities | Maintenance faults, building passes, desk moves, hazard reports | Building access system, asset register of sites and equipment | Time to fix, by site |
| Finance | Supplier set-up, purchase approvals, expense queries | ERP or accounts payable system, approval limits | Supplier set-ups with an independent bank-detail check |
| Legal | Contract reviews, NDAs, privacy enquiries | Contract repository, CRM for the counterparty | Contract turnaround time |
| Marketing | Creative briefs, campaign assets, event support | Project tools, digital asset management | Briefs returned for missing information |
Identity is the link between all of them. When the portal knows who the requester is, their manager and their location from Microsoft Entra ID or Okta, forms get shorter and approvals route themselves.
What is ESM used for? Five examples
- Onboarding and offboarding. Atlassian's example is a new marketing manager: without ESM the hiring manager emails HR, HR emails IT, and facilities hears separately about a desk. With ESM one request creates the tasks for every team, and offboarding reverses them on the last day.
- Facilities requests and hazard reports. Faults and hazards are logged against a site, so a recurring fault at one office shows up in the reports rather than in someone's inbox.
- Supplier set-up and bank-detail changes. A finance request type with a required approval and a call-back step is an easy control against payment-redirection fraud.
- Contract and NDA intake. Legal gets complete requests (counterparty, value, deadline) instead of "can you look at this?", and the business can see where its contract sits.
- Marketing and creative requests. For a global manufacturer's go-to-market team, our Atlassian implementation brought requests and launch work from marketing, product development and creative agencies onto Jira Work Management, Jira Service Management and Confluence, after three proof-of-concept builds in a sandbox.
How is ESM different from ITSM and HR service delivery?
ESM vs ITSM. ITSM (IT service management) is the same discipline applied to IT, and it includes practices most business teams don't need: change management for live systems, problem management for repeat incidents, and major incident response. ESM takes the parts that travel well (the portal, request types, service levels, knowledge and automation) and leaves the rest. Atlassian puts it as "ITSM plus ESM", not one or the other.
ESM vs HR service delivery (HRSD). HR service delivery is ESM for one team, often sold as its own product. ServiceNow's HR Service Delivery covers HR requests and employee journeys "from hiring to exit". The choice is between a dedicated HR product with deeper case management, and HR running on the same service platform as IT and facilities.
ESM vs shared services. A shared service centre is an operating model: one team serves several business units. ESM is the practice and tooling. A shared services team usually needs ESM, but you can adopt ESM without restructuring anyone.
Which ESM platforms are there?
Most ESM platforms began as ITSM tools, so the shortlist looks similar:
- ServiceNow. HR Service Delivery and other workflow products sit on one platform alongside its ITSM. Prices are quote-only.
- Jira Service Management (Atlassian). Atlassian's pricing page says even the Free plan includes "templates for HR, marketing, and more", and paid plans support "unlimited customers", meaning staff who raise requests don't need a licence. Our guide to enterprise service management on Jira Service Management covers rollout order, confidentiality controls and the Privacy Act.
- Freshservice (Freshworks). Its Freshservice for Business Teams offering names HR, finance, facilities and legal teams, with no ITSM implementation needed first.
- Others seen on Australian shortlists include TOPdesk, Ivanti and ManageEngine.
Great Minds is an Atlassian partner, so we implement Jira Service Management, and we connect whichever service platform you choose to the HR, finance and identity systems behind it.
What does ESM cost in Australia?
ESM platforms are priced per agent: the people who work on requests. In ESM that includes the HR advisers, facilities coordinators and legal staff who answer tickets, which is the line most first budgets miss. Staff who only raise requests are usually free. Published prices on 6 November 2026, converted at the RBA rate of US$0.7014 on 5 November 2026 (RBA), before GST:
| Platform and plan | Published price | About A$ per agent per month |
|---|---|---|
| Jira Service Management Free | US$0, up to 3 agents | 0 |
| Jira Service Management Standard | US$21.50 per agent per month | 31 |
| Jira Service Management Premium | US$55.28 per agent per month | 79 |
| Freshservice Starter | US$19 per agent per month, billed annually | 27 |
| Freshservice Growth | US$49 per agent per month, billed annually | 70 |
| Freshservice Pro | US$99 per agent per month, billed annually | 141 |
| ServiceNow HR Service Delivery | Quote only | Not published |
Jira Service Management prices are Atlassian's Service Collection pricing on monthly billing; Atlassian says annual billing saves up to 17%, and per-agent rates vary with the number of agents. Freshservice prices are from its pricing page, which does not list a separate price for Business Teams. As a worked example, a 10-person HR team added to Jira Service Management Standard is 10 × US$21.50 = US$215 a month, about A$307 before GST.
Three checks for Australian buyers
- Data residency. HR, legal and finance requests hold more personal and commercial information than most IT tickets. Atlassian's data residency includes an Australia location (the AWS Sydney region) for Jira Service Management on Standard, Premium and Enterprise plans, not Free. Ask every vendor the same question.
- Who can see what. A shared platform means HR cases and IT tickets sit side by side, so permissions need designing before HR goes live. The Privacy Act's employee records exemption has limits (job applicants and contractors are two); our Jira Service Management ESM guide sets them out.
- Billing currency. Several vendors invoice in US dollars, so exchange-rate moves flow into your budget. Our Atlassian licensing in Australia guide explains paying in AUD through a partner.
When do you need ESM?
You likely need it when two or more of these are true:
- HR, facilities or finance can't say how many requests are open or how long they take.
- A new starter's first day depends on someone remembering to email three teams.
- The same questions (leave, payslips, building access) reach HR every week.
- Requests for supplier or bank-detail changes arrive by email with no recorded approval.
- IT already runs a service desk, and other teams have asked for the same.
- Leavers keep their building passes or system access after their last day.
Start with one team whose requests are frequent and low in sensitivity, often facilities, and use it to test your portal, permissions and integrations before HR cases move across. Our guide to getting started with Jira Service Management covers the first set-up steps.
Frequently asked questions
Do business teams need a separate tool for ESM?
Not usually. Most organisations extend the service platform IT already uses, which keeps one portal and makes cross-team requests such as onboarding possible. A separate HR product makes sense when HR needs deep case management that the shared platform can't provide.
Do employees need a licence to raise requests?
On the main platforms, no. Licences are for the agents who work on requests. Jira Service Management's paid plans allow unlimited customers, its term for people who raise requests.
Is ESM only for large organisations?
No. The practices suit any organisation where several teams handle internal requests. A small organisation can start on a free or entry plan with one team and a handful of request types.
Talk to us
Extending your service desk to HR, facilities, finance or legal? Our enterprise service management practice covers service design, the platform build and the integrations with your HR, finance and identity systems, and our Jira Service Management consulting team handles the Atlassian side. More plain-English explainers in our glossary: what is ITSM and what is a CDP. Talk to us.


