What We Build and Maintain in PHP
- corporate and service websites with an admin panel for editing content;
- online stores, either on established platforms or custom-built for a non-standard catalog and pricing;
- portals for customers, dealers or partners with documents, orders and history;
- internal systems: request tracking, calculations, management reports;
- backends and APIs for mobile apps and for data exchange between services.
When PHP Isn't the Right Choice
We don't force PHP where it doesn't belong. Another language makes more sense if:
- the product is built around analytics, machine learning or data processing, where Python and its libraries are stronger;
- you need a real-time application, such as chat, collaborative editing or live updates, and the team wants one language on the server and in the browser, so Node.js is worth considering;
- the website is a blog or a few company pages edited by a marketer: custom development is overkill, and WordPress will do (it's also PHP, but you'll hardly need to write code).
Framework, CMS or Plain PHP
For new projects with custom logic, we recommend a framework such as Laravel or Symfony: the code stays predictable, and any developer who knows the framework can get up to speed quickly. A CMS (WordPress, OpenCart, Drupal) is the faster route when the task is standard. We use plain PHP only for small scripts, because a system built to last for years is hard to hand over when its structure was invented by a single developer.
Taking Over a Project Built by Someone Else
Often the job isn't a new website but an existing one: the previous developer is gone, there's no documentation, and the site still needs to grow. We don't suggest rewriting everything right away. First we assess what can stay, what should be replaced gradually and what is genuinely dangerous.
Often it's enough to upgrade the PHP version, remove dead code, move settings out of the code into configuration and cover the most important scenarios with tests. If the system is large and outdated, we move it to a new foundation piece by piece; learn more on our legacy system modernization page.
Databases, Integrations and Support
PHP projects most often run on MySQL, MariaDB or PostgreSQL. When a PHP website is slow, the cause is usually unnecessary database queries or missing indexes rather than the language, so the database is where we start troubleshooting.
Typical integrations we build: sync with QuickBooks, CRMs, payment services, UPS, FedEx and USPS shipping, email marketing, and supplier price list imports. After launch we can stay on for support: updating PHP and libraries, monitoring errors and adding features.
What to Prepare Before Kickoff
- For an existing site: access to the code repository, the server and the database, plus any documentation.
- A description of what the system must do and who will use it, including roles and key scenarios.
- A list of the external systems it needs to connect to, with API access where available.
- Information on who changed the project before and how, if you know it.
What Affects Cost and Timeline
- Type of work: a new project, enhancements or untangling someone else's code. The last is hard to estimate upfront, so we start with an audit.
- Amount of logic: how many user roles, documents, calculations and statuses the system has.
- Code condition: PHP version and whether there's a framework, tests and documentation.
- Integrations: the number of external systems and the quality of their APIs.
- Load and security requirements: number of users, data sensitivity, backups.
After an audit or a discussion of your project, we show you an estimate broken down by phase, so you can see what you're paying for.
Frequently asked questions
Isn't PHP outdated? No. The language is updated regularly, and major services and popular CMSs run on it. Specific code can be outdated, but not PHP itself.
Will you take on a website built by another team? Yes. We review the code and the server first, then tell you honestly which parts are solid and which will need to be rewritten.
Why upgrade the PHP version if everything works? Old versions don't get security fixes, and new libraries and modules won't install on them. The longer you wait, the more the upgrade will cost.
Which is better for a new project, Laravel or Symfony? Both are reliable. Laravel is usually faster to get started with, while Symfony is more often chosen for large, long-lived systems. We recommend one after discussing your project.
Should we rewrite an old PHP website in another language? Rarely. A rewrite from scratch is slow and expensive, and business logic is easily lost along the way. It usually pays off more to clean up the existing code and replace problem areas gradually.
Can you keep supporting the project after the work is done? Yes. We update PHP and libraries, watch error logs, fix issues and add new features as your needs change.
Why Promodex
PHP is one of our core languages: our portfolio includes AGER, Avanta Medical Center, Booking Health and JustVPS, part of 750+ projects since 2015. The code is written by in-house developers who work alongside designers, marketers and SEO specialists, so one team can build your website and promote it. Before we change anything, we explain what changes and why, and after launch we keep the project updated and improving.