Live TV : Ustream

In less than an hour, teams from the TechCrunch Disrupt hackathon will begin presenting their apps and they will have just 60 seconds each to make the judges (and audience) fall in love with what they’ve built.  There are several outcomes to optimize for during your presentation, but the two that stand out to me are:

1. Win the hackathon by impressing the judges
2. Win public interest and get the crowd excited about your app (a la GroupMe last year)

You can try going for both, but my personal opinion is that public interest trumps the opinion of a few judges who’ve only had 60 seconds to evaluate.  With a little hustle, you can set yourself up to optimize success.  If you’re product sucks, no amount of hustling will save you, but if you’re looking to tip the scales favorably in your direction this could be the key.

Know the Judges

I haven’t found them listed on the Disrupt hackathon website, but a few have already tweeted that they’re on the way to judge.  Look up their profile, follow them, read their bio page (if they have one, most VCs do)

Pre-Seed the Audience with Your Product

Start giving away beta access to people now, create a Twitter account for your app, and jump into conversations and get feedback.  If you have a small but vocal group of fans cheering for you after you demo that’s a little more social proof, and the judges will notice.

Use Technical Difficulties as Free Time to Vamp

It’s likely some of the demos will be plagued with technical difficulties: a Mac that finally decides to give up after having its CPU pushed to the limit all night, a broken cable, a missing dongle, a screen with some screwed up resolution.  You can protect against some of this by asking to quickly connect your computer to the monitor you’ll be using to present ahead of time, just to be sure, but the odds are something unexpected will go wrong when you’re not expecting it.  Instead of getting pissed or flustered, use that time to crack a joke, show some of your personality, and show that you can be calm under pressure.

Don’t Waste Precious Seconds on How You Built It

The judges and audience (unless they ask explicitly) probably don’t care about what you used to make this happen, so don’t waste precious seconds taking about your technology stack.  Unless of course its Twilio, in which case I’d like to know so I can write about you!

Use the Last 5 Seconds to Create Warm Fuzzies

As you’re about to be kicked of the stage remember to be gregarious:

• thank your team
• thank the organizer
• shoutout to any special people who helped you
• let us all know where/how we can connect with you (your Twitter name, app URL etc.)

Draw the Fucking Owl

Hopefully you’ve been doing this for the past 24 hours, good luck teams!

Congratulations to TechCrunch, who announced yesterday at TechCrunch Disrupt that they have been acquired by AOL.

I’ve been reading TechCrunch since before I knew I was going to do startups.  It all started because my friend Blake Scholl was doing a startup, and I set up Google Reader to track TechCrunch so I would be sure to see when his company got coverage.  At the time I was working for a Fortune 1000 shipping company as a business analyst, and had nothing to do with startups.  I got addicted to reading the damn thing in the spring of 2007.

TechCrunch is the reason I found out about Twitter, Twitter is the reason I came to understand social media, and there were a few hundred steps more before I landed here in San Francisco to work on Twilio.

If you write in a paper journal, you might have noticed how the daily ritual becomes like a benchmark in your life.  In a way, it gives you deja vu — but in another way it helps you mark the passing of time.  Reading TechCrunch is like that for me.

I’m happy to for Michael Arrington and the whole team there, and I hope they get some much needed rest and a chance to celebrate this weekend with their friends and family after TechCrunch disrupt wraps up.

Wait… what?

This quote from Steve Blank (which I realize is taken out of context, but such is the nature of Twitter, I’m not sure where he was speaking today) definitely rubs the marketer in me the wrong way.  Why would you ever want to exclude marketing and sales folks at your startup from the launch party (or any of your employees for that matter), as if they had no part in it?

Treat Marketing as a 2nd Class Citizen, Get 2nd Rate Marketers

My first reaction was to feel at bit nauseous about all the startup founders and employees who are influenced by Eric Ries and his popular Lean Startup methodology for product and market development, and probably read this tweet.  I feel like supporting this attitude encourages one of the most painful, costly, and damaging mistakes that was made at my last startup — and after thinking about it for a couple hours, I can’t not say something.

This isn’t ultimately about Steve’s quote, or Eric’s support of it, which I see as symptoms of the problem. It’s something I’ve wanted to write about for a long time because I experienced it firsthand in my previous startup and it was very damaging to the product, culture, and IMO ultimately the company.

This mentality of “developers before everyone else” is poisonous in startups, and it’s on the road to dangerous levels of hubris, and “pivoting”, or changing the direction of the business multiple times, due to a disconnected view of the world fueled by a Field of Dreams mentality (“if we build it they will come”).

Here’s why…

• Sales and marketing are helpful to have before launch, to make plans for achieving goals
• The greatest insult to a great product, and the people who created it, is to market it poorly
• To grow the business, cofounders need to trust marketing and sales to focus on things that the technical co-founders can’t or shouldn’t have to deal with on a daily basis
• To make great early marketing and sales hires it had better be “our startup” together, in spirit not just in equity stake.
• It’s not about the launch party, its about launching

Order of Operations

When a startup is founded, ideally the entire team is technical.  There is probably someone who is the most business-minded, but not a dedicated sales or marketing person.  If there is a non-technical member of the founding team, they’re probably (hopefully!) very deeply engaged in the product development aspect of the startup, and have earned the trust and respect of the engineer(s) co-founders.

Depending on the product and other market conditions, it is possible that the founding team of engineers will launch without anyone in sales or marketing at all, and their developer design and active use of social media will help them spread the word.  This is exactly what happened with Twilio, which was launched in November 2008 without anyone whose entire job was to take the product to market.

If the product offering is compelling enough, or the cofounders are particularly interesting to the community, getting a TechCrunch story will require little more than a thoughtful email to the writers and a slide deck on Slideshare.  This is the best case scenario, and in my opinion indicates a very well-rounded founding team with strong awareness of their market (business savvy) — even if their primary focus is building technology.  However, after that initial burst of attention and activity there are many questions to be answered that have a more to do with building a business than building a product — like how to continue to gain and retain customers.  This is where sales and marketing are helpful to have before launch, to make plans for achieving these goals.

Getting Past Day Zero

The launch of a new product is just the beginning of what will hopefully be a lasting and happy relationship with customers, press, analysts, and the marketplace in general.  It is a moment of inflection and incredible stress for the entire organization, whether it is three people, thirty people, or three thousand plus.  It is gloriously terrifying, and its something teams bond over.

• There is no question that the vision and actual act of creating of the product is what makes it all possible, and that the people who build things that have never existed before are some of the most amazing human beings on Earth. The greatest insult to a great product, and the people who created it, is to market it poorly. This is the core of how I approach marketing.  Every day that I am spreading the word about Twilio, getting more people to signup, use, and pay for our product I’m honoring the ingenuity that created it, as well as the combination of intellect and execution that continues to make it better.

A Matter of Trust and Focus

When I interviewed I remember the exact moment I was sitting with Evan Cooke, CTO and one of three cofounders, and he offered me the opportunity to work at Twilio as their first hire.  I looked him in the eye and told him, “I can do this job, but we have to agree that marketing will never become a second class citizen to software development”.  I was actually afraid, for a moment, that I wouldn’t get the job but I told my husband later that I’d rather know right then what kind of company it was going to be than be miserable for the next year figuring it out.  That was 18 months ago, and I’ve never ever felt for a moment that there was a disconnect between the engineering team and the marketing team, which now includes a customer service manager and two developer evangelists, in addition to myself.

One of the hardest lesson I’ve learned in business is that despite all my energy and intelligence, I can’t do everything by myself.  Talented people making tough judgement calls aren’t fungible, and in general human beings don’t scale very well unless we can find other people to help us achieve complex and long range goals.  The goal of a business is to organize a bunch of individuals to achieve a common goal, and properly celebrating achievements is a big part of keeping them organized.  Fortunately, if we recruit well we can come to trust marketing and sales to focus on things that the technical co-founders can’t or shouldn’t have to deal with on a daily basis.

This initial division of labor within the startup seems to be a painful transition for technical cofounders — especially those who have never managed other people before.  It becomes even worse because the cofounders are managing people who are experts in something the cofounder might not understand very well like sales or marketing.  For the executive, it is harder for them to validate skills and expectations or pass judgement firsthand when they don’t have operating experience with a particular kind of role.  This is where building deep trust, and fostering an open culture where the sales or marketing person is responsible for sharing and educating about how they’re achieving their goals is important.  It’s also a strong case for objective metrics everyone can agree on, such as adoption numbers or revenue goals.

“You Attract What You Are” – Warren Buffett

I often read about developers who feel they’ve been made into lackeys by some MBA with an idea who wants the software engineer to “just code my startup”.  It’s written with so much disgust.  “How dare they undervalue what I bring to the table so much, or suggest that it’s their company and I’m just coding up the project?”  Followed by, “what kind of developer would ever sign up for something like that?”

Flip this around for a moment.  Do you think good, honest, hardworking non-technical employees are going to join your company if you tell them they’re there to “just market my startup” or “just do customer service for my startup” or “just sell my product”?  To be good at any of those tasks, and especially to be the first person to say “I’ll follow you, take less salary, some equity that might not be worth anything, and work 24/7” you need to have ownership – it had better be our startup, in more than just an equity stake.  You better mean it, because these people will be the human embodiment of your brand.

I love this quote from Warren Buffett, “you attract what you are” and I find myself reflecting on it often.  I haven’t fully tested this, but I’d be curious to hear if it holds true — does a culture where writing code is considered the most important productive activity in the company attract marketers and salespeople who think their job is the most important thing in the company?  Do people with a disconnected view of reality attract other people with an equally disconnected perspective?  My gut says yes, although I could use some more data.

The corollary here is that if you are the kind of culture, or the kind of the founding technical team, that sees the launch of your first product as the groundwork for building a fully fledged successful business – you’ll attract early sales and marketing hires who want to be part of this long term vision.  Here are some things I’d suggest you look for in your first marketing hire.

• wants to know how the product works
• is endlessly curious, and isn’t afraid to ask a lot of questions
• never has to be told the same thing twice
• will stay up all night while the engineering team races to ship
• is always thinking about how to simultaneously increase throughput and ROI, while decreasing operating expense (definition of “lean”)
• loves customers obsessively, and doesn’t have a cynical bone in their body
• knows when to be a bulldog
• is humble – for example, they would clean the bathrooms when they can’t afford a janitor
• understands the tradeoffs of time vs. money, and values both
• someone who is a logical decision maker and isn’t afraid to argue for what’s right, or back down if it’s not worth the fight

Great Marketer or Great Generalist?

You might have heard the adage “every startup needs a great generalist”.  I’m not sure where it comes from, but it makes a lot of sense to me.  Some of the hats I wore early on at Twilio to remove workload from the engineering team included: customer service department, recruiter, office manager, shipping/receiving, project manager, sales rep, product tester, PR agent, etc.  That was so insanely fun, and we eventually hired people to take over these roles, but early-on it served two major purposes:

1. run the company like a real business, achieving strategic goals
2. make the dollars spent on non-engineering labor worth every penny, and more

The Company That Launches Together, Stays Together

To get back to the original comments that inspired this post, it’s not about the launch party, it’s about launching.

Your launch party is for show, usually to bring attention to your new product and group together all your well-wishers and potential customers so you can say, “ta da!”  It’s a branding thing, and very different from that moment at 3am where you crack open a $4.99 bottle of sparkling wine you bought at Trader Joe’s and say to the team, “we’re live”.  Or that moment at 2am where you find a member of your customer service pouring over every last detail of the freshly written FAQ.  Or that moment at 11pm where you merge in your latest changes and your sales guy offers to run out and get pizza because the engineering team is starving but has hit on some nasty conflicts.

These aren’t the most important tasks, but they make launch just a little easier and they keep us human and connected through the exhaustion and struggle to build great products and companies.  They do honor to the people and products that make startups possible.

Practice Makes Perfect

I didn’t start out my career as a marketer, and I’m sure I don’t have it all figured out, but I can tell you how I try to live by this at the startup I’m working on today.

At Twilio we have a culture where everyone contributes to customer service and the majority of developers attend marketing outreach events, speak at conferences, create marketing materials like screencasts or how-to content for our website.  When we hire people for non-engineering roles, we require them to write a basic application using our API.  With regard to sales, we take pride in making money, and openly share our revenue numbers and balance sheet with the entire team at our weekly all hands, and celebrate big sales wins together.  We’re hiring.

My beloved side project TweetToCall recently turned one year old, and I’ve been procrastinating on re-styling it to look more like a Web 2.0 service and less like a weekend project.  This post on TechCrunch tonight about the death of phone numbers motivated me to give it an hour of my time while playing Mario Cart with Kevin and digesting an awesome steak dinner I made for us.  Because really, when else can I justify working on a side project these days?

The Changelog (Sort of)

I had updated the main page with this lovely style inspired by a cool piece of graphic art I bought on iStockPhoto, but still needed to refresh everything else.  Tonight I went through and tested everything again to make sure it is all working.  The signup process, phone number validation and listing of TweetToCall enabled friends have been reviewed end-to-end and I’m happy to report the code has aged nicely.  I think we might be doing some inefficient things with API requests to Twitter on certain commonly reloaded pages (really need pagination for those users who are developing a bigger phone book), but that won’t impact the majority of users at this point.  Definitely on the list though, since it drives me nuts when I’m testing.

As for the design update, all I have to say is CSS is amazing (there is knowing this and really KNOWING IT, I’m feeling the latter)… the time savings on this update after the previous were minimal.  I updated the header, deleted a couple divs, and bam.  While it’s still ugly (hey, I’m not a designer) it is a lot less offensive than before.

Other Improvement Plans

I’ve talked a lot about adding Facebook Connect as the next integrated social network, and now I’m thinking Firefox/Chrome plugins could be cool as well.  Ultimately, I think I will probably move this all over to DialSocial.com where it will be much less Twitter centric.   Other than a few media mentions from back when Jajah launched their @call feature almost a year ago, I don’t think I’ve accumulated much brand value, and having the Twitter account suspended endlessly makes it even easer to abandon the TweetToCall brand.

Another thing on my list is to get @tweettocall unbanned on Twitter, it has been stuck in that state for over a year now and I haven’t been able to get any responses to my support requests (this happened when my own Twitter account @daniellemorrill and @twilio got banned in a widespread block to try to control some malicious spam during the Gov 2.0 Summit in D.C.).

Why It’s Just a Side Project

Beyond the fact that I am super happily employed at Twilio (the voice API platform TweetToCall is built on), I just feel like there’s no point in really building this out and pumping a bunch of money into marketing it.  There is a big barrier to getting users to sign up – getting them to give their phone numbers.  Twitter, and to a lesser extent Facebook, have all their users and this is really just a feature they could easily implement.  The one way I might be able to make it more valuable is to have more networks that you can hook into from a single place — but for now it just feels like a feature, not a full product and certainly not a company.  If you feel differently, please let me know I’d love to hear your thoughts.

Update: No, it isn’t TweetToCall – although I love that project (yes, it still works and has a few thousand users now) and do think Twitter is going to become the new phone book.  TweetToCall should be a feature of Twitter, and if anyone wants the code etc. I should just open source it.

You know that Julia Roberts movie where she doesn’t realize how much she’s in love with her best friend until he calls to say he’s getting married to someone else, and then falls off that bed?  That’s how I feel about my startup idea getting founded and funded by someone else.

To be clear, I’ve probably had thousands of ideas for startups – but I’m a fan of failing fast and most of them have been crappy, or usually technically “cool” but not monetizable.  That’s okay.  But this idea was actually something I pitched in the few moments I had between leaving Whrrl and joining Twilio.  It was something that nabbed me an offer to be an EIR with a reputable VC, which I was honored to receive but ultimately turned down.  Most importantly, it was an idea that I am still obsessed with.

Today, I read that someone I know of and respect a great deal received some funding for this business, and is forming a company to execute on it.  It haunts me.  I know I’ll get over it, and I’ll be watching closely in the next year to observe how it goes as I consider whether or not it is the startup I’ll found someday.  I can’t deny part of the pain is over not being first, but that is mainly pride.  The rational part of me (or mercifully rationalistic) reminds myself that it may benefit me in the long run not to build a product in a consumer market that will require so much education.  Time will tell.

Bottom line: the timing is wrong for me.  I love my current company so much, and it is exciting, challenging, fun, growing, amazing — all the things we dream of when we talk about starting companies.

Ideas are a easy to come by, but ideas that you can imagine executing on for YEARS of your life are not.  When I learned of Twilio I was immediately intrigued, and when Jeff approached me about joining the company I couldn’t say no.  The alignment of market, team, and timing is undeniably awesome.  Twilio is an idea I enjoy walking around inside of, thinking about constantly, living and breathing the brand.  If I ever found a company as incredible, cohesive, and useful as Twilio I will have succeeded — so for now I’ll have to swallow this momentary pain, and look forward to the exciting future.

I love when I can finally talk about something secret that I’ve been working on.  Yesterday we launched Twilio SMS, a new API that makes it ridiculously simple (or as someone on Twitter said, “stupidly simple”) to send/receive text messages from Twilio numbers.

Here is the screencast we made to go with it – which I am very proud of 🙂