Show HN: How to Shut Down a Venture Backed Startup [pdf]
After shutting down my own venture-backed startups a few years ago (and since helping dozens of startups do the same) I put together a comprehensive guide on how to go about it.
After shutting down my own venture-backed startups a few years ago (and since helping dozens of startups do the same) I put together a comprehensive guide on how to go about it.
It is a fairly brutal process - especially for people who've never gone through it before (which is most founders). So many steps involved and traps to fall into. Botched one thing for my own dissolution (and I paid a lawyer thousands of dollars to help) and had to pay out of pocket a year later :(
Really appreciate the kind words though - thanks for responding and taking a read
I went through YC in 2018. I had visions of running a trillion-dollar startup and surfing with Zuck into the sunset.Over 4 years, I had built 2 startups. We sold one but had to shut down the other.After finally calling it quits, I was burnt out. All I wanted was a clean break, but instead, what I got was a metric ton of the world’s worst chores.It was the never-ending long tail of dissolution....
And totally feel ya there re: Github. We personally use Linear for tasks other than just product dev but totally understand the draw for wanting to combine version control with tasks.
It's amazing how helpful keyboard shortcuts and just raw performance is when you're using a tool as frequently as one does with PM.
Wondering how you have/are managing to do it?
Thanks so much for reading it and I've definitely been getting things sorted out. Best of luck to you as well!!!
Love the idea of upvoting edits. Will definitely test that out more :)
We've seen freelancers and agencies record feedback themselves while on the phone with their clients but appreciate your honesty - super helpful for us.
2) Agree with this as well. Trying to think of ways to make this work for multiple personas.
3) Another great point. Red highlight box means you have either selected that element or someone has made an edit to that element.
4) Love the ideas in that paragraph. We're thinking about removing the screenshot and bringing more of that functionality into just one screen to reduce cognitive load. We'll be playing with this in the next coming days so would love to hear what you think then!
And yep that's how it used to be designed. We recently changed it because our users (and us internally lol) we're having difficulty making sense of the page when there was so much going on. Will definitely keep that in mind though and maybe make it optional if you want the comments to show on the right-side!
We've been thinking about having an "advanced" toggle which would hide the "developer focused" inspector and just leave a comment field. Wondering if you have thoughts on how we could do this better??
4. Ohhh I see. Yea that's an awesome idea. Basically showing a diff between different design decisions? We'll definitely play around with that and see what we can do!
2. We're currently working on adding the ability to edit just one element or all that are associated with that class. Should be live in a few days!
3. Yes and yes. We're super interested in this idea as well. We've been testing out showing all the style elements in use on any given page ( i.e. on this page you're using these 5 grays, 4 type styles etc.). With that information, we can allow users to "add" those elements to their saved styles and see if something on the page doesn't match. For instance, the red we use is #C8080A but I can now see that in these 8 places we're using a red that doesn't match. Would love to hear your thoughts around this!
4. There is actually a "History" tab located on the side-panel where you can view the changes made to that page over time. Let me know if that's what you meant and how we could improve the visibility/usability of that!
Would love to hear how you'd envision editing the HTML? Wondering what types of edits you're currently making to the HTML via the console?
Just added that to our backlog :) Wondering how you envision those changes within Toybox being displayed/integrated in Asana?