Validation board
QuietHours
QuietHours is a focused bet on helping Senior ICs and tech leads at remote-first companies. Validate the pain fast, ship something embarrassing, and let real usage decide what to build next.
Verdict
Avoid
Pain or willingness-to-pay signals are weak. Consider a sharper niche or a different angle.
Scores
Problem & audience
Problem
Knowledge workers are constantly interrupted by Slack. This app blocks notifications during focus blocks, auto-replies with your next free slot, and shows a weekly focus report.
Target audience
Senior ICs and tech leads at remote-first companies
Value proposition
For Senior ICs and tech leads at remote-first companies who struggle with knowledge workers are constantly interrupted by slack, QuietHours is a focused tool that removes the friction in minutes, not weeks.
MVP scope
Include
- •Single landing page describing QuietHours
- •Email signup capturing interest from Senior ICs and tech leads at remote-first companies
- •One core workflow end-to-end, no edge cases
- •Manual back-office: you do the work behind the scenes
Exclude
- •User accounts beyond email
- •Payments and billing
- •Mobile app
- •Admin dashboard, analytics, settings
- •Anything that takes more than half a day to build
Customer interview questions
- Walk me through the last time you tried to knowledge workers are constantly interrupted by slack.
- You mentioned people use manually setting slack dnd today — what makes that painful?
- If a tool solved this perfectly, what would you stop paying for?
- Who else on your team is affected by this?
- On a scale of 1–10, how painful is this today — and why not lower?
- If I built this in a weekend, would you try it next week? What would make you say no?
- What would you expect to pay per month for something that just worked?
- You mentioned Slack DND — what do you dislike about it today?
- What would make you switch away from Slack DND?
- What do you pay for Slack DND (or similar tools) today?
- Which feature of Slack DND do you actually use day-to-day?
Outreach messages
Hey — building a tiny tool for Senior ICs and tech leads at remote-first companies who deal with knowledge workers are constantly interrupted by slack. Most of them currently rely on manually setting slack dnd. Not trying to replace Slack DND — looking at a narrower wedge. Not selling anything yet, just 10 min on a call to learn how you handle it today. Worth a chat?
Anyone else here senior ics and tech leads at remote-first companies and frustrated with knowledge workers are constantly interrupted by slack? Most of them currently rely on manually setting slack dnd. I'm sketching a project around it and want to make sure it actually helps beyond what Slack DND already does. What would you want it to do?
Quick favor — I'm exploring an idea called "QuietHours" for Senior ICs and tech leads at remote-first companies. Do you know 1–2 people who might be a fit for a 10-min chat? Happy to send them a 1-liner you can forward.
Weekend build plan
Friday night
- •Write the one-sentence promise of the product
- •Sketch the landing page hero on paper
- •Set up repo, deploy a 'hello world' to prod
Saturday
- •Build the landing page with one clear CTA
- •Wire the signup form to a list
- •Ship the core workflow — manual is fine
- •Send to 5 friends for brutal feedback
Sunday
- •Post in 2 communities where Senior ICs and tech leads at remote-first companies hang out
- •DM 10 potential users directly
- •Track signups vs visits — aim for >10% conversion
- •Decide: double down, pivot, or shelve
Risks to watch
- •Users say it's interesting but don't change behavior
- •You'll over-build before getting 5 real conversations
- •Distribution: a great MVP nobody sees is just a hobby
- •Differentiation: without a sharp wedge, Slack DND will out-execute you.
Informational use only. Not professional advice. The author is solely responsible for the submitted idea and related content.
This is a public read-only view of a QVVB board.