Tangensys • Plan, deliver, measure
PHP development
Understand the current application before making changes. Legacy work starts with dependencies, hosting constraints and the business functions that must keep running.
The work to plan together
A scope shaped around this requirement.
- Code reviewScope
- Fixes and upgradesReview
- New featuresCheck
- Be foundSearch, maps and AI answers
- Be chosenClear pages and offers
- EnquiryCall, WhatsApp or form
- Follow-upYour team responds
In short
What does PHP development involve?
PHP development covers custom PHP applications and maintenance of existing PHP code, including legacy systems.
When PHP development is a useful fit
Businesses running older PHP systems
Understand the code and supported environment before promising a simple version upgrade.
Custom portals
Scope forms, permissions and integrations around the workflow the application must support.
Agencies
Define the exact maintenance or feature work and the staging checks your client requires.
Problems worth addressing first
Use these situations to identify the work that deserves attention before expanding the scope.
- Legacy code nobody understands
- Security updates are overdue
- Features need adding to an old system
A practical example
An older booking system can be upgraded in stages, testing booking and payment flows before changing the production runtime.
This is an illustrative scenario to explain the approach, not a claimed client project.
The work we can include
The final quote identifies the deliverables, quantities, approvals and exclusions. Select the work that serves your goal rather than assuming every item is required.
- Code review
- Fixes and upgrades
- New features
- Migration plans
Where we usually begin
Unsupported libraries, unavailable source code or unclear ownership may change the plan. We agree whether to maintain, modernise or replace the application.
Practical detail
Choose maintain, upgrade or replace with evidence
A legacy PHP site may still serve a useful business process. Review compatibility and the critical journeys before deciding that a complete rebuild is necessary.
| Part of the work | Example output | How to review it |
|---|---|---|
| Compatibility inventory | Runtime, framework, extensions and external connections | Unsupported dependencies and constraints are recorded. |
| Regression set | Login, enquiry, payment or other essential journeys | The proposed change does not silently break existing work. |
| Decision record | Maintain, upgrade or replace with reasons | Each option names its dependencies and work that remains. |
| Release recovery | Backup, restore and rollback instructions | The business knows how an unsuccessful release is recovered. |
For example, a small compatibility fix may preserve a stable workflow; extensive unsupported dependencies may justify replacement. The choice follows the review rather than a universal rebuild recommendation.
Separate a repair from a wider modernisation
PHP work may be a small, clearly defined bug fix, a new feature or a review of an older application. Those are different commitments. Start by reproducing the requested behaviour and identifying the relevant framework, runtime, database and hosting constraints.
A working but undocumented application can contain business rules that are not obvious from its interface. Capture those rules before restructuring code. A sensible first task may be a diagnosis and a small tested correction rather than a promise to rewrite the entire system.
Check normal, invalid and permission-limited cases for the changed feature. The handover should identify code changes, configuration dependencies and release instructions. Security findings and major upgrades require an explicit follow-up scope rather than being silently bundled into a minor repair.
Free technical review
Start with a clear scope and a practical next step.
Tell us what you want to improve and share the relevant website or project details. We will review the starting point, recommend a suitable scope and provide a custom quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Process
How the work is delivered
Review the starting point
Review the current setup, examples of the problem and the information needed to agree the work.
Agree scope and sign-off
Discovery covers existing code, users, data and external systems. We turn the main workflow into sign-off checks, then agree milestones and responsibilities.
Deliver and review
Changes are reviewed on a test environment before release. Handover includes agreed documentation, access and a maintenance route; ongoing support is separately defined.
Hand over the next steps
Review the agreed outputs together. Confirm what your team maintains and what needs a separate ongoing arrangement.
What progress should mean
Measures that match the work
Measure resolved defects, supported dependencies and regression checks. Keep a record of changes and a tested rollback route.
A record of delivery
See what was completed, reviewed and still dependent on access or approvals. Project delivery and business results are reported separately.
Clear limits in the data
We explain what can be verified and where a result is only an estimate. Contact clicks, conversations and sales are different actions.
Scope and responsibilities
You keep ownership of your business accounts and approved deliverables under the agreed contract. Any third-party licences, subscriptions or usage fees are identified before you commit.
Can you estimate an inherited PHP application without reviewing it?
Only a provisional range of effort may be possible from a description. A useful quote needs the issue, environment and relevant access. Discovery can identify whether the work is a local fix or depends on broader upgrades and undocumented integrations.
Does old PHP code always need replacing?
No. Its condition, supportability and business importance matter. A maintained application and an unsafe unsupported one need different decisions.
Can you guarantee an upgrade will not affect the site?
No change is risk-free. A representative test set, staging review and recovery plan reduce uncertainty and make the release clear.
Do you upgrade old PHP versions?
Yes, with testing before release.
How is PHP development priced?
We quote against your goals, current setup and agreed scope. The quote separates delivery from third-party costs and ongoing support. You receive a custom quote within 2 working days.
How long does the work take?
The timeline follows the size of the agreed scope, access, content and approvals. We confirm milestones in the quote; a simple change and a full implementation need different schedules.
How will we communicate?
Your point of contact agrees a review rhythm with you. We use email, WhatsApp and scheduled calls, with decisions and scope changes recorded clearly.
What do you need to get started?
Share your current website or system, your main goal and examples of what is not working. We then agree the access and information needed for discovery.
Is everything included in the free review?
No. The free initial review helps define the next step. Detailed research, design, implementation and ongoing support are included only when stated in your quote.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days