1. Our Agreement
This Statement of Work (“SOW”) is subject to the terms and conditions of the SAU/CAL Terms of Service. As noted in the Terms of Service, this SOW and the Terms of Service together comprise a legally binding agreement between us. When you purchase this Service from us you accept the terms of the Terms of Service and of this SOW.
2. Overview of Services Under This SOW
Sprint-based pricing is a transparent billing process where SAU/CAL bills weekly for what is done in the last seven days, giving You greater control over the direction of Your projects and budgets. You will have the opportunity at the end of each week of work (“Sprints”) to review the work and sign off on the scheduled work for the upcoming week, ensuring no surprises down the line and better launch readiness. You will also have the opportunity to pivot as needed since Sprints allow for iteration and inspiration.
3. Weekly Fee
You will be charged the price set forth on the Service description page per week.
4. Expected Deliverables
The parties expect that at the end of this SOW the Deliverables specified in Schedule 1 of this SOW shall be delivered to You. Client-directed changes or unexpected technical challenges as discovered through the development process may ultimately mean that the Deliverables at the end of the Sprints will be different than the Schedule 1 list. Expected Deliverables are an estimate. You are purchasing development services on a weekly basis, and are not purchasing a product with a predefined set of specifications.
5. Estimated Number of Sprints
If SAU/CAL has estimated the number of Sprints that will be required to deliver the Schedule 1 Deliverables, that estimate will be in the SAU/CAL Discovery Report. Ultimately however the number of Sprints required and exact Deliverables will be determined by You – this is an SOW for delivery of services on a time and materials basis.
6. Post-Delivery Warranty
Developer time shall be included, at no extra cost to You, at the end of the Sprints for any bug fixes, server configuration issues, or other minor issues that crop up post-delivery, within 15 days. This clause shall not apply to issues caused by updating plugins or WordPress core after delivery. The amount of developer time allocated under this clause shall be limited to 0.5 hours multiplied by the number of Sprints (e.g. 0.5 hours x 3 weeks, for a 3 Sprint project).
7. Versioning
Note that all Deliverables shall be aimed at the current version of Your website platform (e.g. WordPress) and applicable plugins, as of the day that work begins that interacts with that component of the system. If an important update becomes available during the development process then it is possible that this could create delays and/or additional work (outside of the estimate).