Building in public is useful even when nobody is following you. Documenting what you tried, what went wrong and what comes next creates a record that others can learn from. We put together a simple guide to writing better public updates. 3f.vc/article/how-to-write-a…

Most early founders don't have impressive numbers to share. That's fine. A failed experiment, a wrong assumption or an unexpected learning can make for a useful public update. Here's how to write one that people can actually learn from. 3f.vc/article/how-to-write-a…

You don't need users or impressive numbers to write a public update worth reading. Your mistakes, failed experiments and what you learnt from them can be useful to another founder. We wrote a short guide on how to make your public updates worth reading. 3f.vc/article/how-to-write-a…

Predicting hardware failure is an ML problem. Knowing who will pay to prevent it is a startup problem. We explore the difference: 3f.vc/article/predicting-har…

intercom’s 2011 seed deck is 8 slides long and there’s no financial model anywhere in it. half the deck is just “here’s what this thing does.” they raised $600k on it. We went through the whole thing here: 3f.vc/article/why-intercoms-…

Want to improve your pitch deck? We've added real startup pitch decks to Entrepreneur Eklavya, each broken down slide by slide to explain what works and why, with links to the original slides. Study the thinking behind decks that raised money, then apply it to yours. entrepreneur.eklavya.io 3f.vc/article/how-to-improve…

Want to know why Dropbox’s 2007 deck worked? Ask for a slide-by-slide breakdown, then click any cited slide and the real deck opens right on it. Answers you can actually check.