We invoice at the end of each sprint. Client settlement can be immediate or due to an advance we can carry on with the next sprint. As we work with other developers, must ask clients to either run their sprints against an initial deposit, or pay on invoice for continuity.
The other option is that the client does not pay at the end of the sprint, and after a month their Staging site is mothballed. Our repository is kept available so that paid for code can be released to a live site on our Cloud server or the Client’s own arrangement.
The strict rules are:
1. Client is in credit by taking an offered down-payment option and pays on invoice before the end of the next sprint, and we give that client continuity of development.
2. A Client can always access their paid up source code repository.
3. A client can stop when they want. At project completion or at any release stage. We may propose new plans for a client which they do not have to act upon.
4. A client pays by Sprint a charge based on the number of developers required – that has been estimated. If more developers are needed to reach a deadline, or specialists need to be employed for a single sprint, then that would proportionately increase the charge for that Sprint. If it is more than one developer added, we may ask for a down-payment.
5. Developers are paid at the end of each sprint.
6. Clients who have completed a full and active project with RemoteDevelopment and who have their live site hosted with us, will be offered a monthly invoice and settlement.