NEWFreshservice is now a Ploy integrationSee what shipped
1.0ITSM SCAN

Understand where your IT team’s time goes

We read twelve months of access requests from your service desk — what people asked for, who approved it, how long they waited. You get a costed picture of where the time goes, and how much of it Ploy gives back on day one.

Read-onlyConnected in minutesThe report is yours either way

ITSM scanREAD-ONLY12 MONTHSREADINGConnected 4 minutes ago · no agent, no write access
Your service desk
Salesforce access for new AESD-4471 · Raised 2 min ago
Add me to #deals-emeaSD-4468 · Waiting on approver
Access to Mailbox-salesINC-8830 · Reassigned twice
New starter — joins MondaySD-4462 · 11 systems to set up
Data warehouse read accessSD-4455 · Open 3 days
GitHub — payments repoSD-4450 · Needs tool owner
Leaver — offboard todaySD-4444 · Escalated
Something else: ConfluenceSD-4439 · Free-text request
Salesforce access for new AESD-4471 · Raised 2 min ago
Add me to #deals-emeaSD-4468 · Waiting on approver
Access to Mailbox-salesINC-8830 · Reassigned twice
New starter — joins MondaySD-4462 · 11 systems to set up
Data warehouse read accessSD-4455 · Open 3 days
GitHub — payments repoSD-4450 · Needs tool owner
Leaver — offboard todaySD-4444 · Escalated
Something else: ConfluenceSD-4439 · Free-text request
1,284 read2,910 read4,420 readLUNA · CLASSIFYING
What comes back
4,420ticketsread and classified across 25 request types
68%fully automatable from day oneDAY 1
9 minof IT effort per request, gone
13.9d→ under 1dmedian wait for a new starter
£174ka yearrecovered across effort and waitingROI
1.1CONNECT

Minutes to connect. Nothing to install.

The scan reads your service desk. It does not touch it. No agent, no write access, no change to a single queue or workflow — and you can revoke it the moment the report lands.

01~5 MINUTES

Connect

Authorise Ploy against your service desk. Read-only OAuth, no agent to deploy, and nothing changes about how your tickets flow today.

02RUNS OVERNIGHT

Read

Luna pulls twelve months of tickets and classifies every one — request type, system, who asked, who approved, who provisioned it, how long it took.

03WITHIN 48 HOURS

Report

You get the analysis back and we walk you through it. Volume, automatable share, wait times, and what the whole thing is costing you.

Three steps, and you are only involved in the first one

Most teams are done with their part before the meeting they booked to discuss it has finished.

Jira Service ManagementZendeskFreshserviceSIIT

Whichever desk you run

If your requests live somewhere else, tell us — the scan reads tickets, and a new desk is a connector rather than a rebuild.

tickets:readticket_fields:readusers:readtickets:writeadmin

Read-only, and only the tickets

Ploy reads ticket metadata and text. It does not read attachments, it does not need admin, and it never writes back.

1.2WHAT COMES BACK

Your access requests, finally counted

Every scan answers the same four questions: how much of this is there, when does it land, how long are people waiting, and how much of it can go away. Here is what that looks like.

Access request analysisLAST 12 MONTHSALL DESKSALL TEAMSEXAMPLE SCAN
REQUESTS RAISED
4,420in 12 months+73%
MEDIAN TIME TO ACCESS
22hrs+18%
IT EFFORT
2.9FTE a year+0.9

Requests per month

The final month is shown to date, with the rest of it forecast in the lighter cap. Up 73% across the year, and on track for roughly 700 a month by December.

AVG 368
AugSepOctNovDecJanFebMarAprMayJunJul

Automatable from day one

Every request type cross-referenced against your identity provider and the systems Ploy already connects to.

68%DAY ONE
Automatable3,006Needs a human1,414

When the requests land

Every access request of the last twelve months, by weekday and hour raised. Hover a cell for its count.

MONDAY IS 24% OF THE WEEK’S VOLUME
000102030405060708091011121314151617181920212223
Mon
Tue
Wed
Thu
Fri
Sat
Sun
QUIETBUSYPEAK · MON 09:00 · 106 REQUESTS

What to automate first

Each request type by how often it lands and how long people wait for it. Bubble size is the IT effort it costs a year; filled bubbles are types Ploy provisions directly.

8 hrs1 day3 days14 days
AUTOMATE FIRSTSFUNMBNSDWJRLVSLCCGH
0REQUESTS PER MONTH →
IN THE ZONE6 request types, about 2,808 tickets and 1,336 hours of IT time a year. Ploy provisions every one of them directly.

Behind the catch-all queue

The free-text queue is usually the second largest request type on the desk, and the one nobody has ever broken down.

Remote desktop and jump hosts11.3%
Claude8.5%
SharePoint and OneDrive6.2%
Cloud console and key vault4.5%
GitHub, including Copilot4.2%
Confluence3.4%
Mailbox-sales3%
Developer tooling1.8%

A sixth of the volume arrives as free text, which is why it has never been reportable. Naming what is actually in there is usually the first thing a team changes — most of this list becomes a catalogue item people request themselves.

Every request type, ranked

REQUEST TYPE12-MONTH TRENDCOUNTMEDIAN WAITPLOY
Salesforce access request7368 hrsFULL
Something else (unlisted)71024 hrsPARTIAL
Mailbox-sales and shared mailboxes62322 hrsFULL
New starter (from the HRIS)41813.9 daysFULL
Data warehouse access4113.7 daysFULL
Jira access and amendments3623.6 daysPARTIAL
Leaver (from the HRIS)2882.4 daysFULL
Slack channel or group26212 hrsFULL
Cloud console access497.9 daysNONE

The figures on this page are an illustrative profile, not a customer’s and not an average. Your scan reports your own numbers, whatever they turn out to be — and we present them as we find them, including where they are less dramatic than your team expected.

1.3WHAT LUNA LEARNS

The scan does not just count your tickets. It reads them.

Twelve months of access requests are the only honest record of how your organisation really grants access — who asked, who approved, who provisioned, and what they got. That record is what Luna learns from, which is why she starts useful rather than starting empty.

Maya OseiSalesforce92%Dan WhitmoreSlack81%Nadia KhanMailbox-sales76%

Who actually approves

Not the approver named in the workflow — the one whose reply unblocks the ticket. Luna learns the real path from twelve months of who said yes.

SalesforceRevenue OpsHIGHSlackITHIGHSnowflakeDataINFERRED

Who owns each tool

Ownership is rarely written down anywhere true. It is inferred from who answers for a system, who provisions it, and who gets escalated to.

“SALESFORCE ACCESS” RESOLVES TOAccount ExecutiveSales User · StandardSales Ops AnalystSales User · Reports AdminSales EngineerSales User · Read Only

What the access actually is

“Salesforce access” means one thing for an account executive and another for a sales ops analyst. The tickets say which, and for whom.

IT EFFORT, BY WHAT IT WAS SPENT ON
Provisioning52%Approvals31%Deprovisioning17%

Where the time goes

Split across approving, provisioning and taking access away again. Deprovisioning is the smallest share and the one most often skipped.

Run the scan and none of this has to be gathered twice. If you go on to deploy Ploy, Luna already knows your approvers, your owners and what your access requests mean.

1.4THE NUMBER

What it is costing you, with the working shown

Two things drive the return. The effort your team spends fulfilling requests, and the time everybody else spends waiting on them. The second is almost always the larger of the two, and almost never counted.

WHERE THE COST SITS
Conservative10 min per request · 1 hr per joiner · volume flat
Current trajectory15 min per request · 90 min per joiner · volume still climbing
IT effortTime your team spends fulfilling requests
£27,5000.55 FTE
£48,7500.98 FTE
Time spent waitingRequesters idle while access is provisioned
£115,0002.3 FTE
£125,0002.5 FTE
Total, per year
£142,5002.85 FTE
£173,7503.48 FTE

Held constant: Ploy cuts time-to-access by 80%, productivity drops by only 10% while someone waits, and a salaried employee costs the business around £50,000 a year all in. Every one of those is set low on purpose.

NOT IN THE TOTAL
  • The time approvers spend, which the scan measures but the total ignores
  • Reduced exposure from access that expires instead of accumulating
  • Reduced exposure from leavers being fully cut off on the day they leave
4,420

access request tickets read in a typical twelve-month scan

68%

of them fully automatable from the first day Ploy is live

13.9 → <1

days for a new starter to have everything they need

1.5WHY RUN ONE

The worst case is that you learn what your tickets say

You do not have to be buying anything to want this. Access requests are the most measured-and-never-analysed thing most IT teams own, and the data is already sitting in your service desk.

01

You have never actually counted

Almost nobody has. Everyone knows access requests are a drain; very few teams can say how many, of what, or how long people wait. The scan turns a feeling into a figure you can take to a budget conversation.

02

You find out before you buy anything

The automatable share is measured against your real tickets, not modelled from a benchmark. If it comes back lower than you hoped, you have learned that for the price of an OAuth grant.

03

The report is useful on its own

It is a costed picture of how access works in your organisation, and it is yours whatever you decide next. Plenty of what it surfaces — a catch-all queue doing a sixth of the volume, a request type nobody owns — is worth acting on before you change any tooling at all.

04

It costs you an hour

Five minutes to connect, and the walkthrough when it lands. Read-only throughout, revocable at any point, and no change to the way your service desk runs.

Avantia Law
Ploy has transformed how we do access requests & we wouldn't be able to go back to the way it was.
Peter F.Head of IT & Infosec, Avantia Law
Read the story
Liberis
Ploy has enabled us to completely automate employee onboarding and offboarding, saving us 150 manual actions, clicks, and hours of time per employee.
Paul HartHead of IT, Liberis
Welcome to the Jungle
With Ploy, we've turned a tedious weekly task into easy automated flows. We're saving half a day a week and have completely streamlined onboarding across all our SaaS tools. Total game changer.
Devon BrownSenior IT Engineer, Welcome to the Jungle
Luno
Ploy saved me from drowning in spreadsheets, manual licence assignment and SaaS sprawl. It lets us easily make sense of what's being bought, used, and wasted which is more than I can say for most software tools. The best part? They listen, iterate fast, and don't take themselves too seriously. Perfect match.
Simon FishleyGlobal IT Director, Luno
Read the story

Find out what your tickets say

Book a scan and we will connect to your service desk, read twelve months of access requests, and walk you through what they cost. The report is yours either way.