17
14 Comments

Lessons learned from YC Startup School

Slowly but surely we are launching Pikaly.com and we would like to share how YC Startup School helped us with that.

The idea
We experienced that collecting photos from a group of people via Messenger, email or any other app is hard and we want to fix that. When people aren't together in a certain ecosystem (google, apple, dropbox) or network (whatsapp, facebook) for many it is too much trouble to create a new account and share photos. That is why Pikaly is designed to make it incredibly easy and fun to collect high-quality photos. Read more on our Medium story.

From Kevin Hale's talk (How to Evaluate Startup Ideas) we concluded that using the factors Founders, Market, Product, Acquisition, Monopoly we should build a 10X product to succeed. The MVP is not 10X yet, but doing research with this competitive analysis sheet made us confident that there is an opportunity in the market.

Validating the problem
We held a lot of unstructured interviews before Startup School, but started to use the format suggested by Eric Migicovsky (How to talk to users). We created this sheet for it and will continue to interview users while we are testing the MVP.

Building an MVP
Michael Seibel explained in his video (How to plan an MVP) the importance of building an MVP and launching quickly. Since we had ambitious plans it was hard to take a lot of pretty essential features out, like saving collections into your account and receiving notifications for new photos. So we hope that the current MVP can already bring enough value 😬.

Launching
Next up is launching. The video of Kat (How to launch again and again) helped us to decide to launch to friends and family first, then to other founders like you, and then other communities will follow. We found this great list of communities to get visibility for startups and were inspired to find our niche from this article.

Startup School really helped us getting the first product out. Make sure you check out more content from Startup School. We are curious to hear your feedback on our work so far and are happy to answer any questions.

This is how we want to grow into an actual business:
🆓 A freemium consumer product to collect photos in the easiest way possible
💰 Allow businesses to make use of a consumer-grade product to collect, curate and reward photos from consumers and with that cover the costs for freemium users
🔗 Integrate within the websites of businesses to collect and display collected photos to increase usage and stickiness
🚀Become the most awesome and biggest photo exchange service

Our current product backlog:

  • Creating an account to manage collections/albums
  • Receive notifications when photos are uploaded
  • Sync photos with clouds (Dropbox, Google photos, iCloud)
  • An app to easily sync photos locally
  • Embedcode and public API to collect photos from your website
on October 27, 2019
  1. 2

    Thanks for your feedback, I also used it to update the article with it. As Pikaly is a side project I didn’t have time yet to thoroughly follow up 😊Happy to see that you liked the content from YC and the sheets we used. It inspired me to start working on another version, where I combined multiple sheets into one and added a dashboard to track progress. I will publish that on IH soon.

    Also thanks for looking critically at Pikaly. We can clearly improve in explaining how we differentiate from other photo apps like Google photos. The specific problem we found is in sharing and collecting photos from big groups. E.g. not everybody is always in the same Whatsapp group (and you probably don’t want that) and people are using different cloud tools and they don’t want to signup for another new one. Also, most apps are not meant for collecting photos, do you know how to collect photos with Google photos for example...? We believe that nobody is solving the problem of collecting photos well, so while competitors focus on sharing and storage, we can offer a great complementary product for collecting. Read more on our Medium story.

    This is how we want to grow into an actual business:
    🆓 A freemium consumer product to collect photos in the easiest way possible
    💰 Allow businesses to make use of a consumer-grade product to collect, curate and reward photos from consumers and with that cover the costs for freemium users
    🔗 Integrate within the websites of businesses to collect and display collected photos to increase usage and stickiness
    🚀Become the most awesome and biggest photo exchange service

    In terms of features on our backlog:

    • Creating an account to manage collections*
    • Receive notifications when photos are uploaded
    • Sync photos with clouds (Dropbox, Google photos, iCloud)
    • An app to easily sync photos locally
    • Embedcode and public API to collect photos from your website
    1. 1

      you can add this part to your article as well :)

  2. 2

    Thanks for sharing.

    Here are some questions that will hopefully help you:

    ---

    [1] Landing Page

    What's your plan for your landing page?

    As it is now -- if I clicked on your link, I would exit out immediately.

    Your "for weddings" and "for events" pages have some content that could be used to create landing pages specifically for those types of events.

    ---

    [2] How did you get candidates for your user interviews? Are they actually people who have this problem? Would they actually pay for an app to do this?

    If they aren't using a specific tool now, why would they use yours? Do they have enough of a pain to go searching for your app? How will you market to people who have this pain?

    ---

    [3] Strategy

    How did you come up with these factors and ratings?

    i.e. I would ask yourself -- is ease of registration really a winning part of your strategy? Also your ratings are a little odd -- i.e. what's app being a 3 for ease of registration?

    ---

    [4] What is your pricing plan? How will you develop your marketing channels at that price point? What type of conversions would you need to make that feasible?

    ---

    1. 2

      Great questions, definitely food for more thought.

      [1] Landing Page
      The idea is to make it as easy as possible to directly start collecting photos, that is why we thought it was cool to only have one button to create a photo collection (album). I can see that this can be strange without context. Good feedback to improve our landing page with.

      [2] We got a decent number of candidates from our network and from the 'makers' community. That confirmed that a solution for collecting photos for events like weddings and meetups would be useful. We didn't ask them if they wanted to pay for this since we want to build premium features for businesses later on. But we maybe should have done that already. Any tips on how to ask this and how to get more candidates?

      [3] Strategy
      I can see that we maybe gave a wishful rating on some items. The most important problem we discovered is that in case you are not together in a certain ecosystem (google, apple, dropbox) or network (whatsapp, facebook) you have to sign up and/or download an app first. For many people, this is too much hassle.

      [4] This could be a tricky strategy. But the idea is to build a freemium product first and nail the solution. Then offer the same easy of use and consumer brand to business to collect photos from their consumers with premium features, the ideal customer would be Nike collecting photos from a sponsored sports event. What do you think about this strategy?

      1. 1

        [1] Landing Page

        I think this is a common issue for all of us. We're so used to our ideas and landing page, that everything makes sense, and we forget that our users likely have no idea what's going on.

        Testing with users doesn't help this, because our testers are in a sort of testing mindset, so they're going to move through the page and inspect everything.

        Having a couple of example collections beneath the fold would help me understand what the app does.

        ---

        [4] (out of order, because this comes first).

        In the Nike case, wouldn't it be easier for them to just set up a hashtag on instagram? What is your advantage over that?

        Does all of the work you're doing help you get to that advantage?

        I would focus very narrowly on the specific use case you are trying to achieve and the outcomes that those users need. My requirements for my travel photos with friends are very different from a wedding planner, which are very different from Nike.

        I.e. for Nike, their goal might be to have more customer engagement and to get more photos. So they could use something like a built-in reward system to increase engagement, or different types of gamification.

        They would want content moderation features.

        They might want a different type of output (i.e. an easy way to make a slideshow from all of the photos) that are ready for social media (i.e. formatted for facebook, instagram, snapchat), or to pull all photos from instagram with a certain hashtag.

        But would they need a way to sync photos with dropbox/google photos/etc? Probably not.

        I can understand the desire to have a consumer app to spread the word, and to think that would help you get those bigger accounts -- but I think you're building two (or more) different products, and it would be easier to just cut to the chase. Or at least verify that the final app will be sellable, first.

        ---

        [2]

        Again, I would really start by focusing on your paid customers.

        Get a few people to use the app for their events/weddings so that you have some examples you can show to future customers. Even if you can't get people to use the real app, mock up what the results would look like. Make it as real as possible, exactly like what your app would produce.

        Then, you can email some wedding planners with a sales email. See if they would pay for this; they would then either charge or offer it for free to their customers. Test your actual plan.

        Find a few events that you think would benefit from your app and try to set up a sales call; send them your examples and pricing. If you can get a sales call, that's a good sign. If they sign up, that's a great sign.

        Even getting them to use your app for free would be a win -- because there are setup costs. Maybe there's a local Nike (or ideally some smaller brands) event in your city that you could reach out to. Reach out to many, not just 1 or 2.

        ---

        [3]

        I guess I personally don't see the need from a consumer perspective, since we had this issue (sharing travel photos between friends) and we used google photos.

        Downloading it & setting it up was super easy (on iOS) and we've used that solution since.

        I can see the value in having consumers use your app, and hoping that virality brings in paid b2b accounts. I wonder if it's practical given the competition and work involved.

        Cheers & good luck.

  3. 2

    Thank you for sharing!

  4. 2

    What would make me want to use your product over, for example, a Google Photos shared album?

    1. 1

      The most important problem we discovered is that in case you are not together in a certain ecosystem (google, apple, dropbox) or network (whatsapp, facebook) you have to sign up and/or download an app first. For many people, this is too much hassle. We believe that nobody is solving the problem of collecting photos well, so while competitors focus on sharing and storage, we can offer a great complementary product for collecting. Does that make sense to you?

  5. 2

    it's a perfect story. I was also attending startup school at summer. I think it should be republished at hackernoon.com as well. tech community will love it

    1. 2

      I read articles from Hackernoon quite often. It would be cool to share our experience there as well too.But I am not so familiar with the Hackernoon community. Do you think we can use the same article? And can you publish something yourself or do you need somebody to do it for you?

      1. 1

        Yes I think you can use the same content.
        You can also put a backlink to this post. Part of Hackernoon readers are Makers like you and me - so it's a cool and inspirational story. Yes, you can publish story from your personal account - just create one at hackenoon.com and submit a story to review by editors

        1. 2

          Ok awesome, I will look into that soon. I will let you know...

  6. 2

    This comment was deleted 6 years ago

    1. 1

      Thanks for your feedback. We will work on it soon!

      Ps. did you test it on mobile or desktop. On desktop we have a copy url button, on mobile we trigger the native sharing options with the Web share API https://css-tricks.com/how-to-use-the-web-share-api/