An idea for non-technical co-founders: try a service-first business
benogle.com
benogle.com
As a non-technical founder, you are likely good at building and maintaining relationships. You are probably good at selling things. You might be great at framing, so people buy into your vision or get excited about your ideas. These are amazing, difficult-to-acquire skills.
Unfortunately, too many non-technical founders do not have those skills. Many people believe that an idea and "hustle" (working hard, being persistent) is enough. Now they just need to find people to build it, people to market it, people to sell it. They have this great idea! the rest will just fall into place.
The OP saw teams that made it through the YC process. Likely, those are not your average non-technical founders. If you do have those skills, then for sure - this is great advice.
Assuming of course it's not money cause money solves most problems.
Whether they are what is required will depend on the situation.
Domain knowledge is useful, however (i.e. a lawyer at a startup doing online legal documents).
http://techcrunch.com/2013/02/08/thoughts-from-a-former-busi...
I don't usually come across helpful posts on TC, but this one caught my eye. Basically, if you look like the stereotypical idea guy/gal, you need to put the startup dreams aside for a bit, work at an established company, gain some experience, and, here it comes, develop skills.
Now, I'd argue this guy (the TC guy) is spreading himself a bit too thin, but the idea of being the utility player on the team is pretty good. When combined with your work experience, you might be an attractive candidate. Go a step beyond that by following OP's advice and, you know, actually build something.
It doesn't need to be a home run, but it should speak for itself, and when you have something, anything really, that speaks for itself, you're in pretty good shape.
your average non-technical founder is extremely likely to fail. If you want to give advice to the them, it should start: become exceptional.
Another benefit that isn't mentioned in the article: this gets you money in the bank from day 1, making you a lot less reliant on giving away equity to VC's, with all the good that implies. And honestly, if all you need is a technical person to help you scale after you've already got some money in the bank, you can always pay someone to do it - saving you even more equity.
I started working this way at the start of 2012 and all of my projects since then have been far more popular/successful and more pleasing to work on. This is because I'm fully in control of project progress, I can see things through to launch, pushing the limits of my coding skills and bringing my 'concierge' MVP to life.
For those looking for technical help with a project longer term, don't forget that by starting this way you're stripping back and leaving pure technical issues which allows those with technical skills to clearly see where they could bring value which makes offering help very interesting.
I don't remember the company, but I was inspired by a fresh fruit+veg box-delivered-to-your-door founder. He made all the deliveries himself to start with rather than building a grandiose delivery platform or hiring.
I started my B2B company the same way. Initially I copied and pasted my code into customers sites. My 'ordering system' was just a PayPal express checkout. Zero backend. Man was it dull. But as a developer I knew I could automate 90% of what I needed to, when I needed to.
Now it's completely automated apart from support. Meaning my notional margin (cost of sale being my previous contracting rate) is at 85%. And I know I've just written the code I needed to so as to not do the mundane manual tasks anymore.
Could it have been Manuel Rosso of Food on the Table? He was the "Concierge MVP" example from Ries's book. They started by meal planning for a single family. If I'm remembering this right, he and his chef co-founder walked the grocery stores each week looking for the best food values, then drew up the week's menu...for that one family.
http://www.foodonthetable.com/
It worked, and they automated things as they scaled.
> I started my B2B company the same way... Now it's completely automated apart from support.
It's great to hear this. A film industry friend and I started a company last year with a very similar approach, but we're earlier along than you are. So far so good!
All the best for your company!
This is why I've stopped attending meetups that aren't specifically targeted towards devs. It's a shame, because there are many interesting people at those events, but every time I go to one I get sick of explaining why I don't want to work for startup X or be represented by recruiter Y.
In the last year I've met more than a dozen such groups. Of those, 2 had actually done some legwork on their own - one had attended a tradeshow showing nothing more than a powerpoint and had collected some leads. (initially, that was impressive). Another had done a lot of exploratory work, and when I asked them to do XYZ, they actually did it and gave me the results from it.
In both cases, I've extended a bit more of my time to work with these people in hopes of getting the project to a point where we might work together long term. In one case, we simply parted ways because the vision was shifting a lot on his end - no focus. In the other case, that team has actually called it quits - they had simply underestimated the time and effort involved in making it work, and I appreciated the halt vs dragging it on for months on end.
But rarely do I meet groups or people that have done any significant legwork at all - they're the typical "idea man/woman", and just need someone to "make it work".
In fact, USC's online graduate program for education started this way. They were trying to decide whether to do it or not, so they put up a landing page with a broken buy button and bought AdSense against it. When they realized how many people were trying to buy, they decided it was a market worth satisfying and built the program behind it.
There are tons (tons!) of businesses out there that can be made to scale, optimized or otherwise improved through technology, but can be proven out with nothing more than a wordpress blog (or other free, non-custom infrastructure).
I think this article is spot on for most people. A lot of very successful businesses can be started with a wordpress blog and very little technical capability.
A business based around the technology itself is a highly risky venture. I would argue it's a lot lower risk to first develop a business without much technology, build up your customer base and then gradually build technology to automate more aspects of the business as you go.
PayCycle purchased by Intuit for $170million is an example of this. They started doing the payroll for businesses completely manually. Literally writing out checks etc. Then they gradually automated each step of the business.
For most businesses it's a better strategy to build the business first get customers and then build the technology second. Technology startups where you build the technology first are the exception not the rule.
In the movie, Guess Who's Coming To Dinner, Spencer Tracy's character calls his secretary and asks her to check out his prospective son-in-law. Today, we would just ask Siri to do it.
1. You will be working with real, money paying customers from day 1 - right there you are ahead of 90% of startup projects.
2. You get to work your customers to understand their pain points, needs directly, without annoying them - they will actually be delighted that you are trying to understand them better!
3. You have revenue coming from day 1.
4. When you launch your product, you already have a group of people in your target audience, with whom you hopefully have already eared trust.
Anyone else bothered by this view of YCombinator as a kind of university programme?
I may be wrong, I have only met a few YC founders and they all seemed like nice, smart people, but it seems a bit off-colour to treat the mere fact that you've been through the YC programme as some kind of "graduation".
Maybe I'm just being grumpy or something... It's certainly not a big deal... but something just rubs me wrong when I read that sentence...
My takeaways: (1) Look for unconventional ways to create a MVP (2) Hustle is a very valuable asset to a startup. For startups with high hustle-to-technical ratios, they may consider building a culture around hustle rather than code.
There is a vast amount of knowledge one needs to learn just to be a beginner. I don't blame so many idea people for trying to find shortcuts.