How to build your startup without learning code

water

Transparent, tasteless, odorless
OG Investor
How to build your startup without learning code

January 30, 2012

If you can’t code but aspire to start a Web business, odds are you feel just like the ostrich.
Ostriches can’t fly, and to add insult to injury, they’re one of the largest bird species out there. They have to hobble around
looking for something to do while their avian counterparts swoop into the air in boundless directions.
Despite spending years in school and hours at the workplace, without knowing how to code you can’t create your vision. You’re left with two options: learn to code (Codeacademy is worthy investment of your time if you can fit it in), or find a programmer (an undertaking that warrants its own article). Given the frustrations, many would-be entrepreneurs give up on their vision without giving it a real chance. That’s a pity, and it doesn’t need to be that way.

Here are some tips and tool-recommendations to help you build a Web business without learning how to code.

Simulate your vision with visual tools
Recommended tools: Powerpoint, Balsamiq, iMovie

As an entrepreneur, your goal is to assemble the necessary resources to create your idea. Finding the required talent and money means selling your vision. The first knee-jerk reaction is to write a business plan. Although useful, a business plan is not the best communication tool. It can be jargony, dense, overly-complicated, and simply put, it doesn’t showcase your idea. (If you write anything, go for a 2-3 page executive summary.)

Instead, I recommend building a website mockup. Show each page’s function and simulate how they behave by linking them to one another. Powerpoint is a great tool for this since you can link buttons to each slide easily. I recommend investing in a mockup tool (my personal favorite is Balsamiq), which is very user-friendly given its drag-drop functions. If done properly, your mockups can have the look and feel of a real website. Now friends, investors, or potential co-founders can see your vision instead of reading a long, dry document. If you want to take this to the next step, make a video by “screen recording” your mockup (I use Snapz Pro) and adding some narrative and music using a basic movie editing software like iMovie.

Create a prototype using widget-based website creators Recommended tools: Weebly, Wix, WordPress, Google Analytics, Qualtrics
Prototyping is all about validating individual portions of your concept. Use widget-based website creators to quickly and easily put together a prototype. Weebly, Wix, and WordPress (just to name a few examples) can be very powerful when mixed with a little creativity.

Letting potential users interact with something will give you valuable data, which you can easily capture using data analytics. My favorite is Google Analytics because it’s free and easy to implement (it just got a great upgrade too). If you can’t capture particular data, use surveys (Qualtrics is a fantastic tool which lets you capture 250 surveys for free) to engage users.

How do you get testers?
Put the page up on your Facebook wall, send e-mail blasts, or offer a raffle or a perk (for example, first to get access to your site once it’s built). Having data in your pocket will both educate you and provide compelling information when you’re trying to recruit others or raise funds.

Brand your vision Recommended tools: CrowdSpring, 99designs, LaunchRock, Facebook, Twitter
We live in a world where the smallest startup can look and feel like one of the biggest companies out there. Make sure you snag a good domain name and create an attractive logo. You can inexpensively outsource design jobs to sites like 99designs or Crowdspring.

Once you have some visuals and an identity, cover your bases: Create a landing page for your site (LaunchRock is a good tool for that), set up a Facebook page (claim your facebook.com/yourbrand), and start developing an audience through Twitter. Family and friends will want to support you, and potential clients will be interested in learning about your company. Having an online presence gives you a stage where others can share in your journey. You’ll have a community of eager users ready to support you faster than you think.

Enjoy your launchpad and raise money Recommended tools: Kickstarter, AngelList
Your company is now live. You’ve established a presence and have powerful tools to sell your vision. If you want to hire talent, you now have somewhere to point applicants. If you need support, you can show family and friends a preview of what you want to build. If you want to raise money, you can go on Kickstarter or AngelList with a bit more credibility (and hopefully a mockup video in hand).



Tony Navarro (@hoostony) is founder and CEO of Streamcal.com, a venture that redefines the way schedules and calendars are published, shared and consumed across the web. He has an MBA from Wharton and an MPA from Harvard, and currently lives in Boston with his wife. He is also a member of The Young Entrepreneur Council (YEC), an invite-only nonprofit organization comprised of the country’s most promising young entrepreneurs.

http://venturebeat.com/2012/01/30/how-to-build-your-startup-w...





I used www.surveymonkey. com and embedded it in facebook as well as emailed by friends the link.

Using balsamiq to do the mockup.

Using appmobi to do prelim design

Used www.templatic.com for a $5 landing page that includes contacts, twitter feed and other social media buttons on a wordpress site.

www.odesk.com for programming initial version of site.


Hope this helps........



:D
 
good shit. I bought Balsmiq but its giving me some trouble or maybe its the learning curve. I import pics but they dissapear when i open the project up again. Plus i dont see where I can link pages.
 
Ran across this and thought it may help. This was written by the founder of 10sheet, a bookkeeping app. He's describing their process as he's not a technical guy either...


18 months ago I was in a similar position to you. I felt like what I had was a great idea and money to invest in it, but I had no technical partner to help me execute. Fast forward to today and I've got a team of 5 fantastically talented developers, we're finishing up at the TechStars accelerator program, and we're about to raise a Series A. It's very possible to be successful without a technical co-founder, but it takes a little strategy and a lot of hustle. Here are my thoughts on the subject.


1. Find a code ninja to interview your applicants
Don't harbor any illusion that you have the ability to discern the technical ability level your applicants. You don't. You need a bonafied code ninja to interview the candidates for you. Your only role in the interview process is to assess cultural fit and soft skills, and then feed the remaining candidates to your interviewer.

Find an interviewer who works at Google, Amazon, Facebook or a similar organization if you can. Someone who's technical ability has been validated by an objective third party that you can trust. Don't know anyone at a premier tech company? That's where the hustle comes in. If you want to start a tech company, you NEED to know talented people. So get networking and make it happen.

Don't settle for an interviewer that's 'good enough'. You are putting the future of your startup in this person's hands. This person will make the most important decision in your startup's early life. So don't compromise on quality.

Don't take this to mean that you should try to strike up superficial friendships with talented people in order to use them for their skills for free. That's definitely a douche move. What you CAN do is put yourself in the best situations to strike up genuine relationships with talented people. Or you can just be up front about it, find these guys on LinkedIn, and pay them for their time (if you can get them interested).

2. Generate a super talented applicant pool
Before you select a candidate, you need a pool of talented people to choose from. Use every weapon at your disposal to generate leads: oDesk.com, elance.com, craigslist.org, authenticjobs.com, local tech meet ups on meetup.com, house parties that your engineering friends throw, parties thrown by Computer Science and other awesomely geeky groups at your College.

This process typically takes a while. We spent months at it, generated over 300 applicants, and did 20 interviews before finding the right candidate.

By the way, there are right and wrong ways find leads. If you need a guide, here's a good start. http://alexeymk.com/recruiting-penn-engineers-intro-emails-that-d

3. Interview the right way
We've tried 10+ interview strategies and there's only one that's worked for us consistently over time: pair programming. Have your interviewer sit down (locally or remotely) and watch the candidates write code. You'll test them for their real coding ability, not their ability to answer questions or present well. Lots of people can talk big game about code, few can back up the talk with real skill.

4. Fire fast and start over
If a candidate has got all the way through your interview process but then fluffs the job, don't be afraid to get rid of them and start the hiring process over. Until you have real investors, there's no real pressure to hit milestones. Even if it slows down your development in the short-run, you'll be glad you did it. We fired our first two hires before we found our superstar technical lead.

5. Give them equity once they've proven themselves
To really keep your tech lead motivated, committed, and invested in your success, you need to give them substantial equity in the company. This doesn't need to happen right away. But once that person is 100% battle tested and you know exactly what you're getting, it's time to lock it down. You should set up Stock Vesting over a number of years, (which is an entire topic unto itself). The ownership amount should be up for discussion, but something in the 3-10% range should be sufficient if he's taking a salary and you funded the company out of your own pocket at the beginning.

Additional notes:
Hiring a remote CTO can be a great solution. Eastern European countries (Russia, Ukraine, Romania, etc.) have fantastic untapped talent pools. Our CTO is from Russia and we relocated him here once we raised our seed round; it worked out quite well for us. We've hired 3/5 of our developers from Eastern Europe. oDesk.com is a fantastic platform for recruiting there. Hiring remotely from India, however, doesn't seem to have worked for anyone that I know that's tried it (including us).
Don't hire someone who can only work part-time. You want someone who eats, lives, and breathes your project. Anything short of that and they just won't perform the way you need them to. If they're only willing to work part-time for you, they're clearly not passionate about your project.
Resist the temptation to go with a development shop. They're super expensive and not particularly motivated to make you successful.
Don't read dev blogs and think you know anything about what languages or solutions your dev team should use on your project. It's fine to present ideas to your team, but don't argue with your dev lead that he should use Ruby on Rails because "all the other cool startups are doing it." Let your dev lead make the right decisions for your project with his superior knowledge and experience.

#homebase
 
Last edited:
Ran across this and thought it may help. This was written by the founder of 10sheet, a bookkeeping app. He's describing their process as he's not a technical guy either...


18 months ago I was in a similar position to you. I felt like what I had was a great idea and money to invest in it, but I had no technical partner to help me execute. Fast forward to today and I've got a team of 5 fantastically talented developers, we're finishing up at the TechStars accelerator program, and we're about to raise a Series A. It's very possible to be successful without a technical co-founder, but it takes a little strategy and a lot of hustle. Here are my thoughts on the subject.


1. Find a code ninja to interview your applicants
Don't harbor any illusion that you have the ability to discern the technical ability level your applicants. You don't. You need a bonafied code ninja to interview the candidates for you. Your only role in the interview process is to assess cultural fit and soft skills, and then feed the remaining candidates to your interviewer.

Find an interviewer who works at Google, Amazon, Facebook or a similar organization if you can. Someone who's technical ability has been validated by an objective third party that you can trust. Don't know anyone at a premier tech company? That's where the hustle comes in. If you want to start a tech company, you NEED to know talented people. So get networking and make it happen.

Don't settle for an interviewer that's 'good enough'. You are putting the future of your startup in this person's hands. This person will make the most important decision in your startup's early life. So don't compromise on quality.

Don't take this to mean that you should try to strike up superficial friendships with talented people in order to use them for their skills for free. That's definitely a douche move. What you CAN do is put yourself in the best situations to strike up genuine relationships with talented people. Or you can just be up front about it, find these guys on LinkedIn, and pay them for their time (if you can get them interested).

2. Generate a super talented applicant pool
Before you select a candidate, you need a pool of talented people to choose from. Use every weapon at your disposal to generate leads: oDesk.com, elance.com, craigslist.org, authenticjobs.com, local tech meet ups on meetup.com, house parties that your engineering friends throw, parties thrown by Computer Science and other awesomely geeky groups at your College.

This process typically takes a while. We spent months at it, generated over 300 applicants, and did 20 interviews before finding the right candidate.

By the way, there are right and wrong ways find leads. If you need a guide, here's a good start. http://alexeymk.com/recruiting-penn-engineers-intro-emails-that-d

3. Interview the right way
We've tried 10+ interview strategies and there's only one that's worked for us consistently over time: pair programming. Have your interviewer sit down (locally or remotely) and watch the candidates write code. You'll test them for their real coding ability, not their ability to answer questions or present well. Lots of people can talk big game about code, few can back up the talk with real skill.

4. Fire fast and start over
If a candidate has got all the way through your interview process but then fluffs the job, don't be afraid to get rid of them and start the hiring process over. Until you have real investors, there's no real pressure to hit milestones. Even if it slows down your development in the short-run, you'll be glad you did it. We fired our first two hires before we found our superstar technical lead.

5. Give them equity once they've proven themselves
To really keep your tech lead motivated, committed, and invested in your success, you need to give them substantial equity in the company. This doesn't need to happen right away. But once that person is 100% battle tested and you know exactly what you're getting, it's time to lock it down. You should set up Stock Vesting over a number of years, (which is an entire topic unto itself). The ownership amount should be up for discussion, but something in the 3-10% range should be sufficient if he's taking a salary and you funded the company out of your own pocket at the beginning.

Additional notes:
Hiring a remote CTO can be a great solution. Eastern European countries (Russia, Ukraine, Romania, etc.) have fantastic untapped talent pools. Our CTO is from Russia and we relocated him here once we raised our seed round; it worked out quite well for us. We've hired 3/5 of our developers from Eastern Europe. oDesk.com is a fantastic platform for recruiting there. Hiring remotely from India, however, doesn't seem to have worked for anyone that I know that's tried it (including us).
Don't hire someone who can only work part-time. You want someone who eats, lives, and breathes your project. Anything short of that and they just won't perform the way you need them to. If they're only willing to work part-time for you, they're clearly not passionate about your project.
Resist the temptation to go with a development shop. They're super expensive and not particularly motivated to make you successful.
Don't read dev blogs and think you know anything about what languages or solutions your dev team should use on your project. It's fine to present ideas to your team, but don't argue with your dev lead that he should use Ruby on Rails because "all the other cool startups are doing it." Let your dev lead make the right decisions for your project with his superior knowledge and experience.

Man this shit was so right on time. I've been struggling with this myself and just attend Finish Weekend to try to connect with other developers with dismal results. Here is another one that was posted on TechCrunch:

Editor’s note: This is a guest post by Mick Hagen (@mickhagen), founder and CEO of Undrip. He was previously the founder of Zinch which was acquired by Chegg last year. He made headlines in the Fall with his rap campaign – an unorthodox approach to fundraising. You can learn more about him at MickHagen.com.

Last summer when I started working on Undrip, I was in a tough spot. I grew up doing web and graphic design so I was a pretty good front-end developer and designer. But I knew nothing about back-end web development – loops, branches dictionaries or functions were all foreign concepts to me. I was a single founder who couldn’t code.

Against the Odds

Every week I get emails from entrepreneurs seeking my advice asking how I did it before, and how I’m doing it now. They find themselves in similar situations in that they’re looking to build a tech startup with little to no technical skills. They’re frustrated by their inability to make forward progress and they usually either give up and fail, or outsource if they have some extra cash (which usually leads to failure).

If you’re a single founder who can’t code, your chances for startup success are near zero. However, there’s still a chance.

And a chance is all you need.

Inspire or Die

There’s only one skill in the world that can make up for your lack of design or dev skills. It’s a skill you have to learn and learn to do well: You must learn to inspire.

Your survival will hinge on your ability to inspire, persuade, and convince makers that they should join you on this adventure. It’s the only chance you have. You know you can’t do this alone. You shouldn’t do this alone. And you won’t do this alone.

Easier Said Than Done

Some non-technical entrepreneurs are so incredibly charismatic, persuasive and charming that all they need is a clean napkin and a wide smile to sell the vison and get people excited. They’re able to attract talent with no problem. If that’s you, congrats. Run with it. As long as you have creators, makers and builders on your team, you’re in the game and able to fight. Give them the equity they deserve (a lot!). Make them owners not mercenaries. Your idea is worthless without them – accept that now and nobody gets hurt.

As for the rest of us, we’ve got more convincing to do.

When I was recruiting people to help build Undrip, I could have just dazzled people with designs. For many folks, that’s all you need to help inspire. But I wanted to take things up a notch. I wanted to personally build something that potential teammates could see, feel, touch and play with. I wanted to share a fully functional product that I would muscle together with my bare hands – Chuck Norris style. So I had to learn to code.

Becoming a Builder

I spent all last summer learning how to code [0]. I practically lived on StackOverflow, Github, IRC channels, and Google… soaking it all in like a sponge and working on a real product that would force me to learn. I had afew friends who answered my dumb questions and guided me through some snags. In the end, I built the first version of Undrip almost all on my own. It was perhaps one of the greatest accomplishments of my life. At the end of last summer, I felt like I could I do anything. It was an incredible experience [1].

It was never about learning to code so that I could be a one-man army. And it certainly wasn’t about creating a large-scale, production-ready web app that millions could use. In fact, not even a dozen people could use it [2]. It was all about inspiration – putting more arrows in my quiver so that I could get out and inspire people to join me. I wanted to demonstrate that I could dig in and learn, and that Undrip was a product worth fighting for.

Handshakes & Smiles

As much as networking sucks, it’s a necessary evil when you need builders. You can’t inspire people if you don’t know anybody to inspire. I’d much rather be working, designing and getting stuff done.

Throughout the summer of me learning how to code, I did everything I could to meet engineers. I would go to python meetups and other hacker gatherings. I would search directories, github and twitter lists for python engineers in the Bay Area who I could meet with in person. It was never about asking them to work with me – that’s the wrong approach. it was always about cultivating the relationship and learning from them as I was doing my best to speak their language (python/django). They felt like they were “giving back” and helping a n00b. I remember meeting Mike Malone, Kenneth Love and so many others at coffee shops in the Bay Area. I drove to a small town in the East Bay to meet Kenneth at a local Starbucks. I was immersing myself into their world and building as many relationships as I could. Inspiration always starts with a relationship.

Money Can’t Buy Everything

When you can’t inspire people to join you, it’s very tempting to use that cash in your piggybank to hire a contractor/freelancer. You wanna pay to play.

That rarely works.

I was a design freelancer in college. I would ask for as much money as possible, and I would try to spend as little time on it as possible. That was the name of the game. Contractors just aren’t invested in the long-term success of your product. They’re gypsies moving from one thing to the next. The lack of ownership and commitment will cost you more money, more time and more heart ache in the long run.

What happens when your freelancer is “done”? We all know products are never done. So soon you find yourself back at square one, having to pay someone to fix bugs, tweak features, etc. That hole in your pocket gets larger and larger.

For most that’s just not sustainable. Sooner or later you’re gonna need to inspire people to join you. You’re gonna need partners, owners, motivated team members. A little contract work is never bad when you’ve got people who can maintain, manage, and build the product where it leaves off.

Only One Way Out

In the end, you’ve got just one path ahead. There’s no other way around it.You have to inspire. You can learn to code. You can learn to design. You can learn to hustle. You can learn to do a lot of things. But all of them should be mere tactics to your end goal: inspiring others to believe in you, your vision and your product. That inspiration needs to be so strong that they leave everything they’re doing to jump on that life raft with you to start paddling.

It’s insanely hard. It’s insanely crazy. And it’s insanely rare.

But it’s possible. May the odds be ever in your favor.
 
Last edited:
good thread.

I also recommend freelancer.com

Used to use them more when they were vWorker (and before that, rent-a-coder). Get LOTS of stuff done that way,for pennies.

I recently had a design contest for a logo, got 65 entries and only spent $30. Now I'm about to trademark dat bitch!
 
after you feel comfortable let us see the work
good thread.

I also recommend freelancer.com

Used to use them more when they were vWorker (and before that, rent-a-coder). Get LOTS of stuff done that way,for pennies.

I recently had a design contest for a logo, got 65 entries and only spent $30. Now I'm about to trademark dat bitch!
 
Back
Top