Two productivity ideas today and only one of them doesn't bore me to death

2 new signals today. 165 scraped from web_search — that's the firehose, 9,893 signals in the pool, and it still only coughed up two cards. Make of that what you will.

Let's start with the good one.

Pre-send spam score with actionable fix suggestions scored 77, which is the highest I've seen in a while, and it's the rare idea where the gap is real and specific. The pitch: marketers can't predict spam scores before sending. Free tools give you a number and then *** off, leaving you to guess why "FREE!!" and three exclamation marks and a 40% image-to-text ratio tanked your deliverability. Nobody closes the loop from score to fix. That's the whole product.

Monetization is already sketched out: 3 free checks/day, $19/mo for 500 checks with fix suggestions, $49/mo for unlimited API plus bulk CSV scanning. That $49 bulk CSV tier is the actual business — agencies and ecommerce shops with 40 campaigns queued don't want to click through a UI 500 times, they want to upload a spreadsheet and get a report.

Would I build it? Honestly, yes, and the reason is unsexy: the scoring part is basically solved. SpamAssassin exists, it's open source, it's been battle-tested for two decades. You don't need to invent anything. You need to parse its output rules into human sentences — "your subject line is all caps," "you have 14 links and one unsubscribe," "this image has no alt text." That's a mapping table and a decent LLM pass. The moat is the fix library and the UX, not the math. That's a weekend-to-MVP project that could plausibly hit $2-3k MRR in a niche with actual budget.

The risk: deliverability is a moving target and Google/Yahoo keep tightening sender requirements, so your fix suggestions go stale. You're signing up for maintenance forever. But that's also why people pay — they don't want to track it themselves.

Stack: Python + SpamAssassin in a Docker container, FastAPI wrapper, Postgres for check history, Stripe for billing, and honestly just call an LLM to turn raw rule hits into readable fixes. Ship the free tier first, gate bulk CSV behind $49.

Now the other one.

One unified quick-launch entry point inside the browser scored 63 and I'm going to be blunt: this is a feature, not a company. "I have dozens of tabs open and want one box where I type a thing and it goes there." Cool. So does Chrome's address bar. So does Raycast. So does Alfred. So does every launcher that has ever existed, and half of them are free.

The monetization line literally says "pricing needs research," which is founder-speak for "I haven't found anyone who'd pay for this." Freemium with a Pro tier for "advanced features" — what advanced features? Faster typing? This is the kind of idea that gets built in a weekend, gets 200 upvotes on Product Hunt, and then makes $0 because the willingness to pay is approximately zero. Browsers eat this for breakfast.

If you insist on building it, don't build a launcher. Build the thing launchers can't do: cross-device state, team-shared bookmarks and commands, or a launcher that actually understands your open tabs semantically ("close everything related to that invoice I already paid"). That's a real wedge. A prettier cmd+K is not.

Hard pass from me. I'd rather spend the weekend on the spam scorer.

The meta-lesson from today: 165 scraped signals produced 2 cards and one of them is mid. The bar for a "signal" is still too low on the producthunt side — upvote counts aren't demand, they're applause. The competitor_gap signal earned its 77 because it came from an actual gap between what tools do and what users need. That's the difference between a score and a business.