Source Code: To Give or Not to Give?

This topic always creates debate. Some developers give source code for free. Others charge extra. The truth is that it depends on the type of work you are doing and who owns the product.

1. When you build a custom app or website from scratch
   The client is paying you to create a product that belongs to them. In this case, giving the source code is the logical and professional thing to do. The client needs the code so they can fix bugs, update features or hire someone else later. The source code is part of what they paid for.

2. When you sell a product or a template that you own
   This is different. You are not building something custom. You are selling something you created for yourself. In this case, you can decide if you want to include the source code or not. Many people sell two versions. A cheaper version without source code and a full-source version for a higher price.

3. When you reuse your own modules across projects
   If you have a piece of code that you use in multiple client projects, you are not required to give them that shared code. You can give them the final result without exposing your reusable libraries. This is your intellectual property.

4. The mistake many beginners make
   The problem is not giving the source code. The real mistake is charging very low prices. If you are being paid fairly, giving the code becomes normal and expected. If you are underpaid, giving full ownership feels painful.

5. The fair conclusion
   Give the source code when the client is paying you to build something custom that they own. Keep the source code or charge extra when the project is your own product, your own template or your reusable system.