How to Choose a Development Contractor: A 10-Question Checklist
Ten questions worth asking a studio before signing a contract, and the signs that reveal an unreliable contractor.

The main signs of a reliable contractor: they ask questions about your business before naming a price, show working projects, fix the scope of work in the contract, and explain what happens after launch. Below are ten questions worth asking before signing, and the signals that suggest you should look for another contractor.
Ten questions before signing the contract
- Show me similar projects. Not a list of logos, but working links you can open and check yourself
- Who specifically will work on the project? It happens that an experienced team sells the work and interns do it
- What is included in the price and what is paid for separately? The answer should be in writing and detailed
- What happens if the timeline slips? The contract should specify the responsibility of both parties
- Who owns the code after handover? The right answer is the client, along with all access credentials
- What is the warranty and what does it cover? Clarify the difference between fixing bugs and making improvements
- How are revisions handled and how many are included in the price?
- What happens after launch? Is there support and how much does it cost
- How often will you show interim results?
- Can I speak with one of your previous clients?
Signs that should raise a red flag
They name a price right away without asking a single question
The cost of development depends on the task. An exact figure named before studying it is either an understated amount that will grow along the way, or a template solution that suits everyone and no one.
They promise timelines many times shorter than the market average
An app in two weeks or an online store in three days means either a template with minimal changes or a two-to-threefold overrun. It is worth understanding both scenarios in advance.
There is no contract, or it is a single page
The contract should fix the scope of work, timelines, cost, acceptance procedure, and the responsibility of the parties. Without this, a dispute will be impossible to resolve.
The portfolio is only pictures
Beautiful images of layouts do not prove that the project was launched. Ask for working links or apps in the stores.
They cannot explain things in plain language
If a question about technology gets you a stream of jargon without any explanation of what it gives your business, communication on the project will be just the same. A good contractor explains complex things in simple terms.
They demand full prepayment
The normal practice is to split payment into stages tied to results. Full prepayment deprives you of leverage if something goes wrong.
What matters more than price
The difference in cost between contractors often turns out to be less significant than the difference in the result. A site for 400 000 ₸ that brings in requests is more valuable than a site for 150 000 ₸ that brings in nothing — the latter is simply money written off.
Judge not the quote but the understanding of the task. A contractor who asks questions on the first call about your business, customers, and current problems is more likely to build what you need than one who immediately discusses the number of pages.
