Archive for the ‘Software’ Category

Letter of Intent Deal Terms for a Company Sale

Following the nondisclosure agreement, the letter of intent (LOI) is typically the first step in formalizing the company sale process when a company auction process is not involved.  The LOI stage is usually an exciting time for the seller—the seller is full of optimism, there is no deal fatigue, and the new relationship with the buyer has not yet been tested by heated discussions.

The LOI can accomplish a lot.  At a fundamental level, it establishes whether there really is a deal on key issues.  Often times, first time entrepreneurs and those who have not been through a company sale process are willing to proceed with a lengthy “no shop” or “no talk” exclusivity requirement, based only on a non-binding agreement on price.  While purchase price is obviously an important term, it by no means is the only important term.

In most deals, a seller in a company sale process has the most leverage at the LOI stage of negotiations.  The seller has not invested a lot in the deal and it’s the easiest point at which to just say “no” to a request of a buyer.  Rarely, however, do terms get better for the seller after the LOI stage.  On the flip side, buyers will typically take aggressive positions after the diligence process or on the initial draft of the purchase agreement.  They know sellers have committed a lot to the deal and at some point in the process, become committed to making the deal happen for a variety of reasons.  Often, a seller is willing to concede more at a later stage than what the seller would have been willing to do earlier.  As a result, it’s typically a good idea for a seller to get tentative agreement at the LOI stage on key terms that inevitably have to be negotiated.

From a seller’s perspective, here are some of the areas worthy of consideration of including in the LOI:

  • Deal structure, especially if the seller is looking for capital gains treatment
  • Items that affect net proceeds at closing
    • Escrow holdback amount and time period for the escrow, or a statement that there will be no escrow
    • Working capital adjustment amount or a statement that there will be none
    • Earn-out (if any) or a statement that the listed purchase price does not include one
  • Duration of the survival period of seller’s representations and warranties
  • Basket and cap for post-closing liabilities
  • Indemnification cap exclusions
  • Employment requirements of key individuals or at least which individuals or types of individuals the buyer intends to retain, post deal (e.g., 80% of software engineers)
  • Targeted closing date

Buyers will often resist some of the provisions under the guise that, “we don’t know enough information at this point, so we prefer to agree upon those terms after the diligence process.”  The same thing though could be said of the purchase price.  The reason to negotiate the points earlier is that it places the burden on the buyer to change them later.  Once a term is in the LOI, the parties usually tend to feel sort of a “moral” obligation to adhere to those terms.  Buyers frequently need a major diligence finding to justify a modification to a term contained in the LOI, even though those terms are usually nonbinding.

Including more deal points in the LOI also helps to limit surprises later that may surface, such as, “we always require sellers to have no indemnification cap for breaches of representations related to intellectual property.”  Moreover, without touching on the key deal points at an early stage, it’s hard to determine whether the parties have a basic meeting of the minds, even with the assumption that there will be no material surprises in the diligence process.

As with most other things, deciding on the appropriate amount of detail in the LOI is a balance.  On the one hand, it requires including enough detail to help ensure that there really is likely a deal, while also, from the seller’s perspective, taking advantage of the leverage that a seller typically has at the LOI stage.  On the other hand, the seller should not put too much pressure on the buyer at the formative stages in adding too much detail and unnecessarily elongating the time period of the LOI stage.  Striking the right balance is the first step in a successful sale process.

by Matt Storms | Permalink | No Comments

 

Closing the Software Deal – Part 2

Closing software deals with less legal hassle demands more than just a good agreement – it requires a well-informed and well-equipped sales team. If your company offers SaaS or licenses software to other businesses, consider these additional tips to close deals quickly and at a lower legal cost.

Build a Legal FAQ

Your team should know most of what’s in its agreement and why it’s there. Customer stakeholders who are not attorneys are quite likely to ask your sales team questions that are both ‘legal’ and important to the deal, long before an attorney is involved. Getting the answers right demonstrates your company’s experience, preparation, and ability to ensure customer success, all while speeding the deal to close. Getting the answers wrong – or not knowing the answers – simply decreases the likelihood of closing the deal or increases customer acquisition cost for no good reason.

A few examples of questions for which most sales teams should know the answers, particularly in SaaS deals:

  • What are the details of your SLA? Do you offer credits or refunds? If so, how are they calculated? What’s been your uptime historically? When do you schedule routine maintenance? Are you using third party hosting providers? If so, who?
  • Do you use data uploaded by your customers into the platform for any reason other than providing your service? If so, what are you using and why are you using it?
  • Are customers able to download their data from your platform? If so, how quickly can it be done? In what formats? Where are you storing that data?

You may even find it helpful to develop a ‘legal’ FAQ written by your attorney with guidance from your sales leaders. Sales leaders can ensure the FAQ includes answers to the legal-related questions they commonly field in the trenches, while your attorney can ensure the answers reflect what’s in your agreement. When new questions come up on a recurring basis, your attorney can also update your agreement where appropriate.

Create a Decision Tree & Fallbacks

Assuming you’ve closed enough software deals to know what is and is not negotiable in your agreement, how can you be more efficient? When you’re part of a small startup, virtually everything filters up. But, as your company grows, that cannot continue when the number of deals grows as well. What types of matters need to be on your plate – and what types of matters can you leave to the head of sales? Are you leveraging what you negotiated in prior deals?

They say the most important question in law is, “Who decides?” That’s absolutely true when closing a software or SaaS deal. If certain issues are commonly negotiated and you concluded they are minor, then consider whether it’s more efficient for your company to leave those issues to someone else. If other issues are more significant, then make clear who does and does not have the power to negotiate those items.

When you leave certain issues to someone else, provide alternative provisions that you and your attorney wrote and approved. You can even create an alternative version of your contract with footnotes for each of those alternatives.

Train the Team

Obviously, these solutions will not matter if your team does not know how to use them. But by this point, you may be asking yourself whether they have the time for what amounts to legal training. After all, they are busy trying to close deals, and they want to stay focused on the big picture.

If you’re convinced that some basic tools and process can help your company close software or SaaS deals with less legal hassle, put those tools to good use. Build an FAQ and iterate on it. Document a decision tree. Provide written alternatives. Critically, take the time to train your staff on how to use them. An hour of legal training and negotiating during employee onboarding or annual meetings can prevent more expensive back and forth months later. At the very least, the materials become simple resources your reps can leverage if they don’t remember the details.

by Paul Temple | Permalink | No Comments

 

Closing the Software Deal

Is your software deal stuck in legal limbo?  Need to get it closed to ‘make numbers’ before EOQ?  If your company offers SaaS or licenses software to other businesses, consider these three tips to close deals with less legal hassle.

Don’t bury the lead

SaaS agreements and licenses that do not make the fees obvious to your customer’s counsel do no one any favors.  If the deal means your customer will pay you $25,000 or less per year for three years, and their legal counsel can quickly see that, counsel will very likely treat it accordingly – hopefully with a lighter touch than a deal 20 times that size.

If you instead bury the dollars and cents deep in the agreement, or worse still – put them on a separate file your customer’s lawyer never receives – the lawyer may be more likely to spend more time and more money aggressively negotiating with you.  $25,000 worth of negotiation for a $75,000 deal makes no sense.  For large deals, expect a thorough review no matter where you put the financial details.  But don’t encourage your prospective customer to spend more on legal expense than makes sense relative to the deal size.

Also, take a moment to describe your platform in the agreement.  In my experience, agreements from some hot names in tech right now lack minimal descriptions of their platforms.  If your customer’s attorney knows nothing about the offering, you’re much more likely to wind up negotiating issues that are totally irrelevant to your deal.  That’s nuts.  Take a moment to describe the offering, if only at the most basic level.  You will save your team and your customer valuable time and legal expense.

Know your market

Are you selling into a regulated industry?  If so, do you know what regulatory burdens your customers face, and if they’re changing?  Does the platform you’re pitching impact your customer’s ability to comply?  If you don’t know the answers to these questions, you’ll find out sooner or later – perhaps painfully.

For example, if you’re selling into the healthcare industry, you should know whether your offering will impact your customer’s ability to comply with HIPAA.  You should know what a BAA is, and you should be prepared to answer why your company will or will not sign one.  Another example . . . if your offering will gather information from people residing in the EU, you should be aware of European privacy law and potential changes that may impact you and your customers.

Don’t wait until your customer’s counsel brings up these and other market-specific issues during negotiation.  Draft a deal that accounts for them and be prepared to explain your thinking.

Plan for what comes next

If you’re like most in the software business, you live and die with churn and LTV.  You’re much less likely to see positive movement on those metrics if you don’t have a clear plan to ensure customer success with your software or platform.  In other words, you need to meet customer expectations about your offering.  Great software companies exceed those expectations.  Others let sales teams close the deal and throw it over the wall – leaving things like implementation or integration to another day.  Don’t be that guy.

One way great software companies set expectations is with a plan that the customer approves early in the relationship.  This doesn’t make sense for every provider, especially low price providers, and the plan doesn’t require every little detail.  But for high-touch, high-end solutions, customer users and leaders should play a role in crafting a plan that the customer approves.  Be open to this, even if it impacts CAC in the short-term.  It saves both you and your customer time and money in the long run, establishes trust among their users and your staff, and reduces the risk of buyer’s – or seller’s – remorse.  Critically, you’ll be more likely to start customers on a path to upsells, renewals, and referrals.  If your platform isn’t just “plug and play,” and your sales team already poured time and money into cultivating the deal, take a little extra time to set clear expectations and consider an early sign-off on the same.

by Paul Temple | Permalink | No Comments

 

Got EU Data?

Emerging tech companies take note – if you collect the personal data of European citizens from the United States, or otherwise transfer that data to the U.S., recent developments mean your legal obligations may change soon.

Background

Citizens of EU member states have an explicit right to privacy.  In practice, this means companies can transfer EU citizens’ personal data out of the EU only if the destination country has an adequate level of protection.

Historically, it has not been a problem to store EU citizen data in the United States.  Under an agreement between U.S. and EU regulators, which is often referred to as the “Safe Harbor,” a U.S. company could transfer that data to the U.S. by certifying to the U.S. Department of Commerce that it would adhere to European privacy principles.  The U.S. Federal Trade Commission, in turn, could bring enforcement actions against the company if it failed to comply.  More than 4,000 companies took advantage of the Safe Harbor to transfer data to the U.S., from Amazon and Google to emerging tech companies in the upper Midwest.

After Edward Snowden revealed that the US government may have indiscriminately conducted mass surveillance of EU citizens’ personal data, an Austrian Facebook user complained to EU authorities that the U.S. lacked adequate protections. On October 6, 2015, the Court of Justice of the European Union ultimately agreed and invalidated the Safe Harbor framework.

Bad Alternatives

The ruling had an immediate impact on businesses of all stripes that relied on the Safe Harbor, particularly emerging tech companies.  They were left with a handful of bad alternatives –

  • keep the data in the EU – potentially expensive or unworkable;
  • obtain user consent or use model contract provisions – also potentially expensive or unworkable, especially for companies already processing data on behalf of existing business customers with an EU presence; or
  • leverage binding corporate rules – a time-consuming process ultimately requiring approval of EU data authorities.

Worse still, the Court of Justice of the European Union ruling implicitly called into question some of these alternatives.  Recognizing the problem, EU regulators gave themselves and their U.S. counterparts until January 31, 2016 to find an alternative.  This set off intense negotiations among regulators.

Privacy Shield

On January 28, 2016 the U.S. Senate Judiciary Committee approved a bill that would allow EU citizens to sue the U.S. government for privacy violations.  Just a few days ago, on February 2, the European Commission and the U.S. Department of Commerce announced the outline of a potential Safe Harbor replacement, dubbed the “Privacy Shield.”  According to the releases:

  • U.S. companies will have stronger obligations to protect personal data of EU member state citizens. Among other things, they will be required to comply with the decisions of the EU data protection authorities regarding personnel data.
  • U.S. companies will remain subject to enforcement actions for privacy violations by the FTC, and EU privacy regulators will have the ability to refer complaints of EU member state citizens to the FTC.
  • If an EU citizen lodges a complaint regarding inappropriate activity by U.S. authorities, a new Ombudsperson at the U.S. State Department will review it.
  • Alternative dispute resolution for certain complaints will be made available for free.
  • The U.S. will commit not to indiscriminately conduct mass surveillance of EU citizens. S. guarantees regarding limits and oversight will be reviewed annually by the European Commission and the U.S. Department of Commerce.  U.S. national security agencies will be invited to participate in those reviews.

To Be Determined

The outline lacks many details that will prove vital to providing a meaningful and lasting legal alternative for U.S. technology companies.  Important outstanding questions include:

  • Will free alternative dispute resolution result in an increased number of complaints?
  • Will U.S. security agencies take up invitations to participate in annual reviews, and will those reviews be meaningful? If not, will the Court of Justice ultimately invalidate the Privacy Shield as it did the Safe Harbor?
  • Will the Privacy Shield be suspended if EU authorities conclude that the U.S. failed to comply with the Privacy Shield’s limits?
  • By when will the EU and U.S. finalize these and other Privacy Shield details? EU regulators suggested that final approval could take up to 3 months, but some EU lawmakers and privacy advocates are already arguing the Privacy Shield is not enough.

In The Meantime

While the Privacy Shield winds its way through the EU legislative process, the chair of the group composed of EU data protection agencies said the group will not take enforcement action against U.S. companies that continue to use existing legal alternatives like model contract clauses and binding corporate rules.  While these alternatives may be difficult for many emerging technology companies, they currently remain likely the only legal way to collect data from the U.S. of EU citizens or otherwise transfer EU personal data to the U.S.

by Paul Temple | Permalink | No Comments

 

AlphaTakes – Series A Preferred Stock Term Sheet (part two)

In this second of a two part AlphaTakes video series, Matt Storms discusses the second half of the Series A Preferred Stock term sheet for an emerging technology company, using the Series A term sheet published by the National Venture Capital Association.

Here are the key takeaways from this video:

  1. The three most common alternatives to anti-dilution provisions:
    • Weighted average
    • Full ratchet
    • No anti-dilution provisions
  2. Several provisions are not typically heavily negotiated in Series A financings:
    • Pay to play requirements
    • Attorneys’ Fees
    • Registration rights
    • Participation rights
    • Drag-along rights
    • No shop requirements
  3. Keep an eye on the big picture

by AlphaTech | Permalink | No Comments

 

AlphaTakes – Series A Preferred Stock Term Sheet (part one)

In this first of a two part AlphaTakes video series, Matt Storms discusses the first half of the Series A Preferred Stock term sheet for an emerging technology company.  He provides a summary of some of the key terms of the Series A term sheet, using National Venture Capital Association (“NVCA”) model document.

Here are the key takeaways from this video:

  1. The NVCA documents are great resources for understanding the Series A financing, but are fairly investor friendly.
  2. Typical preferred stock dividend provisions alternatives include the following:
    • If and when paid to the common stock
    • Accruing and cumulative
    • If and when declared by the board
  3. Most common preferred stock liquidation preferences alternatives include the following:
    • Non-participating preferred
    • Participating preferred
    • Participating preferred with a cap
  4. Preferred stock typically includes special voting rights, such as designating one or more members to the company’s board of directors and veto rights over certain company actions.

by AlphaTech | Permalink | No Comments

 

Announcing AlphaTakes—Videos for Emerging Technology Companies

We are excited to announce that in coming weeks, we are starting a new video series called AlphaTakes. The goal of the initiative is to provide clients and others with background on the variety of recurring issues that emerging companies face through their development, from startup to sale.  Our hope is that the videos will supplement the existing articles for emerging technology companies that is already contained on our website.

Technology Company Startups

For startups, we plan to cover topics such as the incorporation process, allocating founder shares, common mistakes of startups, and calculating the stock option pool.  We have a number of other ideas as well, based on the questions we receive from entrepreneurs.

Scaling Technology Companies

For operating companies that are scaling, we plan to have videos that go over the different types of financing structures, common mistakes of software companies, the Series A Financing term sheet, liquidation preferences, and anti-dilution provisions.  As bringing on employee talent and contracting are important for scaling companies, we also plan to touch on issues related to employees and contracts.

Emerging Companies Considering Sale

For companies considering a potential sale, we plan to cover common sale transaction structures, how to prepare for a potential company sale, letters of intent, and use of investment bankers.  We also will look at some of the commonly negotiated terms in sale transactions as well as recurring issues that arise during the sale process.

If you have any suggestions on potential topics for us to cover in AlphaTakes, let us know!

by AlphaTech | Permalink | No Comments