We spent 200k with the agency, they finished the project — do they have to give us the source code?

happened to me too, got the same answer (ip is ours)... then found another agency, they did reverse engineering for 3 thousand lira.

if you paid 200 thousand lira for software, it's impossible for them to be right about not giving the source code.

Source code: backend code + database schema + API documentation + deployment guide. Don't ask for all of it.

Be direct: 'If you don't deliver the code to us within 30 days, I'm sending a lawyer.' It'll cost them 20k, they'll give the code.

For requesting source code send a dated written email cite the contract clause, threaten to have your legal advisor send a notice.

Here's how it went for us. Mistakes made on the who owns the source code side are usually reversible but expensive.

Correct me if I'm wrong.

Timely topic.

exactly like that but ask who prepared the quote and who will actually do the work.

the biggest time-waster for us was not knowing who had the final say. this is my opinion, I'm not claiming it's absolute truth.

This approach has a cost, which isn't discussed. Everyone rushing into who owns the source code gets stuck at the same point.

Processes without records never improve because you don't know what to fix. I'm also curious if anyone does it differently.

Great work. Weekly written progress reports are much more useful than asking for dates.

If I were you, I'd go this route.

I'm a small business, let me explain from my side. Everyone rushing into who owns the source code gets stuck at the same point.

I'd say don't rush. Just because everyone does it doesn't mean it's right.

If you don't write this down from the start, it leads to arguments later. If I were you, I'd go this route.

There's a common mistake people make when doing this. If you get three different answers on a topic the question was asked wrong.

Just because everyone does it doesn't mean it's right. I'm also curious if anyone does it differently.

There is something to watch out for. If acceptance criteria aren't written, when the work is done is open to debate.

Noted, thanks.

I felt relieved reading this answer so it's not just me. Implementing a change request process doesn't slow things down it speeds them up.

When we decide without measuring we always end up in the same place. If you post the result here, it will help others too.

Let's separate the concepts, they're getting mixed up. When you try to change everything at once, nothing settles.

Start with a small trial; don't commit to everything at once. If I were you, I'd go this route.

Great work.