Mike Hadjadj, a retail and SaaS expert, has just published a book (in French) called SaaSpocalypse. Every year, he supports two to three hundred start-ups as a mentor, advisor and investor, mostly in the retail sector. In his own words, he isn’t predicting the end of software vendors, but he does see their value being hit hard by the changes AI is bringing. I interviewed him to understand what this shake-up means for vendors, their customers and the whole SaaS ecosystem. SaaSpocalypse Now! And The Value Drain Mike Hadjadj presenting his book SaaSpocalypse (in French) at the Visionary Marketing offices in October 2026 TL;DR With SaaSpocalypse, Mike Hadjadj isn’t predicting the end of software vendors. He’s saying the price of software is now negotiable. French e-commerce giant La Redoute rebuilt a €360,000-a-year tool in 48 hours using AI. Three factors can shield a SaaS vendor, namely urgency, value and stickiness. Big vendors are not spared. Some retailers have halved their Salesforce budget, or even cut it to a third. Gartner is looking in the rear-view mirror, while Mike is watching the 2027 contract renewals. His advice to vendors is simple. Talk to your customers now and ask them why they pay. SaaSpocalypse Now! or How to Build a SaaS Without Coding M.H. The book started with a chat at my physio’s. I’d had an accident and needed rehab. He’s a bit of a geek and told me he was setting up a new business line without buying any software or paying for a single SaaS subscription. Using Base44, a tool owned by Wix, he’d rebuilt a small CRM, a training tool and a small accounting and invoicing package himself. That intrigued me. I run La Retail Tech, a community that has been going for four and a half years, with lots of content and around 3,000 members. Our community platform was grossly outdated. It had stopped evolving and every small request was sitting in a support ticket for three weeks. We Dreamed It, and AI Delivered I don’t sleep much, so I gave it a go and I spent a few hours talking to an LLM, asking it to rework parts of the site and give it a modern look. I ended up with a front end, which I showed my team after the weekend. They recognised the site they’d been dreaming of. We had almost launched a tender, complete with requirements definition and technical provisos. That meant bickering over compromises with the team, because not everything is possible. With AI, everything is crystal clear. I talk and hey presto! It’s done. SaaSpocalypse Now! Mike Hadjadj during a demo for his community, La Retail Tech. Image by Optimalways I’ve kept going since the book came out. The front end is done and I’m now tackling the back end. The agent kept misunderstanding me, so I found another agent that handled my agent, which I talk to on WhatsApp. It knows my whole environment, runs the tests and writes very detailed prompts that I just copy and paste. I can’t code, and neither can my physio. So the question isn’t whether people can do it. It’s about who will still pay, for what, and where the value sits. That’s one of the book’s main stances. A French E-commerce Giant Rebuilt a €360,000-a-Year Tool in 48 Hours M.H. The other trigger was meeting French e-commerce giant La Redoute at an event. They used a visual product discovery tool, created by an Israeli start-up. The tool worked very well. Other French retailers used it too, such as Monoprix and Castorama, but you could tell it was nearing the end of its life. They were all looking for a replacement and asking me if I knew of one, before launching a tender. La Redoute put two people on it for 48 hours, with AI. They studied how the tool worked, rebuilt it, tested it and released it. The copy is better than the original, because they could tune it to their own environment, something that a software vendor seldom allows. La Redoute was spending €360,000 a year on the tool, now they don’t. SaaSpocalypse Companies of All Sizes Are Following Suit Digging deeper, I found out that companies of all sizes, including large ones with the right skills, are already going after commoditised tools that aren’t core to the business. If the tool falls over, it’s no big deal. The savings are huge. When I talk about value destruction, it’s because the rebuild cost nothing like the old price. Two days, two people, a bit of maintenance, updates, testing and tokens. There’s simply no comparison. A small part of the value shifts to in-house skills, and some is bought externally, at a very different price. Most of it is destroyed. There’s also a whole industry around SaaS spending. Agencies, consultancies, integrators and, above all, start-ups, which means funds and fundraising. If the pie shrinks, all of that ecosystem will be hit. Urgency, Value or Stickiness, What Protects a Software Vendor? M.H. I’ve been supporting start-ups for a very long time, as a mentor, an advisor, in incubators and accelerators, and as an investor too. Until now, I judged them on unwritten criteria, to decide whether I believed in them, wanted to back them or even invest. How innovative they were, how good the team was. That has changed, and I’ve come up with a new three-part test. The first criterion is urgency. The need has to be pressing, driven for instance by regulation or competition. The second is value, which must be blatant, immediate and measurable. The third is new to me, and it’s stickiness. This is what will refrain end customers or competitors from copying your product in a few minutes. SaaSpocalypse, an Innovator “Disrupted” by Its Own Customers In the book, I cite Smartway, a pioneer in the fight against food waste. Its software tracked the best-before dates of perishable products in stores, to decide when to pull an item from the shelf and what discount would guarantee a sale. A salad or a yoghurt might go at 22% off one day and 40% off the next. It first sold well to independent supermarkets and hypermarkets, whose owners are managing their own money. Then the central buying groups perceived the value of that piece of software. The IT divisions of the big French retailers, such as Leclerc, Intermarché or Carrefour, built more or less the same thing, which didn’t work as well but cost far less. It took them two to three years to get there. SaaSpocalypse, version 1. The author warns that “this book is best read quickly, as it may age badly.” The Better a Product Is, the More Likely It Is to Be Copied The difference is that today, the better your product is and the more widespread, the easier it is to copy. The bulk of the work is no longer the code. It’s modelling what you can help the customer earn, the processes, the interfaces. Smartway was smart, because it moved into other areas, such as fresh produce and ordering, with higher barriers to entry. Commoditised SaaS companies, on the other hand, are finished. The better they are, the faster they get copied. A young company with no stickiness will sell pilots, their customers will love the result and decide to rebuild the software. You can’t blame them. “The better your product is and the more widespread, the easier it is to copy” Mike Hadjadj For English retailer Save Your Wardrobe, stickiness is part of the equation. Its platform handles repairs for big leather goods and clothing houses, a field that’s still archaic. Anyone can digitise appointment bookings but Save Your Wardrobe also built and runs a network of approved repairers. They didn’t mean to do that at the outset. But now, it’s become a significant barrier to entry. Other barriers exist, such as standards and certifications, notably in payment systems and hardware. There is also external data customers need to buy to operate properly. Every vendor should ask itself why its customers wouldn’t have a good reason to copy its products. Are Big Vendors as Vulnerable as Small Ones? M.H. I was invited to talk about my book a few weeks ago at an event a vendor was hosting for its partners, on the eve of a trade show. I said not everyone would be hit in the same way. Small SaaS vendors would be hit straight away, while the big ones such as Salesforce would be hit later, and on core issues. The next morning, at the show, a friend told me a big brand had just cut its Salesforce budget to a third. That afternoon, the boss of another retailer told me he had renegotiated his contract and halved it. Mandatory Modules They Never Needed Their reasoning is simple. They were paying for mandatory modules they never used. Others were useful, but never quite satisfying. What interests them is the engine. They tell Salesforce, Oracle or SAP that they’ll only buy the engine, that they’ll rebuild the rest themselves by vibe coding, and that they therefore want the price divided by two, three or four. These big vendors aren’t stupid. They’ve understood that the value has shifted. I’ve worked for software vendors before, including one that pioneered CRM before Salesforce. All our value rested on two things. What we brought the customer, meaning process modelling, and how we delivered it, meaning the code, its robustness and its ease of use. To extend the product range, we were better off buying small companies than developing in-house, which would have taken years and cost a fortune. Between 1999 and 2006, we took over twelve small vendors, covering marketing, emailing and other functions. SaaSpocalypse and Why the Value Is No Longer in the Code Today, it’s the complete opposite. I show an agent an existing feature, ask for the same thing but improved, tailored to my needs, and it’s done almost before I’ve pressed the transmit button. The value is no longer in the code. It’s in the ability to express, visualise, project and model what you want. Anyone can writ