Lunch Pail Daily

Today's episode is all about the benefits of getting in the arena and building even if an idea isn't a financial success. Inspired by this article.

I just finished Company of One by Paul Jarvis, a book about staying small. Jamming in this episode about ideas from the book and how they relate to Lunch Pail Labs

It's the weekly, week in review episode (here's the template I use). Discussing the wins and losses and all that jazz at Lunch Pail Labs this week (2-21/22 - 2/25/22)

A lot of success is doing the obvious thing for a long period of time but it can be hard to know when to pivot or keep going the course.

I ran into a product habit article about pivots and resonated with the approach. TLDL; You pivot when and only when you learn something significant. Jamming about that in this episode.

Had a fun conversation last Saturday with no-code 45  about getting started with no-code. There are 100s of no-code tools so it can be overwhelming to choose which tool to start with. Jamming on some no-code archetypes and tools for those (operations no-coder, pm no-coder, design no-coder, no-coder who codes)

I spent January and part of February in ship 30 for 30 cohorts. I've gotten a few questions about what I thought about writing every day and the experience in general so thought I'd share for folks who are considering joining!

I'd recommend it but make sure you really have the time for writing, exploring, and meeting others to really get the full value of the cost. 

An underrated benefit of no-code, especially for non-technical makers, is that because the investment to build is relatively lower, a micro exit can be an excellent outcome for a product. Jamming about exiting, where it might fit into the no-code services ecosystem and a few marketplaces to exit.

It's the weekly, week in review episode (here's the template I use). Discussing the wins and losses and all that jazz at Lunch Pail Labs this week (2-14/22 - 2/18/22)

I'm having more conversations with early founders on their MVPs and what they think is required. I ran into the riskiest assumption test recently, which I will help guide these conversations in the future.

More riffing on the software stack as the firm and the operational stack for Lunch Pail Labs. Here are the tools mentioned