This type of email would give me shivers.
“We finally have the contract from ____________ [insert massive company name, big logo]. We need to close by EOW (in 36 hours) before their budget runs out.
Huge win for the company! CEO is ecstatic!
Their legal won’t accept any changes. PO already issued.
Please approve for signature.
Thanks….”
You open the attachment—it’s a 100-page master software and services agreement that’s more suited for development services than your pure SaaS product.
No limitation of liability, demand for IP transfer, pages of infosec and quality assurance exhibits, and somehow, you’re indemnifying the customer for everything under the sun, including damages if Santa has to replace all eight reindeer.
We can’t accept this as-is and the CEO has eyes on this deal!
And it’s my problem and responsibility to resolve alone!
Or is it?
Over the years, I learnt a few truths and mindset tricks on how to deal with this type of situation:
What’s your experience?
If you found this useful and want more insights on SaaS contracts, grab “10 SaaS Contract Basics You Must Know!” Download here.
