SaaS Browser recently published a case study on Flexilay — a candid conversation with our founder, Toby, about why he built the platform, the mistakes made along the way, and what's coming next. It's one of the clearest tellings of why Flexilay exists, so we wanted to share the highlights here.
Read the full case study on SaaS Browser → How Flexilay got started
The problem that wouldn't go away
The idea didn't come from a market report. It came from watching the same thing happen thousands of times a day: a customer browses a store, carefully builds a cart, reaches checkout — and disappears. Not because they didn't want the product, but because they couldn't justify the full amount that day.
Merchants were left with two bad options: lose the sale, or push customers toward a buy-now-pay-later product built on credit and steep fees. Meanwhile, people kept asking for old-fashioned layby — which was simply too painful to run manually.
Nobody had modernised layby for ecommerce, at least not well. Customers wanted a responsible way to budget without taking on debt, and merchants wanted a simple way to recover abandoned carts without adding administration.
That gap is what Flexilay was built to close.
What worked: talking to merchants, not building in isolation
The biggest growth lever wasn't advertising or social media — it was direct conversations with merchants. Demos, early prototypes, and store owners invited to criticise everything. Those conversations reshaped the product, and some of our best features came straight out of them rather than the original roadmap.
What failed: assuming customers were the audience
Early on, we poured time into highly configurable payment schedules, assuming flexibility alone would drive adoption. It didn't. Merchants cared far more about operational simplicity, automation, and reducing abandoned carts than about dozens of payment options.
That lesson reset our philosophy: every feature now has to solve a measurable merchant problem and make running a store easier — not just be technically interesting.
Answering the questions merchants actually ask
The most common questions come from merchants, not shoppers. Their first concern is almost always cash flow — "When do I get paid?" — closely followed by "What happens if a customer stops paying?"
Rather than explaining those away, Flexilay is designed around them:
- Complete visibility over every payment
- Automated reminders to reduce missed installments
- Products released only once payment is complete
- Optional early payout so businesses get cash flow sooner
Customers want something different: transparency and control. That's why we invested heavily in a dedicated customer portal showing payment history, remaining balances, and upcoming payments. When customers always know where they stand, they're far more likely to finish the plan.
"We've wanted a modern layby/schedule payments solution for years — finally, we have it." — A Flexilay customer
What most people get wrong about flexible payments
The assumption is that flexible payments are about helping people spend more. We think that's backwards. There's a large, growing group of consumers who actively avoid debt and credit checks, and simply want a disciplined way to budget for the things they want. Traditional layby served them for decades — it just never evolved alongside ecommerce.
The market doesn't need another credit provider. It needs a better payment experience built around responsibility, transparency, and simplicity. (More on that in why Flexilay isn't BNPL.)
What's next
The immediate focus is launching publicly on the Shopify App Store and onboarding our first group of merchants. Beyond that: advanced merchant analytics, abandoned-cart automation, deeper marketing integrations, and enhanced customer self-service — plus expanding beyond Shopify and WooCommerce, with Xero and Odoo integrations already running.
The long-term vision is simple: make Flexilay the default layby and scheduled-payments solution for online commerce, globally.
Huge thanks to SaaS Browser for the feature. Read the full case study → or see how Flexilay works.