Posts Tagged ‘startup’

6 Things a Non-Engineer Should Know Before Founding a Web Startup

Tuesday, April 27th, 2010

Despite the obvious look of shock and panic on the faces of my WePay teammates, I recently committed my first lines of production code.  Although It took over a year and a half for me to contribute to WePay’s code base, and it’s still not particularly substantive (a few lines of html on the exterior of our site), it still feels pretty darn good.

I’m not trying to become a developer. Trust me, there’s a ton of other stuff that needs to get done at WePay. I just discovered something that our site needed (and something that I really wanted because it would make my job easier), which wasn’t going to get built unless I found a way to build it.   We’ve received quite a few requests for “How To” guides, and I’ve also gotten tired of answering the same “how do I…” questions over and over again, so I built the How To section of our site. Specifically, How to Collect Money Online, How to Send Bills, How to Collect Donations, and How to Sell Tickets.

In addition to my first official commit, WePay also just hired Rasmus Lerdorf, the creator of the PHP programming language. All in all, I thought this was an appropriate time for me to reflect on the non-technical things I’ve learned about programming since founding WePay.

[Side Note: In a lot of my posts, I think I come off as a self-loathing non-Hacker, which is entirely unintentional and mostly untrue. During our summer in YCombinator, I was one of the few non-developers, and I was frequently asked: “if you don’t write code, what do you do all day?” The question annoys me for a variety of reasons, but mostly because I did a lot. I think there are abundant non-technical factors that lead to a startup’s success, and the responsibility for making those things happen tends to fall on the shoulders of the non-technical people (assuming the company has those – in our case, we did). At some point, I’ll write another post about what a non-engineer does, or should do, during the early stages of product development. In the meantime, I just discovered this post, which is pretty damn good].

So, without further ado, what I’ve learned:

  1. Don’t be Helpless. As the only non-developer at WePay, it’s pretty tempting to become technically helpless. That would be a big mistake, and there were times when I’ve gotten pretty close, and it has paralyzed the company. Programmers != Technical support, and a team of developers does not an IT department make. Installing software, setting up a network, changing copy on the site, etc. is not necessarily the job of the developers (in fact, it may necessarily not be their job). I’ve seen arguments about the difference between a programmer and a hacker, and from what I understand, the difference boils down to one thing: hackers will always find a way to get something done.  If you’re a programmer, you can also be a hacker (I would argue that our programmers are), but you don’t have to be a programmer to be a hacker. One of our corporate maxims: everybody’s a hacker.
  2. Almost nothing is trivial. I used to say: “this should be a pretty trivial change,” a lot more than I should have. Just because something is logical and it makes sense, does not mean that the code can easily support it. From what I can tell, nothing is more frustrating to an engineer than a non-engineer asking for something complex, and treating it as if it’s trivial.
  3. The 90/10 rule. When you first start building a piece of software, you can pretty much do whatever you want because you’re not constrained by what you’ve already built. So the first 90% goes by very quickly, and you can see a ton of tangible progress. You go from nothing to a lot very quickly, and it’s exciting. The other 10% takes forever (literally forever, see #4), and it’s hard for non-engineers to see that progress being made.
  4. Software is never finished. Software is like a living breathing organism. It’s never “complete”. For startups this is obvious: the application changes and morphs, it adds features and takes them away, it scales, etc. Even for non-startups, though, the software is never finished. It needs to be updated, vulnerabilities need to be patched, and bugs need to be fixed. I used to think that you build the product and then you get people to use it. As it turns out, these two things happen at the same time, from the beginning, and throughout the entire lifecycle of the company.
  5. Non-engineers are not “designers” by default. It’s easy to say: “since I don’t write code, I’m in charge of designing the site and improving the user experience.” And after saying that, it’s easy to put together a bunch of wireframes and say: “make this”, then do some QA and say: “fix that.” That’s not design and it’s certainly not improving the UX. There is both an art and a science to design and UX work, which takes as much time to master as it does to master most technical skills.  I think most non-technical founders working on their first Internet company miss that point. Because you are non-techinical, does not mean you are by default an authority on design and product; in fact, it could easily mean the opposite. If you want that role, you have to work for it (more details in a later post). Edit: Just read a comment that said: “don’t automatically assume engineers can’t design!” I couldn’t agree more.
  6. Don’t pretend to be more technical than you are. Especially in the Bay Area. First of all, it’s incredibly transparent (even to non-technical people), and you will lose all credibility. It also pisses off engineers. On the other hand, being honest about your technical skills, genuinely asking for help, and trying your best to contribute, is like trying your best to speak the local language in a foreign country- it’s a sign of respect and humility.

Good advice? Give WePay a try, it’s free to sign-up!

From the Entrepreneurial Society and Entrepreneurship Lab (E-LAB) at SJSU to WePay

Wednesday, March 24th, 2010

Stephen Guerguy just began his internship at WePay to fulfill a requirement for the Entrepreneurship Lab (E-LAB) at San Jose State University.  The course explores all facets of managing and growing a young, entrepreneurial organization, including building the team, sales, marketing, operations, and finance. It provides the opportunity to learn with practical internship and roundtables with entrepreneurs, venture capitalists, and others, in the new venture ecosystem.

I just read WePay’s latest blog post about interning for a startup when you’re young, inexperienced, and non-technical. The post said that you should “be persistent, network your way in and demand a job….[and] demonstrate a deep knowledge of and passion for the product.”  I think my experiences may add a little color to this advice.

I’m the president of the Entrepreneurial Society (ES) at San Jose State University. I’m also a junior majoring in finance, and will graduate in Spring 2011, hopefully with high honors. I joined the Entrepreneurial Society at SJSU because it introduces business students to non-traditional career opportunities.

Instead of helping students land stale accounting or finance jobs, ES works with entrepreneurs and angels in the Valley to help students formulate their ideas, build business plans, and compete in events like The Neat Ideas Fair & The Business Plan Competition.

My goal as president has been to build previously non-existent ties between the College of Engineering and the College of Business at SJSU, so students can build relationships and leverage complimentary skill sets. Business students need to understand and appreciate the value of engineers, especially at early-stage startups. WePay has a 5:1 ratio of engineers to non-engineers.  My goal is to establish at least a 1:1 ratio in the Entrepreneurial Society. In addition, I am in the process of planning ES Tech Trek, which will include an in-depth visit to 5 startups and VC firms next fall.  I think it’s important for students to learn about entrepreneurship in the field, in addition to in the classroom.

About a month ago, Rich started reaching out to local student clubs and organizations to better understand how they manage group finances.  Since I was one of the people he contacted, I asked if he wanted to grab lunch; I wanted to better understand how WePay could help ES, but I also wanted to start building relationships with startup founders in the area.

Around the same time, one of my entrepreneurship courses at SJSU had begun bringing in startups to pitch their ideas to students. The class also required students to intern for a funded startup to get the kind of immersive experience that one can’t get from a classroom. I connected Rich with my professor because I wanted WePay to participate in the program.  Now a few weeks later, I’m writing this post from within a sunny office in downtown Palo Alto.  There’s a big WePay sign on the wall across from where I am sitting, and I’m two weeks into one of the most exciting internships I have had. I plan to write a future post about my roles and responsibilities here, and what I hope to accomplish during my time at WePay.

Give WePay a try, it’s free to sign-up!

So you’re inexperienced, non-technical, and you want to work for a startup. Another post about internships.

Wednesday, March 24th, 2010

Since news broke about our financing and I started to blog about startup-related things, we have gotten a lot of interest from entrepreneurial students that “love startups” and “really want to work for one.”

We are aggressively hiring engineers, so if an engineer reaches out to us, it’s a pretty straightforward process.  Are you a Cultural fit? Technical fit?  If yes to both, then we probably want to hire you.

Since we are not currently hiring non-engineers, the process is not so straightforward when non-technical candidates reach out to us looking for jobs.

For starters, if you’re non-technical and inexperienced, you’re fighting an uphill battle, since you’re looking to fill a position that doesn’t exist.  One way to get around this is to ask for an internship.   For one, it’s easier to get an internship than it is to get a full time job.  This is probably pretty obvious, but it’s definitely worth noting.

I intentionally let potential interns fall through the cracks all the time. I don’t really want to spend time interviewing and hiring them, and I know that once I do, it’s just going to take up even more of my time. New hires (interns especially) require training and direction.   More often than not, the amount of effort I put in to training and directing an intern is less than the amount of tangible value I get out of the relationship.  The other option is for me to put in no effort, and hope that you can figure it out on your own.  I have rarely been pleasantly surprised by this approach.

So how do you get an internship with a startup that’s not looking to hire interns? Be persistent, network your way in and demand a job. Offer to do a trial period. If you’re super inexperienced, volunteer to work unpaid.  It also helps if you can demonstrate a deep knowledge and passion for our product.

Most importantly, know how to answer the following question: “What do you want to do if I hire you.”  I’m too lazy (or too busy) to answer this question for you. And if you can’t answer it before I hire you, that means that I have to take the time trying to figure it out after I hire you. That’s a pretty big deterrent.

The following answers send red flags: “I’ll do anything you want me to” or “I like everything” or “I’m not sure.”  This tells me that I’m going to spend more time trying to think of tasks to give you, than you’re going to spend actually accomplishing them.

A better answer would be: “I can help you accomplish X because I am good at Y”. The more specific you are, the easier it will be for me to see where you fit in the value chain. Do you have a deep knowledge of our target market? Can you do customer service? Can you make pretty graphics? Edit videos? Everybody can think of something they are good at; all you have to do is figure out how that relates to some aspect of what we do on a daily basis.  Remember that most startups only do two things: they build a product and they get people to use it. If you’re not technical, then you just need to make the case that you’ll somehow contribute to the latter.

If you’re an intern, you better be 80% doer and 20% thinker.  The worst thing you can say is something like this: “I am a management major, so I can help you create a plan and define your goals”. I would much rather hear something as simple as: “I will help you get more users.”

If you can finagle an internship, then you just have to kick ass while you’re there. How do you kick ass while you’re there? Pretty simple: accomplish something tangible.  Get customers. Own a project or role (company blog, customer service, community outreach, etc.). Get press.  It doesn’t really matter: as long as at the end of your internship, I feel like we would suffer a major set back if we let you get away. If that’s the case, then we would be crazy not to offer you a job.

Check out the progress of our start-up. WePay is free to sign-up.

How to intern for a startup

Thursday, March 18th, 2010

I recently met with the head of business development for a pretty big and wildly successful company. He was their 10th hire, and he started off as an unpaid college intern.  That got me thinking.

I’ll eventually write a post about what startups look for when we interview potential interns, but for now I’m just going to tell the story about how we discovered and hired our first (unpaid) intern, and how we converted him into our second full time (paid) employee.

About six months after Bill and I founded WePay, we were invited to attend Olin College’s Meet the Startups Day.  Olin College is basically a school of 300 or so brilliant hacker-types (Olin actually offered full tuition scholarships to every undergraduate in attendance… until the economy crapped the bed).

Meet the Startups Day is a career fair for Olin students interested in working for startups.  Bill and I were pretty excited to attend because at that point we had not made much progress actually building our product, and although Bill is technically oriented, we needed all the horsepower we could get.  Luckily, we had the arrogance and naiveté to think we had something to offer in return.

So we show up with a laptop and a bunch of business cards. We used the laptop to loop a screen cast of our “prototype” (which, in retrospect, was a piece of crap), and we used our business cards to look, well, business-like.

The business cards didn’t do the trick; every other company had a pretty impressive exhibit, and the people representing those companies looked far less…childlike.

We attracted the fewest number of students, but the students we did attract were particularly enthusiastic.  I think there was a small group of students that genuinely wanted to work for an early-stage startup, and they knew exactly what that entailed.

Olin gave every company that participated in the event a USB stick that contained the resumes of all the students in attendance.  Now that I think about it, that was pretty ingenious…

Three months later, when we were accepted into YCombinator, I looked through the resumes and found Karl Schults, the one name that I remembered from Meet the Startups Day.   Karl was pretty young and earnest, but he was also crazy smart (as far as I could tell).

I gave Karl a call and I said: “Hey Karl, you might not remember me, but I was at Meet the Startups a few months ago. We just got accepted to YC, and we’re about to move out to Silicon Valley. Do you want to intern for us? We can’t pay you, but we’ll buy your plane ticket, give you a place to stay, pay for your food, and provide you with a great experience.”

Karl definitely had the choice to take a paid internship (and if he didn’t, Google and Facebook dropped the ball).  He decided to work unpaid for WePay because he knew he would have the opportunity to write production code and own large parts of the application.

Before the summer, Karl’s only experience with php was a 2 week project in one of his programming classes at school. By the time the summer was over, he was a pro, and had committed as many lines of production code as anybody else. He worked long hours with the rest of us, and his programming skills improved dramatically.

When the summer ended, Karl went back to school… for one semester.  Immediately after we closed our first round, we made Karl an offer. He became our first post-financing hire.  He postponed school, and he now works with us full time in Palo Alto.

Lessons learned:

  1. If Karl hadn’t started networking with startups early, we never would have found him (and he never would have found us).
  2. If Karl hadn’t made a solid impression, and found a way to keep his name in the back of my mind (USB stick….brilliant), I wouldn’t have even thought to reach out to him again.  A monthly “lets-keep-in-touch” email would probably accomplish the same thing.
  3. Karl could have taken a paid internship at a big company. His resume would get a boost, and he would have gotten a ton of “awesome” experience doing QA, writing documentation, and playing Farmville.  Taking an unpaid internship is a bit like early-stage investing: you risk your resources now in the hopes that it pays off in the future. The amount you invest is equivalent to the opportunity cost of working there. Karl bet on us early, and it turned out to be a good choice.
  4. Karl crushed it over the summer. Bill and I never questioned whether we should hire him. It was an obvious decision: once we raise money, we’ll hire him full time.

Give WePay a try today. It’s free to sign up!

5 things I “knew” (or should have known) before starting a company, but didn't fully understand until now

Thursday, March 11th, 2010

I founded WePay with Bill Clerico in August 2008, with the simple goal of making it easy for groups to collect and manage money online. We were accepted in YCombinator in May 2009, and raised just under $2 million from August Capital, Max Levchin, and a few other well-know angel investors last December.

I can’t say much about running a company post-financing because we have only been doing it for a few months, and to be honest, I haven’t really had the opportunity to reflect on it.

However, I have taken some time to think about some of the things I have learned over the past year and a half (from conception to financing), and I’ve decided to share a few of them here.

A quick caveat: I’m fully aware that every one of the following points I’m about to make has been made before, multiple times, by people smarter than myself.  There’s this great quote in Frost/Nixon that goes like this: “In boxing, there’s always that first moment, and you see it in the challenger’s face. It’s that moment that he feels the impact from the champ’s first jab.  It’s kind of a sickening moment, when he realizes that all those months of pep talks and the hype, the psyching yourself up, had been delusional all along.”

It’s one thing to know how strong the champ can hit, and something quite different to feel it.

That’s kind of what it’s like to start a company: “Yeah, yeah … I know it’s going to be hard – everybody has told me it’s going to be hard – but I’m ready for it, and I can handle it.”

Trust me, you’re not, and no matter how much you think you know about what it’s going to be like, when that first jab comes, you’ll begin to truly understand for the first time.

Paul Graham says that good startup founders can be described in two words: relentlessly resourceful.   I agree, but I would add two words of my own: arrogant and naïve. Arrogant enough to get in the ring, and naïve enough that you still think you will win after you feel the first punch.

The following are the five things that I “knew” (or should have known) before starting a company, but didn’t fully understand until now.

1. If you are not full time, then you are at a huge disadvantage

Going full-time was one of the best early decisions that we made.   More than anything else, working full time on your startup makes it MUCH harder to quit.  Once you burn the ships (quit your job, drop out of school, etc.), you’ve officially committed. I can name at least five times I would have quit if I wasn’t working full time, or if I had other options. In fact, if the timing had worked out differently (better or worse, depending on how you look at it), I would have gone back to law school after a year-long deferral.

Working full time on an idea also gives you a degree of credibility. Or rather, not working full time takes away almost all credibility. If your idea is so great, why haven’t you committed to it? Why should I invest and risk my money, if you’re not even fully committed.

For us, part-time was not an option.  That being said, if you don’t need credibility or require anybody else’s commitment (time, money, etc.), then part-time may be a viable option.

2. Picking the right cofounder is the most important early-stage decision you will make.

It’s almost cliché to claim that picking a cofounder is like getting married. Picking the right cofounder is more like finding your soul mate.

You need to find somebody that you cannot succeed without, and they need to feel the same about you. You need to contribute something so unique and valuable that your cofounder would have a very difficult time building the business without you.  I have watched a ton of early-stage startups (run by some very smart people) fail because the cofounders didn’t complement each other well.  Three very smart people and a business plan, does not a business make.

I recently saw a post on Hacker News, where somebody created a three-column spreadsheet. Column 1 = “I am”; Column 2 = “I am looking for”; Column 3 = “I am working on.” Literally 99% of the rows read something like this: “I am a business guy/entrepreneur/mba/professional; I am looking for a technical cofounder; I am working on a website/new kind of social network/etc.” Everybody wants a technical cofounder because you can’t build an Internet company without one (I guess you could outsource development, but as it turns out, that rarely ends well).

And even more worrisome, is that people often think to themselves: “if I could only find somebody that knows how to program, then everything will be okay.” Building a web-app is far more complex than us non-techy folk could ever imagine, and believing anything else is a sure-fire way to waste a ton of time and money.  Believe me, if you are “building a website that will do X”, then 99% of the early-stage work happening in your company will be building the website that does X.

If the only thing you are bringing to the table is an idea, then you have nothing to offer.  Think about what only you can offer a potential technical cofounder before you start looking for one (i.e. contacts with potential customers or partners, deep knowledge of a particular industry or space, access to capital, etc.).

Bill happens to be a close friend, but that’s not why he’s a good cofounder (it may be necessary, but it’s certainly not sufficient).  Nobody in the world has Bill’s exact skill set, and looking back on it, that skill set is exactly what we needed.  In regard to the close friend part, that’s a given – you’re going to be dragged through hell on the way to building a successful company, so you probably want to pick somebody that makes hell a little less painful.

Paul Graham says that startups die because founders quit.  Your cofounder should be somebody that refuses to quit, and somebody that inspires enough confidence in you, that you will refuse to quit as long as they are still around.  I can’t count the number of times that was all we had going for us.

3. Traction is the only thing that matters

Well, maybe not the only thing, but it matters a whole hell of a lot.  Getting people to use your product and consistently growing the size of your user base is perhaps the single most important thing an early-stage company can do.  In fact, some would argue that it is the definition of early-stage success.

VCs never really invest in ideas.  They say they invest in great teams or great founders, and I believe that this is often the case.  A great team with a [decent?] idea is sometimes enough.  But I’m pretty sure that “great team” or “great founder” has a very, very limited definition; namely, somebody with a previous exit (IPO or acquisition), or deep and wildly impressive domain expertise.  Unfortunately, by definition, no first time entrepreneur has either of these.  They have ZERO credibility.  So how do first-time entrepreneurs gain momentum and raise money? They build something that people like and use.  If you can do that, then you just have to convince VCs that you can keep doing what you’re doing (building something useful and getting people to use it).

This might seem obvious, but it wasn’t obvious to me for a very long time: the only thing that you should try to do early on is to build something that people use.

4. Unless you’re part of the Silicon Valley in-crowd AND you have traction, you’re not going to raise venture capital

When Bill and I first founded WePay in Boston, we spent a lot of time thinking about the VC industry, hanging out with other first-time and unfunded entrepreneurs who talked about VC firms and partners as if they were celebrities and close friends.

There were dozens of networking events with workshops on how to raise venture financing, create a decent pitch deck, pitch effectively, etc. There were even more events that gave entrepreneurs the “opportunity” to get in front of VCs and angel investors.  We saw the same group of young, networking entrepreneurs every time.

We thought: “hey, this must be what starting a company is all about.”

We had this incredibly naïve notion that if you came up with a great idea, you could raise a few million bucks with a few slides and some undergraduate-style market research.  There was huge credibility gap that we had little chance of overcoming. We spent a lot of time tweaking and refining our pitch deck, meeting with VCs, networking, and thinking we were making progress.  We thought VCs loved us, despite the fact that we rarely got a second meeting.

Luckily, during that period, we also got a lot smarter in the payment space – learning about payments in general and forging partnerships. If it wasn’t for that, our first 6 months in Boston may have been a complete waste of time.

When we finally moved to Silicon Valley, two things happened: we built a product, and we got a foot in the door with the in-crowd.  I think one of YCombinator’s greatest accomplishments is its ability give young and un-connected entrepreneurs almost instant access to the Silicon Valley elite.

With a product, some promising feedback from early users, and some healthy Silicon Valley buzz, fundraising was a profoundly different experience than we originally thought it would be.

5. Customer Acquisition is tough

I’m not sure what it’s like for companies that don’t charge users, but for those that do, acquiring customers is a pretty significant challenge.

I’m convinced that customer acquisition is the most overlooked and understated challenge faced by first-time entrepreneurs. At least it was for us.

How can our product not grow virally? It’s fulfilling a real need. I know I would use it. All my friends say they would use it. The idea is earth shattering, and it solves a problem that everybody has! Customer acquisition? HA! The product will sell itself!

I have seen a lot of successful approaches to customer acquisition, but every one of them was a difficult uphill battle, carefully planned, and masterfully executed.  Some social networks recruited celebrity early-adopters that brought their followers along with them. Some clever startups sell their product before they build it (in other words, they lock up some early marquee customers – usually through personal connections, or previous employers).  Other companies have huge marketing budgets, or aggressive and experienced sales-forces (but that’s obviously a lot tougher for bootstrapped or early stage customers).

We have taken a multi-channel approach, but each one of those channels has required a ton of thought and relentless execution. Customer acquisition (at least in the early days) should not be taken for granted.

Check out the company Rich and Bill started. WePay is free to sign-up!

Boston College undergrad TechTrek visits Silicon Valley

Thursday, March 4th, 2010

For the second time this year, a group of ambitious Boston College students made the long journey to the West Coast to visit tech companies in the Bay Area, including eBay, Google, Social Text, and others. WePay was fortunate enough to host the group for a few hours last night.

Unlike last time, this was a group of undergrads (rather than grad students).  I was AMAZED at how sharp and knowledgeable they were.

During a QA session, one of the students said: “You guys have a group of 24 people in your target demographic sitting in your office. What are the biggest problems you’ve faced while trying to acquire new users, and do you think you could benefit from a group brainstorming session?”

Suffice it to say that the two hour brainstorming sessions that followed was one of the most helpful we have had since we founded this company. We learned a ton about student clubs and organizations, collecting dues for campus groups, splitting expenses in 8-person apartments, etc.

It was an awesome visit, and we are excited to keep in touch with them.

Join these students and visit WePay. Give us a try, it’s free to sign up!