David Croushore

A Man in Progress

The $1 Billion Challenge

In a recent article for The Economist, Ron Conway outlines fields where he expects to see the next billion dollar companies emerge.  While I generally agree with his prognostications, one line in the article struck me more as a challenge than a prediction.

“Perhaps 2012 will see a company develop a $1 billion business inside 12 months.”

That line got me thinking about a new paradigm for viewing business ideas.  After spending the last two years diving head first into the world of tech start-ups, I’ve seen some patterns emerging.  Everyone wants to be Google or Facebook (obviously), but at the same time most accept that they probably won’t be.  

What has struck me most when talking with entrepreneurs “on-the-ground,” trying to get their idea ready for the world, is how few of them are willing to pursue really big ideas.  Most of the (pre-launch) founders I’ve met are working on something that sounds like a nice feature to add to an existing platform.  Then there’s the Groupon clones or the “Facebook of” crowd.  

The common characteristic is that these entrepreneurs are thinking small.  Yes, We Are All Weird according to Seth Godin, and niche marketing may very well be the wave of the future, but that doesn’t mean that there isn’t room for more big companies.  Groupon (regardless of what you think of their prospects on the stock market) got so big so fast because it appeals to a broad audience.  Sure, each deal might target a niche, but the service is bigger than that.

The $1 Billion Challenge

But, what if some of us stopped thinking about the ideas, the technologies, and the things we wish Facebook would do.  What if we got a group of really smart people together and asked a simple question: Is it possible to build a $1 billion business in 12 months?  

That’s exactly what I want to try. At worst, it will be a thought exercise that guides the development of participants’ business models.  At best, we’ll change the world.  

I’m not proposing a startup weekend, though I think those are fantastic.  I’m proposing drawing a blueprint for how a company that could scale that fast would have to look, and if the big idea and the disruptive business model come together, then we’ll worry about starting up.  

If you’re interested in joining, drop me a line in the comments, or shoot me an email.  

Are you up to the challenge?

Comments

Race Report: Ironman 70.3 Eagleman

Yesterday I ran the Ironman 70.3 Eagleman in Cambridge Maryland.  I finished in 6 and a half hours, a shade above my goal of 6 hours, but not horrible.  Here’s how it all went down.

The river was a warm 82 degrees which made wetsuits illegal for the swim.  My tri-gear is not exactly swim friendly, which caused me to have some extra drag on the swim.  The buoys were really far apart at this race, so spotting was extremely difficult.  On 2 occasions I started heading for the wrong buoy until I realized no one was around me.  I probably added an extra 300-400 meters to my swim by going off course, and in choppy water that really adds up. 

Coming out of the swim, the water gets really shallow about 100 meters from the finish.  Everyone stood up and walked, but every step was really painful as you have to fight through waist-deep water to move your legs.  In the hopes of saving my legs for the bike and run, I swam until I couldn’t swim anymore, which meant about 30m of walking through the water.  It was kind of a cool scene seeing 30-40 people walking through the shallow water and descending on the beach.  The early-morning sun made for a cool background.  For me, that was where the race started: after the swim, when it was time to hop on the bike for 56 miles.

I took my time in transition.  No need to hurry when the race is still over 5 hours from finished.  The one or two minutes I could save there were just not that important.  Started biking out and felt pretty good.  Had some tightness in my hip adducters for the first 10 miles or so, but thankfully that loosened up.  Held my 18mph goal pace for the first 7 or 8 miles at a nice low RPE, probably a 12 or 13 (out of 20).  I decided I could stand a little more, so I pushed it up to about a 14 and rode the next 20 or so miles at between a 19 and 20 mph pace.  Hit the one hour mark at 18.6 miles, which was right where I wanted to be.  My fastest 10 miles were miles 25-35.  I rode the two 5-mile splits there in a little over 15 minutes each, just a shade under a 20mph average. 

Every 5 miles, I took a sip of Accelerade and water.  At mile 30, ate a zone bar which was melty and disgusting.  Probably needed a couple hundred more calories on the bike and definitely should have drank more water.  I only had two bottle holders, so I had to skip the first two water stops, which was a mistake.  I should have grabbed a bottle and drank at least half of it each time. 

After mile 45, I slowed down to prepare for the run.  The last 10 miles were my slowest by far, going over 17 minutes per 5 mile split, but that was part of the plan.  I finished the bike in just a shade over 3 hours, just above my goal pace of 18 mph.  I felt really good about the bike leg; I had some fatigue in my legs (to be expected) but I didn’t think I overdid it, so I would have some energy left for the run.

Took my time in transition again.  Decided not to wear the ankle brace I had brought (my left calf has been giving me warning signs of a strain for a couple weeks, but held up for the race and feels fine the day after).  Came out into the run strong, but after about three quarters of a mile, my quads started to cramp pretty bad.  I realized that I had needed to hydrate more on the bike, and needed to make up for it on the run.  Walked until my quads relaxed, then ran again until they cramped back up.  At the first aid station, I grabbed 2 cups of gatorade and pounded both in an attempt to get myself re-hydrated enough to end the cramping.  Around mile 3 it worked, as my quads relaxed and I was able to run a bit more.  My legs were not with me on the run, though.  I could run about a half-mile at a time before they would fatigue to the point that I had to walk for a minute.  Each water stop I took in a couple cups of water or gatorade, and threw another cup of water on my head or down my back.  It was 90+ and there was a 3 mile stretch that was completely exposed, with no shade, just hot asphalt.  You could see the heat rising off of it.  Brutal.

I took a rest stop shortly before the turnaround.  About that time I realized my attempt to rehydrate was causing problems.  I just had a ton of water in my stomach sloshing around with each step, and was afraid I might have hyponatremia issues if I kept up that pace.  I decided to forgo the water at a couple aid stations, opting to just ice down to stay cool instead.  I hit the turnaround at mile 6.6 at 1 hour and 20 minutes into the run.  On the way back, I was able to sustain my running pace a bit more, and found some friendly running companions to talk to, which made it easier to keep going.  Feeling the calorie deficit hitting me, I had to do something at the aid stations.  Solid food seemed like a bad idea, and I couldn’t do gatorade.  I opted for the pepsi, which is pretty calorically dense for very little liquid.  That worked really well (the caffeine may have helped a little as well). 

I have to give a shout out to the huge party I went by three times (near the finish of the bike, and on the out and back on the run) - these people knew how to have fun, and they made the race so enjoyable.  Lady in the white dress drunk off your ass and dancing in between the two columns of runners, you are a rock star.  Thanks for the high five.  Guy who decided to play the lead-in to the Black Eyed Peas “Let’s Get it Started” on loop (“runnin’ runnin’ and runnin’ runnin’…”), nice touch.

I came around the corner with about a mile and a half to go, and could see the finish line across the inlet.  I got a goosebump or 200 from that.  About a half-mile out decided I wasn’t stopping until I crossed the finish line.  Came in strong - negative split the run by about 6 minutes for a 2:30something half marathon on the end. 

My right shoe was completely soaked in blood from my toe, which must have gotten cut early in the run.  It was already scabbed over by the time I finished.  Sunburn around my right shoulder where my tri-top didn’t stay in place is really bad.  Also have sunburn on my lip, which just sucks.  Beautiful tri-top tan lines will make me look like I’m wearing white suspenders for the next few weeks. 

Many thanks to my wife and my parents for coming out.  I don’t know if I’d have made it without the support.  Also, thanks to my wife for taking care of me after the race.  She carried my bags to the car, drove me home (through a ridiculously scary thunderstorm that hit right as we crossed the bay bridge - terrifying), made me dinner and poured me a couple (much-needed) glasses of wine. 

Morning after - everything is sore, but nothing feels injured (fingers crossed).  Sunburn and random chaffing can be treated.  Blisters will go away with time.  Muscles will recover.  The feeling of having raced 70.3 miles in one day will never go away.

To quote one of my running companions, “Pain, blisters, and death are all temporary.  Glory lasts forever, and so does this fucking run.”

Comments

Five Years Ago

Five years ago I was finishing my junior year of college, going to work as a swim coach for the second summer in a row, and generally missing the point of being 21 years old.  It turns out that drinking beer and playing FIFA soccer on playstation 2 every night by yourself isn’t the most meaningful existence… who knew?

I’d love to go back and tell myself that I was going to NCAAs the next year, so to work out a little more (1 tenth of a second would have made me a national champion 9 months later;  3 more days in the weight room that summer could have made me 1 tenth of a second faster).  I’d love to tell myself that I should start thinking about my career and that I wasn’t going to stay in school forever.  I’d love to tell myself that I should start to work on building the life I wanted.  I’d love to tell myself to watch out for a trap here, to avoid a mistake there.

But I wouldn’t tell myself any of those things.  I’d just let the life I’ve lived play out the way it did.  For every wrong turn I made five years ago led me to find a new path that brought me to where I am today.  And today I am in a very good place.

Am I as far along as I would like to be in my career?  Do I have all the skills I would want to have?  No.  But I do have a great career ahead of me and plenty of time to make up the gap.  I have a loving wife and a deep understanding of myself, neither of which I would have if I’d not made my mistakes in the last few years. 

What I can tell myself, the me of five years from now, is that now was the time that I kicked my life into high gear.  I took care of the foundation in the last few years, and now it’s time to fly.

See you in five years.


 #Trust30 is an online initiative and 30-day writing challenge that encourages you to look within and trust yourself. Use this as an opportunity to reflect on your now, and to create direction for your future. 30 prompts from inspiring thought-leaders will guide you on your writing journey.

Comments

My Personal Message

I have a favorite personal mantra:

Everything in the world is perfect, including my desire to change it.

Obviously not everything is perfect - dictators lash out violently against their citizens who ask for freedom, politicians cheat on their wives and post it all on twitter, and the Phillies sometimes lose - but the point is that these imperfections create meaningfulness for our lives.  If no problems existed, we couldn’t spend our time trying to solve them.  That would make for a pretty boring life.

So accept imperfection as a reality, but don’t accept it as an end-state.  Work to change the world, but remember that the obstacles you encounter, the imperfections of the world, are the very things that make progress possible.


 #Trust30 is an online initiative and 30-day writing challenge that encourages you to look within and trust yourself. Use this as an opportunity to reflect on your now, and to create direction for your future. 30 prompts from inspiring thought-leaders will guide you on your writing journey.

Comments

The Difference Between Vectors and Pixels for Scalable Design

I’m not an adobe user, except for acrobat, and even that I try to keep to a minimum.  It’s not that I’m opposed to adobe products, it’s just that they are insanely complicated and make my little brain hurt.

That said, both this site and my new Team Disruption website (coming soon) need logos, and adobe is the industry standard, offering 30 day trial periods to beginners like me so we can make our once-in-a-lifetime logos and then go back to fearing adobe products again  (note to adobe: maybe make an amateur version?  Or just tell us to use Microsoft paint and come back when we’re serious, idk).

Anywho, I did not realize that there was a difference between designing a logo using pixels (photoshop) versus designing one using vectors (illustrator).  I saw a great lynda.com video today though that illustrated the difference.

It comes down to scalability.  When an image is designed in photoshop, it is rasterized, meaning that it is defined by pixels.  That means that as it gets scaled up into a larger image, it begins to look “hairy.”  You’ve probably downloaded an image from the web and stretched it out before; note the little lego-block effect that happens and that’s what I mean. 

An image designed using vectors, however, does not have this issue.  When the image is resized to something larger, it maintains the same quality.  That’s a nice feature, and something I’ll be looking for as I design these sites.

Comments

To Fly

The setting couldn’t be better: 5am in an apartment in Brooklyn, and wind-up fish toy hanging from Jay’s lapel, because why not?

Late night discussions tend to turn to philosophy, at least for me.  Maybe that says something insightful and not altogether flattering about me, or maybe it doesn’t say anything at all.  That night, I decided I could fly.

Not that I could fly in a literal sense of learning to pilot aircraft, or of growing wings and flapping them to create lift.  Rather that I could overcome any obstacle, and that the impossible is the only thing worth trying.

Entrenched industries with deep pockets can be scary.  Who could take down Exxon or Coke?  Those are big challenges worth pursuing.

That’s why today I decided to start a new group, which I’ve temporarily named Team Disruption.  The “Team” part is a little bold, since right now it’s a team of one, but I plan to change that soon.  The goal of Team Disruption is to take on the most powerful, entrenched, and “unbeatable” industries in America, revolutionize their businesses, and take down Goliath.

Follow Team Disruption on twitter.  Meetup group in the DC area coming soon.  Facebook group coming soon.

Rational people and realists not allowed.  Dreamers and Doers only.

Happy disrupting.


 #Trust30 is an online initiative and 30-day writing challenge that encourages you to look within and trust yourself. Use this as an opportunity to reflect on your now, and to create direction for your future. 30 prompts from inspiring thought-leaders will guide you on your writing journey.

Comments

Waiting to Live

For those of you who haven’t heard, Tim Ferriss’s The Four Hour Workweek is a must read.  It turns out, though, that the main idea isn’t so original after all. 

Life wastes itself while we are preparing to live. – Ralph Waldo Emerson

Huzzah!

No matter who is telling you to live now, instead of waiting, it seems that almost everyone chooses, what Ferriss calls, “the deferred life plan.”  We work all week to get to the weekend, and work for 40 years to get to retirement, and THEN we’ll live a little.  The problem, of course, is twofold. 

1) A lot can happen in 40 years.

2) By the time we hit 65, we’re not quite so up to the task of livin’ it up.

Most of us spend 40+ hours a week working jobs we hate, with people we don’t like, to buy things we don’t need.  Of course, that isn’t everyone.  Some people love their jobs and their coworkers.  But if you aren’t one of them, take this page from Hugh MacLeod’s excellent book, Evil Plans: Having Fun on the Road to World Domination:


#Trust30 is an online initiative and 30-day writing challenge that encourages you to look within and trust yourself. Use this as an opportunity to reflect on your now, and to create direction for your future. 30 prompts from inspiring thought-leaders will guide you on your writing journey.

Comments

What the Jibberish After the ? in URLs Means

I never really gave it much thought, but when I see a URL pop up with a ? and then a bunch of jibberish behind it, I usually just assume it’s something totally arbitrary.  Turns out I’m wrong (who knew).  Not only does that jibberish contain valuable information, but now I can actually use it too.  This probably shouldn’t be exciting.

Let’s talk about a fictitious webpage:

www.davecroushoreisawesome.com/index.php?dave=awesome&response=totally

If you went to that link, and that was a real webpage, it’s possible to pull in the values “awesome” and “totally” which are stored in an array, with the names “dave” and “response.”

Awesome!

Totally!

Comments

One Place to Visit

There is one place that I absolutely must visit before I die: New Zealand.

I don’t really know why, but there’s something alluring about New Zealand.  The landscape looks like nothing I’ve ever seen before (at least in Lord of the Rings), and the people sound great, too. I once heard that they consume more ice cream there per capita than any other country in the world (a fact that Google validates quickly).

Of course, getting to New Zealand is no easy task, and in order to make the trip worthwhile, I’ll need to go for a while (and probably stop by Australia along the way). 

My next big international trip will be to China this winter (to kick butt in a business plan competition), but after that, my next jaunt overseas will have to be New Zealand. 


#Trust30 is an online initiative and 30-day writing challenge that encourages you to look within and trust yourself. Use this as an opportunity to reflect on your now, and to create direction for your future. 30 prompts from inspiring thought-leaders will guide you on your writing journey.

Comments

A Fun Fact About Prime Numbers

Take a random integer: let’s say 17783.  Is it a prime number? (yes)

If you had to go about checking whether or not that was a prime number, how many numbers would you have to divide it by before you could be sure it was prime?  That’s a more fun question. 

The first instinct is to say, 17782, since you need to be sure that every number lower than 17783 doesn’t divide it.

Of course, it quickly becomes obvious that you only need to test other prime numbers, since those would necessarily show up in the prime factorization.  Even then, that’s too many.  Why test, for example, 17761 (the next prime below 17783) since it can’t possibly divide a number so close.  It’s tempting to jump to the idea of testing primes below n/2.  Even that turns out to be more than necessary though.

In fact, you only need to test up to the square root of n in order to determine that n is prime. In the case of 17783, that turns out to be only 32 numbers (the 32 primes below 133, which is close to the square root on 17783).

Then again, you could always just look it up here.

Comments