> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/agency-white-label/customers/charge-customers.md). # Charge customers ### How should my Agency charge my customers? You have the flexibility to set your pricing structure and you can continue to bill your customers directly/offline. However, it's advisable to consider industry standards. Many successful agencies opt for one-time payments to provide their customers with convenience. Here are some advantages of charging a one-time payment: * Instant revenue: You receive the full payment upfront, ensuring immediate revenue for your services. * Simplicity: Billing is straightforward for both you and your customers, eliminating recurring billing concerns. * Lower churn: Typically, lower customer churn as they've invested in the app. Charging in alignment with industry norms can enhance the perceived value of your services and simplify the billing process for both you and your customers. Ultimately, the choice of how to charge your customers should be based on your specific business model, goals, and your understanding of your customers' preferences. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.appmysite.com/agency-white-label/customers/charge-customers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.