SEO and marketing decision

Coucou

A technical user can build a useful subset (appointment detection + SMS+landing page) quickly, but reproducing the vendor's polished multi-integration product, onboarding, and managed support is non-trivial.

Visit website
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-off34 h to build

$25/mo6 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

  • Detect appointment → send SMS with branded landing page → collect Google review → optionally auto-draft reply and publish excerpt/widgets

What it still won’t have

  • Polish, onboarding flows and prioritized support included by vendor
  • Built-in integrations with specific appointment platforms listed (Planity, Treatwell, Booksy, Kalendes) unless reimplemented
  • Legal and deliverability handling for SMS at scale and phone number management
  • Refined UX copy, templates, and trust signals (reviews, visual design) the vendor markets

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Coucou 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 minimal self-hosted review-solicitation service using Node.js (Express), PostgreSQL, and React for a single-salon tenant. Core features in scope: (1) connectors: webhook endpoint and a CSV importer for appointment systems, normalizing completed-appointment events; (2) SMS sender using Twilio with templated messages and shortlinks; (3) branded review landing page generator (per-tenant template) that redirects to Google review and records completions; (4) duplicate/recency filter to avoid repeat solicitations; (5) Google Business Profile read + reply drafts via Google OAuth (store tokens securely); (6) simple admin dashboard showing sent SMS, collected reviews, and basic stats; (7) one-click export of review text as PNG for social. Out of scope: multi-tenant billing, deep integrations with Planity/Treatwell SDKs, automatic Instagram posting. Include configuration for deployment (Docker), instructions to obtain Twilio credentials and Google Business API OAuth credentials, automated tests for webhook processing, unit tests for dedupe logic, error handling for failed SMS sends and failed Google API calls, logging, and a small migration script for DB schema.
How we checked2 sources · 2/3 runs agreed · evidence score 53

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • Evidence score53

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 · 2

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