
AWS rebuilds its MSP program around AI agents and ties more funding to tagged revenue
AWS is rebuilding its managed services program around AI agents, and it wants partners to start tagging their work now because more of its funding programs will depend on it through 2027.
The news comes ahead of re:Invent. By AWS’s own count, it has almost three times as many partner launches as last year, from agentic AI inside AWS Transform to new agents in Partner Central, its partner portal. In The Channel talked to Julia Chen, vice president of AWS Specialist and Partner Core, who walked through the news before answering questions about what it means for a smaller, SMB-focused MSP.
For MSPs, the date to watch is January 1, when the updated managed services validation checklist, version 8.0, becomes mandatory. Chen said the checklist is already posted, runs more than 30 pages, and mixes mandatory and recommended items across business, people, governance, platform, security and operations. Her advice: print it out, mark what you can and can’t do today, and ask AWS questions. She argued the agentic approach benefits smaller MSPs most because it lets them scale without adding headcount, and said AWS intends to pay more for agentic MSPs in 2027.
The second theme is money. AWS is simplifying a funding framework that Chen said has been hard for small partners to navigate, distilling its funding vehicles into about 14 deliverables and outcomes, with more consistent rules rolling out across 2027. From January 1, AWS says, funding benefits are based on attributed revenue, measured through AWS Revenue Measurement, the new name for what partners knew as PRM. Chen said partners should be tagging their workloads now. It doesn’t all have to be done by January 1, but AWS plans to publish a schedule of when each program starts requiring it, and a partner that isn’t tagged won’t be able to use a program once it switches over.
There’s more for partners who do migrations and marketing. AWS is folding the Migration Acceleration Program (MAP) into a single agentic workflow in AWS Transform, and plans to simplify MAP from three phases to two next year. Demand Center, which unifies co-marketing and co-selling in Partner Central, builds marketing assets such as case studies and solution briefs in minutes, and partner account planning launches November 19.
In this episode of In The Channel, Chen discusses:
- What the agentic-first MSP program means for smaller, SMB-focused MSPs, and where security fits in
- What to do now to be ready for the updated validation checklist
- How AWS’s simplified funding framework changes things for small partners
- What AWS Revenue Measurement tagging involves, and what happens to partners who aren’t ready
- Which Partner Central AI tools to try first, and how value realization plans change renewal conversations
- The one thing she says partners should do in the next 90 days
Listen to this episode of In The Channel to find out more.
Read Full TranscriptRobert Dutt: Hello and welcome to In The Channel from ChannelBuzz.ca, providing news and information for the Canadian IT channel for the last 16 years. I’m Robert Dutt, editor of ChannelBuzz.ca and your host for the show. Every year, AWS saves up a lot of partner news for re:Invent. This year, a big chunk of it is landing early. By AWS’s own count, there are almost three times as many launches as last year. For a Canadian MSP or VAR, the question is the same as always. What does this mean for my business and what do I need to do about it? AWS is rebuilding its managed services program around AI agents.
It’s simplifying how it hands out partner funding, and it’s changing how it measures the revenue partners bring in, a change AWS says more of its programs will depend on through 2027. There are also new AI tools inside Partner Central, AWS’s partner portal, aimed at trimming the busy work of building campaigns, finding customers and tracking funding. That’s a lot of news, so my guest starts by walking us through it herself. Julia Chen is vice president of AWS Specialist and Partner Core at AWS. From there, we dig into what changes for an MSP with a small team, what to do before the updated managed services validation checklist becomes mandatory on January 1, what AWS wants partners tagging, and the one thing she’d tell partners to do in the next 90 days.
Let’s get into it, my chat with Julia Chen.
Robert Dutt: Julia, thanks for taking the time. I appreciate it.
Julia Chen: I’m so glad to be here. Thanks for speaking with me.
Robert Dutt: There’s a lot landing for partners ahead of re:Invent. I guess let’s start with the headlines. What’s the news and sort of the why now for making some of these changes?
Julia Chen: How much time do you have, Robert? I have a lot. I, no joke. We actually counted and we have almost three times as many launches as we had last year, so it’s a lot of stuff, but I’m really, really excited about it. So, if I, if I start with like the big headline, the big headline is AI, of course, right? And there’s two vectors in which I think about AI. One is that we’re enabling our partners to sell more, sell and deliver more, you know, AI augmented business outcomes. So that’s like headline number one, which is that’s, you know, that’s the goal. The other thing is, you know, we’re drinking our own champagne over here.
So we’re using the AI to make it easier for partners to do business with us. So as always, the whole goal of everything that I do and my team does and, you know, what AWS wants is for us to be the best vendor for any partner to work with. So we want to inspire, enable, and invest in them so that they’re able to build the most profitable growing practice on AWS. And so with that in mind, we have a bunch of things that we’re excited about. And so I kind of, I think about the journey of a partner, or actually it’s the journey of a partner with a customer in kind of different phases, right?
So usually they’re building solutions and a practice, they’re marketing, then they’re selling and delivering, and then they’re growing that relationship with the customer. So if I kind of walk through, I’ll sort of walk through that journey and the different things that we’ve got going on. Across all of that. And so if I start with build. I mean, one thing that partners have definitely asked us about in this last year is around forward deployed engineering, right? Which is like, you know, you hear FDE everywhere. And so the partners have been asking, like, what do we need to know about it? How do we participate with AWS in FDE?
And so you would have heard earlier that we made a $1 billion investment in FDEs. And that is always very exciting for us. We’re very serious about it, our customers are saying it adds a lot of value. And so we definitely want our partners participating with us in FDE. So there’s different motions that partners can participate in. Obviously, there’s some FDE engagements that AWS will lead by themselves, but then there’s some that we will absolutely do with partners, and then we’re also expecting our partners to be leading FDE engagements themselves. So that’s one thing that’s very exciting.
Also, we have a whole, a whole class of products under Amazon Connect, and so we have an Amazon Connect competency that is coming out as well. This Amazon Connect Customer Software competency validates partners across three categories. Customer Experience with solution extensions, and then Connect A2A collaboration agent certification, and then Connect Customer, which is powered by the partner platform. So these replace the Amazon Connect Service Ready designation, which sunsets in June. So that’s exciting because this connect category of products is really out of the box. AI augmented solutions for vertical specific use cases. One other competency that’s coming out that supports all of this AI foundation is around the AI data competency.
So that has new categories around the full data lifecycle from databases to AI ready foundations to new performance-based signature benefits, and all of that is super exciting because that is the foundation to having a good AI practice for our partners. So that’s on build.
If I move over to marketing, our partners have been asking for a long time to get more self-service in the marketing space. Obviously, we have a lot of different assets that we’ve created over time, but I’m really excited that we’re going to be announcing Demand Center, which really unifies the co-marketing and co-selling in Partner Central. So it brings the campaign management and the MDF automation altogether. So partners don’t have to keep switching between platforms to plan campaigns, request funding, track performance. What else is really cool? This is another example of where we are using our own AI to make life easier for our partners to help connect them to what they need faster.
It actually builds marketing ready assets like case studies, white papers, solution briefs, all that stuff, in minutes for our partners. And so our partners will really be able to use this straight out of Partner Central and create whatever assets they need from their own content with the AWS content right away and then they can then just like stick it onto marketplace or wherever they want to market.
I want to talk a bit about migration and modernization because that has been sort of a mainstay staple for the cloud business, you know, since it started. And for us, I think our partners are very familiar with the Migration Acceleration Program, MAP, which has been around since 2016. And so MAP continues to upgrade every year or two, and this year is no different. And from the AI lens, what we’re going to be talking about is AWS Transform. So AWS Transform is a tool that we have free of charge for our partners to use to help accelerate migration and modernization. In fact, 56% of AWS Transform adopters saw double digit margin gains and 65% faster delivery, which outpaces all the other tools on both revenue and win rate.
And so this is from an Omdia study that they did.
Now, what we’re doing, the exciting announcement is that we’re actually integrating MAP end to end into a single agentic workflow. So from the first opportunity discovery all the way to the final cash and credit disbursement. So this agentic MAP experience actually handles the assessments, the deal qualification, fund requests, contracting, execution, resource tagging, incentive disbursements, all these things that used to be manual and the partner used to have to keep track of it and do each thing one by one. This is all going to be in this agentic MAP experience that’s in AWS Transform. So highly, highly urge our partners to go explore that. We’ll be talking about it a lot at re:Invent.
The MAP program itself is also going to be simplified. It used to be three phases. Next year, we’re going to be simplifying it into two phases, a proof of value phase, and then a deploy phase, and then we will continue to have sort of outsized, increased payouts for strategic workloads, right? Like VMware, SAP, mainframes, and others. So I’m very, very excited about that. We’re going to be implementing performance indicators, so partners can get a real-time view and track their delivery track record. And stronger performers will get accelerated payments and elevated benefits. So we’re excited about that as well because our strong MAP performers are going to get a lot of benefits that I think they’re going to like.
I would also say that, well, before I go there, let me move to managed services. So if I think about customer experience, customer retention and growth, I’m very excited about agentic managed services. So we’ve been spending all of 2026 talking about this, you know, we’ve talked about it at multiple Partner Equips, and then you will have seen that we’ve already put out our latest validated checklist for managed services, where there’s a bunch of agentic requirements. And so the reason I’m excited about managed services is there are customers, have been, you know, as the technology and the AI and all the things get more complicated. Our customers are really asking for more help, managing their, you know, managing their technology estate.
And there’s a ton of partner opportunity here. So Omdia forecasts that the market’s going to grow to $650 billion in 2026. So this is managed services, and 61% of the revenue comes after you sell, which is fantastic, right? So that’s for our partners. It’s like you do all this delivery work, but then after that, there’s a whole bunch of opportunity to continue managing and growing and nurturing and helping the customer out with their additional use cases. So our managed service partners show 3.4 times larger engagements, 29% better retention and five times more customer growth, which is why we believe in it. And I think the customers are talking with their wallets.
So it’s exciting because a lot of our partners have asked us, what does agentic managed services look like? Like, what does that mean? And this validated checklist can seem a little daunting at first. So I printed it out. It’s over 30 pages of mandatory and recommended items across the business, across people, governance, platform, security, and operations. And it’s very deliberately a mix of mandatory and recommended. You’ll see a lot of things in that checklist that are recommended, and those are meant to be sort of best practice. Those are best practices that we want our partners to start thinking about and investing in and developing. So I’ll give you a sense of some of the requirements that are in this checklist so that you get a sense of how things are changing, right?
So managed services are not new. Managed services have been around for decades, but what is it about agentic managed services that are important? I mean, from a business standpoint for our partners, agentic managed services actually allow them to scale without adding headcount, right? So the idea is to get more revenue, more profitability by, not just automating, but making intelligent, a lot of the things that humans used to have to do that now, now a lot of the agents can take a first pass at and save a lot of time. Some of the business requirements, I mean, we’ve always had business requirements around customer references and success stories, but then we also now want the AI competency alignment.
We need an AI transformation roadmap, and then a customer realization framework. So these are things that we want them to think about from a business standpoint. From a people’s standpoint. The partners need to have AI and ML certified, folks on staff, recommended to have a dedicated AI practice lead. So again, that’s recommended. It’s not mandatory for this, but we want our partners to start thinking about that and also recommended to have an FDE team. On the governance front, there needs to be a documented change management process, a responsible AI policy and framework. Recommended, we want an AI agent and model governance and lifecycle documented. There’s data governance as well.
So this is super important in the world of AI. We need to make sure that the data quality lineage, permissible scope, consent management, retention, all of that is documented, and then also vendor and third-party AI management. In terms of platform, right? We want to see that they have a CI/CD deployment and automation platform, and an agentic AI platform, Amazon Bedrock and foundation model platform, these things have become requirements and recommendations, and we want our partners to be thinking and building in this way. And then obviously in the space of security, right? Cloud security posture management was always required, but cyber recovery and resilience, encryption and key management, workload security, AI security governance, prompt injection prevention.
All of these kinds of things have become part of this validated checklist. And I know that it seems kind of daunting, but our intention really is for our partners to come with us on this journey. We think that this will give them a leg up in the market and that customers will really, really appreciate this. You know, and we want to bring as many partners with us on this journey as possible into this agentic managed service world.
Business value realization is another one that we have talked about in years past and we’re continuing to talk about now. But we have an agentic BVR journey now in Partner Central as well. So again, applying our AI tools into some of our programs that allow our partners to be able to, in a much more automated and on-demand way, generate a value realization plan for their customers with AI powered recommendations, working backwards from the KPI that the customer cares about, not just the, you know, not just the cloud revenue, for example.
And then maybe let me end with a security one that I’m really excited about. So there will be a bunch of security announcements at re:Invent this year that we’re excited about. But sort of one thing that I want all of our partners to think about is the Security Health Improvement Program. So partners can deliver this assessment to customers that’s a very comprehensive security assessment that we provide, and the partners can customize to their own liking. But we think that’s critical in this age of AI. Like we really want partners to develop this security assessment in their own way. You know, we’ll give you everything that we’ve got, but like that is the key to opening up, kind of the biggest objection that customers have to AI, which is around security, right?
One of the biggest blockers that we hear about is that security is the thing that they worry about and that’s the thing that prevents them from going fast with the AI.
The last thing that as a tool I’m excited about is Partner Central agents, like we continue to augment Partner Central with a lot of different agents that allow for lead enrichment and prospecting, allow for solution matching. So co-sell support, right? So our field can find the right partners and partners can find the right opportunities. And now we have partner account planning, launching on November 19. And what that’s going to do is allow partners to upload target account lists and match propensity and program eligibility. And if we don’t have a match, we won’t share anything internally about the partner’s account list, but it’s sort of a clean room.
That allows for our partners to see what they, what’s available to them in the propensity that we know about of that customer list. We continue to add tools. Funding agent and other agents within Partner Central that will let partners see how they’re doing against all different, you know, initiatives and competencies, et cetera, and opportunities that they have better than they have before. And overall, we’re simplifying our funding framework. So I do believe that our partners will be seeing over the course of 2027 a lot of simplification and more consistent rules and funding levels across our various programs because in the past, that’s not always been the case.
All right, so you asked me for a summary. I’m sorry, I think I read you the encyclopedia there, but those are truly kind of highlights and things that I’m so excited about going into re:Invent.
Robert Dutt: That is a lot of territory. There’s a lot to dig into there. I guess let’s start with the MSP program. You know, with the move to agentic first. For a smaller SMB-focused MSP, you know, what actually changes here? And is this, is this sort of an opportunity for them or is this primarily for folks who are of a scale where they can, you know, have those FDEs and that kind of investment that’s required there?
Julia Chen: No, so this is definitely for all size MSPs. And I think it, in fact, maybe counterintuitively. It benefits the smaller ones more, right? Because it means that they can scale with less headcount. And so a lot of the tools that I’m talking about, you know, building a platform on Bedrock, et cetera. It doesn’t, it’s not, it doesn’t take an army. Like we’ve had very small and medium-sized MSPs come and do this checklist. And they’re able to do it, and it doesn’t take a lot of people, which is the beauty of it. I mean, it definitely takes some investment in human time to learn all the different tools.
But our intention, as I was saying, is to bring as many of the MSPs with us as possible and we need, we need them of all sizes. If you listen to my Partner Equip keynote from San Francisco, I talk about a partner called Workmates in India, and they’re not a huge, they’re not a huge MSP. They’re quite small, in fact, and they were able to identify their entire practice and see huge savings and efficiency gains, and, you know, now agents are reviewing the vast majority of the tickets that they have. So they were able to scale their revenue multiples without adding any headcount. And so that is the vision that we have for these MSPs, right?
Robert Dutt: So there are five stages of the program, basic reseller through emerging, established, market leader, I think, and strategic. Where do you find sort of the typical SMB-focused MSP lands out of the box and what is moving up earn?
Julia Chen: What does moving up earn? So it earns more profitability, right? So like, without fail, from three different sources, from the partners themselves, from analyst research, and I have all different analysts research, from all the various analysts firms, and then from our own internal data, they earn higher profitability. Now, we will, AWS will, we have the intention in 2027 to pay more for agentic MSP. However, the partner themselves will earn more from the customer, and the profitability will be better as well, because again, you’ll be able to process a lot more of the work without adding humans to it, and the humans are the most expensive part of the MSP.
So I think like that is out of the box, some of our smaller MSPs. I mean, you would think typically land earlier in the stage, but then actually, I mean, we’ve, I’ve met at Startup Summit and other places, I’ve met MSPs that develop, they either develop or they acquire tools because there are a lot of different ISVs right now creating agentic MSP tools as well. They’re able to leapfrog the earlier stages of MSP and actually get straight to agentic pretty quickly if they find the right tools.
Robert Dutt: On the security side, MSPs can add SHIP engagements and continue across their customers. You know, what does that mean for an MSP that isn’t in the kind of pure MSSP kind of lane in terms of building out their portfolio?
Julia Chen: I think I would say start with SHIP, and you don’t have to, like, if you’re not able to, you can partner with another MSSP, I think, in the beginning, but I do think that there’s the security space is getting so, broad. I would say, especially with AI, that sort of the world’s your oyster, right? You don’t need to do it all, I would say, I think that you can, you can start with AWS’s suite of security tools and again, more are going to be announced. I think that you’ll find that they’re becoming more intuitive with the AI inserted into it where you don’t have to have, you know, deep, deep, deep, many years of experience to be able to leverage the agents to be able to help you diagnose and patch and a lot of it’s preventative as well, which is like help the customer set up a secure environment to begin with.
I think all of that work becomes very doable with a lot of the tools that we’re putting out and the guidance that we’re putting out. So I would, I would say that perhaps in the past, MSSP has seemed like a very intimidating, you know, an intimidating role to play, I would ask partners to keep an open mind and check out the tools that we’re putting out and, you know, start small, but do the assessment. And I think, like, you’ll see that you’ll be able to keep moving up that chain as well, that maturity curve on delivering security. It starts with data, right? So it starts with all the data governance and all of the data best practices, which anyway, these MSPs will have to go through themselves to get the MSP validated designation.
Robert Dutt: Okay, and the validation checklist, 8.0, goes, or becomes mandatory rather, January 1st, I think. What should an MSP be doing now to be ready for that and make sure their ducks are in a row, as it were?
Julia Chen: I would say study the guide. So it’s already posted. So go study the guide and then ask us a lot of questions, right? And then come to some of these Partner Equips and some of the events that we have because a lot of MSPs we find are sharing best practices with each other. And again, you don’t have to homegrow a lot of this stuff, right? There are things that are platforms out there that are available for purchase or that, you know, and then we continue to put out tools as well. So what I would say is like just like print the thing out and stare at it, right?
Figure out what you can and cannot do, where you have questions about it, and give us feedback, by the way, because we have every intention of bringing all of our MSPs along with us, and also our non-MSPs, right? We want, you know, we want a lot of our consulting partners to become MSPs. Like there is a lot of value to be delivered and there are just not enough of them to fill all of the customer demand.
Robert Dutt: On the funding framework. If a small partner applies for funding today, you know, what’s, how is that going to look different next year?
Julia Chen: So, my goodness, I, in the olden days, if I can say that, in the olden days, a small partner would struggle, because we do have a lot of different funding vehicles, and a lot of times if you don’t have someone helping you out within AWS, it was hard to know them all and find them all and figure out which ones to use for what purposes. And so going forward. I’m super excited. So Partner Central, we continue to add a lot of agentic functionality that will allow our partners to be able to find and use the right funding vehicle and then the simplification that I talk about, right?
We’ve distilled all of these funding vehicles down to certain set of deliverables, behaviours, and outcomes that we have our partners, you know, that our partners deliver as value. So we talk about build solutions, build capabilities, market, right, migration, modernization, managed services, business value creation. In the end, there’s about 14 different deliverables and outcomes that our partners usually deliver on our behalf that we think adds value, and those are the things that we fund. So I mentioned these 14 things because you’ll see that things are going to start clustering around these 14 behaviours, activities, outcomes. And the funding journey will become simpler because it’s going to be more consistent on the back end.
So we’re doing that work right now. That’s a transformation happening all across 2027, but our partners will see that things will become more consistent, more structured, easier to find, and the payment, like the funding request claim payment process is going to become all very consistent, which is what partners have been asking for years.
Robert Dutt: Also, from January 1, the funding benefits are based on attributed revenue. What’s being measured and what does a partner need to do before then to be ready and make sure, you know, they’re, again, their ducks are in a row?
Julia Chen: Yeah, so AWS Revenue Measurement is, partners would have heard it called PRM last year, but we’re now renaming it to AWS Revenue Measurement. They need to tag their work effectively, like their workloads with that. Because also across the course of 2027, our programs are going to be requiring that be the case so that we can pay on that. And so partners should be doing that right now. A lot of our partners have already started. Actually, the vast majority of our partners already have tagged, have tagged workloads using PRM, but now the rest of the work needs to be done, which is like originally they, a lot of them have tagged one or two of their products, for example, or one or two workloads just to try it, and now we need everything to be tagged that way.
So that’s the work to be done collectively by all of us, by the way, in 2027.
Robert Dutt: What happens if a partner doesn’t have everything tagged and everything set up by Jan. 1?
Julia Chen: I would say it doesn’t have to be all by Jan. 1, but like we will release the schedule of when programs are switching over to require it. And so, I mean, unfortunately, if it’s not tagged and you rely on a certain funding program, you won’t be able to use it after that program switches over. So they should be looking out for that. That announcement will be coming out shortly. But then they’ll have a schedule of like when the various programs switch over.
Robert Dutt: On the AI tools in Partner Central, you know, I don’t want to ask you to choose which of your kids is your favourite, but if a small partner tries one of the new AI tools this month, which would be the first one you’d urge them to get to know?
Julia Chen: That is so hard. I think a small partner would benefit from the journey, right? So there’s an agent that will walk you through the journey of all the things that you need to do to become a partner, to get competencies, to, like all of the different things. And I think that’s, if you will, that’s almost like the concierge tour guide agent, I guess, if you think about it. So that, I think, is probably for a small partner just starting with us, that’s probably the most useful one. It’ll give you the overview. It’ll tell you the next steps. It’ll tell you best practices. I mean, and from after that, it really depends on the partner, right?
So if it’s about migrations, then we should, you know, you should go look at the migration stuff, if it’s about co-sell, if it’s about, it depends on if the partner’s a consulting partner or a technology partner. But effectively, we have so many of them in there and it’s not just try one necessarily, but like they’re all there. They’re all there for the, you know, our partners to try and consume. And so I would say like try as many of them as you can. I think you’ll find a lot of benefit. You’ll get, you know, you’ll get enablement data faster. You’ll get your performance data faster.
Funding agent helps with finding out like what you want to use, like what funding vehicle you want to use for what opportunity. So, I mean, in my view, yeah, it’s hard to pick a favourite child to your point.
Robert Dutt: The value realization plan going in there, how does proving value after go-live change an MSP’s renewal conversation?
Julia Chen: It’s hugely important because I think that like, if you have strictly a financial conversation with the customer, that, I mean, that sort of restricts you anyway to just the buyers. Like, the value realization, sort of our business value realization thesis is that customers are buying a business outcome, and you have to show them the business outcome. So if they’re trying to reduce order to delivery cycle time in a factory, and you just show them that they consumed this much AWS revenue in a month. You’re talking apples and oranges, right? So that order to delivery cycle time is important to them. You have to show them that you did or didn’t achieve that.
And by the way, if they want to do more than what you were able to deliver, that’s again, more work that needs to be done, more agentification that needs to happen or more, whatever. So it really, I mean, I find that it really up-levels the conversation to the business leader. Then you’re talking to the business owner of the process, right? You’re not just talking to the IT folks, saying this is your, you know, this is your, you know, cloud spend last month. And so for, in my view, it’s vital that our partners learn that language of the business outcome that the customer signed up for, in addition to, like all of the things that they do to manage the environment as well.
Robert Dutt: So it builds out the plan, as I understand, and sort of flags risks early, things like missing customer sponsorship. Is that something the customer sees, only the partner, or how does that flow work?
Julia Chen: It’s up to the partner to decide. I mean, they should be building it with the customer, but it is up to the partner how much of it they want to show to the customer, but ideally they work on it together and then the customer sees it, right? So a lot of the things in there are things that the customer needs to do, to your point, which is, do they have sponsorship, right? Like, do they have the right, you know, mechanism set up, do they have the right metrics? You know, do they have all of the right process in place? Are the people enabled on the customer side as well to be able to receive the solution that the partner built?
I think all of that is critically important because a lot of times the problem isn’t that the technology failed. The problem is that the customer did not absorb it or adopt it properly because they weren’t configured to. Either the organization wasn’t right, the people weren’t trained, the processes didn’t change around the technology. And so those are all the pieces that we need to ensure, collectively, like AWS and partners need to ensure that the customer is properly configured to absorb the solution.
Robert Dutt: And is value realization plan open to any partner or is it tied to a particular program or piece?
Julia Chen: We have a formal program for it. But I think any partners should use it, right? Like it’s a good best practice. So that is something that every partner should be thinking about, which is like, how do you tie your services and your solutions to the customer’s actual business outcome. It’s a very, it’s not an easy thing, by the way. It’s a different language. It’s a different mindset and it’s a different practice in a way, but I think it’s important that we all get there.
Robert Dutt: What do you find? Are there any common traits among partners who get that quickly and successfully make that switch to that different mindset?
Julia Chen: It’s interesting. I mean, there are a class of partners that are business consultants to begin with. And so they’ve been speaking that language, and I think, so it’s interesting. We’ve got partners that are more centric on the technology historically that are moving more towards this business outcome, conversation and mindset and practice. And then we’ve also got some business consulting partners that are moving more towards the tech as well. And so these things are kind of merging. But there are a class of partners that have been speaking in the language of business outcomes from the start, but I think that historically, it’s been hard for one partner to be able to do it all, but I’m seeing that partners are growing in both directions now.
Robert Dutt: We covered a lot of territory. There’s a lot going on, no doubt. I’ve asked this a couple times along the way in terms of, you know, it was specific things what partners should do to be ready, but taken in a broader sense, across this whole estate of changes you’re making to the program. If an MSP owner or VAR, who’s in the program, you know, over the next 90 days, what, if there’s one thing that they should do, what should it be to get ready and to take the most advantage of these changes?
Julia Chen: I would say definitely be tagging everything with the AWS Revenue Measurement, right? That thing is important because it underlies almost everything that we’re doing going forward. So I think that’s important. And then the second point is to explore all of these different tools and specializations and program changes that we’re putting out. If anything is not clear, again, we love feedback. So if anything is not clear, if it seems like too big of a leap, if something is not accessible or not, like it’s too hard, like let us know. I think all of that is things, you know, those are things that we need to know because we want everybody moving with us, right?
Like what we’re putting out is what we see kind of our fastest partners doing and getting success out of it. And so we clearly want all of our partners to be moving in that direction because that’s what we believe that customers are asking for.
Robert Dutt: A lot to study and take away from there. Julia, thanks for taking the time and good luck in rolling all this out and a successful re:Invent.
Julia Chen: Thank you so much. It was great to talk to you, Robert. I really, really appreciate it.
Robert Dutt: There you have it. Julia Chen from AWS on the partner changes coming ahead of re:Invent. Thanks to Julia for making the time, and thank you for listening today. A few things to take away. First, AWS’s pitch to MSPs is scale without adding headcount. Julia argued that smaller MSPs may benefit most because agents can take a first pass at work that used to need more people. She says AWS intends to pay more for agentic MSPs in 2027 and that partners should also earn more from their own customers. Second, if you’re in the managed services program, the updated validation checklist becomes mandatory on January 1. It’s already posted, it runs over 30 pages, and it mixes mandatory and recommended items.
Julia’s advice: print it out. Mark what you can and can’t do today, and ask AWS your questions. Third, and this was her number one for the next 90 days, tag your work for AWS Revenue Measurement, which partners may remember as PRM. Julia says it underpins almost everything AWS is doing next. It doesn’t all have to be done by January 1, but AWS plans to publish a schedule for when each program starts requiring it, and once a program switches over, untagged work means you can’t use it. Finally, try the new tools and tell AWS what’s unclear or out of reach. She said they want the feedback.
Keep in mind, these are AWS’s own plans and numbers, so watch for the details as they roll out. If you’d like to hear more conversations like this one, follow or subscribe to the ChannelBuzz.ca podcast in your app of choice, and if you have a moment, leave a rating or a review. It’s the best way to help other channel folks find us. Until next time, I’m Robert Dutt for ChannelBuzz.ca, and I’ll see you in the channel.
More episodes from "ChannelBuzz.ca"



Don't miss an episode of “ChannelBuzz.ca” and subscribe to it in the GetPodcast app.








