PHP
PHP development
Most of what we build and run is PHP. Laravel for new applications, Adobe Commerce for large retail, WordPress where content and marketing lead, and a steady stream of older codebases that someone needs to take responsibility for. Our office is in Sydney and the team works across Australia and New Zealand.
What we do with PHP
Laravel for new applications
The default for anything we start from scratch: a strong ecosystem, a deep hiring pool in Australia, and conventions a new developer can read rather than a house style only we understand. Portals, internal tools, APIs and platforms that have to integrate with everything else the business runs. More on Laravel.
Commerce, which is PHP too
Adobe Commerce and Magento are PHP applications, and they are the most demanding PHP most businesses will ever own: large catalogues, complex pricing and integrations that reach into the ERP. That work lives on our Adobe Commerce page, but the engineering underneath it is the same discipline as everything else here.
Taking over what nobody maintains
Someone leaves, an agency relationship ends, or a system quietly becomes business-critical without anyone deciding it should. We take these on, starting with an assessment rather than a rebuild: get it running locally, find every system that writes to its database, and establish what is actually covered by tests. What the first two weeks look like.
Version upgrades that do not stall
Running past end of security support means any vulnerability disclosed after that date stays open on your server permanently. The upgrade is rarely one step: it is a chain of dependency bumps where each one moves something else, and the distance you are behind decides whether this is maintenance or a project. We will tell you which it is before you commit budget to it.
Performance work on applications that got slow
Slow PHP is usually not the language. It is an unindexed query, an N+1 that appeared when someone added a relationship, a cache that silently stopped working, or a third-party call in a request path nobody profiled. We measure before changing anything, because the alternative is paying for a rewrite that fixes a database problem.
Working alongside your own developers
The arrangement we most often recommend is one in-house developer who owns the system, with us alongside for the hard parts and the peaks. Code review, pairing, and the work nobody has time for. It is also the arrangement that leaves you least dependent on an agency afterwards, which we think is the right way round. See how that works.
When PHP is the wrong answer
Three cases where we would point you at something else, because pretending otherwise costs you more later than it costs us now.
Real-time, persistent connections, heavy concurrency
Live collaboration, streaming, chat, anything holding thousands of open connections. PHP can be made to do it and it is not what it is for. That is a Node conversation and we would rather have it early.
The problem is the data model, not the code
If the database cannot express what the business now does, a new framework inherits that intact and hides it behind nicer syntax. Fix the model first. It is less satisfying and considerably cheaper.
You need one small thing changed, once
If a contractor who already knows the codebase can make the change safely, use them. Bringing in an agency to learn a system for a single ticket is a poor trade for you, and we would say so.
The proof
Work we have shipped, not a capability deck.
- Aelia Duty FreeAdobe Commerce, which is PHP at its most demanding: duty and tax rules that vary by traveller, real-time inventory across seven airport stores in two countries, and SAP integration.Read the case study
- Intelsat Content PortalA structured content platform with entitlement and access control, built and maintained as a long-running application rather than a one-off project.Read the case study
- Booka for Venues NSWThe booking and event-management platform every stadium in the Venues NSW network runs on, including per-space scheduling and an audit trail.Read the case study

Ecommerce practice lead
Maxim Baibakov, Chief Technology Officer - Australia
Commerce work runs through a dedicated team rather than being picked up by whoever is free.
Common questions
Is PHP still a sensible choice in 2026?
For a large share of business software, yes, and the version matters more than the language. Modern PHP 8.x is fast, strictly typed where you want it to be, and carries the two most mature commerce platforms in the world along with the most widely deployed CMS. Where it is a poor fit is real-time systems with persistent connections and heavy concurrent workloads: that is a Node or Go conversation, and we would say so. The usual reason to move off PHP is a genuine architectural constraint, not that the language feels unfashionable.
We are on an old PHP version. How urgent is the upgrade?
Urgent if you are past end of security support, because you are no longer receiving patches and any vulnerability disclosed after that date stays open on your server permanently. The upgrade is rarely one step: it is a chain of dependency bumps where each one moves something else, and the work scales with how far behind you are and how much of the codebase is covered by tests. Two versions behind is routine maintenance. Six is a project, and it should be planned as one.
Can you take over a PHP application nobody currently maintains?
Yes, and it is a large share of what we do. A takeover starts with an assessment rather than a rebuild: get it running locally, find every system that writes to its database, establish honest test coverage, and identify the parts nobody can touch safely. Until those four things are known, no decision about the codebase can be costed. We have written up what the first two weeks look like.
Should we rewrite our PHP application or improve it?
Improve it, far more often than people expect. A rewrite restarts the clock on every bug the current system has already found and fixed, and it is usually reached for because the code is unfamiliar rather than because the architecture is wrong. Rewrite when the constraint is structural: the data model cannot express what the business now does, or the framework is unsupported and cannot be upgraded. Not because the code is ugly.
Do you use Laravel, or plain PHP?
Laravel for most new work, because the ecosystem and the hiring pool are both strong, and because it gives a team conventions rather than a house style nobody else can read. But a great deal of PHP we support is not Laravel: Magento and Adobe Commerce are PHP, WordPress is PHP, and plenty of business-critical applications are framework-free code written years ago that works. We support all of it.
Should we hire a PHP developer or use an agency?
Hire if the work is continuous and you can keep someone busy and learning: a permanent developer who knows your business is worth more than an agency over the long run. Use an agency when the work is bursty, when you need several skills at once, or when nobody in-house can review the code being written. The arrangement we most often recommend is neither: one in-house developer who owns the system, with us alongside for the hard parts and the peaks.
Trusted by
“I’ve worked with Michael and the Team for a number of years now on a web development project of strategic value to the University. Michael and the team work in deep partnership and are genuinely invested in the success of the project and the maximising the impact it can deliver to end users. Always exceeding expectations, you will not find a more amiable, grounded and technically proficient team!”
Kelly Whitney
WSU Associate Director; Careers, Talent & Organisational Success
“We partnered with Shakewell in 2024 to help improve and maintain our website technology. The team are friendly, diligent and routinely demonstrate a breadth of technical understanding that is hard to find. Their support has put us in a much stronger position to scale and enhance our web presence.”
Aidan Arentz
Digital Product Owner of Merivale
Engagement models
How we work
Four straightforward ways to engage us. Pick the one that fits, or mix them as your needs change.
Staff Augmentation
Add experienced Shakewell developers, designers or specialists directly to your own team. Engagements typically run three to twelve months, but can be as short or long as you need, you get the skills without the commitment and cost of hiring full-time.
About staff augmentationFixed-Scope Projects
Have a defined outcome in mind? We scope it, price it and deliver it as a project, a clear timeline, agreed milestones and a single point of accountability from kickoff to handover.
Embedded Delivery Teams
For larger or longer-running work, a cross-functional Shakewell team (development, design and delivery management) plugs in as your delivery arm, working to your priorities and your reporting cadence.
Support & Maintenance
Already live? We keep websites, stores and apps secure, updated and performing through ongoing retainers, business-hours support as standard, with 24/7 coverage available for critical issues.
About support & maintenance







