Suggestion: Write modular contracts

[pauljacobson]

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.

[pauljacobson]

@zkrige In terms of help to make these enhancements, what sort of use case would this contract address? I may have a model I could adapt for this.

[zkrige]

Generally this is a contract I use for doing custom software development or providing freelance capacity to clients

[pauljacobson]

@zkrige I have a couple models that may be helpful. I need to dig them out of my archives and I'll work on something for you when I get a chance.