Project overview
CHING is a billing and subscription management platform for Israeli businesses and SaaS companies. When designing the product, the challenge was not to invent a completely new way to manage payments. The category already has mature products, familiar interaction patterns, and clear user expectations. The opportunity was to understand what already works - and use it intentionally.
The Challenge
Products like Stripe have established many of the conventions users now expect from billing platforms. Customers, subscriptions, products, prices, payments, and invoices are all concepts that users may already recognize from other tools. Introducing a completely different structure or interaction model could make CHING feel unfamiliar without creating any real value. For a financial product, familiarity can be an advantage.
The Design Approach
Instead of starting from a blank canvas, I studied established billing products to understand the patterns that have become industry standards. The goal was not to copy individual screens, but to understand the logic behind them:
How is information grouped?
What actions are given the most visual weight?
What terminology do users already understand?
And where does consistency make the product easier to learn?
These patterns became a foundation for CHING's experience.
Familiarity Over Novelty
In some products, differentiation comes from introducing a completely new interaction. In CHING, unnecessary novelty could create friction. Users managing money need to understand what is happening quickly and feel confident before performing actions such as creating a subscription, changing a price, or reviewing a payment. Using familiar conventions reduces the amount of learning required and lets users focus on the task itself. The design principle became simple:
Do not introduce a new pattern unless it solves a real problem.
But Familiar Does Not Mean Blindly Copying
Established patterns are a starting point, not a rulebook. A pattern that works for a large global payment infrastructure product does not automatically fit a smaller, more focused billing platform. Throughout the product, I looked for moments where existing conventions added unnecessary complexity or did not match CHING's users and their workflows. In those cases, the goal was to preserve what felt familiar while simplifying the experience around it.