top of page
Recurly
Technology
Saas Platforms
Subscription Billing & Revenue Management Platform
Won by specializing in subscription billing intelligence — dunning automation, failed payment recovery, and churn prediction — helping SaaS and media businesses recover revenue that Stripe and Braintree's generic payment tools left on the table.
1
MODEL
BUSINESS MODEL
SaaS, API Platform
model bm
HOW THEY BUILT IT
Founded 2009 in San Francisco. Raised ~$40M+ from investors including Accel Partners and Polaris Venture Partners. Serves 2,200+ subscription businesses including Sling TV, Asana, BarkBox, Twitch, and Zillow. Core platform: subscription management (plan creation, upgrades, downgrades, pauses, cancellations), recurring billing automation, dunning management (automated retry logic for failed payments), involuntary churn reduction (account updater, intelligent retry), revenue recognition reporting, and subscription analytics. Key differentiator from payment processors (Stripe, Braintree): Recurly is a subscription management layer that sits above the payment gateway — companies can use Recurly with multiple payment gateways simultaneously, applying its dunning and retry intelligence across all payment methods.
HOW TO ARCHITECT IT
1. Subscription billing is not a payment processing problem — it is a revenue lifecycle management problem. Stripe charges a payment; Recurly manages the subscriber relationship through upgrade, downgrade, trial, pause, cancellation, and involuntary churn recovery. Build for the lifecycle, not the transaction.
2. Dunning management (the intelligent retry of failed payments) is the highest-ROI feature in subscription billing — recovering 20–30% of failed payments that would otherwise be lost represents direct revenue recovery with no new customer acquisition cost.
3. Gateway-agnostic architecture (connecting to Stripe, Braintree, Adyen, and others simultaneously) removes the 'we'd have to switch payment processors' objection by making Recurly a layer above the gateway rather than a replacement for it.
4. Enterprise subscription businesses ($10M+ ARR) generate the most revenue per customer and have the most complex billing needs — invest in the features (multi-currency, revenue recognition, complex plan logic) that SMB-focused billing tools won't build because the margin is too thin at small scale.
DISTRIBUTION MODEL
Self-Serve Website, Enterprise Sales, API Distribution
dm
HOW THEY OPERATIONALIZED
Self-serve API integration for developer-led organizations — documentation-first onboarding where a developer can integrate Recurly's billing API without a sales conversation. Enterprise sales team for subscription businesses processing $1M+ in annual subscription revenue where the ROI of dunning optimization is large enough to justify a dedicated account management relationship. Developer ecosystem (Recurly's REST API, SDKs, Recurly.js) as distribution — if Recurly is embedded in the billing stack by the developer who builds the subscription flow, it becomes the default platform for the entire organization.
HOW TO REPLICATE WHAT WORKED
In subscription billing infrastructure, the developer who integrates the payment and subscription flow is the de facto purchasing decision-maker — even if they are not the budget owner. Documentation quality, API design elegance, and developer community presence are the real sales motion for subscription infrastructure. A developer who builds a clean Recurly integration and deploys it successfully is the best retention mechanism available — the integration becomes embedded in the product's codebase, making it a technical switching cost rather than just a contractual one.
| PATTERNS OF THIS MODEL
PATTERNS IN LAYERS THAT SIT ABOVE PAYMENT INFRASTRUCTURE:
1. SUBSCRIPTION BILLING IS A LIFECYCLE PROBLEM, NOT A PAYMENTS PROBLEM. Stripe charges a card; the value is in upgrades, downgrades, pauses, trials, proration and recovery. Build for the relationship, not the transaction.
2. DUNNING IS THE HIGHEST-ROI FEATURE IN THE CATEGORY. Recovering 20-30% of failed payments is pure revenue with zero acquisition cost — quantifiable in the customer's own dashboard within a month.
3. GATEWAY-AGNOSTIC ARCHITECTURE REMOVES THE BIGGEST OBJECTION. Sitting above Stripe, Braintree and Adyen simultaneously means the buyer never has to switch processors to buy you.
4. INVEST WHERE SMB-FOCUSED RIVALS WON'T — multi-currency, revenue recognition, complex plan logic. Enterprise subscription businesses carry the ACV that justifies the engineering.
CAUTION: the payment processors are moving up-stack into billing. Layer businesses must own something the platform below cannot easily replicate — here, recovery intelligence across multiple gateways.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — BILLING IS A LIFECYCLE PROBLEM, NOT A PAYMENT PROBLEM.
Standard: Stripe charges a card; the subscriber relationship spans trials, upgrades, downgrades, pauses, cancellations and involuntary churn. Build for the lifecycle and you are not competing with the processor.
GOLDMINE 2 — DUNNING IS THE HIGHEST-ROI FEATURE IN THE CATEGORY.
Standard: recovering a meaningful share of failed payments is direct revenue with zero acquisition cost — the easiest ROI conversation in B2B software. Lead with the recovered dollars, not the feature.
GOLDMINE 3 — GATEWAY-AGNOSTIC ARCHITECTURE REMOVES THE BIGGEST OBJECTION.
Standard: sitting above Stripe, Braintree and Adyen simultaneously means the buyer never has to switch processors to buy you.
THE PIT — THE LAYER ABOVE A PAYMENTS GIANT IS A FEATURE THE GIANT WILL SHIP.
Stripe Billing did exactly this, with distribution Recurly cannot match and marginal price near zero. ~$40M raised against Stripe's balance sheet is not a fight; it is a race to depth in the accounts Stripe serves badly.
THE SECOND PIT — VOLUME PRICING MEANS YOU OWN YOUR CUSTOMERS' CYCLICALITY.
When their subscriptions shrink, your revenue falls with no churn event.
MOVE WITH CAUTION — THIS CATEGORY IS ALREADY CONSOLIDATING.
Zuora went private at ~3.7x revenue in February 2025. Model the exit multiple your model actually supports.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
MARKET TYPE
Fragmented Market
WHY THEY WON
Subscription billing and management is fragmented across: payment processors with billing features (Stripe Billing, Braintree), dedicated subscription management platforms (Recurly, Chargebee, Zuora), and revenue management suites (Maxio, Paddle). The category is growing as the subscription economy expands — more businesses moving to recurring revenue models creates new demand that is not yet served by the incumbents at every price point and use case.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
When Recurly launched in 2009, dedicated subscription management platforms as a distinct product category barely existed — Stripe was not yet public (launched 2010), and the available tools were either full ERP billing modules or manual workarounds. Recurly entered genuinely new territory as a purpose-built subscription billing API for internet businesses — a category that the existing payment processors and enterprise billing vendors had not recognized as a distinct market worth building for.
FOOTHOLD STRATEGY
fs
Beachhead Strategy
SaaS startups processing their first subscription revenue were the initial beachhead — developers building subscription products who needed billing infrastructure before they had the scale to justify enterprise billing vendor evaluation. The developer-first API integration model made Recurly the path of least resistance for a technical founder who needed to get billing working in a weekend rather than negotiate a contract with Zuora.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
ROI calculator content showing the dollar value of failed payment recovery at different monthly subscription revenue levels — the clearest demonstration that Recurly pays for itself through dunning optimization alone before the subscription management features are considered. Case study library for subscription businesses in specific verticals (media streaming, SaaS, box subscription services) showing dunning recovery rates and involuntary churn reduction metrics. Developer documentation investment — Recurly's API documentation quality was consistently cited by developers as a switching factor from competing platforms.
KEY LEARNING
The dunning management value proposition is the most powerful conversion tool in subscription billing: showing a prospect the percentage of their current failed transactions that could be recovered with intelligent retry logic creates an immediate, quantifiable revenue gap that the prospect cannot ignore. In infrastructure SaaS, documentation quality and API design are not afterthoughts — they are the product for developer buyers. A clean, well-documented API that a developer can integrate in hours beats a feature-rich platform that requires a week of integration work at every sales conversation.
gc
Market Context
| MARKET INTELLIGENCE
THE STANDARD: CAPITAL EFFICIENCY AND FOCUS is a viable strategy against funded rivals — provided you never fight them on breadth.
RULE 1 — SUBSCRIPTION BILLING IS SQUEEZED FROM THREE DIRECTIONS PERMANENTLY.
Processors adding billing (Stripe, Braintree), enterprise platforms (Zuora), revenue suites (Maxio, Paddle, Chargebee). A pure engine must be clearly best at one thing or it is a feature.
RULE 2 — INVOLUNTARY CHURN RECOVERY IS THE MOST DEFENSIBLE VALUE, BECAUSE IT IS MEASURABLE.
Retries, account updater and dunning recover revenue visible in the customer's dashboard within a month. Anchor price to recovered revenue.
RULE 3 — BILLING IS THE HARDEST SYSTEM TO REPLACE, WHICH CUTS BOTH WAYS.
Exceptional retention, brutal acquisition. Displacement needs a migration product, not a feature list.
RULE 4 — PROCESSOR NEUTRALITY IS THE INDEPENDENT'S REAL ASSET.
Stripe Billing structurally will not be gateway-neutral. Where a platform cannot be neutral, neutrality is durable.
RULE 5 — MODEST CAPITAL IS A STRATEGY IF YOU PRICE FOR IT. ~$39.2M raised across ~7 rounds — a fraction of Zuora's or Chargebee's — before Accel-KKR's majority investment (2019).
MARKET TYPE: Fragmented Market (subscription billing).
| MARKET ENTRY PLAYBOOK
THE STANDARD: ENTERING BEFORE A CATEGORY HAS A NAME MEANS YOUR COMPETITOR IS INTERNAL ENGINEERING TIME. Win by making "we'll build it ourselves" look like a permanent maintenance liability.
RULE 1 — THE API AND DOCS ARE THE PRODUCT AND THE SALES PROCESS.
Time-to-first-successful-call is the conversion metric in an infrastructure category with no budget line.
RULE 2 — ENUMERATE THE EDGE CASES PUBLICLY; THE LIST IS THE PITCH.
Proration, dunning, trials, plan changes, tax and failed-payment recovery are individually trivial and collectively endless.
RULE 3 — A PAYMENT PROCESSOR ENTERING YOUR CATEGORY IS AN EXISTENTIAL EVENT, NOT A COMPETITOR.
Stripe Billing arrives bundled with rails the customer already uses; processor neutrality is the only durable counter-position.
EVIDENCE: founded 2009, before dedicated subscription management existed and before Stripe launched; growth investment from Accel-KKR (reported ~$19.5M, 2019); still independent against Stripe Billing, Chargebee and Zuora. Revenue undisclosed.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: WHEN A DEVELOPER MAKES THE BUYING DECISION, TIME-TO-INTEGRATION IS THE PRICE. Enter where the enterprise vendor's contract is slower than the customer's whole build cycle.
RULE 1 — SERVE THE CUSTOMER BEFORE THEY ARE QUALIFIED FOR THE INCUMBENT. A startup taking its first subscription revenue cannot justify an enterprise billing evaluation and will grow into one — acquiring them early is acquiring their future scale cheaply.
RULE 2 — API-FIRST IS A GO-TO-MARKET STRATEGY. "Working by the weekend" beats "negotiated by next quarter" for a technical founder, and it removes sales cost from the acquisition of your smallest customers.
RULE 3 — BILLING IS THE HARDEST SYSTEM TO REPLACE ONCE LIVE. Revenue, tax, dunning and reporting all depend on it; the switching cost is a risk decision, not a budget one.
RULE 4 — YOUR REVENUE TRACKS YOUR CUSTOMERS' SUBSCRIPTION VOLUME. That is automatic expansion in growth years and silent contraction in bad ones, with no churn event.
EVIDENCE: SaaS startups processing their first subscription revenue were the beachhead, with developer-first API integration making Recurly the path of least resistance versus negotiating with Zuora. It took a growth investment from Accel-KKR in 2019 and has not publicly disclosed revenue or ARR; no exit announced. The category has since been squeezed by Stripe Billing from below and by Zuora — itself taken private at $1.7B in 2025 — above.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
REVENUE MODEL
Subscription, Transaction Fee
PRICING MODEL
Tiered Pricing, Usage-Based Pricing, Add-On Pricing
WHY THEY WON
Monthly subscription fee for platform access based on number of active subscribers managed (scales with customer growth). Transaction fee (percentage of each subscription payment processed through the platform) as a revenue-aligned component that grows with the customer's subscription revenue. Enterprise contracts custom-quoted for businesses processing $10M+ in annual subscription revenue with dedicated implementation support.
Core plan tiers based on number of subscribers and transaction volume; higher tiers add advanced dunning, revenue recognition reporting, multi-currency, and enterprise integrations (Salesforce, NetSuite). Transaction fee component (typically 0.9%+ per transaction) provides revenue alignment with customer growth. Enterprise custom pricing for high-volume businesses where the platform cost is a small fraction of recovered revenue.
TARGET AUDIENCE
CUSTOMER BUYING BEHAVIOUR
tg cb
SaaS companies, digital media and streaming services, subscription box businesses, and any recurring revenue business processing $50K+ in monthly subscription revenue that needs billing automation, dunning management, and subscription analytics.
Developer-led evaluation for technical integration fit; finance/operations lead evaluation for dunning recovery ROI and revenue recognition compliance; procurement decision at director/VP level for enterprise contracts. Triggered by hitting the limits of a manual billing process, a specific failed payment problem that becomes visible at scale, or a revenue recognition audit that requires automated documentation. 30-day trial for self-serve evaluation.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
THE STANDARD: Billing infrastructure should be priced on the money it moves and the money it recovers. Nothing else scales with the customer.
RULE 1 — PRICE ON TOTAL PAYMENT VOLUME, NOT ON SEATS OR SUBSCRIBERS ALONE.
Reported structure includes a $1M TPV minimum on the core Subscriptions product — a deliberate floor that excludes customers too small to be worth serving.
RULE 2 — RECOVERED REVENUE IS THE ONLY VALUE METRIC THAT SELLS ITSELF.
Recurly cites $1.6 billion in recovered revenue for customers across 76 million subscribers. When failed-payment recovery exceeds your fee, the ROI conversation is arithmetic rather than argument.
RULE 3 — MODULARISE SO EACH PRODUCT CAN BE METERED ON ITS OWN UNIT.
Reported structure: Commerce at $399/month plus roughly 1.5% of GMV and $0.10 per subscription order; RevRec starting near $1,200/month scaling on payment volume; Engage scaling on prompt volume. Different meters for different value — this is what mature usage pricing looks like.
RULE 4 — HYBRID PRICING IS NOT INDECISION, IT IS COVERAGE.
Base fee plus percentage plus per-transaction captures small and large customers on the same architecture without a repricing event.
RULE 5 — SELL YOUR OWN BENCHMARK DATA BACK TO THE MARKET.
The State of Subscriptions report (76 million subscribers, 2,200 merchants) is both marketing and proof of scale. In infrastructure, aggregate data is a credibility asset competitors cannot manufacture.
THE WILLINGNESS-TO-PAY INSIGHT: A subscription business is buying revenue it has already earned but would otherwise lose to a declined card. Price against recovered revenue, not against a billing competitor — you are selling money back, and nobody negotiates hard over a positive-return line item.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
THE STANDARD: Charging a percentage of your customers' subscription revenue is the strongest expansion mechanism in B2B — and it makes you visible, expensive and audited exactly when your customers scale.
RULE 1 — PERCENTAGE-OF-VOLUME PRICING BECOMES INDEFENSIBLE AT SCALE. Once a customer processes serious volume, your fee is a large line item for a service they can replicate. The biggest, best customers are structurally the most likely to leave.
RULE 2 — THE PAYMENT PROCESSORS GIVE THIS AWAY. Stripe Billing and Adyen bundle subscription management with the rails customers already use. Free-with-processing is the price you compete against.
RULE 3 — YOUR REVENUE IS A DERIVATIVE OF YOUR CUSTOMERS' CHURN. Billing platforms serve subscription businesses; when their subscriber counts fall, your active-subscriber fee and transaction fee fall together, with no churn event.
RULE 4 — BILLING IS COMPLIANCE-ADJACENT, WHICH SLOWS EXIT AND DOES NOT PREVENT IT. Migration is painful and audited, so decline appears as flat expansion for years before logos move.
RULE 5 — THE CATEGORY LEADER'S FATE IS THE CATEGORY'S WARNING. Zuora — which defined this market — exited to Silver Lake/GIC at $1.7B (~3.7x revenue) with 101% retention. Assume the same ceiling applies.
NOT DISCLOSED: Recurly does not publish revenue, ARR or retention; it has been backed by Accel-KKR since 2019.
Where the model can break
4
MOTION
LinkedIn: https://www.linkedin.com/company/recurly/ | Twitter: https://twitter.com/recurly
GROWTH EXPANSION MODEL
COMPETITIVE STRATEGY
motion ge cs
Product Line Expansion, Market Development
HOW THEY EXPAND
Core subscription billing → advanced dunning management → revenue recognition automation → subscription analytics and forecasting → global payment gateway support (multi-currency, regional payment methods) → enterprise revenue management. Expanding into adjacent billing models (usage-based billing, hybrid subscription + usage) as SaaS companies increasingly adopt consumption-based pricing alongside their core subscription revenue.
Differentiation, Bypass Attack
HOW THEY COMPETE
Recurly bypasses direct competition with Stripe Billing (far more developer mindshare and distribution through Stripe's ecosystem) by positioning as the gateway-agnostic subscription management layer above payment processing — you use Recurly with Stripe, not instead of Stripe. This bypass converts Stripe from a competitor into a complementary payment gateway, removing the most common objection ('we already use Stripe') by making the Stripe integration a selling point.
GROWTH ENGINE
GTM
ge n gtm
API Ecosystem Growth, Content Flywheel
Each developer who integrates Recurly into a subscription product creates a technical switching cost that compounds with every billing logic rule, coupon, plan, and subscriber record added to the platform. The API ecosystem compounds as more payment gateways, CRMs, and ERPs build Recurly integrations — each integration makes Recurly the natural center of the subscription business's financial data stack.
Developer documentation-first self-serve integration + enterprise sales to subscription businesses processing $1M+ ARR + ROI calculator content for dunning recovery + developer community presence.
SUSTAINING MOATS
Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)
moat
Migrating a subscription billing platform with thousands of active subscribers, complex billing logic (trials, discounts, multi-currency plans, upgrade paths), and years of revenue recognition history is among the most technically risky infrastructure migrations a subscription business can undertake. Failed migrations create billing errors that directly damage subscriber relationships. The integration depth (embedded in the product's codebase, connected to the CRM, feeding the revenue recognition system) makes Recurly a structural component of the business rather than a replaceable vendor.
| MOAT INTELLIGENCE
THE STANDARD: In billing, the moat is migration risk, not features. Nobody reprices their revenue plumbing to save money — but they will do it to change business model.
RULE 1 — THE SWITCHING COST IS ACTIVE SUBSCRIPTIONS, NOT CONFIGURATION. Migrating live recurring payments risks failed charges, involuntary churn and revenue-recognition breaks in the same week. That fear is your retention.
RULE 2 — DUNNING AND RECOVERY IS THE MEASURABLE ROI THAT DEFENDS PRICING. Failed-payment recovery is directly attributable revenue — the only argument that survives procurement.
RULE 3 — THE CATEGORY IS BEING REPRICED AROUND THE UNIT OF VALUE. Subscription-era architectures count seats and periods; AI-era buyers count events. Verified in this dataset: Zuora, the category creator at roughly $460M revenue, went private at $1.7B while Stripe paid a reported ~$1B for five-year-old Metronome.
RULE 4 — PSP-ADJACENT BILLING IS THE STRUCTURAL THREAT. Stripe Billing ships with the payment rail the customer already uses; standalone billing must be materially better to survive the convenience gap.
EVIDENCE:
- Subscription management and recurring billing — plans, entitlements, dunning, revenue recognition, analytics — sold to mid-market and enterprise subscription businesses. Accel-KKR has been the controlling investor.
- I DID NOT VERIFY CURRENT OWNERSHIP, REVENUE, CUSTOMER COUNT OR HEADCOUNT. No disclosure obligation; any figure is an estimate.
- Competitive reality: Stripe Billing, Chargebee, Zuora, Maxio, Paddle (merchant of record), plus usage-metering specialists Metronome and Orb.
THE SIGNAL: your customers stay because moving is frightening, not because you are loved. That protects you from competitors and not from a change in how the market counts value.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — SELL THE FAILURE MODE, NOT THE FEATURE
Subscription billing is bought because payments fail, dunning is manual and revenue leaks invisibly. Lead with recovered revenue.
Target subscription-native companies too complex for a gateway and too small for enterprise billing.
REFUSE: becoming a processor. Processor-neutrality is the position.
$1–5M ARR — PRICE ON VOLUME PROCESSED, WITH A FLOOR
Volume pricing converts your customer's growth into yours; the floor protects you when their volume falls.
WATCH: recovered revenue per customer, reported monthly. It is the renewal argument.
$5–10M ARR — MAKE CHURN MANAGEMENT THE SECOND PRODUCT
Dunning, retries, pause-instead-of-cancel and win-back are worth more than invoicing.
Publish subscription benchmarks from aggregate volume — it becomes the category's vocabulary.
$10–50M ARR — DEFEND AGAINST THE PROCESSOR BUNDLING BILLING
Stripe Billing and equivalents are effectively free to customers already paying the processor. Depth and neutrality are the only defences.
Move up into revenue recognition and compliance, where the purchase becomes a risk decision.
$50–100M ARR — TAKE THE CONTROL INVESTMENT WHILE GROWTH IS STRONG
Accel-KKR took a majority position in 2019; the company has operated under that ownership since.
NOTE PLAINLY: no ARR disclosed; third-party estimates exist and disagree.
$100M+ ARR — CONSOLIDATION, NOT BREAKOUT
Billing is a feature of larger commerce and finance platforms at this scale. Independence requires owning revenue recognition or a vertical.
Rule: never build a business whose core capability the processor beneath you can ship for free — unless depth and neutrality are your entire strategy.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: In infrastructure, the developer who writes the integration is the real decision-maker — documentation and API design are the sales motion, and the deployed integration is the switching cost.
SEQUENCE:
1. Sit on top of existing payment rails rather than competing with them — no processing licence, instant gateway compatibility.
2. Optimise for the engineer: API elegance, documentation quality, sandbox quality. These are conversion assets, not developer relations spend.
3. Make the integration deep enough to become a technical switching cost, not just a contractual one.
4. Monetise on a mix of subscription and transaction volume so revenue grows with the customer's billings.
5. Sell dunning and revenue-recovery outcomes — recovered failed payments are the clearest ROI in the category.
WHAT WORKED:
- Developer-led adoption in a category where the budget owner isn't the evaluator.
- Embedded integration code becoming genuinely expensive to remove — the strongest lock-in available to middleware.
CAUTIONS:
1. STRIPE BILLING IS THE STRUCTURAL THREAT — the processor bundling billing into what the customer already uses. Adequate and already-there, again.
2. BILLING HAS NEAR-ZERO ERROR TOLERANCE. Mistakes cost customers real revenue and trust immediately, which makes operational rigour the actual product.
3. THE CATEGORY IS SQUEEZED BETWEEN ZUORA (ENTERPRISE) AND CHARGEBEE (SMB); current ARR and ownership details are undisclosed.
bottom of page