Skip to content
← All articles
6 min read

How to choose a software development company: questions, access, and red flags

When deciding how to choose a software development company, the biggest risk is not missing a feature, but losing control over your own code or infrastructure. Here is a practical checklist of questions, access requirements, and warning signs before signing a contract.

Code ownership and repository access from day one

The contract must clearly state that all intellectual property, source code, and design assets belong to you as they are created, not after final payment. Demand direct access to the version control repository so your team can view commits, branches, and code reviews in real time.

If an agency insists on developing inside their private system and transferring code only at the end of the project, you risk vendor lock-in or receiving an unfinished codebase with no history.

Infrastructure accounts must belong to you

Cloud hosting, database instances, domains, and external APIs must be registered under your organization or dedicated accounts to which you hold administrative credentials. The studio should receive delegated access as engineers, not ownership.

When a vendor runs your staging or production environments on their private servers, migrating to another team becomes difficult and risks operational downtime.

What to ask the contractor to demonstrate

Do not settle for generic slide presentations. Ask the engineers to demonstrate how they manage their day-to-day work and code quality:

  • How they structure commits, pull requests, and automated continuous integration checks.
  • How staging environments are updated and how database migrations are handled safely.
  • How technical documentation and environment configuration instructions are maintained.
  • How sensitive credentials and API secrets are stored separately from source code.

Milestone delivery and acceptance criteria

Work should be divided into measurable milestones with clear acceptance criteria defined in writing before development starts. Each milestone must produce deployable software that can be tested in an environment matching the target setup.

Avoid contracts where payment is tied solely to calendars rather than demonstrable deliverables. Every accepted stage must include updated code in your repository and passing deployment scripts.

Red flags to watch for during discussions

Certain contractor responses indicate future friction, technical debt, or vendor lock-in:

  • Reluctance to grant administrative access to repositories, issue trackers, or cloud services.
  • Proposals to use obscure proprietary platforms or private frameworks that no other team can maintain.
  • Readiness to start programming immediately without clarifying architecture, data models, or boundaries.
  • Lack of automated deployment processes, manual database edits on servers, or no rollback plans.

What a clean project handover requires

A clean handover means any competent engineer can clone the repository, follow the setup instructions, and launch the application locally. Ensure the agreement includes documentation for external integrations, environment variables, and third-party service dependencies.

Retaining full access to your source code and infrastructure ensures your product remains independent of any individual agency or developer.

Questions

FAQ

Didn't find an answer — ask on the call or in Telegram.

Should I choose a fixed-price or time-and-materials contract?

A fixed-price model works well when requirements, data models, and acceptance criteria are strictly defined and unlikely to change. For projects with evolving requirements or exploratory scope, milestone-based time and materials with transparent tracking and regular demonstrations provides greater flexibility without sacrificing control.

How do I ensure code quality without technical expertise?

Require standard engineering practices: automated testing, code linters, pull request reviews, and continuous integration runs in the repository. You can also commission an independent technical audit of the codebase after the first milestone before committing to subsequent phases.

Can the studio use open-source libraries in my project?

Yes, modern software relies on established open-source libraries, but the contract should specify that only permissive licenses are allowed. Avoid copyleft licenses that may force you to disclose proprietary business logic.

Related service

Custom MVP development for your business idea

Start with a working flow you can put in front of users. We help define the essentials, design the service and build a first version around a specific business hypothesis.

Learn about the service
Other articles
Contact

Shall we discuss your task?

Thirty minutes on a call — and you understand the architecture, timeline and engagement format. No obligations.

Or message us on Telegram →Follow our Telegram channel →

Enter your Telegram or email so we can reply.

We reply within 15 minutes.