White-label audits for legacy PHP/Linux systems your agency did not build. Before your agency quotes changes, upgrades, takeover work, or long-term support, StackRefit helps you understand what the client actually has.
The audit gives your agency a clearer basis for scoping, pricing, risk communication, and next-step recommendations.
"The old system works, but we need changes."
"The original developer is gone."
"PHP needs upgrading, but nobody knows what will break."
"The WooCommerce site makes money, but the stack feels fragile."
"We need to take this over, but there is no documentation."
"The client wants AI features, but the foundation may not be stable yet."
| Question | What the audit clarifies |
|---|---|
| What runs where? | Application, CMS/framework, database, hosting, server, integrations, and deployment path. |
| What is outdated or unsupported? | PHP, database, framework, CMS, plugins, packages, server OS, and relevant dependencies. |
| What could break if we change it? | Upgrade blockers, compatibility risks, brittle areas, manual processes, and undocumented assumptions. |
| Are backups useful? | Backup presence, location, retention, ownership, and whether restore has been tested or documented. |
| Can we deploy safely? | Staging status, version control, CI/CD, manual deploy steps, rollback options, and operational gaps. |
| What should happen first? | 30/60/90-day modernization roadmap ordered by risk, effort, and business impact. |
The goal is to make the system understandable enough to discuss risk, quote responsibly, and modernize without immediately forcing a rebuild.
GBP pricing can be quoted for UK agencies at proposal stage.
| Package | Best for | Typical scope | Starting price |
|---|---|---|---|
| StackRefit Audit Lite | Small WordPress or PHP sites | One application, basic hosting review, short risk summary | From €750 |
| StackRefit Agency Audit | Typical inherited agency client systems | Application, CMS/framework, hosting, backups, deploy path, roadmap, white-label summary | From €1,250 |
| StackRefit Audit Plus | Larger WooCommerce, Laravel, custom PHP, or VPS-heavy systems | Deeper infrastructure review, integrations, more complex roadmap, implementation options | Quoted after scoping |
A StackRefit Audit is intentionally bounded. Production changes, upgrade work, stabilization, and implementation are scoped separately after the audit.
StackRefit can remain invisible to the end client, appear as a named specialist partner, or support your team during a client review call depending on the relationship and scope.
Support your agency's takeover recommendation.
Quote legacy work with fewer unknowns.
Give the client a calm explanation of technical risk.
Create a roadmap before asking for larger modernization work.
Reduce pressure on senior developers when the system is outside your usual comfort zone.
Preserve the agency relationship while using specialist legacy-stack depth.
Clarify system type, business context, deadline pressure, known risks, and whether the audit is white-label, agency-branded, or direct.
Collect repository, CMS/admin, hosting, SSH, database, backups, deployment notes, and contacts with read-only access preferred.
Review the agreed system surfaces without making production changes.
Deliver concise findings, assumptions, risks, and recommended next steps.
Join a review call, prepare a stabilization proposal, or help turn the roadmap into phases if useful.
Before quoting changes to the existing system, we are arranging a technical audit of the current stack. The purpose is to understand what runs where, which versions and dependencies create risk, how backups and deployment currently work, and what should be addressed first. This helps us avoid guessing, reduce production risk, and recommend a practical modernization path instead of pushing unnecessary rebuild work.
Most audits take 3-7 business days after access and scope are confirmed. Larger or more fragmented systems may need longer.
Not always. Repository access, CMS/admin access, hosting notes, backup information, and staging are often enough for the first pass.
No production changes are made during the audit unless a separate written scope and approval process is agreed.
Yes. The report can be prepared for internal agency use, as a white-label client-facing document, or as a named specialist report.
No. The best time to audit is before a system breaks, before a risky upgrade, before a takeover, or before quoting a new phase of work.
No. StackRefit starts from the assumption that old systems often contain valuable business logic.
Inherited systems are risky when nobody knows how they work, what they depend on, or how safely they can be changed.