A portfolio and reviews are often what decide who gets your project and your money. But nice pictures and five stars are easy to collect without ever building a good website. Here is how to vet a developer in an evening or two and find out what really stands behind their portfolio.
How to check a portfolio: open the live projects
Portfolio screenshots show a project on its best day, on a large monitor, with perfect photos. What matters to you is how it works now.
Open two or three projects from their links and walk through them as a regular visitor:
- open them on your phone: does the layout hold up, are the buttons easy to tap;
- go past the home page into a few inner pages;
- try submitting a request or adding a product to the cart;
- notice the speed: do pages take long to load on mobile data;
- look for obvious mistakes: typos, empty sections, broken links.
If the portfolio includes apps, find them in the App Store and Google Play. Check the date of the last update, the ratings, and user reviews, especially recent ones.
Keep in mind that a site may have changed after handover: someone else may have reworked it, or nobody has updated it in years. So a broken project is not a verdict, but it is a good reason to ask.
Ask what exactly they did
The same website can appear in the portfolio of a designer, a developer, a studio, and an agency that resold all of it. Each honestly calls it theirs, but each did only part of the work.
Ask simple questions about every project you liked:
- what was the client’s goal, and what changed after launch;
- what did you do yourselves: design, development, copy, everything;
- how long did it take, and how many people worked on it;
- do you still maintain it.
A good developer answers specifically and is happy to talk about what was hard. If the answers stay general (“well, we built the site”) or they get confused about the details of their own project, be careful.
Ask for client references
The most reliable check is talking to someone who has already hired them. Ask for one or two client contacts, ideally with projects similar to yours. Not every client agrees to a call, and that is normal. But if the developer cannot give a single contact, that tells you a lot.
When you talk to a client, ask:
- did they meet the deadline and budget, and if not, why;
- how did the developer handle change requests and problems;
- did they hand over all access, code, and files;
- what is happening with the project now, and who maintains it;
- would they work with this developer again.
The last question says the most. “Yes, we already ordered the next project” is worth more than any review on a website.
How to spot a template or borrowed portfolio
Sometimes a portfolio is assembled from other people’s work or from demo templates. Signs to watch for:
- Not a single link. Only images, and every project is “closed” or “under NDA”.
- Projects look like concepts. Made-up companies, placeholder text, perfect stock photos, not one real phone number or address.
- Wildly different styles and skill levels. Work clearly done by different people, yet it is one developer.
- The same images elsewhere. A reverse image search on Google or Yandex sometimes finds the same screenshots in other portfolios or on template marketplaces.
- Design from a template. If several projects differ only in color and logo, they are most likely the same ready-made theme.
Concepts are not a scam in themselves: designers use them to show their style. The problem is when a concept is passed off as a real, launched project.
Developer reviews: read them critically
Reviews are useful, but they are easy to fake or cherry-pick. A few rules help:
- Look for reviews outside the developer’s site. On a studio’s own website you will only see the best ones. Search the name on maps, in directories, and in business owner communities and Telegram groups.
- Look at the details. A real review usually mentions a specific project, timing, a manager’s name, some difficulty. A fake one reads like an ad: “Great team, fast and high quality, highly recommend.”
- Check the dates. A dozen glowing reviews in one week after a long silence looks suspicious.
- Check the authors. Treat profiles with no photo, no other reviews, and a recent creation date with caution.
- Read the negative reviews and the replies. Almost everyone has a complaint or two. What matters is how the developer responds: calmly sorting it out, or getting rude and blaming the client.
No reviews at all is not a reason to walk away either: a newer developer may simply not have any yet. In that case, live projects and client conversations carry more weight.
Start with a small paid stage
Even after all these checks, the only way to really know what working together is like is to do it. Instead of a free test task, order a small first stage and pay for it.
A small paid stage tells you more than any portfolio: you see how the developer listens, whether they hit deadlines, and what they hand over at the end.
A free test task works badly for both sides. Strong developers often decline, and those who agree do it in a hurry. A paid stage solves this: the work is done seriously, and you pay an amount you can afford to lose.
A good candidate for this stage is a clickable prototype or a site structure with the key screens. It is useful on its own, even if you then go with someone else. Why starting with a prototype makes sense is covered in “Prototype and first version”. For reference, at NOVO a prototype of a website or CRM starts at $300, and of an app at $400.
What vetting a developer cannot replace
A portfolio shows what a developer can do, but it doesn’t guarantee they will do your project well. So checking their work goes together with other steps: a contract, staged payments, and the domain and access in your name. What else to ask before paying is collected in “15 questions to ask a developer”, and the most common signs of an unreliable contractor are in “12 red flags”.
In short
- Open portfolio projects live, on your phone, and try to go through them as a customer.
- Ask what exactly the developer did on each project, and expect specific answers.
- Ask for one or two client contacts, and ask whether they would hire them again.
- Look for reviews outside the developer’s site, and pay attention to details, dates, and authors.
- Instead of a free test task, order a small paid first stage, such as a prototype.