Opportunity area · theme founders discuss · intermediate

Community opportunity: wearing heart outside chest

Discussion · Wearing heart outside chest. Community signal ≠ product. Extract the recurring job, ignore the loudest anecdote, then narrow. Industry pocket: hrtech. Original insight: community volume predicts attention, not willingness to pay—price a tiny pilot early.

Problem

In hrtech, the default stack almost works—until “wearing heart outside chest” forces spreadsheet archaeology and Slack archaeology at the worst moment. Unexpected challenge: pulling clean context out of the buyer’s existing tools takes longer than the first UI. Hidden cost: QA/evaluation if any step is model-assisted—one bad output can kill the account.

Target user

solo founders in hrtech who feel “wearing heart outside chest” as a weekly tax

Proposed solution

Ship the smallest artifact that makes solo founders finish the job faster with fewer errors—next to the system of record they already open. Discussion rule: quote buyers in their words on the landing page; delete founder poetry. Counter-intuitive advice: shrink the ICP until it feels almost too small. Breadth is how clones are born. Distribution bottleneck: marketplaces and app directories tax you twice—once in fees, once in attention. One caution: avoid “platform” language in year one. Platforms are earned after a wedge works. One recommendation: pick one channel and work it daily for thirty days—one channel done beats four channels imagined. Practical next step: list three current workarounds and price between free and the most expensive workaround. Real-world pattern: Stripe won by removing friction on a job merchants already had—copy the posture, not the category. Straight take: green-light only if you already have access to solo founders or a scar that makes “wearing heart outside chest” personal. Cold pure-tech starts in noisy hrtech categories are a grind.