...
- Medium - @fishman
- 2015.07.28 - Thoughts on Dishero
- "Dishero isn’t working. We have built a great team and phenomenal engineering, but failed in scaling up the business. What I learnt is selling to restaurants is an extremely painful process...The business model has been proven to be difficult to scale. (...) What’s next? Option A: Continue to iterate on the current product & sales strategies/tactics. (...) Option B: Pivot within the restaurant industry (...) Option C: Pivot outside of the restaurant industry"
- 2016.06.16 - My Cofounder Said “I love what we’re doing” And We Shut Down Our Startup
- 2016.07.16 - How to Shut Down a Startup in 36 Hours
- Call every single investor (another reason not to take 51 checks of $5K each). While it’s not always possible, ideally, do it before you inform your team. (...) Have a list of each service your team uses (...) [Deal with health insurance and Worker's Compensation insurance.] (...) If you’re shutting down before you run out of money, you should consider paying severance to the team. (...) [Use eShares to handle equity issues.] (...) [Use Gusto to handle payroll.] (...) [Deal with the government unemployment office.] (...) [Prepare the day before notifying the employees by printing out all the documents you'll need to give to your employees.] (...) [Notify the employees.]
- 2016.08.09 - Imagine Yesterday
- "You can analyze successes of others all day long, but the reality is — there are no recipes for these things."
- "before smiling will have any impact, you must have something interesting to say. (...) You may A/B test “Buy” vs. “Buy Now” on your checkout button. However, if your customers aren’t interested in your product — it won’t matter. You may optimize the size and the location of your share button. However, if you do not have shareable content — it won’t matter. On the flip side, if you do have shareable content — people will find a way to share it. Growth hacking and A/B testing are important only once you have a large user-base, where every percentage point uptick in conversion results in a significant impact. And then, only then, size and colors of the buttons start to matter. As well as timing of the push notifications. (...) Your time is better spent building a hit product, that customers use and tell their friends about."
- Main idea: Don't pre-optimize / over-engineer.
- "if you have 10 daily active users today, and your engagement grows daily by 1%, you’ll have 14,276 DAU in two years."
- Main idea: Small optimizations that lead to 1% growth per day aren't going to lead to huge numbers of users.
Success recipes: There are none. All we know is the four required ingredients:
- Hard work
- Conviction
- Patience
- A bit of luck
- "I once attended a conference where a prominent speaker explained the meteoric success of WhatsApp. He attributed it to the human psychology, yearning for communication, the intimate nature of messaging, and the timing of push notifications. The claim seems quite plausible on its face. However, here is what the speaker was forgetting in his analysis: 1) There’re scores of other messaging apps with a similar feature set, 2) SMS existed a decade beforehand, 3) On the day WhatsApp was just born, we all were already sending billions of intimate SMS messages every single day. It was painful to see him reducing WhatsApp to a red notification indicator. The speaker then explained how infinite scroll, with its easiness and addictiveness, was instrumental to Facebook and Instagram’s successes. Again, such a gross oversimplification of these services."
- "I’m not saying album covers or packaging aren’t important or easy to design. Nor I am saying that studying others’ work isn’t inspiring or necessarily a waste of time. My main point is — none of it will actually help you to compose a timeless piece. There are no recipes for that."
- 2016.08.11 - Song References
- This is just a list of song references in the "Imagine Yesterday" article.
- 2016.08.29 - A Post About Post-Post-Mortem
- 2016.08.31 - How NOT to Raise Money
- 2016.09.01 - Raising Money — Where to Start?
- "I’d like to share a framework that had helped me to raise the funds for a startup that we had shutdown and later restarted with the remaining capital. (...) I thought of fundraising as selling technology products to Samsung. Why? Because that’s exactly what I did in my previous life. Once I started thinking in these terms, it got a bit easier. (...) When selling to Samsung, you must first identify your champion. They must fully comprehend what you offer, so later they can sell your story internally. (...) The champion’s career is on the line here...So your product’s success and your champion’s career are somewhat aligned. (...) Once the champion is fully sold on your product, they go to their Samsung colleagues to tell your story. The champion arranges a meeting for you to present to a larger Samsung audience. (...) [Check out] "The Selling Fox: A Field Guide for Dynamic Sales Performance. (...) Once you’re done presenting, you leave the room. The champion stays there and continues to advocate your product to their Samsung colleagues on your behalf. (...) If you did your homework and armed the champion with all the necessary tools, they will help you to seal the deal."
- This one was pretty helpful.
- 2013.09.13 - Camera-Killing Smartphones And Their Killer Cameras
- "[M]obile phones’ cameras are making giant technological leaps. (...) I worked in the digital camera industry for 16 years...[T]he industry was fine up until 2012, where it collapsed in one year and never recovered. As predicted. (...) What killed the digital camera industry was...Instagram. Or more accurately, the insta part. (...) Cameras could not deliver you likes and comments within minutes of you taking the shot. Customers traded image quality for instant feedback. (...) [S]ome companies figured out that there are certain places where you simply won’t take your phone to. These are the brilliant DropCam and GoPro."
- 2016.10.28 - The Deciding Deep Dive
- "The mobile apps at our previous venture had bugs. (...) Reporting these bugs to our dev team was often a challenge. So Dmitry and I tried to recall our typical flow. (...) What exactly did the user do to get to that particular case? What else the system was doing at the same time? The historical context was crucial in some difficult crash cases. (...) We needed an all-encompassing bug and crash reporting mechanism. It had to continuously record (and store locally) all app screens, touch events and all network traffic. This way, if a problem occurs, everything has already been recorded. So there is no need to reproduce the problematic sequence. (...) Competitive analysis showed that there are two big players in the space of crash reporting and several small players offer some subset of in-app bug reporting functionality. (...) We met with all our previous investors, showed them the demo and the deck with all the collected feedback. It took us some time to answer all their questions, but we did get their necessary commitments. (...) During the New Years break, we started to deal with the legal aspects of transitioning one company into another. (...) Perhaps the most difficult part of the restarting journey was probably lack of tangible deliverables. Throughout our entire careers, Dmitry and I used to build things. And now, for the past several months, every Friday we’d look back at the past week and what did we do? We had been only thinking, googling and excelling (Microsoft kind)…"
- 2016.11.16 - App development, bug reporting, and more in this GeekSpeak podcast with Bugsee
- 2015.07.28 - Thoughts on Dishero
...