Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Finding a technical co-founder

Finding a technical co-founder

Thoughts and advice for non-tech people looking to start something from a technical co-founder.

Michael Kowalchik

August 07, 2012
Tweet

More Decks by Michael Kowalchik

Other Decks in Business

Transcript

  1. WHO IS THIS GUY? • An Engineer, Entrepreneur, hacker, serial

    cofounder • Lots of years at ‘big co’ in R&D • CTO and Co-founder of a new startup that will change the world: Smarterer
  2. WHO IS THIS GUY? • An Engineer, Entrepreneur, hacker, serial

    cofounder • Lots of years at ‘big co’ in R&D • CTO and Co-founder of a new startup that will change the world: Smarterer
  3. WHAT? • Perspective: as a technical cofounder • Prescriptive: not

    in the way you might expect • Pitch: how not to • Pointers: tech person search
  4. Do you believe others can execute your idea better than

    you can? “People will steal my idea...”
  5. Actually, startup ideas are not million dollar ideas, and here's

    an experiment you can try to prove it: just try to sell one. Nothing evolves faster than markets. The fact that there's no market for startup ideas suggests there's no demand. Which means, in the narrow sense of the word, that startup ideas are worthless. Paul Graham - YCombinator
  6. Almost all startups succeed with something other than their original

    idea. “No battle plan survives contact with the enemy”
  7. You believe “If you build it, they will come”. If

    you think all the value in the business is in building the product, why do I need you? You think building a product is easy.
  8. "When you're the janitor, reasons matter," Jobs tells newly minted

    VPs, according to Lashinsky. "Somewhere between the janitor and the CEO, reasons stop mattering," says Jobs, adding, that Rubicon is "crossed when you become a VP." Steve Jobs as recounted to Steve Lashinsky in Fortune Magazine
  9. Moral of the story: look for the ways you are

    blocking yourself. Do not wait because things aren’t how you think they should be.
  10. THINGS THAT DO NOT MAKE YOU A COFOUNDER • ideas

    • MBA • business plan • spreadsheet • weeks / months / years of thinking and dreaming
  11. SO WHAT THEN? • Access to money • Reputation and

    network • Persistence - masochistic streak • Most important: Hustle!
  12. TWO COFOUNDER ARCHETYPES • The Hacker • Solves problems, builds

    things • The Hustler • Connects, Makes things happen
  13. HOW? IMAGINE... • What do you do, day to day

    when you have a TCF? • Why aren’t you doing those things now? • What do you do, day to day, when there are five of you, ten...? • Why aren’t you starting those efforts as well?
  14. • Any way you can prove the business • Sell

    / canvas initial customers • Gather data • Smoke Test PROVE THE BUSINESS
  15. •Are you blogging? •Do you have a product landing page?

    •Are you running adwords experiments? •Are you doing customer development? •Are you concept testing? User Testing / Powerpoint mockups?
  16. GIVE TO GET • You want someone to help you?

    Help others. • Build networks • Use your skills to improve the chances of others in the community
  17. CULTIVATE STARTUP TECH FRIENDS / ADVISORS • Boston community: people

    genuinely want to help • Ask CTO’s especially co-founders for tech advice • connect to their networks • evaluate possible cofounders - uniquely qualified to id them • Legitimize you to other tech people • Buy them a beer :)
  18. ECHO ECHO CHAMBER CHAMBER • Sloan entrepreneur events = no

    hackers • Tech / entrepreneur meetups (lean startup) • Hacking meetups (just lurk, maybe offer to help a tech guy with non-tech skills) • Learn a little bit about how hackers think about entrepreneurship (read hackernews)
  19. SHOULD I LEARN TO CODE? • Yes • know at

    least a little about what you’re talking about • understand the tasks at hand, respect • No • Is this the best use of your time? • There are many other tasks other than building product.
  20. Q?