Skip to main content

Weekend Project: Contracts

I didn't work yesterday (much), aside from reviewing some contracts I'll need to sign prior to a gig I'm taking this week to help a friend. 

Contracts supplied by startups are typically onerous. Their lawyer may or may not be startup oriented, and will usually send some boilerplate of each category of contract, and leave it to the signatories to raise issues. 

I read every line and decide whether I can live with it or not; I can't afford to be prevented from making a living because of some overly paranoid boilerplate. At the same time, it's the startup's job to ensure they aren't hiring a trojan horse. 

Current and future investors depend on the startup's ability to compete, for instance, which is tougher when someone close to the company's secret sauce heads to a direct competitor.

So defining what constitutes a competitor is really important. Usually competition is defined very broadly--like high-level categories. An example: "...any company addressing the internet search market."  Huh. Does that mean Google? Kayak.com? Foursquare? It's so broad that I wouldn't sign something like that. 

You end up making reasonable suggestions to narrow the scope, hopefully without being too big a pain in the ass for the startup. The point is, it's not about you, it's about them, and they're right to be paranoid and protective of their work--to a degree.

At the same time, you sign a couple of these with a few different startups and end up with no place to work because of the overly broad non-compete statements. Contracts tend to be 99% over-protection and 1% about the actual business. Ugh!

Here are a few suggestions for startups hiring outside help:
  • Keep your contracts concise and short. The longer they are, the more time everyone has to spend on them, and that's time spent away from your highest purpose. 
  • Be specific and narrow about your protections; the broader the claims and protections, the more likelihood you'll have a protracted period of refining.
  • The four contracts are typically NDA, Non-Compete, Inventions, and the Consulting Agreement. There should be no overlap between these, but for some reason every startup I work with sends these with all kinds of overlaps--sometimes contradictory overlaps. Or better--consolidate them.
  • Don't obsess about locking everyone down with every last possible restriction. You need to get to work, you need the help, and you don't want to scare people away. It's highly unlikely someone's going to screw you, or be able to screw you. Your success comes down to your and your team's own execution. 
This is just off-the-cuff. Please chime in with your own rules of the road for contracts--I'd love to hear your thoughts on this. 

Comments

Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

The Real Jobs Problem

It's the economy, stupid.  Well, yes, it always has been, if you're in the distortion field of politics.  But whose economy? The pundits, the White House, the Republican candidates all miss the mark. They keep talking about debt, taxes, and monetary policy. None of those things tell the real story behind today's economy.  The Old Economy Keynes was right--in the old economy. Economy gets weak, pump some money into the economy through public works projects, which  1) puts people to work, which  2) boosts the economy and  3) generates new tax revenue, while  4) leaving us with another generation of reliable infrastructure to support  5) more growth (for growth's sake, which is another post).  The Beach Ball Imagine a beach ball, partially deflated to represent a recession. Got it? Now imagine the govt pumping that beach ball back up through sensible public investment (which we haven't seen for decades). The New Economy Same beach ball, same pum