Signatures, Parties, Sprint And Payments ScheduleShuup2021-04-13T11:02:04-07:00
Signatures, Parties, Sprint And Payments Schedule
EXHIBIT A: SIGNATURES, PARTIES, SPRINT AND PAYMENTS SCHEDULE
Non-Fixed Sprint and Payment Schedule.
*Completion and Release. As this agreement has no fixed price or fixed scope there is no official completion or release date set.
New Requests. Any additional new development features or services requested by Customer that delay the original scope of Deliverables and schedule hereunder will accordingly change the final delivery and payment dates. Any additional development requests must be made in writing and are subject to Developer’s new cost and delivery date estimates, which shall be incorporated by reference into this Software Specification and Project Plan.
***Estimated Sprint End Dates. Estimated Due Dates are estimates only and may be revised in the sole discretion of Developer based on Customer requests, needs, requirements, specifications, Developer progress, and change requests.
Fees. The estimated fees, start and end dates are only estimates, non-fixed and are subject to change. Developer will make good faith efforts to meet the estimated dates and fees, but Developer does not and cannot make any guarantees for hourly estimates and start and delivery dates. Customer shall pay Developer by the hour at the rate of $150 per hour until the total fees charged reach the amount set forth in the Estimated Fees for each Feature of the Services as specified. Thereafter, if hours exceed the hours Estimated for the Feature, the Customer can continue the development and shall pay Developer at the rate of $150 per hour for all work in the performance of the Services until the Feature is complete. Developer will provide to Customer an itemized invoice reflecting all hours worked for each Feature. Customer may pay via ACH, Credit or debit card, all payments are subject to a 3% service fee charged by Developer. All fees will need to be paid upfront before the new development can start.
Refunds There will be no refunds for purchased hours. All paid and unused hours will be credited to the customer’s account. Requirements and Specifications for how the credited hours will be used on the current marketplace project must be completed and agreed upon by both parties within 90 days of purchase, or the credited hours will expire without a refund.
Signatures. The Parties have mutually agreed the contents of this General Service Agreement and its Exhibit and have duly affixed their signatures on this __________________ (“Effective Date”).
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cloudflare sets this cookie to identify trusted web traffic.
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
This cookie is managed by Amazon Web Services and is used for load balancing.
Associated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers.
Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
This cookie is set by the provider Salesforce. This cookie is used for ensuring client requests hits the same proxy hosts and are more likely to retrieve content from the cache.
This cookie is set by the provider Salesforce. This cookie is used for properly routing server requests within the Salesforce infrastructure for sticky sessions.
This cookie is set by the GDPR WordPress plugin. It is used to store the cookies allowed by the logged-in users and the visitors of the website.
This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
This cookie is set by the Salesforce. This cookie is used for properly routing the server request within the Salesforce infrastructure for sticky session.
PayPal sets this cookie to enable secure transactions through PayPal.
This cookie is provided by PayPal when a website is in association with PayPal payment function. This cookie is used to make safe payment through PayPal.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
This cookie is installed by Google Analytics.
Set by Google to distinguish users.
Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
This cookie is used for registering a unique ID that identifies the type of browser. It helps in identifying the visitor device on their revisit.
16 years 3 months 6 days 6 hours
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
The pardot cookie is set while the visitor is logged in as a Pardot user. The cookie indicates an active session and is not used for tracking.