Before You Build
Web AppLow Traction

Scarlyfy

Scarlyfy is a WhatsApp AI bot and digital calendar for small medical practices in Latin America. The lesson is that a clear clinic workflow and a ready product still need platform approval, buyer access, and paid demand proof before launch timing is dependable.

View source

Product snapshot

What it was

Scarlyfy is a WhatsApp AI bot and digital calendar for small medical practices in Latin America.

Who it was for

independent doctors in Latin Americasmall clinicsmedical offices coordinating appointments through WhatsApp

Problem / value

It automates appointment booking, reminders, confirmations, and follow-up calls so clinics can reduce manual scheduling work.

Core workflow

A patient messages on WhatsApp, the bot checks availability, books the appointment, sends reminders, calls if the patient does not confirm, and updates the doctor's dashboard.

Product form

WhatsApp AI botdigital calendarclinic dashboardweb SaaS

Pricing model

The founder post said a 14-day free trial was ready and pricing started at $22/month; the official site lists plans from PEN 79 to PEN 319.

Competitors or alternatives

manual WhatsApp schedulingpaper notebooks in clinicsclinic appointment softwareWhatsApp Business workflows

What happened

Summary

Scarlyfy was technically ready but still had 0 paying customers while the official WhatsApp approval path was pending.

Outcome

This is an active low-traction case, not a shutdown case: public sources show product readiness, pricing, and a clear workflow, but not paid customer proof or the later Meta approval outcome.

Core risk

Platform approval before paid customer proof

Demand signal

The public record shows 0 paying customers at the launch-status point. That does not prove clinics did not need the workflow, but it means paid demand had not yet been shown separately from product readiness and platform setup.

Distribution issue

The intended workflow depends on Meta WhatsApp Business API approval. The founder said the review had been pending since May 13, 2026, which meant the official WhatsApp path was a gate on launch and sales timing.

Timeline

  • On May 29, 2026, the founder said Scarlyfy had launched three weeks earlier.
  • The founder reported that the landing page, backend, authentication, multi-tenant appointments, webhooks, and 14-day free trial were ready.
  • The same post said Meta review had been pending since May 13, 2026.
  • At that launch-status point, the founder reported 0 paying customers.

Before you build

Why it matters

For workflow products built on WhatsApp or another controlled platform, technical readiness is not enough. You still need approval, a fallback demo path, and proof that the target buyer will pay once the workflow is available.

Primary check

Treat platform approval as a launch-critical risk, and prove clinic buyer commitment before depending on the full WhatsApp workflow.

Checklist

  • Can the buyer experience the core outcome before platform approval is complete?
  • Who has agreed to pay once the workflow is available?
  • What happens if approval takes twice as long as expected?
  • Which habit must the clinic stop using for this to work?
  • Identify every external approval required before the product can deliver its core workflow.
  • Create a fallback demo or concierge path before waiting on approval.
  • Ask target clinics to commit to a paid pilot, not only to try a free trial.
  • Measure whether users change their current scheduling habits.

Relevant if

  • You are building on WhatsApp, Meta Business API, an app marketplace, or another approval-gated platform.
  • Your product solves an operational workflow but depends on changing existing habits.
  • You have a ready product but no paid customer proof yet.

Less relevant if

  • You already have platform approval and signed paid pilots.
  • Your product can deliver its core value without any third-party approval gate.

Pre-build tests

  • Run a manual appointment-booking pilot with a small clinic before adding more automation.
  • Pre-sell the WhatsApp workflow to clinics while using a demo or concierge version.
  • Prototype the Meta approval path early and document a non-WhatsApp fallback.

Transferable lessons

  • Treat platform approval as part of validation, not as post-build paperwork.
  • Ask buyers to commit to a paid pilot before the full automated workflow is approved.
  • Use a demo, concierge workflow, or manual pilot to test clinic willingness to change habits.
  • Sell the clinic outcome in buyer language instead of leading with the technical stack.

If you build this today

Before building deeper automation, sell a paid pilot around the clinic outcome, keep a demo path that does not wait on approval, and validate whether doctors will change scheduling habits from WhatsApp and paper notebooks.