Before choosing how to build a small website, decide who will update it and what visitors need to do. A five-page business site and a five-step online tool can have very different requirements.
If you need to publish articles and change service pages yourself, WordPress is often a sensible starting point. If the main job is a particular customer workflow, a custom PHP application can be a good fit, provided someone can maintain it.
The number of pages tells you very little about the amount of work behind them. Here is how I would compare the options before committing time or money.
01. PHP and WordPress are different kinds of things
PHP is a programming language used to build web applications. WordPress is a content management system that runs on PHP, as its official hosting requirements make clear.
For this comparison, “PHP website” means a custom application built with PHP, and “WordPress” means the self-hosted software available from WordPress.org. WordPress.com hosting plans are outside the scope of this guide.
With WordPress, you start with an existing publishing system. With a custom application, you choose or build the pieces your project needs. That may include a framework, maintained libraries and third-party services. Custom development still involves reusing good software.
02. Choose WordPress when regular editing is central
WordPress includes tools for managing posts, pages, images, drafts and user access. Themes provide a starting point for presentation, while plugins extend its features. The official feature overview explains what comes with the platform.
That makes it worth considering for a business website where an owner changes service details, a publication with several contributors, or a portfolio whose content changes regularly.
A practical example
A tuition centre wants to update class timings, upload notices and publish admission articles. Those recurring editing tasks make a ready-made content dashboard valuable.
Check the actual editing experience before choosing a theme or page builder. Ask for a demonstration of changing a heading, replacing an image and publishing a new page. Those are the tasks you will live with after launch.
03. Consider custom PHP when the workflow drives the product
A custom application becomes interesting when your website needs to follow a particular sequence: collect information, calculate a result, take a payment, prepare an output and let the customer return to it.
You can shape both the customer screens and the admin tools around that sequence. The tradeoff is responsibility. Editing controls, access rules, recovery steps and integrations must be selected, built and maintained.
WordPress can also support specialised applications through custom plugins and integrations. Compare the effort of extending it with the effort of maintaining a separate application. An existing WordPress site that needs one extra feature may be well served by a focused plugin.
Ask the developer to show how the difficult parts will work, including a failed payment, an interrupted request or an incorrect submission. A working success screen is only one part of the product.
04. Compare the work you will actually need
Use this table as a planning guide. The final result depends on the implementation and the people looking after it.
On a narrow screen, scroll the table sideways to compare both options.
| What matters | WordPress | Custom PHP application |
|---|---|---|
| Everyday editing | A publishing dashboard is included. | Editing tools must be built or integrated. |
| Starting point | Useful when an existing theme and features fit the brief. | Useful when a specific workflow defines the brief. |
| Unusual features | Assess suitable plugins and custom extension work. | Assess application code, libraries and integrations. |
| Ongoing care | Plan updates, backups and checks for the chosen setup. | Plan code fixes, dependency updates, backups and checks. |
| Future handover | Document the theme, plugins and any custom code. | Document setup, data, integrations and admin tasks. |
| Real cost | Include setup, hosting, any paid licences and maintenance. | Include development, hosting, external services and maintenance. |
| Speed and usability | Test the finished pages on the intended devices. | Test the finished pages on the intended devices. |
05. A practical example: SurpriseLinks
SurpriseLinks is a custom PHP product for creating personalised digital gift links. Its main job is a customer journey: choose an occasion, add personal details, pay, preview the generated gift, approve it and share the published link.
The pages support different stages of an order. A preview is part of preparing a gift; the published page is what the recipient opens. That makes the flow a useful example when thinking about custom application requirements.
WordPress could support a similar product with appropriate custom development. A PHP application gives the developer direct control over how that particular flow is organised, along with responsibility for keeping it reliable.
If the brief were mainly to publish gift ideas and let an editor manage articles, I would give WordPress much more weight. The best fit changes with the job the site needs to do.
06. Budget for the months after launch
The WordPress software is free to use, but running a website still has costs. Hosting, setup work, paid extensions and ongoing help can all affect the total. A custom application has its own development and maintenance costs, plus any services it connects to.
Compare quotes against the same list of requirements. Ask what is included at launch, what renews, who handles fixes and how future changes are charged. A low starting price tells you little without that scope.
For WordPress, agree who handles updates and compatibility checks. Its upgrade documentation recommends taking backups before updating. For a custom application, agree who maintains the code and dependencies, checks errors and restores service when something fails.
Whichever route you choose, make sure you can access your domain, hosting, backups and essential project information. Ask for a short handover guide and a demonstration of recovery from a backup.
07. Evaluate speed and security through evidence
A custom build can keep its feature set small, but slow database queries, large images or unnecessary scripts can still hurt it. WordPress performance also depends on the chosen setup. Its performance guidance covers factors such as hosting, configuration, images and caching.
Ask to test the actual pages on a phone, including the main form or checkout journey. Compare what visitors will experience, using realistic content and the hosting you intend to run.
Security needs ongoing care with either approach. WordPress’s hardening guidance discusses keeping software current, access and other protective measures. Custom applications need appropriate controls and a maintenance plan for their own code and dependencies.
Ask who is responsible, how updates are checked, where backups are kept and how a problem is reported. The answers are more useful than a blanket claim that one option is always faster or safer.
Your decision checklist
- Who changes the content? Include the everyday tasks that person needs to perform.
- What is the main visitor journey? Describe each step, including what happens when it fails.
- Which features already exist? Check their fit before paying to rebuild them.
- Who maintains the site? Name the person or provider responsible after launch.
- What does the full scope cost? Include recurring services, maintenance and handover.
For a typical small site with regular publishing needs, I would start by assessing WordPress. For a focused online tool, I would compare a custom PHP application with a WordPress extension approach. For a rarely changing information page, a static website may be enough.
Write down the editing tasks, customer flow and maintenance arrangement first. Those details give you a much stronger basis for choosing how to build.
Official references
The comparisons and recommendations above are my practical assessment. These official resources support the platform descriptions and maintenance considerations. Reviewed on 1 November 2026.
More from the notebook
See how a thoughtful digital gift comes together.
Read the birthday surprise guideBack to all articles