TL;DR Choosing the right software house is a crucial step in bringing your project to life. Asking the right questions helps you understand their experience, technologies, workflow, and pricing models before committing. This article outlines seven essential questions every business should ask before starting cooperation with a software house. From technical expertise and project costs to source code ownership and communication practices, these questions will guide you toward a trustworthy partner and ensure your project runs smoothly.
Working with a software house means entrusting your money, your project, and a significant amount of time to people you haven’t worked with before. Asking the right questions upfront is the most direct way to reduce that uncertainty. Below are seven questions worth asking every software house you’re evaluating — along with how Dotinum answers each one.
Do you have experience in working with similar projects?
If a software house has previously built something similar to your project, they bring two advantages: familiarity with the technical patterns involved, and experience with the decisions that matter most in that type of build. They know what works, what doesn’t, and what clients typically underestimate.
That said, lack of direct experience in your specific niche isn’t disqualifying on its own. The more relevant question is whether they’ve solved comparable technical problems — a configurator with complex pricing logic has more in common with a custom quoting tool than with a standard e-commerce store, regardless of industry. Ask to see the work, not just the category label.
At Dotinum we specialize in product configurators, WordPress websites, and custom web applications. If your project falls into one of those areas, contact us — and if it doesn’t, contact us anyway. We’ll tell you honestly whether we’re the right fit.
Have you worked with clients from my location? If not, how can we handle our meetings?
Location has largely stopped being a barrier in software development. Most professional software houses operate primarily in remote mode and have established processes for working across time zones — regular video calls, shared project management systems, written communication as the default rather than the exception.
The practical question isn’t whether a software house has worked with someone in your country, but how they handle asynchronous communication and what their overlap hours look like. A team in Central Europe working with a US client on the East Coast has 5–6 hours of overlap during business hours, which is enough for daily stand-ups, review calls, and urgent decisions. A team on the West Coast has less natural overlap and requires more deliberate scheduling.
The majority of our clients at Dotinum are based outside Poland — many from the US and Western Europe. We rarely meet clients in person; more than 95% of all project communication happens online. Read more about how remote cooperation works in practice in our interview with Alick, a US-based entrepreneur who built his platform with our team.
What technologies do you use?
This question matters for two reasons. First, the technology stack affects what’s possible, how maintainable the code will be long-term, and whether you’ll be able to find other developers to extend or support the project in the future. Second, a software house that works in a narrow set of technologies will occasionally try to fit your project into their preferred stack rather than the one best suited to your needs.
Ask not just what they use, but why. A team that can explain the trade-offs between different approaches — why they’d use a particular framework for one type of project and something else for another — is demonstrating real technical judgment, not just familiarity.
At Dotinum we build on Laravel, Angular, and NodeJS. For more detail on how we choose and apply our technology stack, read our article Get to know how we work — technologies we use in everyday work.
What technical expertise can you offer? What talents do you have in your software house?
A software house’s team composition directly affects what they can deliver and how smoothly the project runs. A team with strong back-end developers but no dedicated front-end specialist will produce different results than a full-stack team with separate QA. A team without a designer means you’ll need to provide assets or hire separately.
Ask specifically: who will work on your project, in what roles, and with how much experience. Some software houses assign senior developers to scoping and sales, then hand the project to juniors for execution. Asking for CVs or profiles of the people who will actually work on your project is a reasonable request.
At Dotinum our developers have over 10 years of experience in both front-end and back-end development. We also have graphic designers involved in nearly every project.
When can you start working on my project?
Availability tells you something important about a software house’s current capacity and demand. A team that can start immediately may have open slots — which is fine, or may indicate low demand, which is worth investigating. A team with a 6–8 week wait is usually fully booked with active clients, which signals reliability but requires planning on your side.
What matters more than the start date is what “starting” means. Some software houses begin billing from the day the contract is signed; others define project start as the beginning of active development after a discovery phase. Make sure you’re comparing the same definition when evaluating timelines from multiple companies.
At Dotinum we begin work as soon as we have a signed contract with clear project guidelines. The discovery and estimation phase happens before that point.
How much will it cost?
A rather tricky question with universally disliked answer – it depends. It may happen that a software house will have a strict The honest answer is: it depends, and any software house that gives you a firm price in the first conversation without understanding your scope should raise a flag rather than reassure you.
Cost is shaped primarily by three factors: the complexity of what’s being built, the time required to build it, and the seniority of the team doing the work. A simple informational website costs less than a custom product configurator with real-time pricing logic, which costs less than a full e-commerce platform with ERP integration.
What you should ask for at the estimation stage is a breakdown — not just a total number, but what’s included, what’s excluded, how changes to scope are priced, and which billing model applies (fixed price or time & materials). A detailed estimate is a signal that the software house has actually thought through your project rather than quoting a round number to get you in the door.
At Dotinum, cost varies significantly by project type. A 3D product configurator requires more time and specialist skills than a 2D one. A custom web application with complex integrations costs more than a WordPress site with standard functionality. For an orientation on budget ranges, read our article on custom software development costs. To discuss your specific project, write to us directly.
Who owns the source code after the end of the project?
This question needs to be answered in the contract, not in a verbal conversation. Intellectual property ownership affects what you can do with the code after delivery — whether you can share it with another developer, build on it internally, license it, or sell it as part of your business.
The three most common arrangements are: full transfer of IP to the client (you own everything), a license granted to the client (you can use it but the software house retains ownership), and joint ownership (uncommon and usually complicated). Each has different implications depending on your business model and future plans.
At Dotinum we transfer financial rights to the delivered code, meaning the code is created exclusively for you and we won’t reuse it elsewhere. We can adapt the terms to your specific needs — if you have particular requirements around IP, raise them at the contract stage and we’ll find an arrangement that works for both sides.
Before you sign anything
These seven questions won’t give you a complete picture on their own — but the quality of the answers will. A software house that responds to each one clearly, without deflecting or oversimplifying, is demonstrating the same communication standard you’ll need throughout the project.
If you’re currently evaluating software houses for a web project, product configurator, or WHMCS development, we’re happy to answer all of these questions directly. Start a conversation with Dotinum here — no commitment required.
FAQ
1. How many software houses should I contact before choosing one?
There’s no fixed number, but three to five is a practical range for most projects. Fewer than three gives you too little basis for comparison — you don’t know if the first quote is competitive or the first timeline is realistic. More than five makes the evaluation process unwieldy and time-consuming for diminishing returns. The goal isn’t to find the cheapest option from the largest pool; it’s to find a company whose experience, communication style, and pricing match your project well enough to build a working relationship.
2. What should be in a software house contract?
A solid contract covers: the scope of work (what’s included and what isn’t), the billing model and payment schedule, how scope changes are handled and priced, who owns the intellectual property after delivery, the warranty terms and duration, response time commitments for reported issues, and what happens if either party needs to exit the agreement early. If any of these points are missing or vague, ask for clarification before signing. A professional software house will revise the contract without pressure or defensiveness.
3. Is it safe to work with a software house in another country?
Yes, provided the company has established processes for remote communication and a clear contractual structure. The practical considerations are time zone overlap for real-time communication, language proficiency, and the legal jurisdiction of the contract. Many US and Western European businesses work successfully with development teams in Poland, Ukraine, and other Central and Eastern European countries, where technical education standards are high and English proficiency in professional settings is strong. Ask for references from clients in your region before committing.
