DIY, Outsource, Partner... How should I approach creation?
I've developed the idea, asked potential customers questions, got feedback. I know it has potential. So, I designed the website wireframe, business model, marketing model, logo...
But now comes the time where something useable needs to be created. I can show potential customers a wireframe and ask them questions, but until they actually show they are willing to use (and pay) for it, I know I don't have any real traction.
I come here asking for advice on how I should approach creation. There seem to be three approaches:
1. Do it yourself 2. Outsource 3. Find a co-founder
Now, I am determined to learn to the technical side regardless. I've started on that journey, tackling HTML, CSS, and Javascript. I'm no expert, but I understand. I want to go after PHP as well. However, I know I don't have time to be professionally proficient in a reasonable time. It won't stop me from learning, but I'm not sure if it's the smartest way to approach this. But please, tell me if I'm wrong. I don't underestimate the amount of work/experience needed to be a great coder though... so I don't expect to be good enough in a few months.
In regards to outsourcing, I have a good amount of money saved, enough to hopefully create something. However, that something might not even be close to the end goal... and then what? What about when customers ask for more? What about maintenance? What if I do go to investors and it's just me... sure, I consider myself valuable on both the business and design end of things, but with no one to cover the technical aspects, who will want to invest? Which brings me to...
Finding a technical co-founder. I'm from NYC and plan on going to some startup meetings I've found out about. However, I know this is a scary proposition as well. For one, I have nothing created, so will anyone want to even come on board? Then I guess I need to assess options 1 & 2.
I just am looking for some guidance here. I'm at this standstill and I feel overwhelmed with all the options and just pick a direction and go. If that's outsource and then find a technical co-founder once something is implemented, then I'll tackle outsourcing now. If it's DIY, then pick up my pace (hell, quit my job, live at home and make studying and creating my new job) so I can get things going. If it's find a technical co-founder, than go out there and prove myself.
Anyway, I apologize for the length of this post, but I guess I have a lot on my mind here. But any help would be greatly appreciated. Thanks!
6 comments
[ 3.6 ms ] story [ 17.1 ms ] threadAlso, hack! Not just code, but think of ways to validate product-market fit without actually having to build the whole damn thing. Set up a landing page with a button or two that mimics the feature you want to test. If someone clicks on it, at least you'll know there's interest. If not, no big deal. Assuming they click on it, instead of sending a 404 error, put something like "We're building [description of awesome, world changing web app]. If you want to be one of the very first users and brag to all your friends about how in the know you are, sign up below." Then just put a nice tidy email field with a big ole' submit button. Done. You've proven people want what you're building and you have a list of emails of people you know will use your product once you've built it. Use that to convince some superstar to become your technical cofounder.
Startup Weekends and that sort of thing are a great way to meet potential cofounders as well, where people share their idea for a startup, form teams and hack all weekend. Whatever you do, don't waste your money on outsourcing, especially at this point. Startups are a long road. Get out to events, get to know people, and share what you're working on (no one is going to steal your idea). Good luck!
I will take that idea regarding a landing page heart. Especially considering it's something I can manage to put together myself. Perhaps even throw a "comments" field for suggestions on what features customers would want? I could even respond to said customers personally in regards to their comments/suggestions. Let me know if you think going that far would be beneficial or bothersome to potential customers (I personally would like that type of attention as a customer).
Anyway, sounds good about not outsourcing. I won't bother with that, especially since my website cannot be implemented properly without a significant amount of time and effort... and therefore, money. I feel as if just a landing page with email and suggestion form would be 100 times more useful than some minimally featured, half-assed version of a website I paid for. Since that website might actually end up turning people away.
Any advice in regards to startup events? For instance, there is one in NYC on October 11. I will go, but I won't know anyone. Now, I'm decently outgoing, so I'll try to introduce myself, but should I try to contact people before attending? Then at least I'll have someone to meet and it won't be as difficult. I don't know.
I understand it's a long road. But it's exciting.
Thanks for the luck. I'll be trying my hardest to ensure success. We'll see what happens.
For startup events, I would say just go and strike up some conversations. People are generally helpful and will share their experiences. It's a good way to learn. Speaking of, when I was first learning about startups I listened to the podcasts at the Stanford E- Corner basically non-stop: http://ecorner.stanford.edu/
I would consider studying Eric Ries and Steve Blank as well regarding "lean startups". "Four Steps to the Epiphany" and "The Lean Startup" are books worth spending the money on.
It's good that you're in NYC. There's a strong community there.
Cheers!
I will keep the landing page simple. Although, I'm not testing a feature with the landing page, but more the concept... to see the interest and perhaps even get suggestions based on what potential customers want.
Quick question in regards to the landing page for you (or anyone else reading this thread):
Would it work to have successive landing pages?
Essentially, the first is signing up to show interest for those who want to get notifications, be part of future testing and perhaps give suggestions.
Once you have submitted your email address, there will be a confirmation page. For those willing to go a step further, I'd have an additional CTA, linking you to a short survey.
I know that having both on the first landing page would probably deter people from signing up in the first place. Yet is having the survey on the confirmation page going to guarantee no one will answer the survey?
Just looking for some conventional wisdom on landing pages. That's the best approach I could think of, but I'm open to advice/suggestions. Thanks!
Don't say anything on the first landing page about future testing and giving suggestions. I would use that email list solely for the purposes of notifying once the product is launched. Don't send anything to those emails until after the product is launched. It's sort of "the boy who cried wolf" thing. People only want to hear from you when there's actually something they can use. Also, people hate spam and you don't want them to start blocking and deleting your emails without reading them because then they'll never know when you actually launched.
Give your survey takers the option to sign up for future surveys by having an email field at the end of the survey.
Also, I really like the idea of putting another email input to sign up for future surveys. So that I can get the emails of those who are interested for launch and those who want to be a part of the process.
Seriously, thanks for the help!