SAASPOCALYPSEverdict #RECURLY-FECC
scanned 2026.05.02 · 05:00
subject of investigation

recurly.com

subscription management & recurring billing platform
verdictCONTESTED
wedge score
45
/100
tier · contested
wedge thesis

the door is market segmentation: Recurly is priced and positioned for enterprise-scale brands, leaving a wide-open gap for indie-friendly, self-serve subscription billing with no demo-gating and no sales call required.

real walls — pick your flank·ship in 10 weeks·run for $47.00 + usage
wedge map

where the walls are.

methodology →
the door

their capital wall is paper-thin — runs on commodity cloud + free tiers.

watch out

switching cost is real — workflow lock-in keeps customers from leaving.

capitaldoor
0.0/10
investment the incumbent had to make
technical
5.6/10
depth of the underlying engineering
network
0.0/10
users compound users
switching
10.0/10
stickiness of customer data + workflow
data
4.0/10
proprietary data accumulates over time
regulatory
0.0/10
real licenses, not SOC 2 theater
distribution
8.0/10
brand SERP grip, knowledge graph, news flow
take

the blunt take.

color around the thesis

Recurly's entire homepage is a "book a demo" funnel — there's no pricing page, no self-serve signup, and no path for a $500/mo SaaS founder to just start. That's not an oversight; it's a deliberate enterprise posture that abandons the long tail.

The core mechanics — plan management, dunning, failed-payment retries, proration, and a subscriber portal — are well-understood problems with open-source implementations. The moat is 15 years of payment processor relationships and enterprise integrations, not the billing logic itself. A focused indie tool targeting early-stage SaaS founders who want Recurly's features without Recurly's sales process has a real wedge.

cost

cost of competing.

their price ←→ your run-rate
what they charge
Enterprise (demo-gated, no public pricing)
custom
/ per contract
No self-serve tier visible; all paths lead to a sales call
annual:custom
what running yours costs
01 · Vercel Pro (for edge functions + webhooks)$20.00
02 · Supabase Pro (subscription state, events, invoices)$25.00
03 · Resend (dunning + invoice emails)$0.00
04 · Cloudflare R2 (invoice PDF storage)$1.00
05 · Stripe (payment processing — fees in txn %)$0.00
06 · Domain$1.00
07 · LLM API (anomaly detection / AI insights, optional)??? — scales with usage
TOTAL / mo$47.00 + usage
▸ break-even:immediately for any solo founder — Recurly's demo-gated pricing means you'd pay enterprise rates; your build runs at $54/mo from day one
build

what you're up against.

est. total: 10 weeks
2 weeks Stripe integration + plan CRUD · 2 weeks dunning engine + retry logic · 2 weeks subscriber portal (self-service) · 2 weeks proration + invoicing · 2 weeks dashboard + analytics
easy
medium
hard
nightmare
01
easy
Plan & pricing CRUD
Create/update/archive plans with flat, per-seat, or tiered pricing. Stripe Products API does the heavy lifting.
02
easy
Webhook ingestion pipeline
Stripe fires events; you persist state. Queue + idempotency key. Standard pattern.
03
medium
Dunning engine with intelligent retries
Exponential backoff, configurable retry schedules, email sequences on failure. Stripe Radar helps but you own the orchestration.
04
medium
Proration & mid-cycle plan changes
Upgrade/downgrade math mid-billing-period is fiddly. Stripe handles some of it; you handle the display and edge cases.
05
hard
Self-service subscriber portal
Skip, pause, swap, cancel flows with cancel-save offers. Each flow is a mini-product. The cancel-save logic alone takes a week.
06
nightmare
ASC-606 / IFRS-15 revenue recognition
Recurly's RevRec product is a full accounting sub-system. Deferred revenue, contract modifications, SSP allocation — this is a separate product, not a feature.
stack

their position.

inferred + measured stack
detected signals· measured
frameworkNext.jsanalyticsGTM
recommended stack · inferred
Next.js 15 (App Router + server actions)Supabase (Postgres + realtime for subscription events)Stripe Billing API + webhooksResend (dunning email sequences)Trigger.dev (retry job orchestration)
rivals

who else has tried this.

indies + alternatives
option A
Lago (self-host)
Open-source billing engine. Docker compose up. Handles metered, seat, and flat billing. Genuinely production-ready.
option B
Stripe Billing (direct)
Handles plans, proration, dunning, and a customer portal natively. You're already paying Stripe — use more of it.
option C
Paddle / Lemon Squeezy
Merchant-of-record model. Handles tax, billing, and churn tools. No build required for digital goods.
compare

similar scans.

same shape - different moat
ready to wedge in?
Get the wedge plan. Cancel some plans.
▸ generated with love, by a heartless robotverdict v2.5 · saaspocalypse.dev