Turn fuzzy intent into structured cards a machine can match
An OG indie hacker building tools that make you happy
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.
Related advice
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.
Be prolific, because a large body of small tools compounds
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.
Let AI curate and summarize the firehose into something personal
Event Newsletter works because AI handles the part a solo builder cannot: reading the constant flood of local events and turning it into a short, personal digest. Bogdan uses AI to find, curate, and summarize, matching events against each user's preferences so the output feels hand-picked rather than dumped. The leverage is not the AI by itself, it is pointing it at a firehose of information that a human could never process at the cadence the product needs. At Indie TM #5 the room also weighed in on which models might suit this job better, which is the kind of input he went looking for.
Serve the smaller cities the big aggregators ignore
Big event aggregators cover major cities and leave smaller ones thin or empty, and that ignored geography is the niche Bogdan is aiming Event Newsletter at. Picking the segment the incumbents skip means you are not fighting them where they are strong, you are serving people they have written off. The room at Indie TM #5 agreed this was the right wedge: a real problem that nobody handles well for smaller places. He also leans on the retro design as a cheap form of differentiation, since personality costs little and stands out when you cannot win on scale.
Extracted from
Indie TM #11: An Intent Graph and the Hunt for Users