Get a quote

WordPress or a custom website: what the site has to carry

WordPress or a custom website is settled by what the site has to carry: pages only, or a request that has to be kept as well. Where the pages are the only thing changing and one kind of enquiry arrives in one inbox, WordPress is the right answer. Diotek opens a survey booking and a service call on separate paths, both recorded in the same application as the public pages.

The question usually arrives sounding like a technology question: should the company site be built on WordPress, or should we have it written for us? The answer is not in the technology. It is in what the site will carry: pages alone, or something your business produces that has to be kept. A site that carries pages is a site for WordPress. A site that has to keep an enquiry, or a catalogue drawn along your own distinctions, needs to be written.

Look at what the site has to carry

What decides between a ready-made product and custom software is whether the product and your business treat the same thing as one unit of information; we have written about that separately. A settings screen does not change that match. It adds fields without touching what the product keeps on its own.

On a company website the question becomes concrete in two places: the enquiry the site receives, and the products the site lists. Where neither has to be kept, the match is complete and a ready-made setup carries your work.

The corporate site where WordPress is the right answer

If what changes on your site over time is copy, images and the number of pages; if the site receives one kind of enquiry and reading the message tells you what it is; and if your customer details, orders or appointments already run somewhere else, then your site carries pages alone. WordPress is the right answer there. A custom build brings no gain; it brings one more codebase for somebody to maintain.

We write small jobs small too. The smallest web job in our portfolio is a menu page read at a table, on the reader’s own phone, in a few seconds: no orders, no payments, no stock behind it. The job set the size of what was written. Our own site went through the same test, and its pages are produced ahead of time because every visitor sees the same page; why we wrote no application for it is covered separately.

First reason for a custom build: requests travel apart

Diotek fits and maintains air conditioning systems, and two unlike requests arrive at its site. A survey booking is about a space: the right unit depends on the room, so somebody has to see it before a quote goes out. A service call is about a unit already running. Both used to arrive on one phone line, and when they piled up at the start of the season only a conversation could tell them apart, while a busy line left the site standing outside the flow as a shop window.

On Diotek’s site the two requests open on two separate paths. Each one sits in the same application and the same data schema as the marketing content, so a request sent after hours is written down instead of living in a phone note. Why the split belongs in the structure rather than in the form is the subject of separating appointments and service requests.

Second reason for a custom build: a catalogue on your own distinctions

If your product list sits on fixed pages and a visitor finds things by browsing, the catalogue is a stack of pages and you are on the WordPress side. If the list has to follow your own trade’s distinctions and a buyer has to compare with a filter, the catalogue is something the system keeps.

Plastik ve Makina is a classifieds platform for plastic processing machinery. Its category tree comes from the divisions inside a single machine family rather than sitting under a broad industrial heading, and new and used are one filter on the same list rather than two lists, so a buyer compares both inside a single search. The list is assembled on the server, and a changed filter redraws the results where they stand. Where a catalogue ends and ecommerce begins falls outside this page; the point here is that a product axis drawn along your own distinctions means the site holds more than a stack of pages.

The table below asks the same question row by row: what changes on your site, where an enquiry lands, whose distinctions shape the list, where that enquiry is kept, and whether a second system is coming alongside. If you stay on the WordPress side in every row, this page has nothing further to tell you. If even one row puts you on the other side, the site has something to keep, and building that is what the web development page describes. If you already run a site and want to look first at what it carries, that is where software consulting starts.

Side by side

Criterion The site where WordPress is the right answer The site that needs a custom build
What changes on the site over time Copy, images and the number of pages change; no new kind of information has to be kept. A new request type or a new catalogue distinction appears; what changes is not the page but what the system holds.
The kind of request the site receives One contact form feeds one inbox, and reading a message tells you what it is. Two different jobs land in the same inbox, and at the start of the season you sort them out by phone.
The distinctions in your product or service list The list sits on fixed pages and a visitor finds things by browsing. The category tree has to follow your own trade's distinctions, and a buyer has to compare with a filter.
Where a request ends up Arriving by email is enough, and the office keeps track of it. Every request, including one sent after hours, has to be written down where the content also lives.
The second system coming alongside No admin panel and no sales channel will be added beside the site. The visitor side and the admin panel have to share one foundation and one maintenance set.

Questions this decision raises

  • Can we start on WordPress and move to a custom build later?

    You can, and your pages carry over. What really moves is the decision about which information is kept on its own: a field the old site never held cannot be filled backwards, so it starts filling on the day you switch. Diotek has kept its two kinds of request on separate paths since day one, drawn into the structure rather than added to the pages afterwards. Note where each kind of enquiry lands on your current site and put that into the quote form.

  • We want to update the site ourselves. Does a custom build tie us to you?

    It does not; your editor changes every field the system defines, without asking us. The limit is not the editor's skill but which fields are opened to them, and a new kind of information is the point where we define it together. Çatalca Merkez Kasap edits a menu price on the page, and nobody reprints the code sitting on the table. We list the fields you will edit yourselves in the first conversation.

  • Requests reach us by email. Isn't that enough?

    It is, when only one kind of request reaches you; a quote that prices two intake paths has priced work you never asked for. It is not, when two different jobs land in the same inbox. Diotek receives a booking about a space with no unit in it and a call about a unit already running; both used to arrive on one phone line and were told apart in conversation. Look in your inbox: two jobs means the form is not what to discuss.

  • Why would a company that sells custom software tell me WordPress is enough?

    Because the same test decided our own site, and it put us on the pages side. The pages you are reading are produced ahead of time, since a service page and a project page look the same to everyone who opens them. The smallest web job in our portfolio is a menu page that takes no orders and keeps no stock; it was written small because the job was small. Run the table on your own site first.

Want to settle the decision together?

Tell us what you are choosing between and we will see which option fits.