Recurly Press Kit

Includes PDF guide, logo image and,
vector image for print.

Download Press Kit (1.2MB) .zip

Guide to choosing a subscription billing provider

Subscription billing models come in a variety of different flavors and apply to many different categories of businesses. However, there are a few common factors that must be considered when selecting the best vendor to handle billing on behalf of your business.

Step One: Define your own billing requirements – what are your needs?

Here is a punch-list of items for you to consider:

Be clear on the structure of your subscription offering:

  • How many subscription plans will you be offering? One plan or multiple plans?
  • What is the billing cycle interval? (Monthly, Quarterly, Bi-Annual, Annual?)
  • Will you offer free trials?
  • Will your subscriptions auto-renew, or terminate on some date?
  • Will your business require one-time payments?
  • Do you need optional items to be added? (Add-ons)

Define how you will you price your subscriptions:

  • Are you charging a flat fee per month?
  • Do you have a variable pricing component? (Requiring ‘metered billing’)
  • Will your pricing change based on usage? (Tiered pricing?)

Communication Requirements:

  • How and when would you like to communicate with your customers?
  • What are your data integration needs? CRM? Finance/Accounting? Mailing lists?
  • How important is it for your billing + subscriber status to be synced up with your application?

EXPERT TIP:

It is very easy to get carried away in the definition process.

Most companies find that they can save a tremendous amount of time, expense and curse words by simplifying wherever possible. Reducing complexity at this stage will also greatly reduce the operational overhead required to manage and account for your billing later on. Remember, you have to live with this system!

Step Two: Items to look for in a subscription billing provider

Think about your businesses end-goals and total cost of ownership (TCO).

Most subscription-based businesses ultimately care about the following:

  • Minimizing Customer Churn
  • Maximizing Lifetime Customer Value (LTV)
  • Maximizing Return on Investment (ROI) – which means minimizing TCO

You cannot achieve these goals if your billing platform doesn’t support key daily functions efficiently. Your billing system should be a valuable tool, not an impediment.

PCI Compliance:

If your vendor is not PCI Level 1 compliant, ‘do not pass go’. You cannot afford to store your customer credit cards with a company that is not invested enough to achieve PCI Level 1 certification.

Functional capabilities:

Daily administration (This is frequently overlooked):

  • Is there a Customer Support console? If so, is it functional? Intuitive to use?
  • Search / Sort / Filter – How easy is it to find accounts?
  • Account changes – How easy is it to make a manual override?
    • Upgrades/Downgrades
    • Pro-ration of accounting? Is this automated or manual?

GotchaReally push on this. Some very expensive vendors require 30+ clicks to make simple manual changes to subscriptions.

Customer Invoicing

Automated – Are customer invoices delivered automatically?

Manual – Can you create invoices manually?

Credits and Refunds (Both whole and partial credits)

This is key functionality to keep your customers happy. It needs to be incredibly easy to issue a credit or a refund.

Transaction History

It is always critical to be able to call up the transaction history for an account in order to provide customer support.

Marketing Support: Coupon and Discount code management

Your business might require coupons or discounts for promotional purposes, or channel discounts. Coupon and discount support needs to be seamless and easy to manage. Not all systems are created equal.

  • How easy is it to set up a new coupon or discount code? (60 sec. max).
  • Can you manually apply coupons or discounts to an account?
  • How flexible is the coupon/discount functionality?
    • One-time, Limited Time, Evergreen applications
    • Percentage discounts vs. absolute dollar off?
    • Expiration date management?
    • Applies to specific billing plans?
    • Limited count offers? “First 500 subscribers receive…”

Error Handling: Credit Card Error and Decline Management

Like it or not, your recurring payments will encounter errors. This is a given when you are charging credit cards on a recurring basis. Cards will be declined for a variety of reasons, and from a variety of sources.

Q: At the highest level, you need to know whether your provider stores credit cards and tokenizes cards in their own environment.

A: If the answer is no, then that vendor cannot remediate credit card errors and declines on your behalf. It’s that simple.

Reporting: Data or Business Insights?

What kind or reporting capabilities do they provide?

Revenue by period, Revenue by plan, Monthly Recurring Revenue (MRR), Cohort analysis, Credit card decline rates, Lifetime value analysis?

Customer Support:

What is the support model? Look at support forums and evaluate quality and timeliness of responses.

Step Three: Evaluate Total Cost of Ownership

Total cost of ownership is often underestimated.

It breaks down simply to the following four buckets:

  1. Cost of Integration (often a hidden cost – Recurly takes days rather than months)
  2. Cost of Administration
  3. Cost of Customer Churn and Non-renewing subscribers (another hidden cost)
  4. Marginal Cost of Billing Service

Is your billing system working for you? Or are you working for your billing system?

Expert Tip:

Most evaluations of subscription billing providers erroneously focus only on #4. Total Cost of Ownership surprises most companies. Ease of integration, ease of use and ease of administration can be very costly. (Employee resignations have occurred over frustration with complex billing systems)

Pricing Gotchas

Be clear on Setup Fees, Cancellation Fees, Extra charges.

(Recurly does not charge for any of these)

Network Availability

Don’t be shy. You’re the customer.

Ask for third party auditing of network uptime and availability reports. [Recurly has proudly maintained 99.994% uptime in 2011]

Final Thoughts:

Expensive ≠ Better

Your subscription billing system should work for you, not the other way around. Paying more for an expensive enterprise ‘solution’ does NOT mean that you get more value.

If you consider the elements from this guide, you will not only be much happier with your ultimate decision, but your business will have a greater chance of success.

If you would like to learn more about Recurly’s capabilities, please contact sales@recurly.com

Leave a Comment

Your email address will not be published. Required fields are marked *

  1. The cost of integrating via Cold Fusion is going to be higher, because it is used by less than 2% of merchants today. Support for CF has been waning all across the web. Nothing personal, it’s just not in demand anymore so it isn’t as high of a priority to support.

  2. @Dan;

    ColdFusion generally writes 1/3rd to 1/4 of the code of most languages extended to “work” with the web. Plus, it’s java bytecode and has more ways to integrate easily out of the box with anything.

    Have you even used it or are you working off outdated hearsay? I work with 4-5 “web” languages a week and CF is no slouch, it tends to trivialize all the web dev work developers want to feel special about.

    Just sayin’.

  3. Sami, although I would have preferred a Java lib, from my perspective Recurly integration has been largely trivial; it’s mostly a case of mapping XML to classes and wrapping it up with REST… which is infinitely easier than developing a complete billing system from scratch (been there, done that…)

  4. Since I was the one who wrote the ColdFusion library, it would have been nice to at least been notified that you were ‘dropping support’ for an open source library that you didn’t even participate in.

    Also, by your same stats page, there are more CF sites than RoR, but you support that. I understand RoR is a much more ‘sexy’ platform than CF, but especially with free app server options like Railo and the next version of CF coming out based on Tomcat and full scripting support we have now, and it is going to be much harder to ignore.

    Anyways… I got a bit screwed when all of the sudden my library stopped working on a project just weeks before launch, so I am going to rewrite it. Don’t think I will be distributing this version though all things considered…