Back to all posts
Buyer's Guide7 min read·October 26, 2026

How to Verify a Software Agency's Portfolio

TB
ThynkBlox Team
Strategy

How do you verify a software development company's portfolio?

Verify a software development company's portfolio by checking what it delivered, who did the work and what the client can confirm. Request a demonstration of relevant features, ask the agency to separate its contribution from work done by others, and speak with a reference who directly supervised the engagement. Treat each project as evidence of a specific capability, rather than proof that the agency can build your entire product.

Start with the portfolio projects closest to your needs. For broader selection criteria, use these questions to ask a software development agency.

What should you ask about each portfolio project?

Ask for a short account of the starting point, the agreed scope and the delivered result. “We worked on this platform” leaves too much open. You need to know whether the agency built the product, added one feature or maintained an existing system.

Use the same questions across shortlisted agencies so that you can compare their answers.

What to establishQuestion to askEvidence to request
Starting pointWhat already existed when you joined?A description of the inherited product
Delivered scopeWhich features or components did your team build?A demonstration tied to that scope
ResponsibilityWho owned design, engineering, testing and release decisions?A breakdown of responsibilities
Team involvementWhich contributors could work on our project?A meeting with the proposed delivery lead
Client experienceWho directly reviewed your work?A reference introduction with permission
HandoverWhat could the client operate without you?A permitted handover example or walkthrough

Ask the agency to distinguish completed work from proposals, prototypes and unfinished engagements. Each can show something useful, but record exactly what you have seen.

What should a useful demonstration include?

Choose a workflow related to your product and ask the agency to walk through it from start to finish. For an ordering application, that might mean creating an order, changing it and showing the final status. For an approval tool, follow a request through submission, review and rejection.

Ask the presenter to explain which parts the agency delivered as they go. Then explore a less convenient path: missing information, a rejected action or an interrupted step. Keep the request within a safe demonstration environment using sample data.

Useful prompts include:

  • Show the feature your team was responsible for.
  • Explain a difficult requirement and the choice you made.
  • Show what happens when the user makes a mistake.
  • Describe how you checked that the feature worked.
  • Explain what you would change if building it again.

A demonstration should help you judge the agency's explanation of its work. It does not independently establish authorship. Connect what you see to the scope description and the reference conversation.

Do not request access to another client's private account or confidential records.

How do you establish who actually did the work?

Separate the agency's past experience from the experience of the people proposed for your engagement.

Ask who led the portfolio project, who made the main technical decisions and who handled delivery problems. Then ask whether those people are still available and what involvement they would have in your project.

Request a conversation with the proposed delivery lead. Ask them to explain a relevant decision, its alternatives and its consequences. If they did not work on the portfolio example, ask which experience of their own supports the proposed approach.

You do not need identical staffing across past and future projects. You need a clear connection between the capability being advertised and the team being offered. Include that connection in your assessment rather than assuming a portfolio logo represents every person at the agency.

How do you distinguish original engineering, maintenance and subcontracting?

Ask the agency to describe its work using specific verbs: designed, built, integrated, migrated, tested, repaired or supported.

For original engineering, ask what the team created and which existing tools or components it used. Do not make “built from scratch” a requirement by default. Assess whether the team understood the choices and delivered the agreed result.

For maintenance, ask what the agency inherited, what it changed and how it checked for unintended effects. Use that evidence to assess maintenance capability. Seek a separate example if your project requires experience defining a new product from an unclear brief.

For subcontracted work, ask who held the client relationship, who employed or engaged the contributors and who accepted the deliverables. Clarify which responsibilities belonged to the agency and which belonged to another supplier.

Subcontracting need not disqualify an agency. Ask how it would affect your proposed team, accountability and handover; see what to check when your agency uses subcontractors. If unfamiliar code is central to your project, include questions from technical debt explained for founders.

How should you check client references?

Ask for an introduction to someone who directly reviewed the agency's work. A reference who can discuss delivery is more useful for this decision than someone who only knows the sales relationship.

Prepare questions around the claims you want to verify:

  • What did the agency take responsibility for?
  • What was delivered, reduced or left unfinished?
  • How did it communicate delays and difficult decisions?
  • How did it respond when work needed correction?
  • What could your team manage after handover?
  • Would you hire it again for a similar scope, and why?

Distinguish what the reference personally observed from what they heard from others. Keep your notes factual and relevant to your decision.

Where possible, confirm the person's role through a contact route you establish independently. Respect their time and confidentiality; do not press for commercial terms or private project details.

What if confidentiality prevents a public demonstration?

Offer alternatives that respect the client's restrictions. Ask whether the agency can provide a redacted walkthrough, a sample-data demonstration, a permitted reference call or a detailed discussion of responsibilities.

Let the agency identify what it has permission to share. Do not ask it to send client source code or documents without authorisation.

Record the limits of the evidence. For example: “Relevant workflow explained; client confirmation unavailable.” That is more useful than treating an unverified claim as established or treating confidentiality alone as a reason to reject the agency.

If an important capability remains unverified, consider a small paid discovery task with a defined deliverable and acceptance criteria before committing to a larger build.

How do you turn the evidence into a decision?

Use a simple claim-and-evidence record.

In this illustrative example, an agency says it built an entire booking platform. During review, it explains that another team created the original product and its own contribution was a replacement scheduling feature. The client confirms that scope and describes a satisfactory handover.

Record the evidence as relevant scheduling and integration experience. If you need a team to define and build a new product, request additional evidence for that responsibility.

Before selecting an agency, check that:

  • Its claimed contribution matches the demonstrated scope.
  • A reference or permitted alternative supports the key claims.
  • The proposed team has relevant experience.
  • Unverified claims remain clearly marked.
  • The evidence covers your project's difficult parts.

Use this record alongside your scope, budget and contract review.

What common mistakes should you avoid?

Judging by appearance alone. Review the workflows, decisions and responsibilities behind the screens.

Assuming a client name proves a broad engagement. Ask what work the agency performed for that client.

Treating every contribution as equivalent. Match the evidence to the responsibility you intend to buy.

Demanding confidential material. Request permission-based alternatives.

Turning verification into unpaid development. Keep requests focused on existing work. Pay for new analysis or deliverables you intend to use.

Frequently asked questions

Can screenshots verify a portfolio?

Use screenshots to identify what you want demonstrated. Follow up with questions about scope, contributors and client confirmation before drawing conclusions about delivery capability.

Should I ask to inspect source code?

Consider a review when code quality is central to the decision and sharing is authorised. Agree on the review scope first; a permitted sample or technical walkthrough may be sufficient.

Should I reject an agency without a similar project?

Assess the underlying challenges your project presents. If direct experience is essential to you, make it a selection requirement. Otherwise, request evidence of relevant skills and keep any remaining uncertainty explicit.


*Want to discuss the experience your project needs? Start a conversation →*

Ready to build?

Let's turn these ideas into your next product.

Start your project