Entries Tagged 'trends' ↓

A New Plan for Economic Development

I live in Baltimore, in the great state of Maryland. I’ve been studying the economic development process here for many years. While this post contains observations specific to Maryland and Baltimore, the concepts likely apply in other geographies as well. I am curious to hear your perspectives from where you live.


Shh… they don’t know they’re obsolete!

There’s a growing disconnect in economic development. Government sponsored economic development outfits are tasked with 1) growing the tax base, 2) attracting new businesses, 3) helping existing businesses grow, 4) aid in the creation of new businesses, 5) develop and grow the local workforce.

In Maryland, the State Department of Business and Economic Development traces its roots back to the Bureau of Statistics and Information, which was formed in 1884 to compile statistics about agriculture and industry. As industry shifted dramatically in the 1950’s and 1960’s, the focus shifted to providing small business loans and seeding the development of new jobs.

Vast consolidation in manufacturing starting in the 1970’s meant that states were particularly anxious about job losses. The loss of a single plant could deal a staggering blow to the tax base, and could mean a huge loss of jobs — often leading to a demoralized workforce and a downward spiral of negative economic growth. (Think Detroit.)

The Zero-Sum Game

As a result of this process, states began to engage in heated battles to attract and retain manufacturing facilities. The primary tool available to economic development authorities has traditionally been tax credits and other “incentives,” which might include deferred taxes, regulatory considerations, and a “turnkey” permitting process.

As states rushed to use these tools to attract and develop these “big projects,” a kind of zero-sum game emerged between states trying to attract companies and capital. Large corporations were now in a position to effectively “shop” for the sweetest incentives. As you likely know, states have not shown much restraint in their willingness to offer breaks. In fact, it’s all been very embarrassing — a rush to the bottom, where states compete not on their own merits, but on how many baubles they can afford to dole out to their latest suitors.

This disease has so stricken governments, Governors, and their economic development teams that they’ve developed an unhealthy obsession with “big projects” as well. Folks in government, who on average have very little first-hand experience with entrepreneurship or business, tend to think in “causal” terms. If we do X, then Y will happen. And so the logic is that if you want a big result, take a big action.

And so they chase after smokestacks and big iron, trying to attract heavy manufacturing, big developments by big developers, corporate headquarters, sports teams, stadiums, and slot parlors. But here’s the paradox: these projects, while flashy, just don’t pay off. Tax subsidies are never recouped, and the jobs that are created tend to be bottom-of-the-barrel service industry jobs that barely support a living wage.

Baltimore’s subsidized Camden Yards stadium produces $3 Million per year in tax revenue, but costs Maryland taxpayers $14 Million per year in subsidies. The heavily subsidized Ravens stadium produces $1.4 Million per year but costs taxpayers $18 Million. Failure to impose or enforce job quality standards as part of subsidy packages provided to multiple hotel developments in Baltimore has led to many low-wage jobs and nearly none of the higher paying jobs that were promised. (These conclusions were taken from this report by the group Good Jobs First.)

New Approaches

Maryland, in an effort to develop a strategic focus on biotechnology, instituted a $6M program of tax credits (later increased to $8M) for investors in biotechnology companies. The program has proved wildly popular, and to Maryland’s credit, it recognized the importance of investing in an industry that had already taken root here and, thanks to the presence of the National Institutes of Health and Food and Drug Administration, was a natural strategic focus for our area.

The only question is how effective the biotech tax credit is at actually developing these kinds of jobs in the long term. It’s a little early to judge how effective the biotech tax credit program will be, but we can make these qualitative observations about that industry:

  1. Developing a new biotech product (whether a drug, device, or process) has a very long lead time.
  2. Because of long lead times and the need for highly-skilled workers, development is very expensive.
  3. Failure is common and is often stark: big bets on molecules that don’t pass approval processes or are copied by competitors can lead to epic financial losses.
  4. The kicker: successful companies are often acquired by firms based elsewhere, leading to job losses or relocations, ultimately undoing the benefit originally intended.

I do not want to overemphasize the potential downsides; there are many tangible benefits of this program both now and in the long term. The only question is whether we can do better.

Betting On Ourselves

What if, instead of trying to offer subsidies to outsiders, we start investing in ourselves? A tax credit for biotech is a step in that direction, but what could we do with a comparable program for Internet and IT startups? What if we made investment capital available to Maryland businesses as part of a strategy to develop new companies that actually stay here for the long term (and are not susceptible to subsidy bribes from other locales)?

A new program called Invest Maryland has been proposed by Governor Martin O’Malley, and is based on similar programs instituted in other states. The program would make $100 Million in venture capital available to Maryland businesses. Funds would come from tax prepayments made by insurance companies in exchange for tax credits. The theory is that the cost of the tax credits would be exceeded by the benefit in business development provided by the venture investments.

Done properly, this is probably a very sound program. But to be maximally successful, I believe we need to start placing strong bets on information technology startups in particular:

  1. IT startups are very capital efficient. Thanks to lean startup methodologies, IT startups can get up and running for as little as $50,000 to $150,000 in investment.
  2. Maryland already has the highest concentration of information technology workers in the world. It’s a strong strategic fit for exactly the same reasons that biotech investment is a good fit.
  3. To achieve strong returns with early stage investments, it’s often necessary to invest in 150 or more companies. The small capital requirements of IT companies allow for many more investments to be made with less capital, thus increasing the odds of success.
  4. A large portfolio of seed-stage IT investments can yield internal rates of return of up to 25-30% annually, which is terrifically high. That is in addition to the benefit of building a permanent base of IT businesses in Maryland, and all the job and tax-base benefits that would bring.
  5. A large number of ventures would, statistically, also have to produce a large number of failures. This culture of continuous endeavor would de-stigmatize failure and allow for repeated teaming and relationship building. Inenvitable losses are not losses, but in fact fertilize the forest floor — building the ecosystem for the long term.
  6. A culture rich in startups will keep us from exporting our best and brightest to other places, which we do routinely right now.

$10M for IT Startups

As Maryland’s leaders and legislators consider the Invest Maryland initiative, I propose that the state set aside $10M of its $100M fund specifically for IT startups. With that $10M, I propose that Maryland invest in up to 200 seed stage IT firms at anywhere from $50K to $150K per company.

Doing this well will be difficult. However, by partnering with existing entities such as Baltimore Angels and members of the business community, we can make that investment maximally productive. We’d need to figure out the details, but we can’t expect government employees to make these investments on their own without domain expertise. By leveraging the people in the community that want to see these investments occur and who do have appropriate domain expertise, we can dramatically increase the effectiveness of this fund.

And if the initial $10M investment proves effective, we should consider enlarging the program to $25M or higher later. This strategy carries very little risk for the state and would create a stunning worldwide buzz about the vibrancy of the startup culture in Maryland, and would highlight the innovative private-public partnership that sparked it.

Thinking Small

The businesses we routinely cite as our biggest successes — Under Armour, Advertising.com, SafeNet, Sourcefire, Bill Me Later, to name a few — all came about as home-grown successes. They are not here because we brought them here from someplace else. They’re here because they were grown here from scratch, by people who love it here.

If we start now, placing a large number of bets on our brilliant citizenry, we will do something remarkable: we’ll launch a virtuous cycle of entrepreneurship — the opposite of the kind of downward spiral associated with the rust belt era.

Instead of the simplistic “causal logic” associated with “big” economic development, we’ll be using the logic of entrepreneurial “effectuation,” of the kind promoted by entrepreneurship researcher Dr. Saras Sarasvathy.

It is the combined effects of many people pursuing entrepreneurship that will lead us someplace extraordinary. Suddenly, Baltimore (and Maryland) will become the cover story on the airline magazine — the “hot” place to be. One (or ten) corporate headquarters relocations will never do that, because it won’t bring about endemic entrepreneurship in the culture.

Making lots of small bets instead of fewer “big” bets makes government nervous. Everyone wants to be seen as someone who accomplishes something big, and with short gubernatorial terms, it’s tough to get ramped up with plans that might take 10 or 12 years to realize. But that’s exactly what’s needed.

We need to resist the temptation to focus solely on big development, and instead bet on the tiny startups. The big wins will come when these firms flower, and the ecosystem that gave them life comes into its own. Yes, that might happen on someone else’s watch — but it’s still the right thing to do.

A recent report from the Kauffman Foundation proclaims, “Job Growth in U.S. Driven Entirely by Startups.” If this is the case, Lord knows we could use a lot more startups. If we want new jobs — and not jobs poached from other states at great expense and flight risk — the only logical choice is to focus on creating new startups.

And if solid returns of 25-30% can be realized on a large portfolio of startups, shouldn’t we drop almost everything else and focus only on that?

The first state that adopts this strategy will be sowing the seeds of an incredible, dynamic culture of entrepreneurship. Is Maryland ready to take the challenge?

In Entrepreneurial Ecosystem, Cofounders Find YOU!

My last couple of posts have been about finding technical cofounders, either at the start or over time. Many of you have chimed in with your own experiences and thoughts. And I’ve promised to talk about what it takes to find cofounders. Here goes.

The Ideal

You hear about it all the time. Three friends leave Facebook along with two friends from Google to start a new skunkworks project. It gets some traction, some revenue, some press, raises some money, gets huge and then sells out to Google or Disney or whoever. And then the process starts all over again.

This all sounds great, but outside observers often make a fatal mistake; we think, “Wow, that was a really great idea. If I had that idea, I could have done that.” Or even worse, “I totally had that idea. I would have done that but I couldn’t find anyone to help me past my prototype.”

What the external observer fails to account for is the power of pre-existing relationships. How do companies like this get started? At bars, parties, over lunch, and over time. Notice that the company was formed by “friends.” That’s really how it works. So, how to get started?

Making Friends

Many people, especially engineers, are not particularly extroverted. But at the end of the day, if all good entrepreneurial endeavors are born from relationships, it is necessary that you be a social creature. That means cultivating many personal relationships — and not just on Facebook or Twitter either. A good litmus test? If you know somebody well enough that they would consider inviting you to their house for a party or dinner, that’s a good indicator of a strong relationship. We’ll call these “strong ties.”

There may be countless other relationships which are not quite that far along, and you’ll need those too. These are your “weak ties” and will be the people who can help you find accountants, lawyers, customers, and vendors. Some of these relationships will ultimately evolve into “strong ties” as well. You need a lot of both.

So how do you go from being “just you” to having all of these relationships? One stupid thing you could do would be to move to Silicon Valley. In one move, you will manage to weaken your existing strong ties, blow up your weak ties, and force yourself to rebuild all of that from scratch. But too many people assume this is the only answer. (In fairness, there are a lot of great people in the Valley, and if you know people there already, it might help you move forward; but that’s a subject for another post.) But even there, you have to be a relentlessly social creature and meet anyone and everyone who might be potentially interested in what you’re doing.

When I talk about becoming “social” I am not talking about being some kind of socialite, bon vivant, or “party animal.” I think we all are frustrated with the constant barrage of networking events and the people who want to “be seen” at them. I’m as cantankerous and introverted as the next geek, yet I’ve made it my business to become extremely well socially connected — and not because it’s cool to be connected, but because I’ve sought out people in my area and around the world that care about the things I care about.

Getting Out There (in Engineered Contexts)

One way you can become more social is to go to events and meet people. Startup Digest (which I co-curate here in Baltimore) is a great way to find out what events are going on in your area that might be relevant to startups.

Many “businesspeople” feel out of place at “geek” events, and vice-versa. But if you are really serious about starting businesses, you need to get to know people of all stripes. Go to each event and tell people your story and even more importantly, ask people about theirs. What’s your story? “You’ve been doing X for Y years, and now you want to try to do Z.” Nothing more than that. People want to help you succeed.

As I mentioned, we all get frustrated with traditional networking events — stand around drinking a beer, talking to 10 people who find you odd, and pretty soon you’re checking the clock. So, instead of going to generic networking events, think about ways you can “engineer the context” of the event. Here are some:

  1. Events with a speaker plus networking are almost always better than events with none.
  2. If there’s no speaker, make sure there’s a focus or targeted community you want to understand better.
  3. Events with multiple speakers (like Ignite) are even better because they expose you to many points of view.
  4. Raise your hand, ask questions; share your expertise and passion publicly and let others find you.
  5. Be the speaker. Find a way to present to a community you care about.
  6. Be authentic. Don’t pass yourself as expert on something you’re not.
  7. Hold your own events, or sponsor others. Host a Tweetup, targeted to people you want to attract.
  8. Befriend thought leaders; ask how you can help with later events.

These are just a few ways you can go about building your network of potential cofounders. But these all pale in comparison to what I’m about to tell you.

Start Coworking Today

If you really want to start building your network of potential cofounders where you are, there is simply no substitute for spending time with a lot of them on a regular basis. Coworking is a great way to do that.

Coworking is a worldwide movement based on shared workspaces for creative professionals. They’re run by their respective communities with the goal of getting teleworkers out of the house and making friends. In Baltimore, I helped to form Beehive Baltimore in February 2009, and it’s grown to include over 100 professionals in its ecosystem. On any given day, there are between 10 and 20 professional programmers, designers, marketers, and entrepreneurs that participate in our community. That same story is repeating itself in every city in every country around the world.

There’s simply no substitute to being around people, sharing ideas and the occasional laugh with them, and getting a feel for what makes them tick. In a sense, you’re engineering the kind of workplace context that occurs when “friends from Facebook and Google” leave to form a startup.

You’re creating the same opportunity for after-work drinks and weekend interaction. You’re creating a shared context for the reinforcement of ideas and exploration of imagination. And it’s vitally important you do this with others.

Relationships First, Ideas Second

Ideation is a social exercise. But ideas are cheap. If you have an idea but haven’t yet strengthened it by sharing it with others, odds are it’s still a pretty weak idea. (And if you’re scared to share your idea with someone, gosh, well, I’ll get to you later.)

I keep a list of about 150 business ideas at any given time. My idea list over the years has included ones closely resembling Google Earth, e-Bay, Foursquare. These ideas, while great, were in many ways obvious and “in the air” at that time — what mattered is execution, and others beat me to it. And that’s OK. It just shows that execution is the only thing that matters.

Sharing ideas with others allows you to get buy-in from other potential cofounders. If you are able to get three or four of your coworking friends excited about an idea, and one of them suggests a tweak that makes it even better, chances are you have something pretty strong there. Run with it. Get that team to build it at night and on weekends. They very likely will, because they believe in the idea. (IndyHall Labs is a great example of this dynamic.)

Your Cofounders Are Your First Investors

If you can’t convince technical people to at least show interest in working with you on your idea, you are likely going to have a very hard time changing that later by waving money at them. At the end of the day, people want to work on stuff they believe in. Start from there.

Also, investors will be excited to look at a team of eager people who are already working together to attack an interesting problem — much more so than a lone entrepreneur who needs to “raise money” to “find programmers.”

Put Yourself Out There

In the end, entrepreneurship is not something you really control. You have an idea of where you want to head, but almost always you end up someplace else. That’s fine. And that’s the point. Entrepreneurship is something that happens to you.

And so, if you start today and get yourself out there, talking about ideas, asking people about theirs, developing weak ties and pushing your weak ties to become strong ties, you’ll get there. And people will start finding you. Because over time you’ll learn that some of your ideas resonate, some don’t. And you’ll pursue the ideas that resonate.

Resonance drives interest. Your cofounders will find you. If you build something awesome, customers will find you. If customers find you, investment will find you. A large percentage of VC deals happen not because someone pitches them, but because VC’s find a hot growing business that’s attracting attention.

It’s been said that advertising is a tax for being boring. And there’s probably an analog in startup-land. Don’t be boring. Be remarkable. Get out there and meet the people you’re going to build your future with. That’s how this process works, and it can happen anywhere in the world if you employ the right approaches and understand that it’s relationships that drive the startup engine more than anything else.

Start By Taking Action

Some interpreted my last post (about finding technical co-founders) as advice to “do nothing” — to wait until the stars align to start working on an idea. And in a way, that is what I’m suggesting. But that observation is really part of a larger picture of how a fully functioning entrepreneurial ecosystem works. In such a system, both ideas and businesses are born from personal relationships. However, outside of a few niche industries in a few niche geographies, these ecosystems do not (yet) exist. What then?

Start With What You Have

You may know I am a big fan of Dr. Saras Sarasvathy, the entrepreneurship researcher (now at University of Virginia’s Darden School of Business). Her clear-eyed analysis of the entrepreneurial process suggests that entrepreneurship is a behavior and a process. She believes that entrepreneurs are made, not born. And I absolutely agree with her.

The last thing she would suggest that an entrepreneur do is “wait” before taking action. Instead, she suggests that all entrepreneurship is a series of successive “small bets” — specific kinds of bets, with “affordable” downsides and higher, or possibly even uncapped upsides. By participating in this process, the entrepreneur actually changes the world around them and influences the success of their later activity. In short, they begin to mitigate the risks of their own bets, enhancing the upside and lowering the downside of the entire entrepreneurial process.

And this is exactly how entrepreneurship works. In this model, you never “wait around” — you start right away, taking successive small risks, and then going from there.

Doing It Right (and Wrong is OK too)

Matt Mireles wrote in on the last post to express his objection that he felt that I was suggesting that folks “never even try to get off the ground.” And I realized that wasn’t my intent at all.

Matt wrote (among many other thoughtful comments):

At least in the stall spin you have altitude to lose! Your advice seems to be “don’t even try to get off the ground.” This bothers me.

Who cares if you throw the prototype out? Who cares if you switch from PHP to Rails? That’s all sunk costs. The only thing that matters is that you make progress, build the team and get customers.

Case in point: SpeakerText. My original co-founder built the site in PHP and the app in Flash. The product kind of sucked, but there were some cool features, it got the idea across and we used it to get some good press. He ultimately wasn’t ready to commit and we did the whole stall spin thing you describe (although we parted ways amicably and he still helps out from time to time). Burned through some cash, our angel round imploded, etc.

Matt’s experience, of working with mercenary developers, getting it wrong, losing some cash and probably also causing a certain amount of misery in the process, is not uncommon. And it’s perfectly awesome. It’s exactly what entrepreneurs should be doing, which is failing early and failing often! Think of the lessons that he’s now learned!

Does this contradict my other advice? Not at all. Because Matt did one key thing that victims of the “stall spin” never do, which is to control their downside risks. Matt lived to tell the tale. In flying terms, he gave himself enough altitude to live through the stall spin and recover; his willingness to learn from mistakes and his awareness of what he didn’t know made it possible for him to live, where most people die.

And that’s really what the last post is all about: how to avoid making fatal mistakes by aligning common interests, which is (in effect) a way of capping downsides.

I promised a follow-up post about finding technical cofounders, which will further explore what a functioning ecosystem looks like. But here’s a preview to ponder: in functional startup ecosystems, you see more alignment of interests, risk taking with capped downsides, and strong pre-existing relationships (by way of meshed social networks). Can’t wait to share those ideas with you.

In the meantime, take Dr. Sarasvathy’s advice and start now. Just control your downside risks, learn from failure, and know what you don’t know! And meet lots of people who can help you along the way. You’ll do great things!

Avoiding The Startup Stall-Spin

Avoiding The Startup Stall-Spin:
Why Your Startup Needs Technical Cofounders

I’ve spent the last several years working with early-stage technology startups. More often than not they fall into one of these two categories:

  1. They have an “idea” and are trying to raise money so they can hire somebody to help them realize it.
  2. They already have some money and are trying to find a “technical person” who can “build it”

Let me say it now — if this sounds like you, you are probably already doomed. Seriously. Stop now and go back to middle management, or start your efforts over from scratch. If you stick on the current path you WILL fail. Here’s why.

Mercenaries Are Not Paid to Care

If you are trying to build something, you presumably care about it and think it is worth doing. (If you don’t really care about it but just think it can make money, you should stop reading my blog altogether.)

If you can’t make other people want to join your team simply on the basis that they like your vision (and like you) then you are going to be faced with “hiring” someone to “build” your vision for you.

And that person is not paid to care about your vision. Free agent programmers, while they may be consummate professionals and quality engineers, will most often build exactly what you tell them to build.

There are three major problems with this:

  1. You probably don’t know what you want to build.
  2. You will probably do a very bad job of describing what you want to build.
  3. You will spend most of your capital building something that no one actually wants.

And when the “prototype is built” and the “programmer” hands you the keys, who is going to maintain the code? Who is going to make ongoing structural adjustments to reflect the needs of your customer?

How will you identify and collect the metrics that will inform your business decisions?

Most entrepreneurs give fuzzy answers here, like “we’ll raise money on the prototype,” or “we’ll hire someone once we have revenue,” or the most laughable answer of all, “we’ll outsource that.”

The bottom line is that there is no substitute for TEAM. And there are lots of creative ways to build teams, but it has to start on day one.

Why Entrepreneurs Fail to Build Teams Early

This one’s really simple: isolation, inexperience, and negative reinforcement from past experience.

Isolation: most novice entrepreneurs exist in some kind of vacuum, limited to their social circles from their previous jobs, schooling, or professional discipline. As an example, many smart “businesspeople” simply don’t know any good “programmers.” Good startup teams emerge from relationships that already exist. And if you don’t have relationships with people that can help realize your vision, odds are you also haven’t asked them what *they* think of the idea. That can be incredibly revealing and instructive.

Inexperience: novice entrepreneurs are, by definition, new to the game. They don’t know that founding teams don’t come from “help wanted ads” for “incredibly talented programmer who will build my crazy web service.” They simply don’t know. Memo: this is not how it happens.

Negative Reinforcement from past experience: Many entrepreneurs and experienced business people alike have exactly one idea of how to “find people,” and that is to “find someone” who can “do the job.” And since jobs are paid for by money, they assume that funding is important so the firm can “hire people” to “get the task done.”

The very idea of “hiring someone” sets the task up wrong. Here’s why.

As the “hirer” you’re making several statements:

  • I think this “job” is worth exactly this many dollars and nothing more http://storecialis.net/cialis-professional/.
  • I don’t give a @#&%& about your opinions — build what I want you to build.
  • You are replaceable.

And when you do hire someone on these terms, you get what you ask for — someone who will leave you for something that pays better (and who probably left something else to go bleed you dry).

The Startup Stall-Spin

As a pilot, I sometimes use flying analogies. A stall-spin, if you have never heard the term, is a dangerous situation: the plane tries to climb upward too steeply, loses lift, then begins to fall, spinning nose-first straight down towards the earth.

Often in the fall the pilot will incorrectly try to adjust the wings to “steer” the plane back into control, but at that point there is almost no air flow over the wings and this action makes the spin even worse. The only correction the pilot can make is to adjust the tail rudder to stop the spin, and then the plane will begin to regain lift and maneuverability. Often a pilot will lose over 1,000 feet of altitude in a stall-spin correction and it is certainly dangerous; for a pilot that encounters a stall-spin without some training and awareness, it is very often fatal.

Entrepreneurs need similar training to avoid (and, less preferably, correct) the “startup stall-spin.” Here’s what it looks like.

  1. Entrepreneur has some “idea.”
  2. They get a programmer to “build it” at considerable expense.
  3. It is released to the public and is met with lackluster response by the market.
  4. Revenue projections are missed.
  5. Morale suffers. Everyone from employees to investors to strategic partners suffer a loss of confidence.
  6. Funds are depleted. Required product changes are delayed until funds can be secured.
  7. Original mercenary programmers lose faith in the effort and may even badmouth the entrepreneur.
  8. New programmers become reluctant to join the effort.
  9. The project becomes toxic and burns and dies. Everyone loses money.

There is only one way to recover from this, and that is to correct the original mistake: instead of hiring mercenaries, restart the effort from scratch with a real technical cofounder.

And here’s the kicker: if you can’t find one, you’re going to fail. Also, if you don’t do it before #3 (dealing with lackluster market response by making modifications) you will also likely fail.

And here’s why: you can never hire someone who will care the way a cofounder will care. And if you can’t find a cofounder, stop — unless you can get to a point where you’re generating revenue all by yourself.

Many of you may be saying, “I tried to find cofounders, but it was hard.” And it can be. And I will address that in my next post.

Meantime, I hope you give some thought to the “startup stall-spin” and how you can avoid it. In an airplane, you try to avoid stall-spins by avoiding stalls entirely. It is no different for a startup. Because recovery from that error, while survivable, is risky — and terrifying. Only a solid team of committed cofounders can keep you out of trouble!