How do you write source code delivery into a web development contract?

Just asking for "the code" isn't enough; get "uncompiled" (unminified, raw) source code, build scripts, and an environment variables template (a sample .env file) written into the deliverable list. If they hand you minified production code, no other dev will ever make sense of it.

When having it drafted into the contract, definitely do not skip these three items: 1) Transfer of intellectual property rights to the client upon final payment, 2) Mandatory delivery of setup and build instructions, 3) Acceptance criteria requiring the code to be fully functional on an independent server outside the agency's infrastructure.

Set up a GitHub or GitLab account in your company's name right now while it's still in development. Tell the agency, "You will commit code directly to our company repo." It's far less of a headache than chasing down files after the project wraps up.

75,000 TL isn't a bad budget for a corporate catalog, but agencies love vendor-locking clients into their own custom panels. If they claim "we can't hand over the code, it's a trade secret," you can bet it's not custom software at all—they just tweaked a pre-made theme downloaded off the web and resold it.

we fell into this trap two years ago. the agency went under, they didn't pay their server bill so the site went down and we didn't have a single line of code to show for it. we had to build the whole thing from scratch. do not compromise on this, the code belongs to you.

"it'll stay on our servers and we'll give you a panel" is a massive red flag. don't sign off or release the final installment until you spin it up and test it on your own server.

Speaking as a developer myself: even when clients get the source code they usually don't know how to manage a server, so agencies offer hosting by default. There isn't necessarily bad intent there. But an honest agency will say "Of course, we'll hand over a Git repo or a zip archive once the project wraps up" the second you ask. Evasive answers mean either technical incompetence or an intentional attempt at vendor lock-in.

Tie the final milestone payment directly to the full delivery of the source code, and write that condition explicitly into the contract.

Exactly like that. If scope grows, either time or budget must grow. There is no third option.

We experienced almost the exact same thing last year. When we decide without measuring, we always end up in the same place.

Proven by experience.

I have no experience with source code delivery, so I'm asking. The harder it is to reverse a decision, the slower you should make it.

Solutions that work at a small scale collapse when you grow; I learned this late. Hope this helps.

there is somethhing to watch out for. the cheapest quote is usually the least thought-out one.

everyone rushing into source code delivery gets stuck at the same point. btw im also curious if anyone does it differently.

Correct.

How did you solve this? When you try to change everything at once, nothing settles.

If code ownership isn't in the contract, you have no bargaining power when leaving. That's all, sorry if I went on too long.

I disagree with you on this point. Don't hesitate to ask; those who don't ask always pay more.

That's all, sorry if I went on too long.

Exactly, and not many people know this. Access credentials should be opened in the company's name, not personal accounts.

Correct me if I'm wrong.

Exactly like that. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

I'm also curious if anyone does it differently.

If you're going this route, sort this out first. Ask who prepared the quote and who will actually do the work.

Weekly written progress reports are much more useful than asking for dates. Correct me if I'm wrong.