1. Legend
1.1. Nodes are drag and drop, place them anywhere you like
1.2. Use the + and - icons to expand/collapse nodes
1.3. Hover over the circle with lines to read attached notes
1.4. The forward pointing arrow indicates a link associated with the node
2. Where?
2.1. Where will Schnitzelconf be held? In a nasty 1980s hotel ballroom? NO! In a sea of fusty faux red velour that's been crushed by 5 decades of butts in suits? No! Behind the lion, up the stairs… Yes, we're holding our conference in Vienna's incredible Museum of Natural History! It's the center of everything, and so easy to get to, with scenery that can't be beat. And, by the way, we'll have the museum to ourselves. We'll have snacks and lunch in this very (gorgeous) lobby, and the gorgeous staircases and scenery will be ours to look upon while we munch, chat, query, and connect. It's gonna rule!
3. What?
3.1. You'll meet and learn from the founders of successful bootstrapped businesses—including Software as a Service, downloadable software, and digital goods. Hard-won knowledge will be shared. Fun will be had. Wine will be drunk. Inspiration will be sparked.
4. When?
4.1. SchnitzelConf is a 1-day, full-contact conference in Vienna, Austria on September 7. The focus: creating products, launching businesses, and charging real money.
5. Panel Discussion 3 Growth
5.1. Geoffrey Grosenbach Seattle, WA
5.2. Tobias Lütke Ottawa, ON
5.2.1. We tried every software on the market
5.2.1.1. customers that use the software, really like it
5.2.2. Communicating vision
5.2.2.1. develop a strong distortion of reality
5.2.2.2. you can't really plan for more than 6 months in advance, anything else is guessing.
5.2.3. I did all the customer support for the first few years
5.2.3.1. built out a team of Shopify guru's
5.2.3.2. mitigating support
5.2.3.3. you learn about opportunities for you business by listening to your customers.
5.2.4. Think big
5.2.4.1. startup put up a contest award of $100k
5.2.4.1.1. massive success
5.2.4.1.2. ROI achieved before contest was over
5.3. Peldi Guilizzoni Bologna, IT
5.3.1. We're not that big that we have conflicting visions
5.3.1.1. hired people I was in sync with
5.3.1.2. the vision is still the name
5.3.1.2.1. a little too much still in my head
5.3.1.2.2. based on customer feedback
5.3.1.2.3. a give and take between what I want to do, and what people want to do with the ap.
5.3.2. It's stayed the same.
5.3.2.1. building tutorials
5.3.2.2. I'm a bit slower replying than i would like
5.3.3. Team building
5.3.3.1. outcome was far better than I could have imagined.
5.3.3.2. we became a single unit
5.4. Adii Rockstar Capetown, SA
5.4.1. Allow people to make better websites - cheaper
5.4.1.1. listen to the customers
5.4.1.2. Semi-doing what they want
5.4.1.3. Learned to slow down a little
5.4.1.3.1. keep the team small
5.4.1.3.2. woo on the slopes
5.4.2. If we have to add someone to the team to achieve goals, then yes - larger is better
5.4.2.1. if that means 100 people working on the team
5.4.2.1.1. as long as it doesn't compromise my lifestyle, then by all means...
5.4.3. I've become more obsessed with email
5.4.3.1. as long as we can get to a specific user ASAP, things are still fine
5.4.3.2. start email at the top
5.4.3.2.1. answering an email quickly is a win
5.4.3.2.2. the guy who sent an email 12 hours ago, won't mind waiting another 2 hrs.
5.4.3.3. Read "Delivering Happiness"
5.4.4. Don't try and be something that you're not
5.4.4.1. embrace the difference
5.5. Tom Preston-Werner San Francisco, CA
5.5.1. The company becomes the compelling idea
5.5.1.1. We sit in campfire alot
5.5.1.1.1. we talk so much, that the vision becomes shared.
5.5.2. Not yet decided
5.5.2.1. but we shouldn't have to in the beginning
5.5.2.2. we believe that everyone who uses the product will be better off for it
5.5.2.3. It's good to be restrained in hiring
5.5.2.3.1. we will wait until 4 months after we need someone until we hire them
5.5.2.3.2. someone that is going to be idle is toxic to a company
5.5.2.4. you shouldn't have to decide immediately
5.5.3. It's absolutely changed
5.5.3.1. early days, Tom and Chris would handle support
5.5.3.1.1. a tidal wave of unclosed tickets.
5.5.3.2. hired a full time support person to handle Tender
5.5.3.2.1. employee#2 - 5th team member
5.5.3.3. fast response time is key
5.5.3.3.1. twitter
5.5.4. Team
5.5.4.1. you spend so much time with these people, if you can foster an environment that's fun and productive, you've won.
5.5.4.2. Don't be afraid to say you're small
5.5.4.3. You're in a position to provide individual attention and support
5.5.5. Take your weaknesses and turn them into selling points
5.5.5.1. we're only 2 people, and that makes us special
5.5.5.2. we're from this obscure place, that makes us special
5.5.6. Don't forget the global market
5.5.6.1. don't forget about the rest of the world outside your homeland/continent
5.6. Questions
5.6.1. As size grows, how have you kept your vision alive?
5.6.2. How large do you want to grow?
5.6.3. What's changed in regards to your customer interaction since your product has become popular?