August 2022 Summaries

The text discusses the technical challenges involved in building a usage-based metering and pricing system, focusing on key tenets such as high availability, reliability, scalability, and frugality. It provides guidelines for achieving these tenets, including using horizontally scalable services, setting up across multiple availability zones, configuring backups, automating testing, and minimizing costs through burstable instance types. The text also covers application-level aspects such as accuracy, developer friendliness, robustness, and flexibility, with guidelines for ensuring idempotency in event processing, designing for the long term, and providing native integrations with popular tools and frameworks. Additionally, it emphasizes the importance of high performance, security, and observability, with recommendations for stress testing services, tracking system metrics, monitoring application performance, and using log aggregation systems. The text concludes by mentioning the trade-offs made in their previous venture and invites readers to share their experiences on implementing these tenets in their systems.

A billing system with usage based pricing typically consists of Event Sources, UBP Tool, Collection System, and Account State Manager. However, building such a system presents several challenges including scalability, customization, configurability, robustness, and reliability. Keyser Soze refers to the elusive dream of creating an internal UBP tool that can be completely built and forgotten. Some key considerations for designing a usage-based pricing system include idempotency, one-off invoices, customer acquisition initiatives, just in time changes, access control & approvals, account for bugs or outages in event sources, geographic expansion, reporting & projections, and managing the service itself. These challenges require significant investment of time, effort, and funds, making outsourcing internal tooling for pricing a viable option.

The text discusses the journey of a startup named Hypto, which evolved from being a B2C offers app to a neo-bank for SMEs and eventually became a payments infrastructure company supporting crypto/web3 platforms in India. Despite becoming a market leader in this space, Hypto faced challenges due to macroeconomic factors outside its control. The founders decided to pivot the business after realizing that their biggest problem was capturing value from the transactions they processed. They discovered that many SaaS companies face similar issues and started developing Togai, a low-code usage-based pricing platform for SaaS companies to observe, measure, and compute revenue metrics from product usage data without developer effort. The name "Togai" is derived from the Tamil word meaning value, reflecting their mission to help businesses unlock untapped value in their operations.

The text discusses the evolution of software pricing strategies and advocates for usage-based pricing (UBP) as the most beneficial model for both buyers and sellers. It explains how UBP has evolved over time, from being a cost center to becoming value-adding with cloud adoption. The ideal solution involves minimizing the gap between value and price at every point in time through a consumption-based pricing model. However, adoption of UBP has been slow due to the complexity of building accurate and reliable usage measurement infrastructure. The text also introduces "pricing infrastructure" as the set of tools that help implement various pricing strategies for software companies. It highlights Togai's vision of creating an end-to-end pricing infrastructure for SaaS, which involves monitoring, measuring, aggregating, analyzing, gatekeeping, and experimenting with different pricing strategies. The mission is to make pricing a growth lever for SaaS by enabling data-driven decision-making in this area.