zkrige / freelancer_contract

Template freelance developer contract

What's this?

This is my software development contract that I use for contracts with clients. I've decided to put it here for other freelancers to use as well.

If you have suggestions, improvements, or spot a mistake, PLEASE submit a PR

NB: Use this at your own risk. I'm sure there are problems or loopholes. Don't blame me if it doesn't cover you.

freelancer_contract's Issues

Suggestion: Move your variables to a schedule

You've added variables like Rand values in the body of the contract. This can make it a bit harder to update the contract as project scope changes or time goes on and fees increase. Rather create project schedules with all the project variables, such as -

• Fees;
• Due dates for payments;
• Project scope; and
• Relevant time periods (such as delivery, responses, etc).

Change orders modification

"If Developer cannot or chooses not to accept the change order, then Customer may elect to terminate the agreement."

It seems that no provision is stipulated to provide payment if the Customer chooses to terminate the agreement when presented with increased costs due to a change request.

Am I mistaken?

Suggestion: Write modular contracts

On a similar point to #3 , it might also be a good idea to create a modular contract framework. Have your standardised contract terms in one document (same model as website terms of service), with project specific terms and schedules as separate items.

This way you can streamline your contracts from a client perspective. Your project terms focus on the project itself, and reference the standard terms (bit like calling the standard terms as if they are a callback function). If you do it correctly, when the client signs the project terms + schedules, the client also agrees to your standard terms.

One benefit of this is that clients don't like to get caught up in the "fine print". That means lawyers and headaches. They want to sign off on the essentials, while knowing that the important stuff is in place.

The key is to:

• write clear, standard contract terms;
• clearly reference the standard terms in your project terms/docs so the client is aware that they apply; and
• reduce friction in the sign-up and contract approval process.

Suggestion: Add defined terms for greater clarity

It's a good idea to have a glossary of some kind that contains definitions of key terms. You have a very bare-bones version in the header of the contract relating to the parties. You should have more defined terms which you aggregate in a single section.

In contracts, clarity is key and could avoid issues down the line. Most contracts have an Interpretations section that not only includes defined terms, but also interpretation principles. The goal is more clarity about what everything means.