Choose a software development company by things you can check yourself: who writes the code, which live projects it has, what you get in writing before a price, and who keeps the code and the accounts. Ten questions asked before you sign bring out nearly everything that matters. Under each one you will find Bitnoda’s own answer.

1. Who actually writes the code, and who do I talk to?

Ask for names: who designs the architecture, who writes the code, who answers your messages. If you only ever talk to a salesperson, find out who the engineer behind them is.

At Bitnoda, Ion Rusu, the founder, leads every project: he designs the architecture, writes code and makes the technical decisions. When a project calls for it, he works with a small network of collaborating developers, whom he coordinates himself. You have a single point of contact. You can see who he is on the About page.

2. Can I see live projects, not just screenshots?

A screenshot looks good no matter what. A live project you can open on your phone and judge for yourself: how fast it loads, whether it works. Ask for links, and ask what exactly the company did on each project.

On our work page, every case study says how the project was built, with its stack and our role, and where we can, the page ends with a link to the live site. A project done under NDA we show only by stack and role, without the client’s name. That is an honest answer when you get it from another company, too.

3. Do I get a specification and a staged estimate before a price?

A price given after one call is a guess. Ask first for a specification: the list of features, in plain language, and an estimate split by stage.

Our work has four stages: discovery, design, development and launch. After discovery you get the specification and the estimate. We wrote about what sets the price in our article on what a web platform costs.

4. Who owns the code, the data and the infrastructure accounts?

Ask directly and ask for the answer in writing. Three things matter: the source code, the data and the infrastructure accounts, meaning the domain, the server and the paid services. If any of them stays with the company, you cannot leave without its consent.

At Bitnoda all three are yours, and we agree on that clearly before work starts. You have access to the code throughout development.

5. How do I follow progress along the way?

A report tells you things are moving. A staging environment shows you. Ask for an address where you can see every version as it appears.

That is how we work: during development you see every version on a staging environment. We agree on the update rhythm and the channel (video calls, email or chat) at the start.

6. What do I get at the end?

The minimum: the live product, the source code, the technical documentation and access to the infrastructure. Documentation matters more than it seems. Without it, another team cannot carry the project forward. Those four things are exactly what we hand over.

7. What happens after launch?

A launched product needs monitoring, security updates and backups. Ask who does them, and what happens if you want to continue with another team.

We can take on all three, plus new features, at a pace we agree on together. If you prefer your own team, we hand the project over with all its context.

8. Do you work on a fixed budget or iteratively?

A fixed budget suits a well-defined project. Iterative work suits a product that changes as you learn from it. Ask which one the company proposes for your project, and why.

We work both ways: a budget per stage, or iteratively, with priorities revisited regularly.

9. How do you handle personal data and confidentiality?

If your product holds personal data, ask what is collected, where it is hosted and whether the company signs a non-disclosure agreement.

We collect only the data that is needed, ask for consent before analytics and can host the data in the European Union. We also work under NDA. The legal side, such as your privacy policy, is something to confirm with your legal advisor.

10. What goes into the contract?

Everything you learned from the questions above: what is delivered and in which stages, who owns the code, the data and the accounts, what you get at the end and what maintenance looks like. If an answer only came over the phone, ask for it in the contract as well.

Have a lawyer check the legal wording. We can only tell you what the contract needs to cover on the technical side.

Large company, small studio or freelancer: which fits your project?

It depends on how big the project is and how much coordinating you want to do yourself. In a large company there is usually someone between you and the engineer. With a freelancer you talk directly, but you depend on one person. A small studio sits in between.

Bitnoda is a studio. You talk directly to the engineer who writes the code, and on large web platform projects collaborating developers join as a development team. We work remotely with companies in Romania, Moldova and the rest of the EU.

Which red flags show up in a quote?

None of them proves bad faith. Each is one more question to ask:

  • A fixed price after one call, with no discovery stage.
  • No written specification, only a sum and a deadline.
  • No access to the code until the end.
  • The domain or the server sits in the company’s account, not yours.
  • No live project you can open.
  • Not a word about what happens after launch.

See what we offer on the services page and in the FAQ. Or write to us directly.