Q1. Could you start by giving us a brief overview of your professional background, particularly focusing on your expertise in the industry?

During my four years at AWS, I managed strategic partnerships with software vendors in the Public Sector, guiding them through the entire co-sell process—from APN enrollment and ACE pipeline setup to Marketplace listings and coordinating efforts with field teams like ISMs and PDMs. Before AWS, I headed customer success at SID Global Solutions, where I worked closely with the Google Apigee team to deliver digital transformation projects for Fortune 500 clients. Earlier in my career, I was responsible for a $20 million P&L account at UST Global. That journey gave me a unique perspective—I've experienced what it's like to be on the hyperscaler side, the ISV side, and the enterprise customer side. Most people only see one of those angles; having all three has been invaluable.

Q2. Software vendors in 2026 are heavily marketing GenAI and agentic workflows to justify premium pricing. On the ground, what percentage of these GenAI features are driving repeatable, long-term cloud consumption and ARR expansion versus short-lived, exploratory enterprise proofs-of-concept?

To be honest, the numbers don’t look great for most vendors. I’d estimate that only about 20–25% of GenAI features are actually leading to consistent, repeatable cloud usage and real ARR growth right now. The other 75% are still more about 'funded experimentation'—enterprises are spending money to show they’re innovating, but they’re not really rolling these features out at scale yet. The vendors that are actually driving real growth in cloud consumption have a few things in common: their AI features are seamlessly built into existing workflows (not just added on as an afterthought), they deliver a clear, measurable ROI tied to outcomes that customers care about, and they’ve set up their cloud usage to align with a hyperscaler’s co-sell motion—so there’s a shared incentive to grow together. If you’re missing any of those, your demo tends to stay just that—a demo.

Q3. How does co-selling with a hyperscaler differ when dealing with state, local, or federal agencies compared to commercial enterprises? Do isolated compliance networks (such as FedRAMP enclaves) accelerate deal velocity due to high barriers to entry, or do they severely constrain overall addressable market growth?

Things work very differently in the public sector compared to the commercial world. In commercial deals, speed mostly comes down to getting executives on board and having the right financial incentives. Those factors still matter for public sector deals, but the real hurdle is compliance. Getting FedRAMP authorization, IL4 or IL5 accreditation, or meeting ITAR requirements can add a year or more—sometimes 12 to 18 months—to an ISV’s go-to-market timeline before they even see any federal revenue. The new FedRAMP 20X pilot program is helping by cutting the Authority to Operate timeline down to about six months. When it comes to market size, I see things a bit differently than the standard view. Sure, FedRAMP enclaves do limit how many customers you can reach. But for those ISVs who make it through, the competition thins out fast—you might be one of just three or four qualified options in your space, instead of one of dozens. That kind of scarcity means you can command better pricing and enjoy more loyal, long-term customers. The barrier is high, but so are the rewards if you can clear it.

Q4. You drove co-sell execution across AMER, EMEA, and APAC. What are the cultural and structural reasons why a software vendor's cloud GTM might scale beautifully in North America but completely stall out in other regions?

There are three main reasons for this, ranked by how much they matter. First, there’s a misalignment of incentives. The AWS co-sell approach is really built around how things work in North America. PDMs in EMEA and APAC are spread thin across much larger regions with fewer resources, so they focus their energy on deals that are most likely to close and have strong executive backing. If a vendor doesn’t have a local presence or a champion on the ground, they almost never get prioritized.Second, the partner ecosystem just isn’t as mature outside North America. In the U.S., ISVs can tap into a deep network of GSIs and resellers who already know how Marketplace works. But in a lot of APAC markets, that network isn’t fully formed yet. If vendors don’t put in the work to build those regional partnerships before they launch, it’s almost like launching without any real way to get their product out there.Third, procurement culture. In parts of EMEA and APAC, multi-year committed spend instruments like AWS EDP or Azure MACC are less common or architecturally different. Marketplace private offers lose much of their deal acceleration value if the customer hasn't already committed to cloud spend; they're motivated to draw down.

Q5. For mature, legacy software vendors, how widespread is the risk that they will fail these rolling audits and face sudden badge deactivation, and how heavily does that disrupt their inbound lead velocity?

It's more widespread than the industry acknowledges publicly. AWS has tightened its rolling audit requirements regarding customer reference counts, revenue thresholds, and certified headcount. Legacy vendors who earned their badges in a less rigorous era often have compliance gaps they haven't addressed because no one within the organization owns remediation.

The impact on lead flow is real but tends to be gradual rather than sudden. Most ISVs don't rely solely on badge status for inbound. The bigger risk is deal-level: when a procurement team or a federal agency runs a partner compliance check mid-cycle, and the badge has lapsed, it creates friction that can stall or kill a qualified opportunity. I've seen it happen. The fix is clear, but it requires someone internally who treats APN compliance as a revenue-protection function rather than an administrative task.

Important Timelines

June 30, 2026, Deadlines

Partner Central 3.0 Migration: All partners must migrate their partner experience into the AWS Console. This requires linking a primary AWS account and updating IAM permissions. Missing this will cause issues renewing APN memberships.

AI Competency PRM Tagging: Partners holding the AWS AI Competency must have at least one AI service tagged under PRM by this date.

July 31, 2026, Deadlines

Partner Revenue Measurement (PRM) Compliance: The wider AWS partner ecosystem and eligible ISVs have converged on this date as the operational deadline to implement PRM on at least one eligible product listing. PRM is the attribution mechanism AWS uses to credit partner-influenced spend and is required to maintain co-sell visibility and funding

Q6. As an ISV scales its transaction volume through marketplace private offers, what is the true, fully loaded impact on net margins?

The headline number most vendors cite is the AWS transaction fee, which ranges from 3 to 5 percent depending on the tier. That's real but manageable. The fuller picture is more nuanced.

On the positive side, Marketplace eliminates a meaningful portion of procurement friction, accelerates cash collection, and lets customers draw down existing EDP commitments, which can compress deal cycles by weeks.

The margin pressure that surprises most finance teams comes from the cost of maintaining the co-sell motion: partner team headcount, MDF investments, enablement programs, and the co-sell execution tax in the form of deal registration, opportunity sharing, and the time required to manage ACE pipeline hygiene. When you load all of that in, the true cost of a Marketplace-sourced deal can run 8 to 12 percent above a direct-sourced deal. The calculus still works for most ISVs due to top-line acceleration. But CFOs who only look at the transaction fee are looking at the wrong number.

Q7. If you were an investor looking at companies within the space, what critical question would you pose to their senior management?

One question: what percentage of your net new ARR over the last four quarters was co-sell-influenced, and what is your hyperscaler field coverage ratio?

Most software companies can answer the first part. Very few track the second. Field coverage ratio measures how many of your target accounts have an active AWS or Azure PDM relationship associated with them, not just a co-sell opportunity logged. If that number is below 40 percent, the co-sell motion is largely reactive. You're waiting for the hyperscaler to bring you deals rather than generating them jointly. At scale, the difference between a reactive and proactive co-sell motion can represent 20 to 30 percent of net new ARR. That's not a partnership program. That's a revenue strategy. And if management can't answer that question with precision, it tells you something important about how seriously they're treating the channel.