Contracts
In today’s post, I discuss how to deploy MSAs with technology vendors and service providers to help grow and scale your company’s business, how they’re different from Consulting Agreements, and when to use each.
One question I’ve been asked is this: Should my company sign an MSA or Consulting Agreement? The answer is: it depends on the type of relationship the company envisions with this vendor. Long-term relationships between companies often benefit from an MSA, where discrete projects are signed on over a period of time via SOW. The MSA outlines the general terms of the relationship, while each SOW handles the specifics of each project, such as start and end date, compensation, and milestones.
Consulting agreements, on the other hand, are often more appropriate for one-off or short term projects with a service provider, such as a business consultant, or more often, a software developer (individual or agency). However, note that it’s customary for individual software developers providing coding work for a company to sign consulting agreements, even when the work is ongoing and longer-term, with payment on an hourly or milestone basis.
Here are key common terms to include in MSAs, which should inform your discussions as you engage with service providers:
MSAs come in many variations to cover numerous scenarios and relationships, and include numerous other terms not listed above. It’s best to consult with a commercial attorney when considering a vendor for services, as he or she can best advise as to the type of agreement to use (MSA v. Consulting Agreement) and how to draft it to cover the scope of relationship you envision.