SB StartupBasket
All ideas
76 /100 GO Medium complexity

ZapCobra — Pix Automático collections for solo billers

Turns a Brazilian solo biller's WhatsApp contact list into automatic monthly Pix charges, no accounting system required.

views
Evaluation Scores
76/100

GO

Overall Score

16
Problem
13
Demand
11
Build
12
Distrib.
11
Revenue
8
Time
5
Defense

ZapCobra

1. One-liner

Turns a Brazilian solo biller’s WhatsApp contact list into automatic monthly Pix charges, no accounting system required.

2. Trend signal — why now?

Three things landed in Brazil in the last six months, all at once:

  • Pix Automático went live (14 May 2026). The Central Bank’s recurring-debit rail lets a customer authorize once inside their bank app, then get debited automatically every month — no card, no boleto, no manual transfer. The BC’s own guidance names the target verticals: escolas, academias, condomínios, SaaS, clubes de assinatura, contas de consumo. Failure rate is structurally low (2–5%, mostly insufficient balance), and it costs 1/10 to 1/20 of recurring card charges with instant settlement.
  • 60 million Brazilians have no credit card and were locked out of the subscription economy entirely. Pix Automático draws straight from the checking account, so it opens recurring billing to a population cards never reached. Early adopters aren’t small: Nord Security reported Pix Automático hit 28% of its Brazilian payment volume within six months of switching it on.
  • CADE (antitrust) opened WhatsApp to any AI chatbot vendor in March 2026. Agentic commerce inside WhatsApp + Pix is now legal for everyone, not just the incumbents. Q1 2026 Pix volume was ~R$3.4 trillion/month. The rail is the default; the tooling for the long tail is not built yet.

The rail exists. The giants (Vindi, Asaas, Mercado Pago, PagBrasil, OpenPix) already expose it — but only to businesses that have a system to integrate. The 5-million-strong tail of solo billers who run everything from a WhatsApp list and a caderninho has no on-ramp. That’s the gap, and it’s weeks old.

Provenance:

3. The opportunity

The incumbents built Pix Automático for people who already have software. Vindi says “integre sua operação à plataforma.” Asaas and OpenPix are API-first with Shopify/Nuvemshop/WooCommerce plugins. Cobre Fácil and Cora serve MEIs but through boleto and digital-account flows, not Pix-Automático-native recurring.

None of them serve the person who is the system: a personal trainer with 40 alunos, a neighborhood English tutor, a course seller, a small-building síndico, a subscription-box maker who runs the whole operation inside WhatsApp. This person doesn’t have “an operation to integrate.” They have a phone, a Pix key, and a list of names they nag every month.

ZapCobra is the zero-integration on-ramp: import (or paste) the client list, and the product runs the entire Pix Automático lifecycle — sends each client a WhatsApp authorization link, tracks who authorized, fires the monthly charges, and auto-chases the failures — inside the one channel the biller already lives in. The 10× isn’t a better dashboard. It’s there is no dashboard to learn — the biller never leaves WhatsApp, and the AI writes the collection messages in a tone that doesn’t burn the relationship.

4. Target market

  • Primary customer: Brazilian solo / nano service providers billing a fixed monthly amount to 15–300 clients, with no ERP or billing software — personal trainers, private tutors and small course-sellers, small-building síndicos (self-managed condomínios), independent clinics/therapists, subscription-box micro-sellers. Typically MEI or informal.
  • Why they buy: “Todo mês eu tenho que ficar cobrando um por um no WhatsApp.” Manual chasing eats hours, is awkward, and leaks revenue to inadimplência. Personal trainers charge R$750–1,200/month per student — one recovered no-pay covers the tool for a year.
  • Rough TAM reasoning: Brazil has millions of MEIs plus a large informal service segment; the gym/course/condomínio slice billing recurring monthly fees is comfortably in the low millions of businesses. Capturing 20–40k paying billers is a sub-$5M-ARR business — well inside the target and invisible to the gateways chasing merchant volume.
  • Why now for them: Until 14 May 2026 there was no cardless auto-debit rail cheap enough for a R$150/month personal-training fee. Boleto had fees and friction; cards excluded the 60M unbanked-by-card. Pix Automático removed the excuse — but only if someone hands the biller a one-tap setup.

5. Product sketch (MVP)

  • Paste or import a client list (name + WhatsApp number + monthly amount) — from a spreadsheet, phone contacts, or typed in.
  • One tap sends each client a WhatsApp message with a Pix Automático authorization link; client authorizes inside their own bank app.
  • Live “quem autorizou / quem falta” board, all inside a WhatsApp-linked mini-app — no separate login ritual.
  • Automatic monthly charges on the biller’s chosen date, drawn from the client’s account via Pix Automático.
  • AI-written dunning: on a failed charge (usually insufficient balance), it sends a friendly, human-sounding WhatsApp nudge with a one-tap re-pay link, escalating in tone over 3 touches.
  • Monthly cash summary (“R$18,400 recebido, 3 pendências”) pushed as a WhatsApp message.
  • Portuguese-first, reais-priced, works on a cheap Android phone with no onboarding call.

6. AI angle — what’s load-bearing

Two places AI does real work, not decoration:

  1. List ingestion. Micro-billers keep clients as messy free text — a WhatsApp export, a photo of a caderninho, a chaotic spreadsheet. An LLM parses name / number / amount / due-day out of that mess and reconciles duplicates, so setup is minutes not an afternoon. This is the difference between “import your list” and “the biller gives up.”
  2. Relationship-preserving dunning. The single biggest fear is that automated collection sounds like a bank and costs them a client. The sources are explicit: generic “vamos cobrar R$ X” messages lose customers. The AI drafts context-aware, warm, Brazilian-Portuguese nudges tuned to each situation (first miss vs. chronic late), so the biller collects without becoming the bad guy.

Strip the AI and you’re back to a form-filling app that no non-technical trainer will finish setting up. The AI is what makes the tail addressable.

7. Localization angle (if any)

This is only a localization play — it can’t exist outside Brazil. Pix Automático is a Brazilian Central Bank rail; WhatsApp is the default business channel; reais pricing (a R$29–49/month tool for a biller who won’t pay a gateway’s per-transaction merchant fees) is the wallet reality; the dunning tone has to be Brazilian-Portuguese and culturally right. Every wedge here is local. A generic “recurring billing SaaS” loses because it assumes a system the customer doesn’t have and a payment rail the customer can’t use.

8. Business model — path to $1M–$5M ARR

  • Pricing: R$29/month (up to 50 active clients) → R$79/month (up to 200) → R$149/month (200+). Flat subscription, not per-transaction — the biller keeps their raw Pix cost; we charge for the collection autopilot. Optional: small take on recovered-after-failure amounts as an upsell later.
  • ACV: ~R$600–950/year (~US$110–175).
  • Rough math to $1M ARR: ~6,500 billers at an ~R$780 blended annual = ~R$5.1M ≈ US$0.95M. Very reachable within the tail.
  • Rough math to $5M ARR: ~30–35k paying billers, or the same base plus a recovered-payment success fee and a “bring your own list” referral loop. Requires proving retention past the first churn cliff (billers who lose their client base churn).
  • Expansion path: tiers by client count; add-ons (receipt/NFS-e nudge, reminders for one-off charges, a “novo aluno” onboarding link the biller can post to Instagram bio). ACV grows as the biller’s roster grows.

9. Go-to-market wedge — first 100 customers

  • Personal-trainer + tutor communities on Instagram/WhatsApp. These niches live in public: hashtag/geo scrape 2,000 personal trainers and independent tutors posting “vagas abertas,” DM a 40-second Portuguese demo video showing “cobre seus 40 alunos com um toque.” Expect low-single-digit reply, close a slice — enough for the first 50.
  • Síndicos of small self-managed condomínios via síndico Facebook/WhatsApp groups. These groups are dense, vocal about inadimplência, and the síndico is a single decision-maker with a fixed monthly boleto/Pix chase. Post a before/after and a free-first-month code.
  • CREF / educação-física and music-teacher micro-influencers. Partner with 3–5 who already sell “como organizar sua carreira autônoma” content; affiliate them a cut. Their audience is the customer.
  • “Migrate off boleto” angle at Cobre Fácil/Cora users who feel boleto friction — a targeted comparison landing page (“Pix Automático custa 1/10 do cartão e cai na hora”).

If I can’t convert trainers-DMed-a-video into paid trials in two weeks, the idea is wrong — but the audience is findable, single-decision-maker, and feeling the pain monthly.

10. Build complexity — justification

Medium. The web/WhatsApp app and LLM list-parsing + message drafting are off-the-shelf. The real work is the Pix Automático integration via a licensed PSP (Asaas/OpenPix/Efí expose it) plus the WhatsApp Business flow and the authorization-lifecycle state machine (authorized / pending / failed / retry). No proprietary infra, no ML training — but it’s regulated money movement over a PSP, so a small team needs ~3–4 months to a solid v1, not 6 weeks.

11. Gating checklist

GatePass?Note
Legal in target marketPix Automático is a BC-sanctioned rail; we ride a licensed PSP, don’t hold funds.
Ethical — no harm / dark patternsExplicit single-authorization inside the payer’s bank; AI dunning designed to be humane, not coercive.
Market exists (evidence above)Live rail, named target verticals, manual-chase pain documented, 60M cardless newly addressable.
1–5 person team can build thisPSP + WhatsApp + LLM; no custom infra.
Launchable with <$50K / ₹40LSoftware + PSP onboarding; no capital-intensive component.

12. Feasibility score

AxisWeightScoreNotes
Problem intensity2016/20Monthly, hours-eating, revenue-leaking, relationship-awkward. Not daily hair-on-fire, but felt every single month by every target user.
Demand evidence1513/15Live rail + named BC target verticals + documented manual-chase pain + Nord’s 28%-in-6-months adoption. Strong, though direct “tail biller will pay R$29” is still to be proven.
Build feasibility1511/15PSP-mediated money movement + WhatsApp flow = a few months, not weeks. Solidly doable, not trivial.
Distribution clarity1512/15Named, scrapeable, single-decision-maker audiences (trainers, tutors, síndicos). Conversion of the price-sensitive tail is the open question.
Revenue mechanics1511/15Flat R$ subscription benchmarked below gateway fees; $1M path needs only ~6.5k billers. Retention past client-base churn is the risk.
Time to first revenue108/10DM-a-video-to-trainers can produce paid trials within weeks of a working v1.
Defensibility105/10Execution + niche brand + workflow lock-in on the biller’s client list. A gateway could ship a “simple mode,” so speed and tail-focus are the moat.
Total10076/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy (PSP + WhatsApp integration, LLM plumbing) · sales-heavy (converting a price-sensitive, low-trust, non-technical tail requires relentless, human outreach).

Key assumptions to validate (3–5)

  1. Assumption: No-system solo billers will pay a flat R$29–49/month for collection automation. How to test: Pre-sell to 30 personal trainers/tutors via DM with a mockup + Pix link before building; count who actually pays a deposit.
  2. Assumption: Clients (the alunos) will complete the Pix Automático in-bank authorization at an acceptable rate. How to test: Run one real biller’s list end-to-end; measure % authorized within 72h. Kill if <50%.
  3. Assumption: A PSP will let a thin, aggregator-style app onboard many nano-billers without enterprise contracts. How to test: Talk to Asaas/OpenPix/Efí partnerships in week 1; confirm the sub-account / marketplace model and per-biller KYC path.
  4. Assumption: AI dunning measurably reduces inadimplência vs. the biller’s own messages without costing them clients. How to test: A/B the AI nudge vs. generic template on 10 real billers over 60 days.

Risk flags

  1. Platform dependency: Sits on top of one PSP’s Pix Automático + WhatsApp Business API. A pricing or policy change upstream hits the whole model. Mitigate by designing PSP-agnostic from day one.
  2. Incumbent “simple mode”: Asaas/Mercado Pago could ship a stripped WhatsApp-first flow for the tail and crush on distribution. The moat is being faster and tail-obsessed before they bother.
  3. Retention / churn: The customer’s own business is fragile — trainers lose clients, tutors go seasonal. Base churn could be high; the tool must survive roster shrinkage, not just growth.
  4. Trust / KYC friction: Money movement for nano-merchants invites fraud scrutiny; onboarding friction could throttle the very tail that’s the whole thesis.

14. Structured verdict

Score:                  76/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder comfortable with PSP + WhatsApp APIs, paired with a Brazilian sales/community operator who can DM the tail
Time to revenue:        8–12 weeks after a working v1 (pre-sales possible sooner)
Capital to launch:      R$40–120k (US$7–22k) — PSP onboarding, WhatsApp API, small team runway
Top 3 assumptions to validate first:
  1. Tail billers pay flat R$29–49/mo — pre-sell 30 via DM before building
  2. Clients authorize Pix Automático at >50% within 72h — run one real list end-to-end
  3. A PSP allows many-nano-biller onboarding without enterprise contracts — partnerships call week 1
Kill criteria:
  - Abandon if <10 of 30 pre-sell DMs convert to a paid deposit
  - Abandon if client-side authorization completion is <50% on a real list
  - Abandon if no PSP will support a many-small-biller aggregation model at viable unit cost

15. Next step — 1-week validation sprint

  • Day 1–2: Partnerships calls with Asaas, OpenPix, Efí — confirm the sub-account / aggregator onboarding model, per-biller KYC path, and Pix Automático access terms. This is the make-or-break plumbing question.
  • Day 3–4: Build a no-code mockup + a 40-second Portuguese demo video. DM it to 30 personal trainers/tutors scraped from Instagram; ask for a small refundable deposit to “reserve early access.”
  • Day 5: Decide go / no-go. Go only if ≥10 of 30 DMs convert to a paid deposit and at least one PSP confirms a workable many-nano-biller onboarding path. Both must be true — a warm audience with no viable PSP rail is a dead end, and a great rail with no willing payers is a hobby.

Falsifiable outcome: paid deposits from strangers, not “they said it sounded useful.”

Interested in a detailed proposal?

Get a deep-dive with market research, competitive analysis, and implementation roadmap.

Contact us

info@startupbasket.ai