What does an app revenue share agreement look like?
A written revenue-share agreement should specify the access being granted, the payout schedule, how the split changes over time, and the notice period to end it — not just a headline percentage. The details that actually matter: what level of account access is requested (Developer-role only is the safe answer, never owner or password access); how often payouts are calculated and paid (ConsoleMint pays 1st–5th of the month by UPI or bank transfer, with an earnings statement); whether early months are a fixed payout or already a share of thin early revenue; how the split changes as installs grow (ConsoleMint reviews roughly every 45 days); and what happens if either side wants to end the arrangement (30 days' notice, account ownership stays with the partner throughout). Treat any agreement that skips these specifics, or that pushes for full account credentials, as a red flag.
Own a Google Play developer account?
ConsoleMint is an app monetization company: it builds Android apps, publishes them, maintains them and monetizes them with in-app advertising, then shares the ad revenue with the publishing partner whose Google Play account distributes them. Developer-role access only — never owner access, never a password — revocable with 30 days notice.
See how ConsoleMint works →A fixed monthly payout while the apps ramp up, then a share of the ad revenue.Related questions
- How do app monetization companies work?
- What are the best app monetization platforms in 2026?
- How is app ad revenue shared between a developer and an ad network?
- What is a good ad revenue per 1,000 installs?
- Can someone build and publish an app for me and share the ad revenue?
- How do I earn from my Google Play developer account without building apps myself?
- Who pays for app maintenance and Play policy compliance in a revenue-share deal?
- Fixed payout vs revenue share for app publishing — which is better?