{"id":14499,"date":"2026-08-05T10:00:55","date_gmt":"2026-08-05T04:30:55","guid":{"rendered":"https:\/\/gtm360.com\/blog\/?p=14499"},"modified":"2026-08-13T20:30:17","modified_gmt":"2026-08-13T15:00:17","slug":"saaspocalypse-now-part-2","status":"publish","type":"post","link":"https:\/\/gtm360.com\/blog\/2026\/08\/05\/saaspocalypse-now-part-2\/","title":{"rendered":"SaaSpocalypse Now – Part 2"},"content":{"rendered":"

In SaaSpocalypse Now – Part 1<\/strong><\/a>, we saw five updates on the SaaSpocalypse narrative:<\/p>\n

    \n
  1. SaaSpocalypse shaaspocalypse<\/li>\n
  2. Discounts ahoy<\/li>\n
  3. AI hits point SAAS hard<\/li>\n
  4. AI does more than coding<\/li>\n
  5. SaaS can do AI better than AI can do software<\/li>\n<\/ol>\n

    In this second part, we will cover five more.<\/p>\n

    6. New twist in the SaaSpocalypse tale<\/strong><\/p>\n

    The SaaSpocalypse narrative has so far posited that AI BUILD will replace SAAS \/ COTS BUY.<\/p>\n

    But there’s a new twist in the tale. Large companies are using AI not to build SAAS \/ COTS equivalents inhouse but to prune their existing SAAS \/ COTS estates. To take an example, the German automobile manufacturer Mercedes-Benz<\/em> used OpenAI<\/em> and Anthropic<\/em> LLMs to slash the number of its SAP instances from 1000 to 600.<\/p>\n

    \"\"<\/a><\/p>\n

    If this trend gains traction, it will cause a major loss of revenues for SaaS companies.<\/p>\n

    On a side note, I got a jolt when I read those numbers. Back in the day, when I used to sell a competing ERP product, SAP used to claim that R\/3 was so powerful, versatile, and robust that just a single instance of it was enough to run a large company comprising multiple SBUs – or even a conglomerate comprising multiple companies during the last month of its fiscal year!<\/p>\n

    7. Cybersecurity apocalypse<\/strong><\/p>\n

    The threat of AI to security software seems particularly severe and credible.<\/p>\n

    According to the popular narrative, the advanced models of LLMs from OpenAI and Anthropic will be able to scan a company’s IT landscape, find vulnerabilities, recommend fixes, and apply them automatically. Many cybersecurity software customers seem to be buying into this narrative. For example, Conga<\/em>, per The Information’s interview with the contract software firm’s chief information security officer Susanne Senoff.<\/p>\n

    I’m not surprised by this. Cybersecurity software has massive pain areas and is ripe for disruption.<\/p>\n

    In my 40 years of selling enterprise software, the number of security software categories – wholesale categories, not just products within a category – has exploded from 1-2 then to 20-30 now. Back in the day, there was antivirus software on desktops and firewalls for the enterprise network. Now there’s antivirus, firewall, FWaaS, NAC, SIEM, CASB, SWG, and so on. Some of them protect endpoints, others safeguard enterprise networks, private and public clouds. Each product secures just a tiny part of the enterprise’s IT landscape but costs a bomb. As a result, the current breed of security software is expensive, difficult to implement and bought only by large corporations.<\/p>\n

    If AI really works as advertised and finds vulnerabilities and patches systems automatically, I see it wiping out the entire cybersecurity software category and democratizing access to security for companies of all shapes and sizes.<\/p>\n

    \"\"<\/a><\/p>\n

    8. SaaS pushback<\/strong><\/p>\n

    Needless to say, SaaS vendors are not taking the threat of SaaSpocalypse lying down.<\/p>\n

    Some are levying a fees for enabling agentic access e.g. (i) Microsoft<\/em>, which recently announced that customers of Office365<\/em> and its other enterprise software products will need to purchase seats for both<\/em> human users and AI Agents (ii) HubSpot<\/em>, which recently announced plans to charge customers extra if they wanted external agentic AI access to its CRM database.<\/p>\n

    Others are blocking API access to unauthorized AI agents e.g. SAP, which does ot allow OpenClaw<\/em> AI agents to access its BAPI.<\/p>\n

    These pushbacks remind me of the SAP v. Microsoft <\/strong><\/a>and SAP v. Diageo<\/strong><\/a> cases from the 1990s and oughties respectively.<\/p>\n

    9. Skyrocketing token costs<\/strong><\/p>\n

    AI vendors recently switched from seat-based subscriptions to usage-based pricing. (Software Pricing Partners<\/em><\/a> has released a comprehensive list of pricing models for AI spanning AI Credits, Token Pricing, and so on.)<\/p>\n

    One immediate effect of the change in pricing model is skyrocketing of AI token costs for end users. Uber CTO reported that his company blew through the entire 2026 token budget in the first four months of the year itself. According to The Information<\/em>, Uber isn’t alone:
    \n<\/p>\n

    \n
    Many other firms are struggling to navigate Anthropic’s shift to charging customers based on token consumption, which has made it harder for them to gauge costs in advance.<\/div>\n<\/blockquote>\n

    Some companies report firing their AI Agent army and rehiring human workers!<\/p>\n

    If AI gets expensive, that may deter companies from SAAS Repatriation, especially given the other risks associated with the move.<\/p>\n

    10. SaaS is bracing for SaaSpocalypse<\/strong><\/p>\n

    While it’s maintaining a brave front and pushing back on the SaaSpocalypse narrative on the one hand, the SaaS industry is secretly admitting the threat of AI and bracing itself for the threat of apocalypse on the other.<\/p>\n

    SaaS giant Salesforce<\/em> has recently started isolating seat-based revenue into a new bucket. I see this as a hedge against the fall of its SAAS products by highlighting the growth of its AI products.<\/p>\n

    I’m not alone. Vernon Keenan, a software industry analyst who covers Salesforce, sees this as a “nod to the SaaSpocalypse threat”.<\/p>\n

    \n

    There are a lot of moving parts, some indicating that SaaSpocalypse is imminent and the others downplaying the impact of AI on SaaS.<\/p>\n

    Between the first and second parts of this two-part blog post, we’ve seen 10 factors. I judged each factor on its propensity for SaaSpocalypse. This is what I got:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    SLNO.<\/th>\nFACTOR<\/th>\nFOR \/ AGAINST SAASPOCALYPSE<\/th>\n<\/tr>\n<\/thead>\n
    1<\/td>\nSaaSpocalypse shaaspocalypse<\/td>\nFOR<\/td>\n<\/tr>\n
    2<\/td>\nDiscounts ahoy<\/td>\nNEUTRAL<\/td>\n<\/tr>\n
    3<\/td>\nAI hits point SAAS hard<\/td>\nFOR<\/td>\n<\/tr>\n
    4<\/td>\nAI does more than coding<\/td>\nFOR<\/td>\n<\/tr>\n
    5<\/td>\nSaaS can do AI better than AI can do software<\/td>\nFOR<\/td>\n<\/tr>\n
    6<\/td>\nNew twist in the SaaSpocalypse tale<\/td>\nFOR<\/td>\n<\/tr>\n
    7<\/td>\nCybersecurity apocalypse<\/td>\nFOR<\/td>\n<\/tr>\n
    8<\/td>\nSaaS pushback<\/td>\nNEUTRAL<\/td>\n<\/tr>\n
    9<\/td>\nSkyrocketing token costs<\/td>\nAGAINST<\/td>\n<\/tr>\n
    10<\/td>\nSaaS is bracing for SaaSpocalypse<\/td>\nFOR<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Here’s the final tally:<\/p>\n

    FOR<\/strong> SaaSpocalypse: 7<\/p>\n

    AGAINST<\/strong> SaaSpocalypse: 1<\/p>\n

    NEUTRAL<\/strong>: 2<\/p>\n

    TOTAL<\/strong>: 10<\/p>\n

    Although the tally overwhelmingly forecasts SaaSpocalypse, I think it’s still early days.\u00a0To quote Martin Peers<\/a>:
    \n<\/p>\n

    \n
    The impact of AI on existing software firms will take several years to play out, and some firms will come out of the transition better than others.<\/div>\n<\/blockquote>\n

    In other words, only time will tell!<\/p>\n

    PS: Given my rudimentary HTML skills, I’ve always found it difficult to make tables on WordPress. Before ChatGPT, I’d try to code them by myself. I’ve also tried some table plugins but didn’t dig the shortcode concept used by them. After ChatGPT, I started prompting ChatGPT for HTML code for tables of varying sizes for different blog posts. This worked reasonably well but it still took some manual tinkering from one post to another. I thought of another hack this time: I easily made the above table in Microsoft Word<\/em>, uploaded the DOC file to ChatGPT, and asked for the HTML code for an identical table in WordPress. ChatGPT gave me the code, which I pasted blindly in the “Code” view of WordPress editor without making a single change. The table you see above is the result. Mission accomplished!<\/p>\n

    RELEVANT READING:<\/span><\/p>\n

      \n
    1. Will ChatGPT Kill SaaS?<\/a><\/li>\n
    2. SaaS Repatriation \u2013 For & Against Faceoff<\/a><\/li>\n
    3. Three Immediate Consequences of SaaS Repatriation<\/a><\/li>\n
    4. Will ChatGPT Kill Systems Of Record?<\/a><\/li>\n
    5. \u201cWill AI Kill SaaS?\u201d Is The Wrong Question<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

      In SaaSpocalypse Now – Part 1, we saw five updates on the SaaSpocalypse narrative: SaaSpocalypse shaaspocalypse Discounts ahoy AI hits point SAAS hard AI does more than coding SaaS can do AI better than AI can do software In this second part, we will cover five more. 6. New twist in the SaaSpocalypse tale The … Read more<\/a><\/p>\n","protected":false},"author":4,"featured_media":14503,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,18,8,13,1],"tags":[],"class_list":["post-14499","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-b1-integrated-marketing","category-b2-product-v-services","category-it-marketing","category-product","category-mandatory-category"],"_links":{"self":[{"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/posts\/14499","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/comments?post=14499"}],"version-history":[{"count":13,"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/posts\/14499\/revisions"}],"predecessor-version":[{"id":14615,"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/posts\/14499\/revisions\/14615"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/media\/14503"}],"wp:attachment":[{"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/media?parent=14499"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/categories?post=14499"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gtm360.com\/blog\/wp-json\/wp\/v2\/tags?post=14499"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}