Skip to content

kamil-rudnicki/knowledge-base-for-startups

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

35 Commits
 
 

Repository files navigation

(no longer updated, I started using Evernote to build my knowledge base)

The Knowledge Base for Startups

(CC) 2011-2013 by Kamil Rudnicki (http://rudnicki.info)

Ideas

Ideas Creation

Motivation & Expectetions

Strategy

Business Plan

Strategy

Acquisition

Execution

Metrics

Scaling

Lean Startup

Beeing a Manager

Beeing a CEO

Marketing

  • press should love it
  • differentiate, differentiate, differentiate (like No Software sales force)

Recruiting

Team Members

  • Smart Guy Productivity Pitfalls
  • QA - looks at features and code, and propmt programmers for things, that he was too lazy to think about - he decides if feature is ready to be realeased. Also makes sure nothing is broken. Fundamentall difference between dev vs qa is that qa brakes things. Crashes are their fault.
  • Helpdesk
  • Product managers - communicate, thinks about features, talks with coders - only convincing them (peers), talks with customers, make specifications. He is thinking about magic functions, coders thinks about practical making - they must met in the middle.
  • Don’t micromanage, don’t pretend to give decisions to employees
  • Use your own products
  • Don’t make a meetings about problem solving - only when you must communicate something
  • Cutting down communication to minimum
  • Fix things twice - the problem, and never happen it again

Environment & Culture

Schedules

  • Very important - without them, you will do shitty stuff, that nobody care

Design of software

  • Constant learning what they use and don't
  • Let users vote for features (like surveys)
  • Ask why they did not go with us (they resign)
  • Constant usability tests (in house, or other way)
  • Create API and customization
  • If you will have critical mass, create a marketplace
  • Missing Features Are Better Than Partial Features
  • Make people happy - Inability of control things - makes people not try, and lack of effort, which leads to unhappiness, so people are helplessness, people must feel that they can easily get what they want, software shouldn’t interrupt this process. Put the user in control. Give them feedback. Don’t hide things beyond their reach!
  • Obsess over aestetics - you can decorate in some way
  • Constant interation
  • getflow.com, mint, wufoo, stripe, trello, Intercom.io
  • Quick Course On Effective Website Copywriting
  • Why Can’t They Just…?
  • Design ui/ux

SaaS

Sales

  • Error did not try to sell the product, I've just build it
  • http://www.forentrepreneurs.com/predictable-revenue/
  • targowanie się
  • Artykuł
  • Rady
  • http://www.forentrepreneurs.com/hubspot-saas-inside-sales/
  • starać się omijać enterprise -> saas, to przyszłosc to mniej strosowej i stabilnego zysku
  • Selling to bigger companies - two lessons
  • Sales email followup
    1. zadać pytanie - do czego Ci to potrzebne? ask about family? almost not selling? talking as a human beiing. stworzyć dzięki temu więź, nie iść jako salesperson, tylko przyjaciel -> help them their need, they think, i’m consulting
  • czym więcej konkretnych pytań, odpowiedzi, konkretów, tym większa szansa sprzedaży dla tej osoby
  • kluczowe jest z kim rozmawiac, a z kim nie
  • nie: hi, im’ looking if you need xyz, tak, hello, kamil, value your time, don’t waste you time, just let you know what we do, who wer , can i sto pon thurdsay, and see as a consultant, what you are happy, unhappy with your current solution and see can we help you with that

Outsourcing

About

The knowledge base for startups.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published