Un proyecto de Mauricio Gallmur· el prompt es gratis · si quieres que un agente lo corra solo, eso es lo que instalo

¿Puedo vibecodear Debriefing?

PARCIAL · un fin de semana
precio $80/mesahorrarías $960/añotiempo de build varios díascategoría 📡 rss e investigaciónreemplazada por 0 personas

Diffing a competitor's pricing page on a cron and asking a model what changed is genuinely an afternoon. changedetection.io will do the watching for you before you write a line. The gap is everything between a diff and a brief. Most page changes are noise: a rotated testimonial, a reordered nav, a CDN hash. Deciding which changes are real, tying them to hiring and funding signals, and turning that into three sentences a founder acts on is judgement encoded over many iterations. Build it and your first month is mostly you deleting alerts about nothing.

el prompt
Build me a local competitor watch that emails me a weekly brief, to replace Debriefing. Requirements:

- Node 22, TypeScript, SQLite via better-sqlite3, Playwright for fetching, node-cron for
  the schedule. CLI only. No accounts, no telemetry, keys in .env.
- competitors.json lists each rival: name, and the URLs that matter (homepage, pricing,
  changelog, careers). Ship it seeded with 3 competitors and 4 URLs each.
- `watch snapshot` fetches every URL with Playwright, strips scripts, styles, nav and
  footer, converts the main content to plain text, and stores it with a SHA-256 hash and
  a timestamp. Skip storage entirely when the hash is unchanged.
- Diff each new snapshot against the previous one as unified text diff. Discard diffs
  under 40 changed characters, and drop lines matching an editable noise.json of regexes
  (dates, cache-busting hashes, view counts, testimonial rotations).
- `watch brief` sends the surviving diffs for the period to Claude or GPT in one call
  and asks for, per competitor: what changed, why it matters, and one suggested response.
  Require a citation back to the exact URL for every claim, and drop any bullet without
  one.
- Render the brief to Markdown in ~/CompetitorBriefs/YYYY-MM-DD.md and send it via SMTP
  from .env. The file is the source of truth, email is just delivery.
- Keep every snapshot and every brief. `watch history <competitor>` prints that rival's
  changes over time, which is the only way a single diff becomes a trend.
- Out of scope: hiring feeds, funding data, traffic estimates, dashboards and any login
  wall. Public pages only, respect robots.txt, one request per URL per run.
- README: setup, a cron line for the weekly run, the per-brief token cost, and a warning
  that month one is mostly tuning noise.json.

$ ábrelo en tu agente (prompt listo, tú das enter) o cópialo crudo

por qué la gente sigue pagando

Because a diff is not intelligence. The hard part is not fetching a pricing page every week, it is knowing that this particular change matters and the other eleven do not, then saying so in three sentences a founder can act on before a Monday call. That judgement lives in accumulated history and a lot of tuning against false positives. It also survives being ignored: a brief that arrives whether or not you remembered to look is worth more than a script you stop reading in week three.

qué pierdes

xnoise filtering, which is the actual product: most diffs are rotated testimonials and changed asset hashes, not competitive moves

xhorizon watch, meaning the substitutes and new entrants you did not think to add to the list

xthe non-page signals stitched into the same brief: hiring, funding, traffic and LinkedIn movement

xthe analytical step from what changed to why it matters to what to do next

xan archive going back far enough that a change reads as a trend rather than an event

compartir en X ↗"Acabo de reemplazar Debriefing ($80/mes) con un prompt"
la salida

¿No quieres construirlo? Esta gente ya lo hizo gratis.

changedetection.ioTells you a competitor's pricing page moved. Deciding whether that mattered is back to being your job.33kaug 2026open source

sin votos, sin pago por aparecer · solo lo que es real

los números

Precio de Debriefing

starter$80/mes · monthly · $960/año

plan gratisNo standing free plan, but the first debrief is free and arrives in 5 to 10 minutes.

verificado 2026-08-10 · fuente ↗

preguntas
¿Debriefing es gratis?

No standing free plan, but the first debrief is free and arrives in 5 to 10 minutes. El plan de pago es Starter a $80/mes (revisado 2026-08-10).

¿Puedo vibecodear Debriefing?

Parcial. El núcleo de Debriefing se arma en un fin de semana con el prompt de esta página, pero hay huecos reales: noise filtering, which is the actual product: most diffs are rotated testimonials and changed asset hashes, not competitive moves, horizon watch, meaning the substitutes and new entrants you did not think to add to the list. Lee la lista honesta arriba antes de comprometerte.

¿Cuánto cuesta Debriefing?

Debriefing cuesta unos $80/mes (Starter, revisado 2026-08-10), o sea $960 al año.

¿Qué pierdo si reemplazo Debriefing?

Con honestidad: noise filtering, which is the actual product: most diffs are rotated testimonials and changed asset hashes, not competitive moves; horizon watch, meaning the substitutes and new entrants you did not think to add to the list; the non-page signals stitched into the same brief: hiring, funding, traffic and LinkedIn movement; the analytical step from what changed to why it matters to what to do next; an archive going back far enough that a change reads as a trend rather than an event. Si alguno de esos te sostiene el negocio, sigue pagando.

¿Hay una alternativa open source a Debriefing?

Sí: changedetection.io (Tells you a competitor's pricing page moved. Deciding whether that mattered is back to being your job.) El prompt es para cuando la quieres exactamente a tu modo.

Cada semana mueren más suscripciones.

Veredictos nuevos, prompts nuevos, las apps más condenadas de la semana.
Un correo. Te sales en un clic.

gratis para siempre · sin spam · el prompt se queda en el sitio, las muertes te llegan a ti

$semanal: qué recibió veredicto, qué murió.