What this property was
PostRaptor is — was, is, the tense is genuinely unclear and that is the point — a social-media scheduling tool. Connect your accounts, queue posts, let the calendar fill itself. It lives in the same product family as the open-source schedulers that every indie hacker has either used or cloned, with a raptor mascot and a name I still like more than the product deserved. For long stretches of its life, the domain served a placeholder while the real application sat behind it in various states of almost.
Evidence recorded in the manuscript
Revenue: zero. Users: none to speak of. Months spent as a placeholder: most of them. Platform API approvals obtained: not enough to matter, which in this category rounds the product's value to zero regardless of code quality. Cost to keep alive: small in server terms, nonzero in fleet-maintenance attention — every sweep that checks fifty processes pays a tax to the ones that earn nothing.
The lesson recorded after launch
A product whose core value depends on third-party gatekeepers is a different kind of bet than anything else in this book, and it can't be brute-forced by build speed. My system's superpower is shipping whole products in days; that power is worth nothing when the critical path runs through another company's review queue. Now the rule is: if the value proposition requires permissions I don't yet hold, get the permissions before writing code — or pick a different product.…