By Artem Korsakov ·
In short: a contractor's work quality is hard to assess before the project starts. The client sees promises and examples but does not always understand the contractor's real role, the conditions and how the result was checked. A clear project history with confirmations and limitations can help.
Two proposals look similar: timelines, stages, familiar words about experience. One was prepared by a strong team, the other by someone who does not yet understand the task well. The buyer has to choose before the difference becomes obvious. That means doing good work is not enough: it has to be made verifiable.
Why promises do a poor job of distinguishing contractors
A contractor knows its own capabilities better than the client does. The client knows its business better but may not understand the complexity of implementation. This gap makes it hard to assess a proposal even when both sides act in good faith.
The economist George Akerlof described how uncertainty about quality affects markets where the seller has more information than the buyer. His explanation of the mechanism can be read in his own essay on the Nobel Prize website. This is a theory of the mechanism. His essay does not measure any specific contractor market.
The practical conclusion is simple: if differences are hard to check, a strong contractor may look the same as a weak one. You need signals that are harder to replace with nice wording.
What evidence actually relates to the task
A well-known client by itself says little about the quality of the work. What matters is what exactly the contractor did: researched needs, designed the logic, wrote the software, led the team or supported a finished system. These roles must not be substituted for one another.
A useful portfolio project has context:
- what task the client faced;
- which part this participant performed;
- what constraints affected the work;
- what was handed over and how the result was accepted;
- who can confirm the description;
- as of what date the information is current.
Even a small project with a clear role is sometimes more useful than a famous logo without explanation. Similarity to your task is what decides; the prominence of the name is secondary.
Why confirmation needs to be split into levels
The phrase “verified contractor” is too broad. Checking a company's registration, confirming participation in a project and assessing the quality of the result answer different questions. A single badge must not pretend to represent all three checks at once.
A product can show a specific status: “participation confirmed by the client's representative”, “description added by the contractor”, “documents reviewed by a moderator”. Next to it, you need the date and the scope of the check. If the client has confirmed the fact of cooperation, that does not yet mean they agree with all the claimed results.
How to compare projects before choosing
First define the characteristics of your task: industry, scope, systems used, access and support requirements. Then look for similar conditions in the portfolio. A matching technology without a matching process may be of little help.
Ask the contractor to walk through one difficult episode: what did not go according to the original plan and how the decision was made. A good explanation includes constraints and consequences. A story where everything went perfectly tells you nothing about how the team handles problems.
After that, a small verifiable stage is useful: a process review or a working scenario on test data. Its scope and result should be agreed in advance. Such a check takes time and may be paid. It should not be passed off as a free full-scale project.
What to automate in collecting confirmations
You can start with a project card, separate roles, an invitation to confirm participation and a change history. The recipient is shown the exact text they are confirming. Changing a role or result after confirmation should send the corresponding field back for review.
AI is useful for drafting a description from agreed materials and finding missing information. It cannot establish the fact of cooperation on its own. A found mention of two companies must not be turned into a confirmed joint project.
What result to expect from the first version
First check whether a buyer can understand the contractor's role from the card and formulate substantive questions. See whether real clients complete the confirmation and which points they refuse to approve. This is more useful than the number of badges drawn.
The verified projects prototype can show this path on training data. A production product will require moderation rules, access rights and dispute handling. Promising a universal quality rating based on a single questionnaire would be premature.
Related reading: Five stars are not enough: how to assess a contractor's experience; What a business relationship map can tell you about a company.
Частые вопросы ### Does a confirmed project guarantee the quality of the next one?
No. It helps understand past experience under certain conditions. For a new project, you still need to check the team, the scope of work, current workload and acceptance criteria. The history of cooperation complements the choice but does not make the decision for the client.
What if a client does not allow their name to be published?
You can describe the task without disclosing the client and state the restriction explicitly. By agreement, access to individual materials is opened to a specific buyer. The absence of a public name must not be compensated for with an invented recommendation.