MindsetBe prolific, because a large body of small tools compounds
An OG indie hacker building tools that make you happy
Octavian has shipped more than two hundred projects, most of them small tools, since before anyone in Romania called this indie hacking. That volume is not noise, it is the strategy. Every finished tool sharpens your taste, widens the surface area where luck can land, and leaves behind an audience and a reputation that a single big bet never accumulates. Indie hackers tend to over-invest in one idea and agonize over whether it is the one, while the prolific builder simply ships the next thing and lets the portfolio do the arguing. You cannot predict which small tool finds its people, so the rational move is to keep the cadence high and let quantity manufacture both the quality and the lucky breaks. Longevity in this game looks less like one masterpiece and more like a long, unbroken streak of finished things.
Related advice
Octavian ChișTurn fuzzy intent into structured cards a machine can match
A conversation about what everyone is building evaporates the moment the room empties out. Intersect keeps it by asking each person to file their intent as typed cards: what they are working on, what they need, what they can offer, what they are questioning, what they are thinking about, and what they have discovered. Once intent has a fixed shape instead of being buried in chat, software can do the introductions a busy human never gets to: cluster the projects, find the topics two people share, and pair a need on one side with an offer on the other. The general lesson is that matching people is only hard while the inputs are unstructured prose, so give the same information a small, fixed schema and the overlaps compute themselves. The next time you reach for a feed, ask instead what the handful of card types are, because typed intent is the thing a machine can actually act on.
Octavian ChișA needs-and-offers network is worthless until it is dense
Octavian named Intersect's real constraint without flinching: it is not a missing feature, it is a missing crowd. An intent graph only surfaces a useful intersection when enough people have added enough cards, so with a handful of users the cleverest matching engine finds almost nothing. This is the cold-start tax every marketplace and matching product pays, invisible in a seeded demo and brutal in the wild. The takeaway for anyone building two-sided or network-effect software is that the first job is density, not polish: seed the graph yourself, recruit the first cohort by hand, and only judge the product once it is full enough to fire. Until it is dense, the thing you are testing is not your algorithm, it is your ability to fill it.
Andrei StatescuKnow whether you are a starter, and stop designing companies for a finisher
Andrei's resume looks fragmented, Java to C# to Ruby on Rails, four years teaching at the Politehnica, an abandoned PhD, an outsourcing firm, a fantasy novel, until you apply his own reframe: he is a starter, energized by taking projects from zero to first results and drained by the long steady middle. Instead of fighting that, he now designs for it, picking products that can reach a self-sustaining state quickly and planning early for automation and helpers to carry the marathon stretch. The standard startup script quietly assumes a finisher, someone who wants to run the same company for fifteen years, and a starter who signs up for that script abandons it at year two and calls himself undisciplined. Temperament is an input to company design just like market size. Figure out which kind of founder you are from the evidence of your own history, then choose the product shape, exit points, and delegation plan that fit the person who will actually be running it.
BogdanScope a side project to fit the life you already have
Bogdan has a consulting career and two kids, so he deliberately scoped Event Newsletter to something he could run in the gaps rather than something that demands his full attention. The trick is to choose the product around your real available time, not around an imagined version of yourself with empty evenings. A tightly-scoped tool with a narrow job survives the busy weeks that would kill a more ambitious build. For a dabbler, the right size of project is the one that still gets shipped when life gets loud.
Extracted from
Indie TM #11: An Intent Graph and the Hunt for Users