Investigación en inglés. La investigación de esta página (título, briefing, fuentes) está escrita en inglés y no se traduce automáticamente. Solo se traduce la interfaz.

Idea nuevaConsumer Utilities

Quiet Rules

One rules screen for Android: calls always loud, messages vibrate, social apps silent, everything else muted, by app and by category, with a 'why did my phone ring' log.

hace 3 semanas · Evaluada el 22 oct 2026 · ID HBV-261022-H06

Resumen

Briefing

A Reddit poster (Ideas Radar, Oct 22) wants real per-app control of notifications and sounds and has not found it; the same post ran in two Android communities. Android's per-app channel settings exist but are scattered. Existing tools found: volume managers that switch volume by foreground app (Volu, WOW Volume Manager, Audio Profiles).…

Leer el resto

None found with notification-level policy rules on one screen (limited check, not exhaustive). Mass B2C utility, global, SEO-friendly ('silence Instagram notifications but keep WhatsApp loud'). Low-confidence idea; demand evidence is one Reddit thread (post volume is demand, not proof that no product exists).

Descripción

Product: Android app that builds a single policy matrix (rows = apps and categories such as calls, messages, social, promo; columns = loud, normal, vibrate, silent, hidden) and applies it through notification-listener and channel APIs; templates for work hours, sleep, driving; 'why did it ring' log to learn rules; monthly 'noise report' shareable card.…

Leer el resto

Needs Android notification-listener permission. Global Application: any Android user. LatAm Version: Brazil/Mexico Android share is high; PT-BR/ES templates for WhatsApp groups and delivery apps.

Cliente objetivo

Android users 18-45 in Brazil, Mexico and global markets

Problema

Scattered per-app notification settings; missed calls among noise

Por qué esta puntuación

Por qué obtuvo una puntuación menor: Low willingness to pay

Ventaja defensivaHipótesis

Rules templates + log. Templates and learning log. Thin; Hypothesis.

Señales de demanda

Publicaciones en X (7 días)

n/a

Tendencia de la señal

n/a

Demanda en la webAutodeclarado

One Reddit ask in two communities (Self-reported); volume apps with 10K-100K installs.

Mercado y competidores

TAMHipótesisEstimación

$1B+ (Hypothesis) — Android utility apps spend. Method: Hypothesis. Sources: Hark estimate (Hypothesis).

SAMHipótesisEstimación

$40M (Hypothesis) — Android users in PT-BR/ES/EN willing to pay for notification tools. Method: ~50M users x 1% x $5/year ≈ $2.5M near term; $40M ceiling. Sources: Hark estimate (Hypothesis).

SOMHipótesisEstimación

$30K ARR (Hypothesis) — 12 months. Method: ~1,500 payers x ~$20/year. Sources: Hark estimate (Hypothesis).

Competidores

Volu, WOW Volume Manager, Audio Profiles, native channel settings, Tasker

Modelo de negocio

Monetización

One-time unlock or small yearly subscription; free tier with 3 rules

Hipótesis de ingresos (mensual)Hipótesis

Base ~$2K/month, conservative ~$0.3K/month at 12 months (Hypothesis).

Jobs to be done

When my phone buzzes for everything and I miss important calls, I want one screen of rules by app and category, so I can stay reachable and calm.

HXC

Bianca · 27 · Recife: Gets 300 notifications a day, mutes groups manually. Frustration & buying signal: Wants calls loud and everything else quiet in one place; would pay a one-time fee.

Construcción y go-to-market

Stack tecnológico

Cursor + Vercel + GitHub cesarx2 (one repo); Supabase; Stripe

Canales de GTM

Play ASO, SEO/GEO how-to pages, community answers via personas; no founder face, no paid ads

Riesgos

Riesgo principal

Low willingness to pay

Todos los riesgos

Value Risk: Attention — Low willingness to pay. Next: Fake-door price test. | Usability Risk: Supported — Simple matrix UX. Next: Prototype. | Feasibility Risk: Attention — Permission friction and OEM battery killers. Next: Test on 5 OEMs. | Viability Risk: Elevated — Google/Samsung can ship it. Next: Move fast on templates and SEO.

Siguiente paso de validación

Fake-door page + 2 Android community posts; check native features

Fuentes

clauday.com https://volu.support/ https://play.google.com/store/apps/details?hl=en_US&id=com.bhanu.wowvolumescheduler https://play.google.com/store/apps/details?id=com.fnp.audioprofiles

android, notifications, utility, b2c, idea, new, below-bar

¿Quieres la próxima el día en que se evalúe?

La puntuación, las fuentes, los riesgos y el siguiente paso, por correo.

ProductBots.ai

¿Te gusta esta idea? Conviértela en un plan con ProductBots.ai.

ProductBots.ai es un Agentic Product OS: agentes que hacen contigo el trabajo de producto, desde el descubrimiento hasta el plan. Descarga el briefing de esta idea y úsalo como punto de partida.

Abrir ProductBots.ai

El archivo del briefing está en inglés.

Ver una vista previa del briefing

# Briefing: Quiet Rules

Source: Startup Ideas HQ (HB Ventures), found 2026-10-22. ProductBots Opportunity Score: 58/100, evidence confidence 32%.
Evidence labels (Verified, Self-reported, Hypothesis) are kept as written by the researcher.

## Goal for ProductBots.ai
Turn this idea into a validated MVP plan and a first build. Start from the next validation step; do not assume unlabelled numbers are verified.

## What it is
One rules screen for Android: calls always loud, messages vibrate, social apps silent, everything else muted, by app and by category, with a 'why did my phone ring' log.

A Reddit poster (Ideas Radar, Oct 22) wants real per-app control of notifications and sounds and has not found it; the same post ran in two Android communities. Android's per-app channel settings exist but are scattered. Existing tools found: volume managers that switch volume by foreground app (Volu, WOW Volume Manager, Audio Profiles). None found with notification-level policy rules on one screen (limited check, not exhaustive). Mass B2C utility, global, SEO-friendly ('silence Instagram notifications but keep WhatsApp loud'). Low-confidence idea; demand evidence is one Reddit thread (post volume is demand, not proof that no product exists).

## Customer and pain
Target customer: Android users 18-45 in Brazil, Mexico and global markets
Pain: Scattered per-app notification settings; missed calls among noise

## Market and competitors
TAM: $1B+ (Hypothesis) — Android utility apps spend. Method: Hypothesis. Sources: Hark estimate (Hypothesis).
SAM: $40M (Hypothesis) — Android users in PT-BR/ES/EN willing to pay for notification tools. Method: ~50M users x 1% x $5/year ≈ $2.5M near term; $40M ceiling. Sources: Hark estimate (Hypothesis).
SOM: $30K ARR (Hypothesis) — 12 months. Method: ~1,500 payers x ~$20/year. Sources: Hark estimate (Hypothesis).
Competitors: Volu, WOW Volume Manager, Audio Profiles, native channel settings, Tasker
Geography: Global except China; Brazil/Mexico templates first

## Business model
Monetization: One-time unlock or small yearly subscription; free tier with 3 rules
Revenue hypothesis (monthly): Base ~$2K/month, conservative ~$0.3K/month at 12 months (Hypothesis).

## Build and go-to-market
Build effort (agent-weeks): 1
Time to first revenue: 2-3 weeks
Tech stack: Cursor + Vercel + GitHub cesarx2 (one repo); Supabase; Stripe
GTM channels: Play ASO, SEO/GEO how-to pages, community answers via personas; no founder face, no paid ads

## Risks and next step
Main risk: Low willingness to pay
Next validation action: Fake-door page + 2 Android community posts; check native features

## Sources
https://clauday.com/article/13a24602-c681-4a09-9609-9cc6e08d626f https://volu.support/ https://play.google.com/store/apps/details?hl=en_US&id=com.bhanu.wowvolumescheduler https://play.google.com/store/apps/details?id=com.fnp.audioprofiles

Investigación, no asesoría de inversión. Los números conservan la etiqueta con la que se publicaron.