Keep the Plugin’s Knowledge, Not the Platform

SF Scott Farrell • October 3, 2026 • scott@leverageai.com.au • LinkedIn

You can keep what WordPress plugins learned. You don't have to keep WordPress.

Most leaders treat these as one decision. They aren't.

Plugins do real business work: payments, forms, CRM syncs, bookings. The directory lists over 69,000 free ones, and the popular payment and form plugins run on millions of sites. That scale hides something valuable. Years of chargebacks, abandoned carts, duplicate notifications and angry customers are encoded in that code.

Take one payment detail. Stripe can send the same "payment succeeded" notification twice. A good plugin knows this and makes sure the confirmation email fires once, the booking is marked paid once, the CRM updates once. A fresh build written from a clean spec misses that until a customer gets charged, emailed or booked twice.

That behaviour is the valuable part. The PHP wrapper, the shared runtime, the plugin update roulette and the settings buried in database tables only one vendor understands are just packaging.

For most of the web's history you couldn't separate the two. To get the knowledge, you installed the runtime and paid the platform tax forever. AI changes that. An agent can open several independent implementations of the same integration, compare how each handles failures, retries and state, and then check the current provider documentation before anything gets built.

The discipline matters. A plugin is evidence, not authority. It can be outdated, insecure, or designed around assumptions your business doesn't share. Code that shows up everywhere isn't automatically correct. Copying it isn't the goal. Learning what it learned is.

And a narrow deposit flow is not a replacement for a full commerce engine. Existing data, security controls, safe deployment and maintenance still need an owner. Unbundling moves those costs. It doesn't delete them.

So the question about your platform has changed. It used to be "do we still need these plugins?" Now it's "which behaviours must we preserve, and is this platform the only way to keep them?"

If you can't list those behaviours, you're not ready to leave. If you can, staying might just be habit.

Originally posted on LinkedIn


Discover more from Leverage AI for your business

Subscribe to get the latest posts sent to your email.

[rpnnrecommend total="5" thumbnails="false" class="recommendedlist" ]

Leave a Reply

Your email address will not be published. Required fields are marked *

© 2026 Leverage AI, Scott Farrell. All rights reserved. This content is made available on a limited, revocable, read-only basis only. No licence or right is granted to copy, reproduce, republish, scrape, store, adapt, summarise, index, embed, or use this content to create derivative works, work product, deliverables, methodologies, training materials, prompts, templates, software, services, research, or commercial outputs, whether by humans or machines, without prior written permission. This restriction includes internal business use, client work, consulting, advisory, implementation, and any use in or for artificial intelligence, machine learning, data extraction, retrieval, evaluation, fine-tuning, or knowledge-base construction.