I'm not a software developer; I'm just a guy helping Microsoft partners find their path to success. Nitty-gritty technical conversations have never been my arena.
But even a non-techie like myself sees that AI-driven software development is a revolution. Software development will never be the same again, to the benefit of both customers and partners. And this is where I'm an expert. I love to talk about business transformation and driving better business outcomes.
We can thank GitHub Copilot for this new era of software development. To say that GitHub Copilot can help you write code faster and better is an understatement of giant proportions. With GitHub Copilot, you can perhaps get 80 percent of your code generated and can spend time really focusing on the remaining 20 percent.
Here are some ways GitHub Copilot (or current and future competitive solutions) can reduce time and cost in software development:
- It can generate code from natural language descriptions. You can use comments or prompts to describe what you want to do, and GitHub Copilot will suggest relevant code snippets or functions that match your intention. This can save you time searching for existing solutions or writing code from scratch.
- It can learn from your code and style. GitHub Copilot can adapt to your project's context and style conventions, and offer suggestions that are consistent with your codebase. This can improve the quality and readability of your code, and reduce the need for refactoring or debugging.
- It can help you discover new APIs and libraries. GitHub Copilot can suggest code that uses popular or relevant APIs and libraries for your project, and even provide documentation or examples for them. This can help you explore new possibilities and features for your project, and reduce the learning curve for new technologies.
- It can help you test and optimize your code. GitHub Copilot can generate test cases, benchmarks or performance metrics for your code, and suggest ways to improve or optimize it. This can help you ensure the reliability and efficiency of your code, and reduce the risk of errors or bugs.
There might be people out there who say that traditional software development is far better than taking help from AI, or that using AI is like cheating.
My response would be that I've heard similar things before. The first time was when I was young and desktop publishing with the Apple Macintosh was just becoming popular, and the oldies said that it was not good enough. All of us also heard it when cloud computing started to become popular.
But guess what? As these new technologies became got more popular and refined, we haven't looked back.
If I were running a software development practice -- either as an ISV or as more of a custom development -- I would transform the way we work and use GitHub Copilot right away. In so doing, I could significantly increase my team's output and perhaps reduce the number of developers.
This opportunity is, of course, larger in developed economies with higher salaries than in less developed ones, but the same logic still applies: AI-driven software development is here to stay, and refusing to become part of it will hurt your business.
I'm also pretty sure that investors will start demanding that their portfolio companies start to use AI-driven software development. The ones that are stubborn and refuse will probably have less pleasant conversations with their investors.
This is a revolution -- and, for many, still an untapped opportunity. Don't be left behind. Join it instead of watching from the sidelines.
Posted by Per Werngren on February 23, 20240 comments
Probably nobody in our ecosystem has missed the wave of news around AI. Besides the great products we've seen from Microsoft and others, AI has also been widely democratized via ChatGPT, which has really accelerated innovation. In just the year since it hit the scene, ChatGPT has become the engine for multiple solutions that build services on top of it.
At this month's Microsoft Ignite event in Seattle, there was a very strong focus on AI and the marching orders from Microsoft are crystal clear: AI is the chosen path and partners should get on board. But what exactly does a partner play for AI look like?
This is a coat of many colors. There are multiple avenues for partners to embrace AI. In this post, I will go through the ones that I have seen and been thinking about. I'll divide them into two buckets: One is what you can do internally, and the other is what you can do for your customers. (There will, of course, be hybrid scenarios where you utilize the success you have internally and bring it to customers; eating your own dogfood has always been successful as it builds trust.)
AI Within Your Own Organization To Drive Profitability
Marketing is low-hanging fruit for AI. You can use various tools to generate sales material, blog posts and scripts for webinars. You can also use AI for prospecting and for recording videos. AI can reduce your need for outside marketing agencies, not only saving you money but also to enabling you to become more agile in your marketing.
Software development can be powered by AI solutions like GitHub Copilot and Copilot in Power Apps. You can generate the bulk of your code almost instantly, which will radically shorten your development cycle and reduce the man-hours involved. With skilled developers hard to find (and salaries high), using GitHub Copilot will dramatically increase your competitiveness, enabling you to sell projects at a much lower price and most likely also increase your profitability.
Software development with the help of AI is a revolution; my advice is that you fully embrace it. When 80 percent of the code is generated by AI, you can focus your expert developers on refining the remaining 20 percent.
Adding AI to your ISV products is something to consider when you plan your roadmap. Not all products will benefit from adding an AI component, but it's well worth considering as AI might add great new capabilities. We have started to see lots of mission-critical systems adding AI and the purpose is often to provide better abilities to plan, make decisions and analyze.
Everyday efficiency is another area where you can easily use AI to streamline your work and accomplish more in your workday. Using a product like Microsoft 365 Copilot will enable you and your colleagues to free up time. Imagine if everyone in your organization could save an hour per day. That would enable you to grow while hiring fewer people -- and that has a big impact on bottom-line profits.
AI for Your Customers
Strategic advice aimed at customers is an important area that is currently underserved. Your customers will need a strategically focused partner to help them understand what AI can do for them and prioritize where to implement it. But they will also need partners with a great understanding of their industry and their company. The combination of AI and business understanding will fuel your strategic advisory practice for years and is a great avenue for selling other projects from yourself or from trusted partners.
Speaking about trusted partners, when you give strategic advice, it is crucial to know who the best players are to realize the strategies that you have set for your customers.
Implementing AI is not just as simple as signing up for a service. It takes a skilled partner to understand how to classify and structure the data that is being used by AI. There are also security and privacy implications that need to be addressed. AI needs access to the right data -- and that data might be in isolated siloes, which takes a skilled partner to handle responsibly.
The new AI-powered SharePoint Premium is a great solution to transform content management and content experiences and get content ready for Microsoft 365 Copilot. I would also recommend building skills around the new Copilot in Microsoft Fabric (and in Microsoft's various other "copilots," as well). You cannot become master in all copilots, so aim for a general understanding of all and specialize on the ones that make the most sense for the needs of your customers.
Building or customizing copilots for Microsoft 365 will be popular among your customers. Microsoft has just announced Copilot Studio, a low-code tool that enables you to customize Microsoft 365 Copilot and build standalone copilots. You also need to become a master on Azure AI Studio, which is a platform for developing generative AI solutions and custom copilots.
Maintenance contracts for AI refers to offering a retainer for monitoring, policing and fine-tuning your customers' AI setups. This will give you a recurring revenue stream and your customers (and your CFO) peace of mind.
Restructuring software development is when you turn the same approach that I described for your internal software development toward your customers and their own software developers.
Don't Be Left Behind
Start your AI transformation journey by making a roadmap and motivating your organization. Make sure you take the first step quickly, and then take it step by step at a pace that works for you and your organization.
Early movers in AI will become popular and spark enthusiasm within both Microsoft and customers, which will drive business opportunities. (We all know that Microsoft loves partners that are forward-looking and drive its business. If you bet on Microsoft's strategic choices, Microsoft will bet on you!) These early movers also will deliver a more exciting workplace for their people; it's always more fun to be part of the future than belong to the past.
Good luck and let me know how it goes!
Posted by Per Werngren on November 27, 20230 comments
In my previous article, I talked about CPOs -- chief partner (or partnership) officers -- and I'm overwhelmed and a bit surprised by how much interest this discussion has attracted. CPOs are the talk of partner ecosystems -- not just specific to the Microsoft ecosystem, but also in much broader terms, and even with regard to partnering outside tech.
Why Should You Want To Hire a CPO?
One of the biggest mistakes partners make is senior leadership not extending their buy-in and support. People in an organization might go out and forge partnerships, but it's risky when it's not part of the company's strategy.
Another problem is that partnership efforts across a larger organization get reinvented over and over again, as there is little coordination. That means everyone is working in their own siloes and no one shares best practices in a structured way. That can also lead to certain critical issues (like legal ones) getting overlooked or duplicated.
Having a CPO is about making a stand -- internally, as well as externally -- to show that partnerships are important and are part of senior leadership's responsibilities when running the company. It's also about recognizing the people who are working with partners. The value of sending a strong signal about how much you value partnering cannot be underestimated.
Why Should You Want To Become a CPO?
Great question! Being the CPO is one step up on the corporate ladder. It comes with some superpowers but also with responsibilities. You will have a seat at the senior leadership's table, which enables you to participate in important discussions, but also gives you access to the tools needed to navigate your organization toward success.
And, of course, you will become a very important ambassador for your company's partnership efforts. That means that you will need to be socially competent, great with media and the press, and great with partners. And remember that being candid and honest goes a very long way, as everyone will hold you accountable and remember your promises.
So What Does a CPO Do?
A CPO owns the strategy for all partnership efforts, as well as the execution of that strategy. This includes building and nurturing great relations with people in sales and marketing. The CPO might be alone or have a larger group of people reporting directly (or indirectly) to them, depending on the size of the company.
A CPO's effectiveness is multiplied when sales and marketing are aligned with the company's goal and efforts in partnering. The role of being both an internal and external public ambassador is extremely important, as that gives you a great deal of influence -- and that is perhaps your strongest superpower. Using that influence wisely will be instrumental in achieving your company's goals.
As mentioned, the CPO builds, sells and owns their company's partnering strategy. A large portion of the role is dedicated to this ongoing task. You can use internal and external resources to help, but as a CPO, you should have the right level of strategic knowledge and insights to build the strategy yourself. After all, you are the one that needs to sell it internally; the buck stops with you. That means a successful CPO will need to be a true master at partnering with relevant real-world experiences. It's hard work and should be treated as a long-haul venture.
The CPO role is gaining lots of interest. My guess is that this is not the last time we’ll heard about CPOs this fall.
Posted by Per Werngren on October 03, 20230 comments
For as long as I can remember, whenever we in the channel have talked about "P2P" or simply "partnering," we were referring to transactions that either went in a single direction (as is the case with resellers) or a bi-directional flow of deals.
Nowadays, however, people are talking about "ecosystems." What is an ecosystem of partners? As a Microsoft partner, we are all part of a worldwide ecosystem that circles around the concept of doing business with Microsoft and using Microsoft technology. But inside this ecosystem of more than half a million companies. There are smaller ecosystems that circle around either a geographical area, an industry/vertical, a technology, a type of practice or something else.
This is where the path to success lies -- being part of a smaller ecosystem. Unlike the ecosystems in nature, a partner ecosystem is not a food chain, where the stronger eats the weaker. Instead, a partner ecosystem should be about companies that enjoy working together and that see a positive financial outcome doing so.
A partner ecosystem is often built organically. There might be both active and inactive participants. Most of the business (i.e., revenue) will, over time, be handled between the ones that trust each other the most and where the involved parties earn the most money with the least effort.
But what vendors are really dreaming about is building a channel and to be the center of their own sub-ecosystem.
I see a shift in the market where we see a newly found interest for indirect business models. Some of the larger vendors have understood that the cost for selling direct is much higher than when building a healthy channel of partners that acts as either resellers, agents or ambassadors. The knowledge and market contacts that partners got are crucial for success and is hard to replicate. Recent announcements from Dell and others are just the beginning of this trend.
I also see a big increase in support within our ecosystem. Like mushrooms popping up in the woods, there are more communities and boutique firms than ever that are offering help to partners trying to build their channels. We see networks like the well-established International Association of Microsoft Channel Partners (IAMCP), a couple of highly active networks for women, networks for African Americans, dedicated learning companies providing training, podcasters, advisory boutique firms and members-only communities that run their own conferences.
The demand for help is high and there is business for everyone; the tide lifts all boats. Lots of the DIY advice is free or comes at a minimal cost, but if you want someone to do it for you, you'll pay for the gig. I see a newly found willingness to pay for these services, and this itself is proof that the level of interest in building a channel is high.
We've also started to talk more seriously about the need for CPOs, or chief partner (or partnership) officers, as a way to give more weight to the strategic endeavors of working with partners. In many organizations, the task of partnering falls under the VP of sales, but perhaps elevating it to a separate CPO role makes sense if you're really serious about it. Alliance managers should report to CPOs. In my mind, this will be a highly sought-after role given the impact it has. Recruiters have probably already started to look for savvy CPOs as it seems to be this year's hottest new position.
As we enter fall, it's certainly springtime for ecosystems of partners and for CPOs.
Posted by Per Werngren on September 11, 20230 comments
Customers often need multiple partners. The more a customer grows, the more partners it is likely to need and have. Smart customers know that a single partner cannot do it all, and that it isn't wise to rely too much on just one dominant partner, so they end up with an ecosystem of partners in various business areas or geographies. Some partners transact goods like licenses and hardware, but most partners supply various types of services -- and their paths are likely to cross yours now and then.
Traditionally, the holy grail for partners was to become a customer's single "trusted advisor" that influences everything. Perhaps some partners still dream about that. However, nowadays there are often several trusted advisors for various parts of a customer's needs (which makes sense as partners become more specialized to be successful).
As a modern Microsoft partner, it is important to enthusiastically work together with the other partners that your customers have chosen. Collaboration between other partners that are part of your customer's ecosystem is crucial. But collaboration alone is not enough; you need to put your soul into it -- and you should encourage, or perhaps demand, that the other partners do the same. True collaboration doesn't mean complicated or costly, and it doesn't mean having meetings in which each partner sticks to their entrenched positions. Instead, true collaboration means finding the best alternative for your common customer.
I myself have been in meetings where the larger partner tries to freeze out a smaller partner by making things overly complex or trying to grab every opportunity for themselves. I've also seen partners of the same size try to win more business by discrediting each other. This isn't the way.
The best protection against losing a customer is to ensure that they're a happy customer -- and therefore it's crucial for that customer's partners to help each other. You and your team should make every effort to eliminate friction and ensure that all partners are successful. Your customer will love that approach and it will lead to more business opportunities.
So how do you make this happen? Setting up meetings once a month with a recurring agenda is a great way to start. The extent of the customer's engagement with their group of partners determines how long each meeting will take; it can be anywhere between 30 minutes to two hours. Whom to invite will depend on the nature of the engagement -- don't make the groups too large! Taking notes is encouraged but don't make it too formal. And speaking of not being too formal, it doesn't hurt to break bread together once in a while so that you really get to know each other. Familiarity is an underestimated way to success.
In these meetings, take the opportunity to discuss new services and solutions that the customer might need. Discuss it first between yourselves. If, collectively, you see a potential ROI for the customer, then present your initiative to the customer. Just remember that it doesn't hurt if the new business opportunities are evenly spread over time between the partners in the group.
And don't bill the customer for your meetings unless he asks you to do it!
Another piece of advice is to have a "hotline" so that problems in collaboration with your mutual customer get escalated to senior people that can take immediate action. There's no better way to de-escalate than to pick up the phone and talk to your counterparts. If all parties see the long-term value, then problems are often easy to resolve. And solving problems together builds trust.
Becoming a master at orchestrating partners is an art, but it reduces the risk for both partners and customers so it makes sense to invest time to make it happen. When both customers and other partners see you as easy and friendly to work with, you'll generate positive buzz that transforms into more business opportunities for your company -- and that's probably the best ROI you can ever dream of.
A successful relationship with other partners, even if it was only a mutual customer that brought you all together, opens the avenue to finding more joint customers together. After all, you have at least one success story to talk about. So go make friends with your customer's partners and build success together!
Posted by Per Werngren on May 17, 20230 comments
Networking and collaboration might seem fluffy; how can just talking to people be a real job? But in fact, successful partnering happens between people and organizations that trust and like each other. We see many so-called P2P efforts being wasted because there's no genuine interest from the parties involved to make it a mutual success. True and successful partnerships are created when all parties are looking out for each other's well-being and when the level of trust is high.
The networking aspect is a key component here. The channel ecosystem consists of several communities. Sometimes they intersect and sometimes they're isolated and exclusive. A community can be formal with a structured way to membership, but it is more often unstructured. Some communities are online, some are offline and many are a mix of both. Everyone that has an interest can participate.
Your customers might have their own communities, but increasingly, customers and vendors are participating in the same communities. These channel communities are the often the best way to find both partners and customers -- and they're growing in importance. If you join them, you'll need to make sure that you and your company are considered relevant. It's paramount that you contribute to these communities with true value and that you're not just pushing your own services and products.
Channel communities are a great arena for learning about key trends and different technologies, making new acquaintances and getting closer to specific industry vendors. Perhaps the most important benefit of investing lots of time in channel communities is that you will find companies to partner with -- and you might also find customers to serve. Every vital and active community has one or more thought leaders that drive the community forward. By being generous, knowledgeable and active in these communities, you can become a thought leader yourself.
It's important to constantly bring content to your community. All communities need to be fed with content, as that creates topics for discussion. You can deliver webinars that focus on knowledge-sharing. You might even be able to sponsor events at cost depending on the type/size of the community and the event. Sponsoring a get-together for a few people in a local bar is obviously less costly than a premier-level sponsorship at a big vendor's conference.
My point is, the value of a community is the sum of everyone's contributions. It's important to have a "giving" mindset and constantly strive to create value for the community. Taking an active part in communities should be a key component in every alliance manager's list of duties.
Don't limit community involvement tasks to just the alliance manager, though. Instead, make sure you do a thorough analysis of which communities you want to invest in and send the best-suited people to each community. Some communities need technical people, others need marketers and salespeople, or perhaps C-level people. For important communities, send multiple people with different backgrounds and seniority to gain the best outcomes. And don't forget, your "elevator pitch" needs to be thoughtfully written and well-rehearsed so that everyone can deliver it without hesitation. Read more in this article, "The 7 Pillars of a Strong Partner-to-Partner Relationship."
The list of channel communities is endless and constantly changing, so I'm not going to attempt to list them all. My advice is to make sure you have a structured approach and that you and your team participate in the ones where you find it meaningful. Invest a lot in the ones that are core to you -- and then add some more when it makes sense. Just remember that it will take time before you see traction, so wait awhile before you evaluate your participation. In my experience, it goes quicker in social media-based communities and takes longer in communities that meet in-person. However, the most strategic value is often in the groups that meet face-to-face and that occasionally also meet in-person.
Whatever direction you choose, making sure that you engage with various channel communities in a structured and thoughtful way is a job to be taken seriously and will give great return on investment. When you are an active and appreciated contributor in channel communities, doors will open to new partnerships and to winning new deals. In my opinion, investing in communities is the best thing you can do as a partner. Just don't forget that it is a long-haul flight.
Posted by Per Werngren on April 17, 20230 comments
We're now four months into the Microsoft Cloud Partner Program (MCPP), which succeeded the old Microsoft Partner Network (MPN) and went live on Oct. 3, 2022.
I have loved this evolution right from the start. I have felt for some time that the old MPN program was a bit dated and no longer relevant. Partners were constantly testing its boundaries to qualify for Gold competencies, and customers had long stopped paying notice.
The new MCPP is, in my mind, more in-tune with the times and better addresses how customers buy and consume their IT services and solutions today. I think the MCPP's six solutions areas -- Data & AI (Azure), Infrastructure (Azure), Digital & App Innovation (Azure), Business Applications, Modern Work and Security -- better frame the different practice areas that a partner of today might have in the era of cloud computing. On top of these, there are specializations and expert programs for the partners with an even deeper knowledge in certain areas.
I have been part of Microsoft's various partner program changes during my years as a channel insider, and the switch from the MPN to the MCPP represents a natural evolution. Case in point: The concept of collecting points, which is a staple of today's MCPP, comes from an older Microsoft partner program code-named "Octane" from over 15 years ago.
My point is that once in a while, Microsoft will have a discussion with its partners, the result of which is sometimes a new version of its partner program. This is a rhythm that has been going on since the 1990s. And it makes sense; it's important to always improve, making adjustments as the rest of the world changes.
When then-channel chief Rodney Clark announced the MCPP last March, some partners expressed concerns that it would be harder to qualify in the new program as a Solutions Partner compared to the old Gold qualification. I didn't see that as negative, though, because the value of a Gold competency was hugely diluted. To me, one of the main problems with the old MPN was that there was very little useful differentiation between competency levels. I personally welcome a higher bar for standards so that partners have something to strive for and customers have an easier way to determine who has true expertise in a certain field. The old program had become way too easy for the partners that wanted to become Gold-certified.
Some partners said this was a downgrade for them. They feared the cost of losing their benefits. Perhaps they also feared they would no longer have a prominent badge. There have been concerns about the MCPP from partners servicing smaller customers and who tend to be more generalists than specialists. I've also heard concerns from ISVs.
My response to those concerns is that I am certain modern partners will find a place in the new MCPP. Others partners, especially those with legacy business models, should perhaps see this shift as a wake-up call to modernize their businesses. After all, Microsoft is just trying to address the changes in the market; likewise, partners need to evolve if they want to continue to be successful.
The MCPP's six solution areas give valuable insight to business leaders in our community. Partners that invest in any of these six solution areas will stand a decent chance of being in a growth area that will help support their practices. They will also be aligned with Microsoft's priorities, which has huge value: They can piggyback on Microsoft's investments to win in the marketplace.
What we have seen in the MCPP's first four months is the same pattern we've seen many times before. As partners learn about this new version of the partner program, they start to feel more at-ease and capable of planning to obtain their new status within the revamped program. The larger partners have found it easy to make the changes, though smaller ones will need time to achieve the right number of customers, revenue and certifications to reach the minimum required partner capability score (70 points out of 100) to become an MCPP Solutions Partner. Microsoft's decision to allow partners to keep their old benefits, like Internal Use Rights (IURs), was welcomed by the partner community, as it gives partners time to qualify for their desired level in the new program.
When I talk to partners in my network from all over the globe, I sense that most of the more successful ones are on track to adapt to the new MCPP. The key is "less is more." Partners need to specialize in a certain solutions area, instead of trying to fit too many. Being specialized attracts customers who want the best partner in a certain area. It also attracts the right hires. The new MCPP is great for the partners that embrace specialization as a strategy. If you're a generalist, you will find it hard to achieve 70 points in any solutions area -- and I think that's a good thing.
What I foresee is that Microsoft and its partners will educate customers on what it means to have a Solutions Partner badge. As customers understand how it works, it will be easier for them to create a shortlist of the right set of partners to solve their challenges.
I have personally always embraced change in the various iterations of Microsoft's partner programs, and I know that each evolution creates profitable opportunities for the early adopters. This generation will most likely follow the same pattern: They will create and enjoy wonderful new opportunities.
Posted by Per Werngren on February 13, 20230 comments
Nobody has missed the buzz around the chatbot ChatGPT created by OpenAI. This is exciting, and acts as an easily accessible consumer-friendly showcase of what can be done with artificial intelligence.
Microsoft is clearly seeing the light around AI. It has supported OpenAI since 2019 and is now, according to the press, in negotiations to acquire a large stake in the business. We all anticipate that AI will change our world and people's private and professional lives.
AI will need lots of compute and storage power, which makes it a high-potential revenue driver for the Microsoft cloud. Automation through various robotized solutions is also part of AI -- a market that is already huge, and growing.
The great news is that Microsoft partners can benefit from this. Partners should look at this from at least two perspectives, one externally facing and one internally facing.
First, your customers are dreaming of AI-driven solutions, so your job is to help them understand what they need and to deliver it to them. They need a partner that is a trusted advisor, understands their business and can help them figure out what they need. Like car manufacturing icon Henry Ford famously said about the development of the Ford Model T, "If I had asked people what they wanted, they would have said faster horses." AI presents an important opportunity for partners to assist customers in understanding what they need and want.
The low-hanging fruit is in helping customers automate mundane, everyday tasks; gain efficiencies from higher-quality processes; cut costs because fewer people are needed; and speed up response times with better results for end customers. Automating a process that is rarely used doesn't make sense, so instead put your focus on where you will make the most impact and create the highest ROI for your customers.
Partners should consider either building a separate AI practice or mandate that existing practices make a plan for how to add AI in their offerings. This goes not only for professional services practices but also for ISVs and others.
If your business is geared toward a certain industry, you will benefit by having a deep understanding of the processes that are vital for these customers. (If you don't already have the right people for this, you should consider recruiting seasoned experts.) Microsoft Power Platform is a great set of tools when creating magic for your customers but you will need expertise in more technologies to become successful.
Reach out to your existing customers and start the conversations, document your successes and let your marketing team tell the story.
Second, implementing AI in your daily operations will give you benefits that are similar to what you aim to provide for your customers. There are many areas where you can make good use of AI internally. GitHub Copilot from Microsoft can help your software code development work by shortening your development cycle, increasing your quality and significantly reducing cost.
Other areas where AI makes sense internally are in your customer service desk (where you can use chatbots to automate part of the support conversations) and for monitoring your compute resources in the cloud and on-premises (where you can also automate many actions that need to be taken).
The cost of running your business can be significantly lowered if you embrace AI to the fullest. We all know that margins are slim, so any savings are welcome -- and huge savings are warmly welcome! Start small and experiment with AI. Build your knowledge and perhaps recruit a few experts if you don't have the right people already. Make sure that you keep AI at the core of your business decisions and establish internal processes for your senior management team to track the progress and to measure the outcome.
My core message is that you cannot afford not to embrace AI, because your competition will. AI will be a fantastic enabler. There's still time to jump on the train to the future, but some cars have already left the station and you don't want to be the last one out. As always, it makes sense to work together; discovering areas for partnering around AI is a great topic around which you can build alliances and partnerships. Good luck!
Posted by Per Werngren on January 23, 20230 comments
I'm often engaged in conversations with Microsoft partners around how to structure partnering arrangements -- often called P2P, or partner-to-partner, relationships.
Many partners come to me either on the brink of starting their partnering efforts and wanting to know how to build their strategy, or after they've been doing P2P for a while but don't feel that it's working for them.
I genuinely believe that partnering is a great way to drive long-term success. It involves lots of investments and time, but when you do it right, it will give you a great ROI. Partnering not only gives you additional revenue, but it also encourages you to specialize -- another characteristic that I truly believe has its merits for partners, as the days of "Jacks-of-All-Trades" are long gone.
However, if a partnering arrangement is not successful for all parties involved, then it will eventually die, either slowly (because none of the parties care about it anymore) or violently (because one of the parties says that enough is enough and just terminates the agreement). In order to build lasting P2P arrangements, you'll need to have the right mindset, be generous and look after the success of all parties.
Here's a list of what I think makes a strong P2P relationship. It's based on my experiences serving the partner ecosystem for many years, and seeing both tremendous successes as well as quite a few failures.
- Margins: It's important to have a reasonable margin that motivates the efforts around both making the sale and also managing the ongoing relationship.
- Suggested margin is 20 percent for projects/assignments for year one and 10 percent for additional years.
- Suggested margin is 20 to 30 percent for SaaS and licenses for year one, and 10 to 15 percent for additional years.
- It is important that the partner that takes the burden of doing the actual selling gets a decent margin so they can compensate and motivate their sales teams.
- Prime Partner: One of the partners should have the legal agreement with the customer. This partner is the "prime partner" (or "originating partner").
- Documentation: Always document the terms of your partnership. It doesn't need to be complicated, and the Partnering Agreement Template I've created is a great starting point (it's also an official IAMCP template). For every project and assignment, I strongly recommend that you create a Statement of Work (SoW). It's easy to forget to document the terms of doing business or to save it for later, but it's crucial when you bring in more people in both organizations, as it provides an important safety net for all parties.
- Elevator Pitch: Make sure you have a partnering-friendly elevator pitch and practice it so it comes naturally -- even if someone wakes you up in the middle of the night. You shouldn't brag about your company; instead, it should be about what you're bringing to the table in a partnership and articulated in a way so that people want to bring you in. This is art in itself; don't feel embarrassed to practice with your co-workers. Everyone in your company that has conversations with partners should use the same pitch.
- Bi-Directional: It's important that both partners strive to sell each other's services. This is not always possible, but the mindset should be to help each other's bottom-line profits. Partnerships often fail when one partner thinks they are superior and don't care for the other partner. It needs to be a two-way partnership in order to last!
- Visibility: Be proud to show the customer who your partner is and don't try to hide it. Customers love partners that bring in other specialized partners, while still taking responsibility.
- Conflicts: If a partnership is going to survive long-term, you'll need to take care of potential problems early. You'll need to measure and discuss both customer and partner satisfaction regularly so you keep your customers happy and eliminate unnecessary friction. And be generous and help each other! Remember, you're in it together.
Here are some useful assets that will help you standardize:
- The IAMCP's Partnering Agreement Template package (which includes Partnering Agreement Template Instructions, the Partnering Agreement Template and Discussion Questions for Partnering).
- The P2P Maturity Model endorsed by IAMCP and IDC.
Posted by Per Werngren on December 28, 20220 comments
I have been part of the various iterations of Microsoft's partner program since the 1990s. Microsoft has done a great of job of staying relevant with its partner program through the years.
Last week, the company decided it was time to make a major overhaul, announcing that the existing Microsoft Partner Network (MPN) will become the Microsoft Cloud Partner Program effective Oct. 3, 2022.
Our ecosystem has changed a lot since the MPN saw the light of day over a decade ago. On-premises computing is gradually going away, and partner characteristics have changed a lot. Today, we host our solutions in the cloud, and nobody really spends much time on physical infrastructure; all of that is handled by the dominant cloud vendors, who deliver compute from industry-scale datacenters that span the globe. Customers buy a combination of SaaS and bespoke applications hosted by themselves, or a partner, in the cloud. And, thanks to the low-code/no-code revolution, applications (or "apps," as we now call them) can be built faster and better than ever before.
A dilemma of recent years has been that customers haven't been able to differentiate between partners based on their MPN competencies or rank them based on whether they have Silver, Gold or even a higher level of specialized certification. One reason for this difficulty is that many competencies in the MPN were too broad and perhaps not really customer-facing.
The announcement of the Cloud Partner Program last week by Rodney Clark, Microsoft corporate vice president and chief of channel sales, was a welcome one. It will have six solution areas that I think makes sense:
- Data & AI (Azure)
- Infrastructure (Azure)
- Digital & App Innovation (Azure)
- Business Applications
- Modern Work
- Security
The MPN's Gold and Silver designations are going away. Instead, partners will be given the title "Solutions Partner" at the base level, and can opt to qualify for further specializations and advanced programs. This makes it easier for partners and, perhaps even more important, for customers, as they will be more likely to find the solutions that are relevant to them than they could under the old competency system.
Partners earn their designations by proving that they have great customer growth, the right skills, revenue and more. The new system to quantify these factors is called the Partner Capability Score, or PCS. It takes a PCS of 70 (out of an available 100) to qualify for a single solutions area. The points system reminds me of an older version of the Microsoft partner program (internal code name "Octane") from a decade ago, when partners also collected points, but this time it is much better-structured (although I was also a fan of the old scoring system).
Microsoft has put lots of effort into thinking about how to not hurt partners in the transition and give them ample time to make the switch to the new program. For instance, it said that the highly appreciated Internal Use Rights (IUR) benefit will remain, but under the new name of "Product Benefits."
I've always believed that the bond between partners and Microsoft is indeed a true partnership. Partners that invest in Microsoft long-term and strategically will most likely find that Microsoft will do the same with them.
In the new Microsoft Cloud Partner Program, it will be easier for Microsoft to see which partners are driving tangible business growth around the various Microsoft offerings, and they can support these partners even better because their goals are well-aligned. That's a great foundation for a fruitful partnership.
Posted by Per Werngren on March 22, 20220 comments
It's now time to close 2021 and look forward to 2022. Our industry -- and our channel ecosystem -- has re-innovated itself during the pandemic, and we can take pride in having helped people change the way they work.
For 2022, the digital transformation will continue. In many ways, the pandemic has accelerated digital transformation, but the opportunities are still endless. We have only just skimmed the surface; beneath are whole industries that need to transform, and partners with not only technical knowledge but also the right business acumen will become heroes.
Here are my predictions for what partners can expect in the coming year.
- I predict we will see people return to their workplaces but probably not for the entire business week. There will be continued demand for hybrid work environments and online collaboration platforms that give an equally great experience for people working remote as for people sitting in a traditional office. From Microsoft, we will see a huge momentum for Teams, Power Platform and Dynamics to support the transformation, and partners should make investments in these areas. Power Platform, in particular, will continue to build momentum, and partners that bet on building a verticalized practice using this set of tools will become hugely successful.
- Partners will be able to deliver solutions to their customers much quicker than ever before, but it will be important to have deep knowledge of the needs of certain industries (verticals). Customers are increasingly demanding ways to transform their operations from manual to automated through artificial intelligence and machine learning -- that's a game-changer. There is a need for partners that can come up with ideas for what to automate.
- We will most likely see the rollout of mobile 5G, enabling new scenarios where devices are always connected. IoT will get a boost from this, which will benefit ISVs. It'll be well worth watching how Azure Edge Zones will gain traction in the marketplace and take advantage of the 5G boom.
- Microsoft partners that have made a living out of the Cloud Solution Provider (CSP) program will continue to do so, but transacting licenses will not be enough. Partners need to come up with innovative services that add value and differentiation, where the CSP licenses are only a small part of the overall offerings. Microsoft's New Commerce Experience (NCE), which is being rolled out in 2022, has many characteristics similar to Azure Plan and Enterprise Agreement, and it harmonizes the way Microsoft transacts licenses. As with everything new, it'll take a while to learn the ins and outs, but I am sure that partners will learn how to use NCE to their advantage -- just as they have always done with every new licensing evolution.
- The market for cybersecurity is unfortunately growing, as more attackers are orchestrating ransomware and other types of attacks. Most have a commercial angle, and it looks like it's a profitable business (if highly illegal). There's a strong demand among customers for help in preventing attacks. We need more Microsoft partners to focus on building cybersecurity practices around this so that the "good guys" can become stronger and -- at some point -- the attackers become more likely to give up, as the cost of doing business will be too high.
- Hosters will continue to face problems with their existing business model unless they evolve and become modern MSPs that don't try to hold on to legacy datacenters. They should stop their investments and plan to decommission existing hardware and move to the Microsoft Azure cloud. The core asset for a modern MSP -- or virtual hoster, as I love to call them -- is to manage workloads. Owning your own datacenters is a thing from the past.
- The trend of using other partners and individual contractors will continue. Partners appreciate having the ability to build virtual teams with specialized individuals regardless of location or employment status. This makes partners able to move faster and adapt to changes in customers' needs quicker. Hiring gets easier when you can be more flexible with location and care less whether the hiree is on your payroll as an employee, an individual contractor or employed by one of your partners. Flexibility will give you more options to work with the world's top talent. This is a new dawn for partner-to-partner (P2P). More companies understand that P2P is a great way to grow business and build stronger bottom-line profits.
- Leadership is evolving. We have taken giant leaps in the past two years, and we will continue to do so for the years to come. Modern leaders with less prestige, less ego, a genuine interest in diversity and inclusion, and are fans of flexible hours will thrive and attract top talent to work with them. I use the words "with them" instead of the traditional "for them" as that sends an important signal.
- Lastly, I hope that we will go back to physical large conferences again like Microsoft Inspire. Of course, conferences will take learnings from the pandemic and offer hybrid experiences, where people can either travel and meet in-person or participate remotely from the comfort of their homes.
Posted by Per Werngren on December 22, 20210 comments
I got the first alert at 11:40 a.m. EST on Oct. 4 that there were problems with Facebook. As it's not business-critical for me, I didn't pay much attention -- but I did get puzzled when I couldn't connect to WhatsApp, as that is indeed a critical tool for me to interact with my different teams around the globe.
We've now learned that the outage lasted for six hours and involved not just Facebook but also services owned by it, like Instagram, Messenger, WhatsApp and Oculus VR. This was a costly outage for every business that depends on these services, and it shows how business-critical these social media resources have become.
Having led a large multinational hosting business, I know that sometimes problems occur that affect uptime. And any CEO in the hosting or managed services business knows that such incidents can have a big impact on reputation. Most outages aren't as big as the one that affected Facebook this week, but sometimes they are devastating.
Some problems should be expected, and you can take reasonable efforts to prepare for them. According to Facebook, the outage originated from an upgrade of routers. The ensuing problems shouldn't have been a surprise for anyone who works with infrastructure.
What is a surprise is that so much was connected to these routers. Not only did all of those customer-facing services go down, but Facebook's own e-mail system and a bunch of other internal systems -- including the entrance to the Facebook office building -- stopped working. To put it mildly, it looks like Facebook made the mistake of putting all of its eggs in the same basket and not following best practices for an enterprise-class online infrastructure.
Here's some advice not only for Facebook, but for everyone -- including partners -- running and managing business-critical infrastructure:
- Segment your infrastructure so that a problem doesn't spread across your whole environment. Your administrative network should be separated from the network where your customer-facing systems reside. Even if you're not as big as Facebook, separate your different services into several networks. This will also help security, as it will make it much harder for attackers to bring your entire environment down.
- Plan your upgrade. Make sure that it has been thoroughly analyzed and vetted. The higher its potential to impact business, the more you should plan and analyze prior to the actual upgrade taking place. Make sure that you have a decent change-management process in place.
- Never upgrade everything if you can avoid it. Simulate the upgrade in a test environment, then start the upgrade with something less business-critical than a system that is used by 3.5 billion users. The "big bang" model of upgrades fails way too often.
- Make sure that you know how to roll back an upgrade quickly and safely. Learn the right procedures for how to make it happen.
- Rehearse frequently so you know what to do when something goes wrong. It's like a fire drill; you should have procedures and protocols to follow.
- When all of your services are up again, make sure to create a written incident report and discuss the findings inside your organization. This is how my old company learned from past errors. Our mantra was that the same problem should never happen again.
Hope this will help you to prepare for the unexpected.
Posted by Per Werngren on October 05, 20210 comments