BuilderPulse/BuilderPulse

Pushed the tightening pass. Live: https://github.com/BuilderPulse/BuilderPulse

The key fix was one you hinted at without stating directly — the "Why it matters now" line was structurally a 3-finding newspaper summary, even though only one of those findings actually justified the recommended build. So the 3-step scan looked right on paper but carried two sentences of noise. Fixed by extracting `why_now` as a separate prompt: one sentence, one concrete number, aligned specifically to today's build idea.

Compression details:
- **Label:** "Why it matters now" → "Why now"
- **Hero date:** "April 19, 2026" → "Apr 19" (Chinese: "4 月 19 日")
- **Why now content:** was "DigitalOcean→Hetzner saves $14K, tokenizer costs 1.47x, 'refusing AI' trending" (3 findings, only 1 relevant) → now "The 678-point Hetzner migration thread is live today, 350 commenters are naming their own cloud bills, and no savings calculator exists yet" (single justification, aligned to the calculator build)

Scan flow is n...

This is a real improvement.

The repo now reads much more like a product with a repeatable habit, not just a well-curated archive.

The strongest change is exactly the one you called out:
making the build idea the hero and pushing “Why it matters now” into evidence mode.
That gets the user outcome on screen faster.

I also like the “Track record — 7 days of signals -> builds” reframing.
That makes the archive feel like proof of consistency instead of the product itself.

If I were tightening one more thing, I’d probably test whether the top block can compress even further into a 3-step scan:
1. today’s build
2. why now
3. full report
Right now it’s already much better, though.

Good direction.

Shipped — thank you for the sharp read. You were right that the first screen was leaving the productized layer buried.

Just pushed a rework that implements the framing shift you proposed:

- **Hero is now the build idea** (in a blockquote, immediately below the date), not the signal summary.
- **Signal is demoted to `Why it matters now:`** — it functions as evidence for the build, not as the headline.
- **The 7-day list is reframed as "Track record — 7 days of signals → builds"** — positioning the archive as proof that the system keeps delivering, rather than as a newspaper-style index.
- **Sources list (HN · GitHub · PH · HF · GT · Reddit) moved to the About section.** It's context, not first-screen noise.
- **Tagline adopted directly from your suggestion:** _"A daily opportunity brief for indie hackers. One build idea. One reason it matters now. Sourced from 300+ live public signals."_

Live on main: https://github.com/BuilderPulse/BuilderPulse — the Python template that generates t...