What is our primary use case?
I work for management consulting and also my own label, and I work with organizations to implement it.
I have, at one point in the past when I was an end user of the tool before I went into the consulting space to work on the delivery side and installation side of the software.
What is most valuable?
There's a tool called Office Connect that leverages what I call the benefits of both worlds, where we can use the query reporting engine and the modeling engine that's in Adaptive Insights and leverage it into, like, an Excel spreadsheet. That's pretty popular with a lot of our client partners.
Also, the ability to build models to do revenue models or expense or personal planning, and bottoms-up planning. Really, having a tool for a single source of truth. So when you have a lot of typical when we think of the process where a lot of planners are involved, separate spreadsheets. And if you have a lot of people involved, then you have that. Usually, it can be a nightmare. Trying to, right, aggregate that together. So, the aggregation option of the tool is really a big plus.
What needs improvement?
In the software, there's always opportunities, and there continues to be usually, every twice a year, there's two big releases, and they've just done one now. But separately, some of the areas of opportunities for Adaptive Planning to be able to do a little bit more on performance. The high-level performance of data volume allocations is probably an area that could be improved upon.
For how long have I used the solution?
I have been using Adaptive Insights for ten years now. I use the latest version.
What do I think about the stability of the solution?
It's very stable. Its software did go down for some performance issue, but it was rectified within an hour or so, so it's quite stable.
What do I think about the scalability of the solution?
I would rate the scalability an eight out of ten. It's a Workday product; they could do a little bit better to integrate a pure-play integration with Workday, which really doesn't do that. We still have to build out the integration. So, the integration between the Workday fins and HCM is adaptive to scale on that. There needs to be some continued improvement. But since the integration or acquisition of Workday of Adaptive Planning, the product has grown by leaps and bounds, and certainly, scalability improvement is the one area that has gone better.
There are around 170 end users using this solution.
How are customer service and support?
The support capabilities that streamline have gotten better, thanks to what's called Workday Community. It provides a great tool for voicing your issues before resorting to opening a support case. Many times, you can find answers to your questions there. However, in instances where I've had to, usually during a deployment, it's been about four or five times that I'll click through some support cases. Once the product goes live, such occurrences may happen occasionally, but it's not too frequent.
Workday wants you to verify that you've opened up or you've sent your question your support question. You post the support data community first.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I used Oracle Hyperion. It was too complex, and too costly, to have to maintain it. Adaptive planning was truly a tool that the finance team could own and operate, which is pretty historic. So, that is why we switched to this solution.
How was the initial setup?
The complexity of the initial setup depends. This means a lot of it is finances, is never the same for every organization. So, if it's more typical use cases, generally, the setup is a cloud-based tool. It is fairly straightforward. That's the whole idea behind it once your implementation partner helps you to configure, but you want to be doing that knowledge to KT throughout the way because, eventually, in the end, the finance function usually owns the software. So, it is with an asterisk because it does depend. Like, if you're, it depends. A large-scale enterprise company, and you're gonna bring a lot of heavy complexity. So, if it's within the typical parameters.
What about the implementation team?
The deployment is typically between 12 to 18 weeks. That's for the more typical. If it's a larger enterprise, some, some I've worked on, and it's standard over a year. But generally, no more than a year.
What's my experience with pricing, setup cost, and licensing?
Pricing is in line with other cloud-based EPM tools. It is a subscription-based model based upon the number of users and site type if it's an admin or end-user type thing. Compared to some of its competitors, like OneStream, Adaptive is very competitively priced.
What other advice do I have?
Overall, I would rate the solution a seven out of ten. What keeps Adaptive strong that others and some other APM tools lack is the fact that it's sort of connected to Workday. So that's very popular for people when they buy Workday, which is an amazing product on its own for fins and HCM. It is important for many organizations like to have the full suite of tools, not necessarily a best-of-breed approach. So that keeps it pretty strong in popularity.
I would advise you to crawl-walk-run because it's a very modular type of product. So once you get your key foundational elements together, meaning understanding of what you choose to plan on, then you can really create your financial data model structure, meaning you can build out your call centers and your DOL accounts and your work tags. And get that right solid. Be very clear on how you plan if you plan at the division or at the cost center.
Have clarity around key reports first. And do a very solid requirements gathering for the plan, lay that all out, and then don't start building right away. You'll load your foundational elements. Again, your call center structure, your accounts, and load some data.
But then do prototypes, meaning build out small models, get a sense of how it works, and pressure test at first. Then, it's just jumping right in and doing things because it gets a little harder to unpack things if you've invested time developing something without thinking through how the entire planning model will look and the reporting model.
I've done this for quite a long period of time. I've actually had my own consultancy focused on, what a lot of the pitfalls I've seen in. While it's a great tool. There are two components of it. It's the software, but it's probably just as important as how you implement it. How do you manage the project? How do you ensure that an organization can be able to own the project once you step away? That's probably just as important, too.