Website builders such as Webflow, and content platforms such as WordPress, give you speed and easy editing. Custom code gives you control and room to grow. Choose by what the business will need the site to do in three years, because that decides which route stays cheap. We build on WordPress and in custom code as part of our web development service in Dublin, and most web design projects in Dublin start with this question.
What a platform build does well
For marketing sites and teams that publish without a developer, a well-built platform site is the sensible choice. The team edits its own content, rearranges sections without a ticket, and the build ships in weeks. It wins most clearly when the site changes every week.
We build most brand and marketing sites this way, on WordPress with Elementor, a lean base theme and a short plugin list. When a platform site is slow, the usual cause is a page builder loaded with add-ons, a dozen plugins and images uploaded straight from a camera.
Where Webflow fits
Webflow is a hosted visual builder: you design in the browser, publish to Webflow’s hosting and manage content in its CMS. It suits design-led marketing sites where the team wants precise control of layout without a developer for every change.
Check two things before you commit. The first is what leaves with you. Code export is only available on paid Workspace plans, and the exported code leaves out CMS content, ecommerce, user accounts and localised pages; site search and forms stop working on an exported site (Webflow Help Center). Collections can be exported as CSV files, so your content survives a move, but the working site has to be rebuilt. The second is the business logic. Webflow handles pages and content well, while bookings, member areas and billing rules need code that runs somewhere else.
Where custom code earns its cost
Once the site takes bookings, runs member areas or dashboards, or moves payments between systems, the platform’s convenience turns into a limit. Plugins approximate your process, and every workaround adds fees or fragility. Custom code matches the logic to the business, you own every line, and the cost stops growing with the number of records you hold.
The sign is usually a sentence in a meeting: “we do that bit manually”. A member is approved by hand because the plugin’s rules do not fit, or two systems are reconciled every Friday because neither talks to the other. Each is a recurring cost that custom software removes.
The five questions that decide it
1. Who edits it, and how often? If your team publishes weekly, the editing experience outranks almost everything else. If the site changes twice a year, it matters much less.
2. Does the business logic fit the platform’s assumptions? A standard catalogue, checkout and contact form fit a platform. Trade pricing tiers, approval workflows, multi-currency events and membership rules with exceptions usually do not.
3. What has to integrate? One or two well-supported connections are fine on a platform. A chain of systems that must stay in step with your accounts package or operations tool is where platform integrations become fragile. That chain is the job of business process automation, whichever platform the site runs on.
4. What does growth look like for you? For most businesses it means more products, user roles and rules, and platforms cope with extra traffic better than with complex rules.
5. What happens if you want to leave? Ask what you can export, in what format, and what a move would cost. If nobody can answer, you are paying a price you cannot see.
When a hybrid build fits
Many good systems are hybrids: a platform marketing site the team publishes freely, with custom engines behind the parts specific to the business, such as the booking flow, the portal or the automation.
ERP HEADtoHEAD works this way. It is a WordPress site the client edits, with a booking and payments plugin we wrote on WooCommerce and Stripe, set up to bill its Dublin and Birmingham events from their own companies in their own currencies.
A hybrid also lets the marketing site launch while the custom part is being built. Decide early which system owns which data, because hybrids fail when two systems both hold the master copy of the customer record.
What each option costs over five years
A platform build costs less to start, then subscriptions, paid plugins and workarounds that tend to grow with the business. A custom build costs more up front, then hosting, maintenance and someone available to change it; badly documented, it is harder to hand on than a standard one. Compare the two cost curves against where the business is going. Our guide to website cost in Ireland sets out the ranges, and the ecommerce version of this decision is in Shopify, WooCommerce or a custom build.
What you can take with you if you leave
Ownership means you own the code, content and data, the domain and accounts are in your name or transfer to you on request, and another developer could pick the project up. On a platform build, find out what is portable. On a custom build, insist on documentation and a code repository you control.
