In most Consulting Service Projects the Consultant has access to the Customers Data, that data will likely include Personal Identifiable Information (PI) of employees and vendors, perhaps Personal Credit Information (PCI) or perhaps Personal Health Information (PHI). The Customer is obligated to ensure that from a compliance perspective to ensure that information is adequately protected […]
This is the second installment in a 3 part series on some of the most important contractual differences in a Software as a Service (“SaaS”) Agreement. Most SaaS vendors provide there customer’s with a Service Level Agreement (“SLA”). The SLA specifies the hours of operation from the maintenance and support, it also segments the service […]
What issues are generally addressed in the Master Services Agreement (“MSA”) and what issues are addressed in the (SOW). There is no hard and fast rule here, but remember the MSA is a broadly focused corporate position addressing how they generally expect to contract for Services. The SOW is the exact opposite, it is a […]
Most large scale application projects are now provided under the Software as a Service (“SaaS”) business model, subject to a SaaS Agreement, as opposed to an End User License Agreements. In addition, most corporate Master Service Agreements (“MSA”) are basically consulting service agreements that anticipate that any software licenses will simply be appended to the […]
Acceptance is one of the most important terms in any Consulting Services Project. Most payment obligations are triggered by acceptance, so if it’s not accepted, it’s not invoiced and the Customer does not pay for the Service; The Customer’s warranty rights start on the date of acceptance; The Consultant is allowed to recognize revenue upon […]
