- Reaction score
- 9
A good script that's delivered poorly can lead to disputes. This guide helps both parties close the deal smoothly.
1. What the delivery should include
2. Try Before You Buy (Buyer)
3. For the seller
4. Payments
For large amounts, milestone payments, or escrow: a portion upon delivery of the demo and the remainder upon confirmation that it works.
What else would you include in an installment? Leave a comment.
1. What the delivery should include
- Complete and well-organized code, not just an executable file.
- Documentation: Requirements, Installation, Configuration, and Examples of Use.
- List of dependencies and versions (for example, a requirements.txt file).
- License: What the buyer can do (personal use, resale, modification).
- Initial support: how many days and through which channel.
2. Try Before You Buy (Buyer)
- Request a video demo or a live demo.
- Run it in an isolated environment before using it on your main computer.
- Make sure it doesn't request unnecessary permissions or send data to unknown servers.
- Verify that it works with the current versions of the platforms you use.
3. For the seller
- Document everything thoroughly. This will help you avoid many inquiries and returns.
- Explain the known limitations.
- Indicate whether the script depends on third-party APIs that may change or stop working.
4. Payments
For large amounts, milestone payments, or escrow: a portion upon delivery of the demo and the remainder upon confirmation that it works.
What else would you include in an installment? Leave a comment.