Here's a classic startup / side project scenario: You quickly write your Flutter app and start with a Firestore database. You probably also use Firebase Cloud Functions as serverless backend. By time, your projects gets bigger and the user base starts to grow, quickly followed by your Google Cloud bill. As soon as the free quotas are gone, the battle against high read operations - which are the main cause for high bills - beginns. This session demonstrates 1. How to first identify the source of Google Cloud costs in your billing section including the right tooling to keep an eye on your cloud behaviour. 2. How to reduce read operation by design in the first place for Firestore 3. How to track down the source for your high read operations in your Flutter Client / Firebase Cloud Functions to be able to solve the problem. The talk will showcase some Flutter and Cloud Functions code and compare different architectural approaches as well as simple ways to read data and showcase best practices.