WATCH · Software Delivery_
The ‘We’ll Just Use WordPress’ Trap (When It’s Right and When It’s Not)
Saleem Beg · Founder, Teque
● 1:42 · Posted 4 months ago
KEY TAKEAWAYS_
- WordPress is brilliant for content sites, blogs, brochures, and WooCommerce
- If 30%+ of your requirements need custom code, WordPress is probably wrong
- "Can WordPress do this?" vs "Should WordPress do this?" — very different questions
TRANSCRIPT_
We'll just use WordPress. Might be the most expensive sentence in software. Don't get me wrong, I love WordPress. My agency builds with it constantly for content sites, blogs, brochure sites, even e-commerce. With Woo Commerce, it's genuinely brilliant. But here's where it goes wrong. When people try to turn WordPress into something it's not. I've seen WordPress twisted into CRM systems,
booking platforms, membership portals, multi- vendor marketplaces, and every single time the client thought they were saving money by using free software, they weren't. They were buying a cheaper foundation and then spending three times as much building custom functionality on top of it. functionality that fights against WordPress rather than working with it. And here is my test. If more
than 30% of your requirements need custom code or plugins doing things they weren't designed for, WordPress is probably the wrong choice. The right tool for the job isn't always the one you've heard of. Sometimes it's Laravel or a headless CMS or yes, sometimes it actually is WordPress. The question isn't can WordPress do this? It can do almost anything with enough plugins. The
question is [snorts] should WordPress do this? And that's a very different conversation.
“If more than 30% of your requirements need custom code, WordPress is probably the wrong choice.”
Prefer to read? This take is also a written article.
Read the article →
