Social media decision

Groups Reply

A competent developer can build a single-user keyword monitor for Facebook Groups in about a week, but reproducing the paid product's scale, reliability, and polish (and any undisclosed integrations) would be harder and justify continuing to pay for a mature service.

Visit website

Built by Tony Conte, who ships 4 products in this index

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off35 h to build

$30/mo3 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Poll or subscribe to posts in one or more Facebook Groups, run keyword/phrase matching, store matches, and notify the user (email/webhook/UI).

What it still won’t have

  • High-reliability ingest at scale (rate-limit handling, backfills, deduplication)
  • Polished UX, onboarding, and multi-user/team features
  • Robust spam/false-positive reduction and advanced NLP
  • Any proprietary integrations or built-in historical indexing beyond what Facebook API provides

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Groups Reply does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a small keyword-monitoring service for Facebook Groups using Node.js (Express) backend, Postgres for storage, and React for a minimal dashboard. Core features in scope: OAuth integration with Facebook Graph API for group access, a poller/webhook worker to ingest new group posts, configurable keyword lists per group, exact and simple fuzzy matching, storing matches and post metadata in Postgres, email notifications via SendGrid and a webhook notification option, and a dashboard to add/remove groups and keywords and view recent matches. Out of scope: multi-tenant billing, advanced NLP/classification, historical backfill of large archives, and support for other social platforms. Include error handling, retries for transient API failures, basic rate-limit handling, and automated tests for ingestion, matching logic, and the notification path. Provide deployment scripts (Docker Compose) and README with setup and Facebook app permission notes.
How we checked1 sources · 2/3 runs agreed · evidence score 52

How the score was reached

  • Partly verdict base52
  • Evidence score52

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 1

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded