In Practise Logo
In Practise Logo - Blue
In Practise Logo
IP Interview
Published June 3, 2026Conducted May 12, 2026

Workday Customer Case Study: Flex Credits & HR Operations Automation

Executive Bio

Executive Profile Hidden

Summary

Subscribe to access hundreds of interviews and primary research

Or contact sales for full access

Interview Transcript

Disclaimer: This interview is for informational purposes only and should not be relied upon as a basis for investment decisions. In Practise is an independent publisher and all opinions expressed by guests are solely their own opinions and do not reflect the opinion of In Practise.

This is a snippet of the transcript.to get full access.

Why weren't the others selected?

SuccessFactors is pretty awful if you are not using SAP. That is the only reason in my mind to buy SuccessFactors. If you are using SAP, you can make an argument that SuccessFactors is good. It is the same argument I make when we talk about Workday Recruiting versus Greenhouse or some other recruiting platform. Is the "good enough" quality of the application, combined with the fact that it is seamlessly connected to the broader platform, enough to make it competitive against a tool that is best in class at that specific function? For a lot of SAP customers, SuccessFactors is good enough. I was at AutoZone when they made the decision to go to Oracle Fusion instead of Workday, and I know how Oracle did a lot of those deals to get that business. It is not a good platform. At the end of the day, it is still an Oracle tool.

This is a snippet of the transcript.to get full access.

I have spoken to some customers that were probably much larger, but they were actually building on top. They were bypassing some of the agents that Workday has and building their own tool. Building what Workday is actually building with the agents, but building it themselves with API.

I think that is why Workday is doing it, because they don't want people just building their own. I think it makes sense. The 5.2 million API calls per year, I don't think that is an unreasonable number. I think historically, because Workday has never cared about how many calls you were making or how many integrations you were running, we have just said run it every five minutes and walked away. But now we are being more intentional about how we do those. What is really interesting about that is it is going to be interesting to see what that does from a resource consumption perspective on Workday's side. Every one of those API calls takes resources on shared tenants, and there is a distinct cost assigned to that. I wouldn't be surprised to see that resource cost going down as more people start to say, maybe I don't need to run this integration every five minutes. Maybe I can run it every two hours. If you are running an API every five minutes, that is 300,000 calls per year. I know that math very clearly because I have done it multiple times.

This is a snippet of the transcript.to get full access.

Free Sample of 50+ Interviews

Sign up to test our content quality with a free sample of 50+ interviews.

Or contact sales for full access

© 2026 In Practise. All rights reserved. This material is for informational purposes only and should not be considered as investment advice.