12
22 Comments

My Startup failed, what next? What do I do with my code?

Hey everyone.

I built this project over the last 2 and a half years
about.parstar. co (indiehackers is not letting me post the link, so just copy and paste it into search and you should find it)

It is a ed-tech SaaS platform aimed to make participation in large lectures easier and more enjoyable.

After a good period of development, my cofounders and I went to market with cold emails. We had a couple users but really struggled to get people to try or use the product. Plus we are still in college and juggling the startup with school was difficult. We have ultimately given up, assuming we did not find product market fit/did not solve the problem correctly.

We have an awesome code base with tons of features and I'd hate to see it go to waste. I have been thinking about open sourcing the entire project, but I feel that I should still consider what would be the best way to go about that.

If you'd like to explore a demo of the app, here is a demo account:
lnegritto@scu.edu
demo123

Any suggestions would be extremely appreciated! Thanks

on May 6, 2020
  1. 9

    I'll be honest about what I think: treat your code poorly. Take what's reusable in future projects, and scrap the rest.

    Sunk cost fallacy is a powerful thing, and we need to stop glorifying codebases: the sooner you do this, the less attached you become to it - hence the less time you waste in aggregate chasing things that don't work.

    Sure, there was time wasted... but that's just part of the risk. Awesome or not, just dump it.

    (as a side note, things like this are actually a good reason to build with modularity and reusability in mind...)

    1. 2

      I read 'Sunk cost fallacy' and the first thing that popped into my mind was "Damn Sergio's advice is propagating well" before I realised it actually was you. Great advice though

    2. 2

      Yep! This is the answer. As developers we typically think our code base is worth thousands of dollars. Which is some what true, because at work our hourly rate is anywhere from $50-$100 an hour. But just because we put a ton of time into something doesn't mean the code is valuable.

      Scrap it, move on, if you need a piece you can always copy and paste.

    3. 1

      Aha don't you worry ;)
      I have boilerplate for auth, password reset, email confirmation, chat features, the overall layout of the UI, etc.
      I don't necessarily believe the codebase is super incredible.. I have just reaped so much benefit from open source projects in the past that I would enjoy giving back to the community in the same way.

  2. 4

    please can you try another market before totally quitting. The world is big you know, there are many students in Africa or South america that can use this.

  3. 3

    I'm in college and I went through a similar ride. I didn't solve the problem well enough for people to WANT it, so I had to (sadly) get rid of it. Fortunately for me, it was only around 2.5 months before I decided to end it (thanks to @sergiomattei for the advice).

    About your code, I think you should salvage and store some boilerplate code, some tests and some features that were really tough to build.

  4. 1

    As someone from the education industry (worked for a middle school as a teacher, now in admissions), I thin many of my current and previous coworkers would say 'i don't have time for this'. Alot to say about that but at the end of the day, it seems you'd be spending alot of time teaching educators also how to use it. Most educators don't use that much technology that I know of and get overwhelmed easily with multiple tools. One of your first phrases is 'slack for the classroom' on the homepage but that's not relatable for those in the education world (I've been trying to move my internal communications to slack but people are scared lol). As I went deeper into your product, it has alot to offer. So I think that's a good thing! Happy to chat more. I love what you are doing.

    1. 1

      Interesting insight. I appreciate the comment!

  5. 1

    Quick question, sorry if not so pertinent - why are you unable to post the link? Curious because IH seems to be quite permissive about shilling in general.

    1. 2

      a new account can not post links. You need to contribute first to the community and earn some points before you can post a link as far as I remember. I maybe wrong.

      1. 2

        Thanks, good to know.

        Do you know if there are other "features" we can "unlock" on IH?

  6. 1

    Worst case opensource part of it and see the interest.. Out a note if anyone wants to improvements or customization,... they can contact you..

    This is the business modal for some of the big opensource projects like
    Apache Ofbiz, I forget the name of a opensource lab scheduler... (Their core team hourly rate is in hundreds of $$).

  7. 1

    You could try and sell it, I had the same issue and sold it on 1kprojects.com. I didn't think anyone would want a dead app with no customers but it did sell!

  8. 1

    This looks good, especially for work from home. Have you thought about targeting private tutors? They often have bigger budgets and I can see how online classes can help them grow their business.

  9. 1

    Take a day without any electronic devices and spend a day writing about what you learnt in the last 2,5 years. I had a startup for 2 years as well that failed but I have learnt so much from. For example, I did not enjoy the sector/branch. So now I choose something where I get energy from :)

  10. 1

    I tried edtech, it's a really hard business. First thing you did wrong is build something before talking to teachers/students. When you build a product for schools (or any enterprise) you want to build it together with them. Because there are so many edge cases you will miss otherwise.

    I don't know what value you add? My wife is a teacher and they are using microsoft teams for chatting/groups etc. So that space is pretty much taken by MS at this point.

    If you want to succeed in edtech pick on single thing and make that perfect, take a look at kahoot for example. They do one thing and it's free to start and teachers can use it without any approval from higher ups! This is important because sales cycles can be 2+ years (no kidding).

    If you want to continue with this there are a few things I would focus on:

    • Specific education features like live Q&A, teachers ask a questions students fill it in the app.

    • Streamlined classroom sign in (you are selling to teachers for now, make it easy)

    • iOS/Android apps (don't forget tablets, they are populair right now)

    • Figure out an unique edge that no one has, saves teachers a lot of time and is simple.

    1. 1

      We spoke with a lot of professors and students while building the app. I believe where we went wrong was the method of doing so. We asked questions like, "if this was a feature, would you use it?" Instead we should have focused on hearing their problems and brainstorming ideas after.
      We have a Q&A feature, polling, and special features for moderating a classroom env. Never though MS Teams would end up being our competitor though. Def extremely hard to compete because they have features like file sharing and video calls..
      It is built in Vue.js so I could port it into a mobile app. It is very responsive. Thanks for the advice :)

  11. 1

    Sounds like you built the product, but did not receive or find much feedback.

    My opinion is this: take a break if you need, then come back and start talking to people teachers, schools and other students.

    Find out what didn't work and why. Try understand what it would take to convince them to use the product. It may be a total shift, or maybe not.

    Once you do that, evaluate whether it's worth giving it another shot. Feedback will tell you that.

  12. 1

    Your project seems nice with good features. I would suggest you create an actual android/ios app and go with the mobile approach. I am seeing a lot of ed-tech startups be more successful when going with mobile app.

  13. 1

    This comment was deleted 6 years ago

    1. 1

      Thanks for the advice :)