How to Evaluate Production Software Before Hiring a Developer?
By Adrian Butnaru · Independent developer · Blanes (Girona), working remotely across Spain.
Published: · Last technical review:
To evaluate software in production before hiring a developer, I suggest separating what is visible, what is stated, and what still requires verification. Review the authorship, purpose, and limits of each reference. Then connect your questions with the deliverables and conditions you would need to agree on for your project.
Criteria: what each piece of evidence demonstrates
I would not start with a list of technologies. I would start with the work you need to resolve: who inputs information, who consults it, and what needs to happen next. That description allows you to compare a reference against your problem without assuming that any finished application serves as proof of any specialisation.
I suggest distinguishing between a sales explanation, a screenshot, and a functional check. When reviewing a software reference, it is best to separate three levels: a screenshot shows the visual interface, the technical specification describes the functional scope, and progress updates during your project allow you to test the actual behaviour in your browser or mobile phone. None of this evidence on its own demonstrates the commercial outcome your project would achieve.
| Evidence you review | What you can assess | What you must not infer |
|---|---|---|
| Screenshot identified as a demonstration | Visual organisation and context shown | Client usage or results |
| Description of published features | Correspondence between problem and described solution | That they all fit your business |
| Service conditions | What you need to agree on before hiring | An automatic transfer of the code |
| Functional progress on your project | Behaviour you can test | Approval of features not yet reviewed |
Bring an example of your operations to that review, not confidential information from third parties. If you want to centralise records, describe how they are created and who needs them. If you want to attract inquiries, review an example of a website with that objective; do not turn an operational application into a lead generation demonstration.
A general method for reviewing a reference
I suggest noting down alongside each statement what evidence supports it and what question remains open. An accessible page allows you to review what it displays publicly; a screenshot allows you to observe its visible content. Neither authorises entering private areas nor attributing to the developer results that are not substantiated.
Start with the declared authorship. If the reference corresponds to an in-house product, do not turn it into an external client commission. If a collaboration is presented, ask what part was carried out before attributing the entire project to the same person.
Then distinguish an explanation from a verification. You can ask what behaviour would be relevant to your business and what material would allow you to review it without exposing third-party information. I do not propose requesting client credentials or copying their data as a hiring requirement.
Finally, prepare a focused conclusion: what you have been able to observe, what has been described to you, and what you need to agree on for your commission. If a condition remains unanswered, keep it as an open question. A reference can help you discuss things with good judgement, but it does not replace a review of the scope nor does it substantiate future results.
How to read a screenshot without asking more of it than it proves
Look at the image caption before drawing conclusions. «Demonstration data» explains the context shown; it does not substantiate the activity of a specific business. You can assess how pending work is presented, but not deduce adoption, frequency of use, or results that I do not publish.
Then note down what part of your requirement remains unanswered. For example, you may want to know how your user profiles would be distinguished or what information your report should gather. These are questions for agreeing on scope, not capabilities you should take for granted because you have seen a dashboard.
Limits: when you should NOT use this reference
You should not choose a development project simply because its screenshot looks like what you imagine. As a general technical criterion, a similar interface may correspond to different processes and permissions. Visual similarity is no substitute for defining your operations or verifying their behaviours.
Nor should you confuse an in-house product with a client testimonial. Here you have a reference of work I have developed, not a client endorsing your future hiring. I do not add usage metrics, results, reviews, or guarantees to cover what that evidence does not tell.
If your decision depends on owning the code, clarify that separately. For applications and other software developments, I agree on ownership or licensing on a case-by-case basis. The existence of the product does not change that condition. Choosing the developer and choosing the commercial model are related, but distinct decisions.
What I would bring to your review
As a preparation guide, write down one need and one question for each piece of evidence you consult. Separate «I want to organise records» from «I want the application to do exactly this». The first phrase expresses the problem; the second requires verifiable behaviour before becoming a deliverable.
I suggest preparing:
- A process you want to organise and the people involved.
- A visible feature that interests you and the reason why.
- A limitation you cannot accept.
- The ownership or licence you need to agree on.
- The information missing to make a decision, without filling it in with assumptions.
When preparing your inquiry with the checklist, note down what workflows and records you want to organise, who consults or modifies each piece of data, and what ownership or licensing agreement you need. Use these notes to formulate your inquiry, not as an audit of the product or as confirmation that a solution already fits your business.
How we move from reviewing my reference to defining your project
Reviewing references can help you formulate questions, but assessing your project requires understanding your specific requirement. When you write to me explaining your case, I reply within 24-48 business hours with an initial written diagnosis. That timeframe is for the initial response, not for project delivery or incident resolution.
Before programming, we define the concrete deliverables, ownership or usage licence, timeframe, and budget in writing (from €3,500 + VAT* for a custom web application or PWA). During development, you speak directly with me and test each functional milestone in your browser or mobile phone.
Frequently asked questions
What is a demonstration screenshot?
A demonstration screenshot uses prepared information to display an interface; it does not substantiate client activity or results. I suggest reviewing its context and limiting your conclusion to what is visible. If you need to verify a specific behaviour, note it down as an independent question rather than deducing it from the appearance of the screen.
How do I distinguish an in-house product from an external commission?
I suggest checking how authorship is stated and what role the developer played. An in-house product is not equivalent to a testimonial from an external client. If a reference does not clarify that distinction, keep it as an open question; do not attribute collaborations, results, or experiences that the available evidence does not allow you to confirm.