7 min readHow to Verify a Software Development Agency's Portfolio Is Real
An impressive portfolio page doesn't guarantee an impressive agency. Case studies can be exaggerated, outdated, or sometimes not even the agency's work at all. Before you commit budget and timeline to a software development partner, verify what they're showing you is real.
Here's how to check an agency's portfolio claims systematically, what red flags to watch for, and which questions separate legitimate work from marketing copy.
Download and Use the Product Yourself
If the case study is a mobile app, go download it. If it's a web app, create an account and use it. This is the fastest verification step and reveals several things at once.
Does the product actually exist and work? Is the quality level what the case study implied? If the agency claimed they "built a fintech platform processing millions in transactions," but the app has 47 downloads and two reviews from 2023, that's a data point.
Check the app store listing date, review count, and recent update history. An app that launched in 2019 and hasn't been updated since 2021 might mean the client moved on or the product failed. That's not necessarily the agency's fault, but if most of the portfolio is defunct products, it tells you something about the types of projects they attract or deliver.
Ask for Client References You Can Actually Contact
A case study with no client name attached is a warning sign. Legitimate agencies work with real companies who are usually willing to provide a reference, especially for successful projects.
Ask for contact details for at least two recent clients whose projects resemble yours in size, complexity, or industry. Then actually call or email them. Agencies expect this. If they hesitate, push back with NDAs as the excuse for everything, or only offer references from years ago, that's a pattern.
When you speak to the reference, ask specific questions: Did the project finish on time and on budget? How did the agency handle problems or scope changes? Would you hire them again? What surprised you, good or bad? A real reference will give you texture, not just "yeah, they were great."
Verify the Agency's Actual Role in the Project
Some agencies showcase work where they contributed one feature, provided staff augmentation for a few months, or took over a project another team started. None of that is dishonest if disclosed, but if the case study implies they built the entire product from scratch when they didn't, that's a credibility issue.
Ask directly: "Did you build this from the ground up, or was it an existing codebase? What specific parts did your team own?" If they handled backend APIs while another firm built the mobile app, you want to know that before using the case study to evaluate their mobile capabilities.
Check the Timeline and Team Size Claims
If a case study says "we delivered this marketplace platform in six weeks," ask how. Six weeks with two developers is a very different claim than six weeks with a team of twelve working overtime.
Request a rough breakdown: how many developers, designers, QA engineers, and project managers worked on it, and for how long? If the numbers don't add up for the scope described, either the case study is exaggerated or they're leaving out context like an existing codebase, extensive client-side contribution, or cut scope.
Look for Code You Can Inspect
Open-source contributions, public GitHub repositories, or any code the agency can share (even sanitized snippets from private work) let you evaluate quality directly. Not every project can be open, but if an agency has been operating for years and has zero public code, that's unusual.
If the product is a web app, open your browser's developer tools and look at the network requests, HTML structure, and asset loading. You can often tell if the app is well-built or held together with duct tape. Excessive load times, unoptimized images, or messy console errors might not disqualify the agency, but they give you questions to ask.
Ask About What Happened After Launch
A portfolio full of products that launched and then disappeared isn't always the agency's fault, clients pivot or run out of funding, but it's worth asking. "Is this product still live? Is the client still working with you on it?"
Agencies that maintain long-term relationships with clients, provide ongoing support, or get hired for phase two are demonstrating something beyond just finishing a contract. If every case study ends at launch with no follow-up engagement, ask why.
Cross-Check Claimed Technologies and Integrations
If a case study claims the agency built integrations with Stripe, Twilio, AWS, or other third-party platforms, verify the implementation quality when you test the product. Try the payment flow, test the SMS notifications, check if the features actually work.
Also check if the technologies listed make sense together. If a case study claims a React Native app with a Laravel backend and Ruby on Rails APIs, that's technically possible but unusual and suggests either the project had a complicated history or the case study is sloppy.
Watch for Stock Photos and Generic Descriptions
Case studies with stock photos, no client logo, vague descriptions like "a leading fintech company," and no measurable outcomes are often filler. Real case studies include specifics: the client name (or a credible reason it's withheld), the problem solved, the technologies used, and ideally some outcome like user growth, performance improvement, or successful funding.
If the entire portfolio reads like marketing templates, the agency might be new, small, or inexperienced, or they might be inflating their work. Either way, you need more evidence before signing.
Request a Technical Interview with the Team
Ask to meet the developers, designers, or lead engineer who would actually work on your project. Walk through one of their case studies together and have them explain architectural decisions, challenges they faced, and how they solved them.
A team that built the product can talk about it in detail. They'll remember the tricky parts, the tradeoffs they made, and what they'd do differently now. If the answers are vague or high-level, or if the agency resists letting you speak to the actual team, that's a flag.
Trust Patterns, Not One-Off Signals
No single missing detail disqualifies an agency. Some clients require strict NDAs. Some great products fail in the market. Some agencies are excellent but new and have thin portfolios.
What matters is the pattern. If you see multiple verifiable, live products, clients willing to talk, transparent answers about scope and team size, and work that holds up under scrutiny, you're likely looking at a legitimate portfolio. If you see deflection, vague answers, unverifiable claims, and case studies that don't check out, keep looking.
Get It in Writing
Once you've verified the portfolio and decided to move forward, make sure your contract includes similar transparency for your own project. Define deliverables, specify who owns the work, set milestones with acceptance criteria, and include the right to reference and display the work (if that matters to you).
The same scrutiny you applied to their past work should carry through to how they document and deliver yours.
Stardelite is a software development studio working with clients internationally on custom software, mobile apps, and product development. If you're evaluating partners for your next project, we're happy to walk you through our work, connect you with references, and answer your technical questions directly. Visit our services page to learn more about how we work.
References
Share this:
7 min read