Download to read offline
Uploaded byPer Fragemann
Update q2 2014
The document provides a summary of the company's performance in Q2 and plans for the future. It states that in Q2, the company collected $193k in revenue from 145 paying customers, up from $65k and 32 customers in the previous quarter. The company's current plan is to generate $2.5m for 2014 but they are off track from that goal. In the longer term, the company aims to improve its product, grow organically by hiring great new employees, and help customers improve through a people-focused approach and continuous small improvements.
More Related Content
Update q2 2014
- 1. Q2 Update Stuff wedid in April to June
- 2. Customers vs Revenue 0 $ 125.000 $ 250.000 $ 375.000 $ 500.000 $ 0 100 200 300 400 QuarterQ4 ‘11 Q1 ’12 Q2 ’12 Q3 ’12 Q4 ’12 Q1 ‘13 Q2 ’13 Q3’13 Q4’13 Q1’14 Q2’14 Revenue collected 8k 22k 65k 40k 72k 140k 193k 257k 283k 320k 402k Active paying customers 7 19 32 50 73 111 145 195 230 285 350 ~90% of our customers pay for one year upfront We only track revenue that actually showed up in our bank account
- 3.
- 4. Financial outlook • Collected$105k in July already (very good) • $160k in outstanding invoices (this is a lot!) • Current 52-week window: $1.3m • Total revenue year-to-date: $820k • Current plan for 2014: $2.5m — uh, totally off track
- 5. Features shipped • RewroteJIRA and Confluence integrations • Rewrote Google Integration • Reporting for review- and 360 overviews • Usability improvements across the board • Unfortunately, that’s about it. :( Lots of support- related features, bugfixes, performance tuning.
- 6. Longer term plans SmallImprovements 2014/2015
- 7.
- 8. Overarching goal: Joy •Great people we enjoy working with • Great product that we can be proud of • Great customers for whom it’s a pleasure to work • Smooth processes that help us stay sane • Oh, and we need to make money
- 9.
- 10. Organic Growth • Weare hiring and planning to grow • Could be 18 people at end of 2014. 30 at EO 2015 • There was a bit of a slump recently: Hard to find great developers, the competition is stiff • But we do have the money to hire
- 11. Talent Crunch • Butwe will not lower our expectations! • It’s a complex product. Very little “easy work” • Average people will make far more mistakes • They have more questions, less great ideas, and will create unmaintainable code • They require need more process. Which is bad for everyone
- 12. Risk with hiring •I expect everyone to be great from the start • And to get even better over time • Risk: Employee may lose interest, focus or vision alignment over time • Great people may leave • Average people will stay. Forever.
- 13.
- 14. What will webuild? • Whatever is necessary to “help great companies improve” • As long as it has to do with feedback and skills
- 15. Main themes • Functionalimprovements for each module • Crosscutting: Usability, performance, scalability • Integrations: Display external data inside SI, expose our data via REST, and import users+SSO • Beyond the desktop: Mobile application, browser extension, responsive design
- 16. Roadmap: Reviews • MultipleReviewers per review • Discussion-feature for shared commenting • Angularisation so we can make it much more interactive
- 17. Roadmap: Objectives • Overviewscreen • Objective alignment • OKRs • Improved team view • Assign people to cycles • Chronological view
- 18. Roadmap 360s • Ratingsinto Production • Nominate yourself • Allow managers to run the process for their own team • Improved notifications
- 19. Roadmap Messages • Totalrewrite because it has become unmaintainable. Make sortable, searchable etc • More focused on core usecases like note-taking, 1:1 preparations, kudos • split out discussing reviews and 360s and objectives into a similar but different module
- 20. Integrations • Features: Salesforce,Freshdesk, Freshbooks, GitHub, • SSO: Okta, Centrify, etc • Usermanagement: Workday, TribeHR, etc
- 21. Mobile • Ship firstdraft of iOS application, use it ourselves • Then build the more advanced features: Update objectives, trigger reminders, see basic statistics • Start looking for Android developer in Q4
- 22. Usability • Visual cycleoverview • Timeline view for the profile/dashboard • Tutorial mode • General navigation improvements
- 23. Ok, but inwhat order? • It depends! Seriously, there is no master plan • Customer agendas change. What’s important today might be useless tomorrow • Our capabilities change! Front-end dev leaves, Backend developer joins: Suddenly the roadmap ordering changes too • We are opportunistic!
- 24. Planning-considerations • Is afeature/improvement easy to build? • Is it (going to be) used a lot? • Does it complement/complete an existing feature? • Do we have someone to build it? • Does it help with usability? • Does it make us prettier?
- 25. Short term roadmap •Objectives overview • Release notes • Security • Landing page • Overview screens, bring 2D-Chart “home” • Timeline view
- 26.
- 27. US company • Stillin the process of setting up US service company • Will allow us to employ people full time • When we look for new staff in Q4, consider renting office
- 28. Berlin office • Wewill start looking for a new office once we hit 8-9 employees being in on average. Should be around November. • We are looking at immoscout etc every now and then to get a good overview. But most offices are soooo ugly it makes me want to cry
- 29.