Design Pickle • Case Study
Billing + monetization system
Rebuilt billing and monetization systems to unlock subscriptions, usage-based pricing, expansion revenue, and future marketplace economics.
Why this case matters
Billing was a growth constraint, not a back-office problem.
The business wanted to move toward a more scalable SaaS and marketplace model, but the legacy billing foundation could not support the pricing, packaging, and monetization flexibility required to get there.
I rebuilt billing as part of the product strategy itself. That mattered because better billing was not just about cleaner payments. It was about enabling the next phase of the business.
Case Study
Context
Legacy billing was limiting strategy.
As Design Pickle evolved toward a more scalable product and platform model, billing became one of the most important constraints. The legacy state included fragmented Stripe API usage, inconsistent architecture, custom payment flows, and limited support for more flexible pricing models.
Without a stronger billing system, subscriptions, add-ons, usage-based pricing, overages, and future partner payout scenarios would remain constrained.
What I did
Turned billing into revenue architecture.
I modernized the billing foundation around stronger Stripe patterns and reduced the patchwork of inconsistent legacy implementations.
I treated billing as a product system that directly affects conversion, retention, upsell, expansion revenue, customer experience, and pricing flexibility.
I also sequenced complexity instead of overbuilding up front, focusing first on the highest-value monetization capabilities and creating a stronger path to future marketplace economics over time.
Outcome(s)
A stronger foundation for monetization.
Enabled SaaS monetization more effectively, increased ASP and monetization flexibility, improved the company’s ability to support expansion revenue, reduced monetization bottlenecks that were blocking the broader platform strategy, and created a stronger foundation for future partner and marketplace economics.
Why it matters
Billing is a product surface.
This work demonstrates that I understand billing not as backend support, but as revenue architecture. That matters for SaaS, marketplace, fintech, and platform businesses because billing systems either enable or constrain how the business makes money.