Most of the sites in our portfolio are not WordPress at all. BusinessPulse, RoadshowHub, Primos Maternos, East Coast Utility, Identity CoAnalyst and the Atlantic Watch band site are hand built in HTML, CSS and JavaScript, on a mix of platforms and tools chosen for each job. MuniHub, on the other hand, runs on WordPress. So a fair question we hear is: if you can build anything, when is WordPress still the right choice?
The honest answer is that the website is rarely the hard part. Running it, and keeping it easy for your own team to update for the next five years, is.
What WordPress gets right
- An admin people already know. Millions of people have used the WordPress editor. Your staff can add a page, fix a typo or publish news on day one without training on a system we invented.
- Content as the center. Pages, posts, media, revisions, scheduled publishing, drafts and user roles are built in and battle tested. Rebuilding those well in a custom app takes months.
- No lock in. WordPress is open source and runs on almost any host. If you ever part ways with us, any competent developer can pick it up.
- A huge ecosystem, used sparingly. When a genuinely hard problem comes up, someone has usually solved it already. We just choose carefully.
- Cost. For a content focused site, WordPress gets you a reliable admin and publishing workflow for a fraction of the cost of building one.
Where WordPress falls short
The common complaints about WordPress are real, but most of them come from how it is usually set up, not from WordPress itself: heavy page builders, dozens of plugins, bloated themes and dashboards full of upsell banners. That is why we strip it back, write our own theme and features, and treat it like the application framework it can be. The result keeps the familiar admin and drops the clutter.
When we build custom instead
Some projects are applications first and websites second. When the core of the job is a workflow, a calculation or data that changes by the second, a custom build gives a better experience:
- Interactive tools, like the AI search snapshot in BusinessPulse.
- Transactional platforms with approvals, audit trails and analytics, like RoadshowHub.
- Apps where every screen is tailored to a specific role and task.
Even then, the two often work together. WordPress can manage the marketing pages, articles and help content, while the app handles the specialized work, sharing sign in and design so visitors never notice the seam.
WordPress as the AEO layer around a custom app
Custom apps are often nearly invisible to search and AI assistants. Their best screens sit behind a login, are drawn by JavaScript after the page loads, or change with every visitor. An answer engine has little to read and nothing stable to quote.
A lean WordPress site wrapped around the app fixes that. It becomes the public, crawlable home for everything an answer engine wants:
- Plain answers to buyer questions, one page per question, in the words customers actually use.
- Guides, glossaries and how to articles that show expertise and give AI tools something worth citing.
- Structured data describing the organization, product, articles and FAQs, added automatically.
- Case studies and news that marketing can publish the same day, without a developer or an app release.
The app keeps the interactive work and the polished experience. WordPress does the talking, on its own subdomain or under the same domain, with matching design and shared sign in so it feels like one product. It is often the fastest way to make a custom product show up when buyers ask AI who to choose.
The question we actually ask
We do not start with a platform. We start with who will use the site, who will update it and what it must do. If the answer is mostly publishing and persuading, lean WordPress usually wins. If it is mostly doing, we build an app. Often it is a bit of both.
Tell us what you are planning and we will give you an honest recommendation, even if it is not the bigger project.
Comments