It's Wedding Season in the Microsoft Channel.

You may recall from "Microsoft Gave You the Directions. Your Delivery Model Determines the ETA" that one of the calls to action was “Build alliances, specialize, consolidate.”

Well, here we are.

Private equity is buying into the Microsoft channel. Roll-ups are underway, MSPs are moving into Business Applications, and BizApps firms are being acquired. Microsoft is rewarding specialization, ecosystem partnerships, and “Frontier” AI capability over generalists. The field is consolidating, fast.

So yes — it’s wedding season. Microsoft style.

Having spent a decade in M&A, I have a box of “deal toys” in my basement. Lucite tombstones, with the deal value and investment bank etched on the front, presented at closing. The signed deal, the announcement, the champagne — sigh. What a beautiful wedding. But nobody makes a paperweight for what comes next. The marriage. Waking up with a champagne headache while your blended family argues over DoorDash options. The wedding is an event. The marriage is where the earnings projections and value-add promises come true. Or don’t.

Which brings me to the seating arrangements.

In one scenario, both parties sit at the head table: aligned, prepared, and full of promise. Due diligence was thorough. Leadership is unified. The transition plan is documented. Teams were brought into the loop as soon as it was safe, and everyone knows what happens next.

In the other scenario, the party is happening back at the kids’ table: sparkling grape juice, scattered silverware, and a lot of wishful thinking. The deal team nailed the numbers, polished the launch plan, and assumed the blindsided sales and delivery teams would “figure it out.” Eventually.

Which table you sit at isn’t decided by the deal. It’s decided by the strength and style of your leadership, the quality of your due diligence and the maturity of your operation heading into it. Just like AI, the merger won’t fix your leaky structure. It will magnify it. Resulting in a very short honeymoon. In separate rooms.

And if you want to keep your seat at the head table, the first ninety days matter. Customers and teams understand that integration takes work. But they won’t “pardon the dust” for long. The faster you create clarity for teams and continuity for customers, the faster the deal starts behaving like the opportunity it was meant to be.

From a delivery perspective, I recommend the following guidelines:

Give Every Department a Seat. Early. A merger or acquisition, depending on size and scope, is a massive undertaking when done right. And the hardest part isn't the plan. It's trust. For a lot of the C-suite, the real struggle is bringing leaders to the table the moment it's legally safe, instead of holding the circle tight out of habit. I understand the instinct. But the ones most often blindsided are the practice and delivery leads. The exact people who could have added the most value to the execution and de-risked the whole thing. Leave them out and you don't just lose their trust, you lose everything they would have caught.

So trust your leadership team to speak for their people. Get every function represented early: delivery, sales, support, finance, HR. Then map a go-live plan and execute it with the same vigor you'd give your most important customer's go-live.

Planning a wedding takes a hundred details. Building a foundation for a strong marriage takes even more.

Champion One Company. One Experience. The customer experience and reaction to change will almost wholly depend on two things. Timely and clear communication about the change and continued progress on their project, no matter where the project originated. Confusion and uncertainty at the customer level is where trust and loyalty erode. Changes to systems or tools should be communicated before they happen and executed as part of a standardized plan. And the details matter. One set of vocabulary, one look, one UI. If the change is met with resistance, stay the course. You chose those details for a reason. Grandfathered “carve-outs” should be rare. Since most projects run for months, even years, granting exceptions stalls the AI gains and economies of scale your forecasts assume.

This guideline applies internally as well. One company. One set of rules. How leadership handles escalations will set the tone. If Mom says “yes” after Dad already said “no,” it does not make the family more flexible. It makes them easier to split.

Modernize the Knowledge Transfer. If your project data lives in a single source of truth you can use AI to pull historical details and organize information so resources can focus on a customer’s “secret sauce” or issues requiring immediate attention. Pair that with a fully adopted and standardized implementation framework updated in real time and the entire picture becomes clear in short order. Internal transition meetings can be saved for the “human” stuff — like understanding working styles, pet peeves, past grievances, things that add the cherry on top of that seamless customer experience.

One caveat: don't let knowledge transfer drag on. Set a deadline and monitor it. Like any delivery meeting, it needs an outcome-based agenda and clear owners.

Protect Backlog. Empower Resources. Start preparing your delivery system and loading resource data even before the deal is done so your delivery team can hit the ground running on day one. Empowering resources to perform actionable work to drive customer outcomes should be the #1 priority for delivery out of the gate. Period. Make sure everyone has access to tools and environments. When two teams merge, “transition” often becomes months of a “dance off” where no one bills, projects stall and your resource planning returns to the dreaded cocktail napkin. Don’t let it. There’s no reason your early utilization numbers need to tank if you keep your eye on the ball.

Turn Change into Leverage. Change opens a window where bold moves feel expected instead of disruptive. Don’t waste it. Be proactive with resourcing. An acquisition brings new talent, so if projects are humming along in the green, let them ride. But if a project is yellow or red, this is the moment to bring in a specialized skill set and turn it around. A thoughtful look at your portfolio lets you frame midstream resource changes or solution design enhancements as timely opportunities. Because they are. You did this deal because the whole will be greater than the sum of its parts — this is where you prove it.

Of course none of this matters without an Established foundation, Disciplined operations, strong Governance and a plan to Elevate everyone into happily ever after.

See what I did there? Without the ModernOps EDGE, have fun picking macaroni and cheese out of your hair at the kids’ table.

— Let’s elevate! DGM