How to Choose a Software House in 2026 - 12 Questions You Must Ask Before Signing a Contract
Author: Grzegorz Ługowski - Founder & Lead Engineer, GL Omniflow.
Most companies choose a software house based on price - and lose twice as much on rework. These 12 questions in a 30-minute call save an average of tens of thousands of zł and months of delays.
Choosing a software house is a decision whose consequences you will carry for 2-5 years. Not just during implementation, but also with every update, integration, and crisis. A bad decision costs an average of double the original budget - in rework, delays, vendor lock-in, and write-offs for rewriting the project from scratch.
This guide is not marketing fluff. It is 12 questions we run our own projects through and that are worth asking any contractor before signing a contract - whether you are building a corporate website, an application, an online store, or commissioning process automation.
1. Who specifically will be working on my project?
This is the first and most critical question. Many software houses sell "seniors during pre-sales" and hand off implementation to juniors or subcontractors in a different time zone. Ask for named resumes of the people who will actually write your code - and ensure they are listed in the contract by first and last name.
2. Will I get full rights to the source code?
It sounds obvious, but in practice contracts often include clauses like "non-exclusive license" or "code remains the property of the contractor". The result: in a year, you cannot hand the project over to a competing team because you do not own the economic copyright. Demand the full transfer of intellectual property rights - without it, there is no deal.
3. Where will the code be hosted during and after implementation?
Your own GitHub/GitLab repository from the very first commit, accessible to your team, or a closed contractor repo "shared at the end"? The first option is the 2026 standard. The second is a red flag - it prevents progress audits and shifts negotiation leverage during the project.
4. What does the development process look like - sprints, demos, reports?
A professional software house works iteratively: 1-2 week sprints, demos of working software at the end of each sprint, and a transparent backlog. If you hear "we will write the specification, disappear for 4 months, and come back with a finished product" - run away. That is a waterfall model from 2010, where 70% of projects end in failure.
5. Can you show 2-3 real case studies in my industry?
This is not about a portfolio featuring 50 logos in a grid. It is about specific implementations describing the problem, the tech stack used, and measurable results (deployment time, hours saved, conversion rate increase). See what our projects look like - this is the standard you should demand from any contractor.
6. What is the pricing model - fixed price, T&M, or hybrid?
Fixed price works when the scope is rigid and 100% defined - which is rare. T&M (Time & Materials) works when scope evolves - which is usually the case. Best approach: a hybrid - fixed price for an MVP with a clearly defined scope, and T&M for ongoing development. A massive "fixed price for a year" estimate without a breakdown into sprints is a red flag - either the vendor does not know what they are doing, or they are padding a huge buffer for their own mistakes.
7. What exactly is included in post-launch maintenance?
Most projects carry an unseen cost: 15-25% of their total value annually for maintenance. Check what is specifically included in the SLA: incident response time, dependency updates, monitoring, backups, and bundled development hours. Without this, you might discover after a year that "maintenance" is just a hosting fee, and every bug fix comes with a separate invoice.
8. How do you protect my data - GDPR, audits, backups?
Specific answers you should expect: a data processing agreement (DPA), EU hosting (GDPR), encryption at rest and in transit, automated backups with tested restore procedures, and access audits. If the vendor answers with "well, we take care of it somehow" - this is not the software house for a project involving customer data.
9. Do you have experience with my stack and integrations?
Specific questions: have you ever integrated this exact system (Salesforce, SAP, Optima, Subiekt, Allegro, Baselinker)? What does that code look like? Do you have developers with 3+ years of experience in React/Node/Python? "We'll learn on the fly" on your dime is a luxury you should not permit.
10. What is the exit strategy if things don't work out?
It sounds pessimistic, but it is a true test of professionalism. A reliable contractor includes termination terms, knowledge transfer, technical documentation, and contact points for the handover team in the contract. The absence of these clauses means vendor lock-in - and when conflicts arise, you are left with code that no external developer wants to touch.
11. Do you use automated testing and CI/CD?
No tests = every change after a year is a gamble. No CI/CD = every deploy takes two hours of senior developer time. 2026 standards: unit and e2e tests on every PR, GitHub Actions or GitLab CI, automated deploy to staging on every merge, and manual promotion to production. Do not buy without this.
12. What does your SEO and Core Web Vitals process look like?
If you are building a company website, an online store, or an app where customers are supposed to come from Google - technical SEO is not optional. Check if the contractor conducts a Core Web Vitals audit prior to launch, handles JSON-LD structured data, sitemaps, robots, and hreflang. If their response is "SEO is not our domain, we can recommend an agency" - that is a sign the website will be as fast as a tank.
What are the red flags when choosing a software house?
- No named list of team members in the contract - meaning "someone will do it"
- Fixed-price quote for an entire year without sprint breakdown
- Code repository kept private until project completion
- License clause instead of full copyright transfer
- No demos of working software along the way
- A portfolio full of logos instead of case studies with real numbers
- Selling "seniors" during pre-sales, assigning juniors for delivery
- No automated tests, CI/CD, or code review process
- Hosting code outside the EU without a data processing agreement
Which software house is worth working with?
- A discovery call at the beginning instead of ballpark estimates
- Transparent quote within 24h, broken down into sprints
- Working software demos every 1-2 weeks
- Your own repository from the very first commit
- Real case studies with measurable results
- Experience with your required integrations (not "we will learn")
- Maintenance and exit plan defined in the contract
- Tech stack chosen to solve the problem, not follow trends
What should you do after choosing a contractor?
If you are planning to launch a website, store, or app in the coming months - briefly describe your project via our contact form. We respond within 24h with a concrete scope proposal, timeline, and quote. No sales pressure. Also check how our pricing process works and explore our past projects.
You can also read our related guides: how much does a mobile app cost in 2026, what makes a good SEO audit, n8n vs Make.com vs Zapier for automation, and when to choose headless commerce over Shopify.