Video: Pre-deal modeling best practices and GTN impact | Duration: 5412s | Summary: Pre-deal modeling best practices and GTN impact | Chapters: Welcome and Introduction (30.08s), Anaplan Overview (270.2s), Anaplan Platform Overview (413.89s), Pre-Deal vs Gross-Net (624.89s), Design Themes (775.63s), Pre-Deal Solution Capabilities (937.85s), Solution Capabilities Overview (1076.66s), Model Walkthrough (1249.89s), Closing the Loop (1833.13s), Q&A Session (2070.17s), Q&A and Closing (2258.18s)
Transcript for "Pre-deal modeling best practices and GTN impact":
Hi, everyone. Thanks for joining. We're gonna get started in just a minute. Alright. Looks like we've got a good group of people, so we can get started. Welcome, everybody. Thank you so much for joining today's pre deal webinar co hosted by Anaplan and Argano. Just wanna give a quick housekeeping note before we started. We are recording today's session, and we will send the recording to everybody that registered after the event. So if you need to step away or if you wanna send this and share it with anybody that you work with, we've got you covered. So I'm gonna quickly run through today's agenda, and we'll do a quick round of introductions for everybody. And then we'll dive right in. So for today's session, we're gonna start by talking about the technology shift and why customers are moving away from Excel and into enterprise performance management tools like Anaplan. And then we're gonna talk about the connection between pre deal modeling and gross to net forecasting. We'll also touch on some best practices that we're seeing in the space around pre deal modeling. We'll do a live demonstration of what a pre deal model could look like in Anaplan, and then we'll close the loop between pre deal and post deal monitoring and why it's so important to have that closed loop. And then we'll finish the session off with some q and a. So if anybody does have questions, please feel free to put them in the chat. I'm gonna try to monitor the questions as they come in, but we will definitely have time at the end to go through q and a. So for those of you who don't know me, I'm Tara, and I lead the life science strategy here at Anaplan. I've spent the last nine years with Anaplan's life science customers really around the area of, commercial and market access finance. So I'm super excited to be here today, and I am joined by Nikolai, who's a senior solutions consultant at Anaplan. Nikolai has both Anaplan and pharma industry expertise. And then we are also joined by John, who's a principal consultant at Argano. John has over a decade's worth of experience in the pharma industry and pre deal modeling. And then we are also joined by Nico, who's a senior consultant at Argano. Nico has worked with many of Anaplan's life science customers and has a tremendous amount of Anaplan expertise. So I'm excited about everybody that we have today, and I'm actually gonna pass it off to Nikolai to talk about that technology shift. Great. Thank you so much, Tara. Really, so at a glance, Excel got us here and it's earned its place, but the way we forecast moving forward, can can show improvements. Right? So instead of looking at this for workbooks, trying to aggregate data, layer on analog events, etcetera, and then track down your figures, what we can do is actually create a full blown library. And we'll get into some of the nuances when we get into the demonstration later. Alright. Now I know we have a large, large audience here, so we wanted to level set a little bit and share, share a little bit more about Anaplan as a whole and who we are as an organization. So we really are the market leading in forecast and scenario analysis. This slide really speaks for itself with some of our items here, whether it be our 2,800 plus customers, more than half of the Fortune 50 are using us at this point, million plus models deployed. What I wanna draw your attention to is really the $500,000,000 in AI product investment. So at the core, AI is ingrained within Anaplan, whether it's our analyst where our, deterministic versus probabilistic approach where under... Your underlying models can get reference and you know exactly why figures are changing, give recommendations to your deals as you're going to market with them or expanding your your models that are already in place. When we think about legislation changes and maybe, certain agreements that are in place now that are gonna change a year from now, the ability to extend and expand your existing footprint to forecast your, your current and future needs. Tara, next slide, please. One more slide for me. So, Anaplan really is the enterprise enterprise life science leader in pharma, biopharma, and med device. And we wanted to flash this up here, again, because of the audience that we have. Some of you are probably very familiar with our existing logos, and some not not so much. So as Tara mentioned, while while we're focusing on the commercial space today as it relates to pre deal and the connection within GTN, our footprint is is also much larger than that as we think about more traditional FP and a use cases, workforce planning, etcetera. Just to high... Highlight as well, more than 75% of the top 20 life sciences companies trust Anaplan with their day to day forecasting activities and making the decisions on our platform. So for those of you who aren't super familiar with Anaplan, you can think of Anaplan as your planning and forecasting layer that's sitting on top of your executional and transactional data systems. And what you see on this slide is showing how Anaplan's planning capabilities can really be utilized across the entire life science enterprise. So at the top, you'll see strategic planning, and that's gonna be your long range financial planning, portfolio planning, strategic workforce planning. And then in the middle, you move into your enterprise planning. That's your FP and A, your r and d and clinical trials, your operational workforce planning. And then at the bottom is your market access and operations. And this is really where the plan meets the market. So you've got your demand planning, feeding into your commercial planning, your supply planning, and then the two areas that we're here to talk about today. Your pre deal modeling and your gross to net forecasting. And the important thing to note about this slide are the connectors. So nothing is sitting on an island. You can have your pipeline assumptions, your volume expectations, pricing decisions flow across these different layers so that you're working from one set of shared assumptions instead of planning in disconnected Excel spreadsheets. And what I want you to notice is that pre deal modeling and gross to net sit next to each other and they're linked. So the deals that you are modeling before you sign are actually driving that revenue that you're forecasting after, and that connection is really what today is all about. But before we get there, I wanna talk about the planning process. See what's underneath those planning processes, and that's really your data. So on the left hand side, we're bringing data in from your transactional systems, your ERP, your revenue management. That's getting brought into Anaplan. So in the center is the platform itself, and there are many different up... Areas of the platform that you can utilize. And so at the top, we have some of our applications. We've got finance applications, supply chain, sales and marketing, HR. We also just launched a gross to net application this week. So I'm super excited about that. And then we have AI infused throughout the platform. So, Nicole, I talked a little bit about that, and I think we'll talk a little bit more about that later in the presentation and how that actually applies to gross to net and pre deal modeling. And then you have your modeling engine, your workflow, your reporting and UI, and of course, security and administration at every single level of the platform. And then lastly, the platform has your data that's being stored and processed and used across multiple planning functions. And so that's what you're seeing on the right hand side. We talked about other ones but even then that's just a small fraction of the planning and forecasting that you can do within the system. And the important thing to note, especially for gross to net and credo modeling, is that it's being run on the same data, the same engine, and utilizing the same set of assumptions. And so I'm gonna pass it off to John. He's gonna talk about how gross to net and pre deal processes can actually connect and how those assumptions can be utilized across both processes. Yeah. Thanks, Daryl. If you can advance to the next slide. So before we get into pre do modeling best practices, I want to distinguish between pre do modeling and gross knit broadcasting because they share similar practices, yet they answer different business questions. Pre do modeling is focused on specific opportunity before the organization enters into a contract with a commercial customer or a state entity, typically with a managed care organization, a group purchasing organization, or a Medicaid state. Here, we are evaluating multiple scenarios such as different discount incentives to drive a volume growth and typically at what we call the book of business level like performance tiers or formulary access. In addition, we are performing comparative analytics and generating financial outputs to help us make business decisions like which scenario gives us the greatest revenue, the highest return on investment or the lowest breakeven point. Gross net forecasting, in contrast, has a broader perspective. It gives us a bottom up forecast of the expected revenue streams across all channels, customers, and products. In addition, gross net forecasting factors in government price implications that our commercial contracting decisions may have on government discounts. Like pre deal modeling, we also run multiple scenarios and perform comparative analytics to identify the key drivers impacting our gross to net. In some, the simplest distinction is that pre do modeling is hyper focused on a specific contracting decision, while gross net forecasting describes the expected financial outcome across our portfolio. However, these two processes should not be isolated. The gross net forecast can provide baseline volume, pricing, and discount assumptions for pre deal modeling. Then once a proposed pre deal scenario becomes likely, the projected results can flow back into the gross to net forecasting, scenario. And if both pre deal modeling and gross to net forecasting solutions are built on the same platform like Anaplan, the two way relationship can be connected to give us tremendous planning value. So with that distinction, let's go to the next slide and discuss best practices for freedom modeling. One more slide, please, Tara. So there are two major design themes on this slide. The first is how we categorize and describe deals and scenarios. The second is how we integrate data and project volume. Starting on the left, effective pre deal modeling requires more than just storing a deal's name, brand and customer. It begins with defining the deal categories and scenario categories that describe the purpose of the deal and the objectives of each scenario. For example, what is the deal strategy? Is it to obtain access, to maintain it, to improve it, or defend it? For a managed care contract, what form of access are we trying to achieve for the brand? Are there any restrictions like a step edit that we would like to remove? For a group purchasing contract, what performance tiers should we offer to incentivize buying growth? Is there a carve out for high performing members? Lastly, the design should allow us to report notes and assumptions to describe the unique aspects of the deal. In some, these categories give us additional insights into the purpose and objectives of the deal to accompany the quantitative numbers and dollars. The second theme on the right is data integration and projection methodologies. To perform preview modeling, we need foundational data from various sources, syndicated data, customer provided data, demand forecast, claims data from a revenue management system like a model in as well as outputs from a gross net forecast. The best practice here is to automate as much of that data collection as possible and provide a data management area where we can verify that appropriate data is available before we begin pre do modeling. For volume projection, we also want to utilize flexible methodologies depending on where the product's life cycle is with a particular customer. For an existing customer, the volume forecast may be based on a historical business mix relative to demand. For a new customer, the volume forecast may be based on assumptions like an uptick curve or a market share curve from an analog library. These curves contain assumptions such as the expected speed and magnitude of change so that we can model market events, like improved access, erosion, or competitor entry. Finally, the preview and gross net forecast solutions should share outputs so that the separate teams do not have to recreate the same customer forecast, which often happen if these are disconnected solutions. K. So to achieve these best practices, let's go to the next slide and discuss the top capabilities when building a preview solution. This slide lists the common set of capabilities to build in your pre deal solution in no particular order. The numbers here are used as references. First, the organization should have a common scenario forecasting capability across its contracting segments. That does not mean every segment must behave identically. Managed care, GPOs, Medicaid states, for instance, will have different requirements, but the foundational workflow should be standardized such as establishing a deal, creating scenarios, selecting projection methodologies, and applying discount terms. Second, the scenarios need to live in a common repository. If analogies remain in individual spreadsheets or personal folders, the organization loses the ability to compare similar deals and learn from actual performance. Third, pre deal profiling along with deal tracking capabilities are just as important as the calculation. We need to report the assumptions, the purpose, and the objectives of the deal to accompany the projected measurements. Next, the projection capability should include flexibility to use either algorithmic and or analog based methodologies. Algorithmic methods such as linear regression and triple exponential smoothing are appropriate when there is sufficient historical data. Analog methods are especially useful when it's when an expected projection is driven by a market event that will alter the volume from historic trends such as a change in formula access or a competitor product entry. Six, for a managed care contract, the pre deal solution should also include price protection calculations so that we can evaluate various white price action scenarios. Seven, the solution should evaluate consequences beyond the customer that we're evaluating such as best price and FSS tracking customer alerts so that we can raise awareness that a deal may impact our government discounts. Lastly, the solution should accept analogs from multiple sources, including post deal analysis so that we can refine our assumptions for future deal considerations. K? Now let's go to the next slide and discuss how we incorporate all of these capabilities in an Anapan preview solution. The dark blue boxes in this slide list the full capabilities of a preview solution that we built in Anapan, which Niko will, demonstrate shortly. The orange box on the right lists the capabilities of a post deal solution, which we can present in a future webinar. Getting back to the dark blue boxes, many of these capabilities were already mentioned in the previous slide, but still worth repeating here. Beginning with the deal structure and setup, we can create both standard and custom scenarios. Standard scenarios are default scenarios that we typically would wanna model in a deal, such as a base scenario, a best case scenario, and a no contract scenario. Custom scenarios provide flexibility when a deal requires modeling additional scenarios outside the norm. Each scenario can be assigned a status that tells us which of these were exploratory, which were presented to governance, and which ultimately represents the expectation we want to monitor after contract execution. The contract... The deal structure itself must also align with the contract structure. In other words, if the contract offer has varied discount incentives at the book of business level, then our deal and scenario must be modeled at the book of business level. And lastly, we can assign scenario categories to record each scenario. The next area is data automation and projection methodology. Syndicated data, claims data from a revenue management system, and master data should automatically be fed into the model rather than manually assembled every single time we want to model a deal. For volume projection, we can forecast volume in each scenario down to the book of business level using an... Either an analog method or a risk method or a combination of the two. For new products and new customers, we have the capability to add them to the deal even though we don't have historical data. And then in the third area, basically, we're combining price, discount turns, deal valuation, and comparisons. The WACC price should be managed... Centrally managed yet flexible for what if scenario, to test the what... The impact of WACC prices on our deal. Discount terms can be defined in each scenario down to the book of business level by discount type and vary across the time horizon of the deal. Price protection is calculated based on customer specific parameters so that we can evaluate the impact of various WACC price actions. And then finally, once we have the price, the volume, and discount terms combined, the model can generate the deal valuation and allow us to perform financial comparison to support decision making, particularly around net revenue, return on investment, and breakeven. K. With that, let me pass it on to Nico who'll do who'll do a demo on a preview solution that we built in NanoPlanet. Thank you, John. Alright. So let's take a look. Alright. So we're gonna take a look at what this model could look like to let you forecast out your your different scenarios, see what it does to volume and discounts, and compare side by side before you make any decisions. I'm gonna walk through this in the same way that a forecaster would so you can get an idea of how an end user might use this. And I'm gonna do this in five steps. Just going through the section administration, field setup, volume forecast, discount rates, and the evaluation and comparison. I'm gonna spend most of my time on these last pages because this is also where the decisions get made. So everything starts with the data. Your claims data, your WACC data, or your third party market data can all come in from either another Anaplan model that we call DataHub or from any of your source systems, either with the press of a button or automated. In this case, we can see the claims data by book of business. Same concept is true with the... For the WACC. Your actual price history can come in from any of your source systems, and in future periods, you can add price increases or override your WACC price to model out what the price schedule will look like. The next data steps are the different curves. So first, we have the volume growth curves. These drive how the total market grows, and each of these gives you monthly growth rates that you can apply to any deal no matter when it starts. So you can either add new curves based on the assumptions that you want to make with the press of a button here, or you can export the template, model it out in Excel, and then upload it using that way or using this button. And then the same is true for market share curves as well. So adoption curves ramp up faster. Erosion curves might model a competitor or or generic entry, and then you can also enter what your peak market share is to end at a reasonable and realistic ceiling. And you can see all of these different modeled out market share curves on the right. And the same idea here, you can either add them manually, connect to a different system, or edit it, edit the template using Excel. Next, we move to the deal setup. So in this section, you will be able to manage your deals, set up your scenarios, and, see the status of every deal. First, we're gonna start every deal out with the same standard scenarios so that every deal is comparable and answers the same baseline questions. So this might be base case, best offer without contract in this case. And then we get to the deal management. So this is every deal that we have, not just the new ones, but also older deals stay safe here so that we can look back at what we agreed upon in the past, use that to inform future contract terms, for example, and compare what we forecasted to what actually happened to make the next forecast more accurate. Creating a deal is just a press of a button, and any missing input would show up down here so that nothing half finished gets through, to the forecast. Down here, you can either add the standard scenarios to your deal or add custom ones if you need custom ones or rename the existing ones, as well as add the current scenario status and which date. Plus, you can add formulary tiers by year with different access and restriction flags and then assign each book of business to these tiers, giving you, the maximum flexibility. Next are volume forecasts and snapshots. So this section is there to make sure that just because data gets refreshed from your source systems, it doesn't automatically... Needs to flow needs to flow into your forecast. So all of these snapshot pages work in a similar way. Numbers that might not have been approved yet shouldn't just move into your forecast just because they they were refreshed. So for every deal and for every dataset, you can control which data and when you want to bring it into the forecast. So this is true for the claims data, for the market data, as well as for the WACC. Here, for example, you can see that, this is marked in red. So in our source system, we have a more recent WACC data than we are currently using for the forecast. And with just the press of a button, you could bring this data into your into your forecast. And the same is true for your volume growth curves and your market share curves with a visual indication of what changed, from your last snapshot. And then lastly, you end, in the volume forecast. This is where everything from before comes together, And you enter per scenario and per book of business, the curves that drive your market size for each of these, books of businesses as well as your market share forecast for each of them, your peak market share. And then the final market size is just, market share times times market size or the final volume forecast rather, which you can see at the bottom. Next are the contract terms. So these terms are entered, at the lowest level per formulary tier per year. So you can enter your rebates, your admin fees, your price protection cap, as well as any other fees manually per year. You can change them, over time, and we'll be portrayed here. And then for price protection, we know that every managed care payer has its own flavor of price protection. So we pre build some parameters that you can choose from. When does your price protection start? When does it end? What to use as the baseline WACC? How does it reset? What calculation method do you want to use? And all of that lets us follow whichever methodology a payer might use, and then the model calculates your price protection rebate... Rebates, which flow directly back into the valuation pages, which is what we're gonna look at next. So first, this page lets us see one of the scenarios end to end. So starting from the WACC, the volume forecast, market share, resulting in our expected gross sales, the discounts rate... Discount rates that we've seen resulting in the discount dollars and, thereby our net sales calculation or net price calculation. But this is only for one scenario. What, is the real question is which scenario you want to take and what does it cost us, and this is what the next page is for. So, let's stay here for a second. First, you enter... You select the deal that you want to look at and the year that you want to look at first, and you set a baseline scenario. So this would usually be if nothing changes, for example. These KPIs at the top show you what the baseline scenario is like for this time period, and then everything else below compares to this baseline. So the headline comes first. The net sales, how many net sales are we actually gonna expect with each of these different scenarios? And then next, we can see our value gain versus the rebate spend. So the bar... So the net sales gains and the line is the rebate spent or the extra rebate spent that it took to get there. So tall bar with a flat line would be a good deal. So you can see that with contracts, we're spending less rebates, but we're also losing out on a lot of net sales. Next, we can see which levers actually move the spend. So all the amber, bars here are rebates, and the fees are gray. If you hover over it, you can see which discounts are actually driving the change most. And then lastly, we have our gross to net erosion versus the baseline scenario. So this bar right here shows you the the baseline gross to net rate and how all of the other scenarios compare against it. And then if you want, all of the metrics side by side, you can look at this scenario comparison grid, which shows you each of the scenarios and the current status, all of the metrics that you've already seen before as well as some others, like return on investment, which is, your incremental net sales per incremental rebate dollar. So you can see that for every $1 more on rebate spent on this with contract scenario, you would make about $3 more in net sales. Or your units versus breakeven analysis, which shows you how far away each of the scenario lands from the volume that it would need to pay for its own terms. And then if you need an even deeper, view into all of the metrics over all time periods, and you don't want to select one by one, you have a grid below that gives you everything you might need, to look at, also ready to be exported if you want to if you want to do that. So as you can see in just a few minutes, we went from raw data, claims, and WACC to the fully finished recommendation that you can act on, with every assumption traceable and also frozen in time. So with that, I would like to give it back to John to talk about some post deal. Okay. Thanks, Nico. Thank you. I know this webinar is mainly focused on, building a preview solution, but I would like to take a moment to introduce post deal analysis as this process allows us to close the loop, where the learnings from post deal can help us refine our future preview modeling. Post deal analysis has three progressive phases. Phase one asks, are we getting what we expected? This is the measurement phase where we compare actual performance against our initial expectations and identify key drivers of the variances. And depending on on the solutions available, the initial expectations may come from a preview scenario or it can be coming from a customer level gross net forecast or both. Phase two asks, why did the variance occur? It is not enough just to say that volume discounts and net revenue are... Were above or below our expectations. The useful question here is what caused the variances? Did a large health plan move between formula tiers? Did the timing of formula access or implementation change? Did the market behave differently from our selected analog? So this causal analysis phase must be recorded to accompany the analytical insights from the first phase so that we can tell a comprehensive story. Phase three asks, how do we use the findings to improve future results? This is where we close the loop. Here, the findings flow back into few future pre do modeling activities. For example, if an expected formulary access consistently produces a slower conversion rate, we can update the relevant analog. If certain discount terms produce different volume outcomes, we can refine that volume projection methodologies. So in sum, the progression through the phases from measurement to explanation to action strengthens the next contracting decision. To work... To wrap up this webinar, let's go to the next slide to discuss how pre data modeling, gross net forecasting, and post deal analysis should be connected. In this final slide, it brings the whole story together. Pre data modeling, both than forecasting, and post analytics form a triangle of dependencies. Each process provides information that the other two need. Starting with the pre data modeling on the lower left, few scenarios contain the projected volume, pricing discounts, and financial outcomes. Once this scenario becomes likely, those projections should inform the next growth net forecasting cycle. Otherwise, the organization may have different financial expectations for customer across two solutions. Gross net forecasting at the top of the triangle provides the recurring customer level forecast across the channels and customers. It can also supply the baseline volume projection and discount rate assumptions to evaluate a contract in the pre deal modeling solution. Post deal analytics on the lower right then compare actual performance to expectations either from a previous solution or a gross to net forecasting solution. The findings from post deal analysis then float back to the previous modeling and gross to net forecasting solutions to close the loop. The findings can help us refine future scenario assumptions and projection methodologies in the pre deal modeling solution, and the findings can also help us focus on key drivers of gross to net in a mixed gross to net forecasting cycle. Lastly, if all three solutions are built on the same platform like Anaplan, we can achieve a true value of a connected ecosystem where information and data can be shared and archived. So with that triangle of dependencies in mind, I'll hand it back to Tara for our closing questions and answers. Alright. Thanks, John. So I'm gonna open it up to some q and a. Feel free to add any to the chat. I did see one or two come through. So one of the questions is in most organizations' pre deal and gross to net forecasting sit with different teams. Who should own the handoff between the two, and how do you keep assumptions consistent? Nikolai or John, you wanna take that? Yeah. It really depends on the organization. I mean, in certain organizations, both radio and voice mail forecasting may sit in, let's say, market access to group. But really the key is to ensure that we build the solutions on the same platform so that we can easily share information. And not only that, we wanna place in controls whereby for certain scenarios that we want that are more exploratory, we don't wanna publish that and have that fit into the gross net solution. Likewise, if there are also exploratory scenarios in the course of gross net forecast solution, we may decide when I would want to, publish that and share that with the previous solution. Fantastic. Alright. And then there was one other question around price protection. So it's how do you handle price protection? Nico, do you wanna take that one? Yeah. Sure. So we've modeled out, a lot of the parameters that we've seen, used by a lot of different managed care payers and created a system where you can just select which different metrics or which different attributes and parameters for the calculations you want to use. So you don't need to manually calculate anything. You just need to make the correct inputs and decide, which methodology you would like to pick, and then the model calculates for you. Great. And we have one more question. How does Anaplan address the new models that will be needed due to FTC requirements issued to PBMs? Are you building these new methodologies in, or do organizations have to build these solutions out within the system? Nikolai, you wanna take that one? Sure. Couple of ways. One to highlight one of the offerings that I mentioned earlier on in, in our presentation is Anaplan Co Modeler. So it's our agent that can lay over the top of your existing, models and products in your workspace, where by prompting, you can extend and expand that functionality. Really important in this industry, right, as as legislation changes and as we have new requirements. But, effectively, that would then be built out within your, within your company's model. Alright. We got another question. So you mentioned BP and FSS tracking customer monitoring within the pre deal analysis. How are the other government pricing metrics included in pre deal analysis? For example, impact of specific deal scenarios on Medicaid rebates, three forty b discounts, ASP, and associated reimbursement amounts. Yeah. That's a great question. I can take that. When it comes to government price, government prices, what we typically recommend in a built in a previous solution is more of an alert, whereby we're tracking what is the current best price and which customer is currently tracking it. And as you are evaluating various scenarios for a particular customer, and that customer may set a new best price, The impact to government discounts should be fed back into a government, into a gross net forecasting solution. It's because, in that solution, you have a more, holistic view of the entire channel and customer so that you can perform, government price forecasting in there in order to evaluate whether or not a particular discount is certainly gonna impact a government discount. Fantastic. I think that's all the questions we had. Anybody have any more questions?... Q and a. If you... Oh, we just answered that one, Erica. Okay. Thank you. Alright. So thank you all for joining us. We really appreciate you taking time out of your day. Please feel free to reach out to myself or any of the panelists, and we're so glad you were able to attend. Thank you. Thanks, everyone.