The SaaSpocalypse thesis still has to get past the customer's pen-testers

The approvals cut both ways. The column lists what a system has to survive inside a large enterprise: security review, regulatory sign-off, procurement policy, vendor risk assessment, data-residency requirements and an audit trail that has to hold up years later ^[7]. Six separate approvals ^[8], and the incumbent vendor already holds all six for its installed base.

The piece runs as an Entrepreneur contributor opinion ^[13], and the author writes from the selling side. "I've watched a security questionnaire kill a deal outright, and I've sat through a three-month infosec review that ended with the customer's own pen-testers hammering our product before a single seat was paid for," the author wrote ^[3]. That "our" places the author on the vendor side of the table. The column also says most of the end-of-SaaS takes on X/Twitter come from people who have never worked inside or sold into a large multinational ^[15].

The sturdier half of the argument is about incentives. Small founder-led teams buy software to make money or save money; in large organizations, the column says, the operative reasons are "cover my ass" and "make me a hero" ^[9]. "Nobody gets a bonus for vibe-coding an internal tool," it says ^[18]. The column carries no seat, renewal or churn figures, so it leaves open how often internal builds displace paid seats ^[19].

"A vibe-coded tool doesn't just carry technical risk. It carries an employee," the column said ^[10]. The manager who accepts one is then dependent on a single person. The piece puts that in HR terms: what happens when the employee asks for a raise, quits, or has to be managed out while remaining the only person who understands the system that runs procurement ^[14]. "You can fire a vendor. You can sue a vendor. You can put a vendor out to bid and get three competitors to undercut it," the author wrote ^[11].

Every example chosen sits inside the audit perimeter, up to the ERP that runs procurement, finance, staffing and operations at Frankfurt Airport ^[6]. The argument is strongest there. A nine-person team's project tracker skips infosec entirely, and that tier of spend is where the collapse thesis is easiest to believe.

For a renewal signed this quarter, that leaves the buyer where it was: the approvals exist, and the alternative is unreviewed. An agent that produced a plausible app over a weekend cannot sign a contract with a liability clause. It cannot be sued when something goes wrong, and it cannot stand in front of a regulator, the column said ^[12].