What Information Do I Need to Review Your Existing PHP Application?
By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.
Published: · Last technical review:
To initially assess your PHP and MySQL application, I need you to explain what task it resolves, what bug or change you observe, and what outcome you expect, without sending passwords or sensitive data via the public form. I reply within 24-48 business hours and we agree on required access based on scope.
Criteria: a useful description rather than an improvised diagnosis
I suggest starting with a real task from your application. What were you trying to do? What happened? What did you expect to see? You do not need to translate this into a programming cause. If you do not know the exact technology of a component, note it as an open question. I prefer that we distinguish what you observed from what you assume before discussing a solution or a quote.
My maintenance offering is aimed at PHP and MySQL applications that you already have running. It includes security updates, backups, and bug fixes, with new features quoted separately. I cannot turn that general description into a diagnosis of your tool based on a single message. The initial inquiry serves to guide the review and specify what information would be required afterwards.
Proposed outline for your initial message
- What task the application resolves in your business.
- What operation presents the problem and how you observed it.
- What behaviour you expected, if you have a benchmark.
- Whether it is a bug, a maintenance concern, or a new feature.
- What questions you cannot answer yet.
- Whether you know who can authorise a subsequent review.
This is not a contractual intake checklist; it is a proposal to help you explain your case.
I suggest avoiding phrases that take a cause for granted: «the database is broken» can be replaced by what you actually saw. In a hypothetical example, «when checking the report, I cannot find a record I expected» makes it possible to formulate questions without blaming a component. I do not assert that this symptom exists in your application or that it has a specific solution.
What you can share and what I would not ask for right now
Do not send passwords, server keys, or third-party personal data via the public contact form: that first message serves solely to understand your need. Nor should you interpret an initial inquiry as authorisation for me to access your hosting or handle your data. You send credentials by email as outlined in the contract, and you must rotate them once the work is completed. The required access is specified for each review.
If you want to accompany the description with an example, I suggest that it contain no personal data, secrets, or internal information you should not share. You can explain what it shows without attaching the actual document. The purpose of this first message is to identify the problem and prepare the next questions, not to hand over a complete copy of the application via an unagreed channel.
Proposed editorial outline, not a system screenshot:
- Initial description: explain the problem without credentials.
- Clarification: separate the observed need from an assumed cause.
- Review scope: agree on what information and authorisations are required.
- Subsequent access: specify permissions and send them by email as outlined in the contract; rotate them once finished.
The contract specifies sending credentials by email and your obligation to rotate them once finished. The access inventory is agreed with you. If you do not yet know who holds the code or the hosting, I would note it down as information to be confirmed, not as proof that we cannot maintain the tool.
My own proof: a written process and direct contact
On my website, I explain that I start with a written diagnosis. We then define deliverables, timeframe, and budget before development. During development, I communicate directly with you and show functional progress for you to test. I also state that I maintain existing applications even if I did not build them myself. Those facts describe my offering and coordination, not an audit already carried out on your tool.
Assessing the state of your PHP application requires first reviewing your specific case. The initial inquiry is not equivalent to a compatibility report, a security review, or a commitment to take on any codebase. To discuss those matters, we need to determine what review is being requested and what evidence would be necessary.
When you should NOT ask for «a quote to fix everything»
If you can only say that something is failing, I would suggest first pinpointing a specific operation. «Fixing everything» does not describe a deliverable we can verify. If you also want new features, it is advisable to write them down separately. It is not about you needing to know how to code, but rather that we can differentiate an observed need from a set of expectations we have not yet defined.
Depending on your operational urgency, we can narrow down the initial review to a specific task that is currently failing, or prepare a broader maintenance and evolution inventory. The first alternative defines a single question; the second requires agreeing on which areas will be reviewed. I do not assert that either is sufficient without knowing your case, nor that either includes automatic changes. Both diagnostic scope and intervention scope must be explained.
You do not have to gather everything before writing
If you do not know a version, the provider, or access to the code, you can say so. I suggest not inventing that information or attempting to obtain permissions you are not authorised to hold. Starting with an honest description makes it possible to agree on what is missing. I do not take for granted that everyone who uses an application can authorise changes, share its data, or hire its maintenance.
How to prepare the scope discussion
To structure your initial message, indicate that you have an operating PHP/MySQL application and separate what you need covered as periodic maintenance from what new features or deliverables you want quoted. I suggest using these questions to organise your message, not as a substitute for a review. If you have identified both types of needs, describe them separately and add which task you need to understand first.
From that message, I would suggest distinguishing what we can clarify in writing from what requires an authorised technical review. I would not promise a definitive diagnosis from reading a screenshot or a fixed price without knowing what is included. My published process establishes the budget and timeframe on a project-by-project basis. The next useful step is a readable need, not a password sent in haste.
What to set down in writing when you do not yet know the cause
I suggest ending the message with what you need to clarify, rather than an imposed solution. You can state that you do not know whether the issue affects another operation or what information will be necessary to review it. You can also separate what is urgent for your operations from an enhancement you only wish to assess later, without turning that priority into a delivery deadline. That closing helps frame the next discussion without feigning a diagnosis or sending sensitive information to rush a review we have not yet defined.
What to send first and what to reserve for later
I suggest using this distinction to prepare your message without exposing access credentials. It is an initial content guide; permissions are specified for your application and credentials are sent by email as outlined in the contract.
| What to include in your first message | What to reserve for the secure channel agreed afterwards |
|---|---|
| Public URL, if available, and the task resolved by the application | Internal addresses and access to private environments |
| Role under which you observe the issue, without identifying individuals | Technical users and authorised administration permissions |
| Steps to reproduce it without sensitive data | SSH, database, or administration credentials |
| Expected outcome versus observed behaviour | Complete copies of the code, database, and configuration |
| Anonymised description of an affected document | Personal data, private documents, and third-party secrets |
If the URL contains a token or private information, do not include it as is. Describe the screen without sharing the sensitive link. If a screenshot cannot be anonymised, explain what you see in words. The inquiry serves to understand your need and agree afterwards on whether a technical review is required, never to take access as authorised. You send credentials by email as outlined in the contract, and you must rotate them once the work is completed. The required access is specified for each review.
Frequently asked questions
What problem can you describe to me?
You can describe what your application does, what operation is failing, and what outcome you expected. I suggest separating what you observed from the cause you suspect and from any new features you might want to add. You do not need to solve the diagnosis before writing or attach sensitive data. This list guides your inquiry; it does not constitute a technical review already performed.
What access should I agree on afterwards?
Technical access is agreed upon only after guiding the initial inquiry and defining the scope of the review; I never ask for passwords or keys in the public form. Nor should you send complete copies of your code or database in that first contact. Access is specified for each review: you send credentials by email as outlined in the contract, and you rotate them once the work is completed.