Vacation and Vacation/Holiday Policies

I am leaving for a vacation tomorrow for 8 days.  Heading to Poland to watch soccer with some good friends (Euro Championships).  Should be a blast.  I will have extremely limited email access (not bringing my laptop) and no phone.  I think I will just delete all emails received while I am away without reading them (and my out of office message will say that).  Likewise I am going to turn off my voice mail on my cell phone so no one can leave me messages.  Should be an interesting experiment.

Got me thinking about vacation and, in particular, holiday policies at startups.  I recently asked a friend of mine who is an employment lawyer about the rules.  Here is a run down:

1.  There is no obligation to pay anything extra to an employee for working on a holiday (unless, of course, the holiday work, plus other hours worked during that week, causes an “hourly” employee to work more than 40 hours in that week).  Paying extra for holidays is a typical policy in companies in which it is difficult to staff a holiday shift, but this is up to the company.

2.  There is no obligation to pay employees on designated holidays.  The holiday means only that the organization is not open on that day, and that there is no obligation to come to work.  Most companies do pay employees on designated holidays because it feels punitive to the employee to earn less in a pay period merely because there was a holiday.  And, of course, not having paid holidays is a recruitment disadvantage in many markets.  But, these are business reasons, not legal obligations.

3.  It is entirely within an employer’s discretion whether or not to have any holidays; which or how many holidays to observe; and what to pay for hours worked (or not worked) on a holiday — except, of course, that employees must earn at least minimum wage for all hours worked.

4.  It is entirely within the employer’s discretion whether to offer vacation days; how many vacation days to offer; whether to pay for vacation days or not; whether and how employees accrue vacation; whether or not employees can receive an advance against yet-to-be-accrued vacation; and/or whether to pay employees for accrued but unused vacation when they leave the company.

5.  However, if you do offer paid vacation, and you don’t want employees to be able to carryover vacation days from one year to the next and/or you don’t want employees to be paid for accrued but unused vacation when they leave you, then you MUST state that in a written policy that you can prove the employees received.

These are just some good holiday/vacation policy nuggets to keep in mind.  There are more.  As usual, consult a good lawyer!

Clear Communication

My VC partners (one in particular) make fun of me for being extremely literal.  If you don’t phrase a question or statement the right way or with clarity, I have a tendency to get confused and ask questions.  I actually think this comes from my years of practicing corporate law.  After all, if your lawyer cannot state things clearly, you have problems.  I guess I just like overly clear communication.  I also like overly open communication.  While I think that most people like clear communication, some are more open to open communication than others.

This might seem a bit petty and obvious, but trying to be very clear with communication is good practice.  But I am convinced that some purposely practice unclear communication.

Here is an example that made me laugh yesterday.  My partner and I were emailing back and forth about how to characterize an exit transaction where we received stock of a private company for shares in our portfolio company (often called a private to private transaction).  My partner wrote “Show the comparative exchange rate then……”  And I wrote back “What is a comparative exchange rate?”  Showing return multiples in a private to private transaction can be challenging.   We ended up simply writing “CVF received $XXX,XXX of Company ABC stock on $YYY,YYY dollars invested.”    To me, that is clearly showing the return based on the current value of Company ABC stock.  I still don’t know what a comparative return multiple is.  Moral of the story:  use simple straight forward language whenever possible.

One more tip for clear communication:  when emailing a bunch of thoughts on a topic, try listing them out with numbers (1., 2., 3., etc.).  It makes it way easier to read and way easier for the reader to actually respond as they can just respond inline in the original email.   People who email with me often see numbered lists.  I get some grief about it sometimes like “you are being too direct”.  Well, better direct than misunderstood.

If you have some tips on clear communication, pass them along.

When to Bring Up Valuation

If you want to scare off VCs, start your pitch with “we are looking to raise $X at a pre-money valuation of $Y”.   Stating how much you want to raise is fine and recommended.  In fact, even better to state how much you want to raise and how long that amount will last.

However, stating a desired pre-money valuation early in the process is not a good idea.  Here is why.  There are typically just a handful of pivotal terms in a VC deal and they fall into 2 categories:  control terms (like special voting rights for the Preferred Stock and board seats) and economic rights (like liquidation preferences, anti-dilution protection, whether the preferred shares are participating or not, and………pre-money valuation).

In my view, starting off a VC relationship by diving into perhaps the most critical economic term is kind of like, well, moving too fast on a first date.  The good discussion will happen, but give the relationship a while to mature first.  Seriously, pre-money valuation is a function of many things (team strength, size of market, IP, hotness of sector, etc.) that will not all be readily apparent at the beginning.

So, my suggestion is to not bring up pre-money valuation unless (i) asked by the VC or (ii) the relationship has matured to a point where you can sense that a term sheet is likely.  If a VC asks for your input early on in the process about pre-money valuation, be skeptical and careful in your response.  If you give an actual number and it is too high, you have just given that VC a reason to say no (as in “why do I want to deal with an entrepreneur whose expectations are out of whack with my reality”).  Instead, I suggest something like this:  “We expect a valuation commensurate with our state of product readiness and company maturity.  We look forward to discussing that in more detail when your interest level merits”.

Answers to the question that I think are likely unproductive (again, I am talking about early discussions when you are building the relationship), include:   “$6.5mm is expected to buy 25% of the company”.   That is saying exactly what the expected pre-money valuation is.   Or, “Our post-money of our Series A was $10mm”.   No question that a pre-money for the Series B might be above $10mm, but it all depends on a bunch of factors that need time to flesh out.

Bottom line:  valuation discussions too early in the VC relationship game are a huge distraction and will likely backfire on you.   The exception is when you have a ton of interest (the VCs are just crawling over you).  That demand will accelerate the relationship building and the valuation discussion.

The Twitter “Patent Hack”

Every once in a while I read a post that just cries out “re-post”.  Today, Fred Wilson wrote about the Twitter “Patent Hack”.  The post is not extraordinary.  Twitter is extraordinary for its actions.

In a nut shell, when an employee works for a company, that employee signs an assignment of inventions agreement.  This means that inventions that the employee creates on the job are owned by the company.  I hope that you see this as an obvious necessity.  The company is paying the employee to create and the company needs those creations to function and operate.

Twitter has its employees sign assignment agreements (really, every employer has its employees sign them assuming they have good legal input).  BUT, what Twitter has done is to tweak its assignment form to say that it will only use the inventions so assigned for defensive purposes in the event it is later sued for patent infringement.  So, it will use inventions, particularly those that get embodied in a software-based patent, to defend against an infringement claim.

Importantly, Twitter will not use any such inventions (again, think patents) to offensively go after a competitor that might be infringing.  Twitter does not want to stymie innovation by its competitors in the software space.  And, even further, would require any buyer of the Twitter patents (for example, a buyer of Twitter in an acquisition) to get the original inventor’s (i.e., the Twitter employee who originally assigned the invention to Twitter) consent to use the patents offensively.

This is really interesting.  Plain and simple, Twitter is trying to start to de-claw patent trolls in the software patent realm.   I like what they are doing as it applies to software patents.  Truly innovative!

Lessons Learned from Bill Gross

26 minutes is a long time to me, particularly when it is spent watching a video on startup lessons learned.  Well, I just spent 26 minutes and 14 seconds watching Bill Gross at LeWeb 2011 (from December 2011) talk about some lessons learned.  Fortunately he used excellent examples so I was really content watching the entire thing!

My first exposure to Bill Gross was back in 1996 when I represented (as a lawyer) a company from Ithaca in which IdeaLab invested (that company was sold to Microsoft for $50mm about 6 months after the investment).  IdeaLab was then, and still is, Bill’s startup incubator (truly an incubator and not an accelerator).  Anyway, I did not meet Bill then and have not met him to this day.  In fact, many of the things that I have heard about Bill from others are not too flattering.  So, needless to say, I had a preconceived notion of Bill Gross in my brain.  Perhaps that is why I clicked on the video link when it landed in my inbox (thanks to a friend of mine for sending it to me).  In any event, it is a super video and I am looking forward to recommending it over and over again.

Here it is:  Bill Gross LeWeb 2011 video.   Enjoy.