Products and environments
List the selected game set, sites or brands, currencies, sandbox and production environments, and any separately scoped configuration work.
Pricing policy
Price the agreed scope,
not a vague bundle.
FastGamesAPI commercial terms are prepared for the implementation being evaluated. The useful comparison is not one headline number; it is the charging basis, included game and environment scope, operational responsibilities and the conditions that change the price.
Required proposal fields
A commercial proposal should answer these before signature.
Keep the definitions in the written proposal so finance, product and engineering are comparing the same implementation.
How the fee is calculated
State whether the proposal uses a fixed platform component, a revenue-linked component or an agreed combination, with each term defined.
Which records control billing
Define the reporting period, source records, adjustments, currency treatment and the reconciliation route for a disputed amount.
What the base scope covers
Identify onboarding, integration support, routine releases, documentation and standard operational assistance included in the proposal.
What needs separate approval
Call out custom development, exceptional support, third-party work or additional delivery requirements before they create cost.
When terms are reviewed
Record notice periods, renewal or review points, scope-change approval and the treatment of material changes to the selected implementation.
Prepare the quote
Bring the inputs that make the proposal specific.
A useful pricing conversation begins after the intended relationship is clear. Share whether you are evaluating as an operator, aggregator or game team; the game families in scope; the expected environments; wallet and integration ownership; currencies; desired support path; and any required customisation. If an input is still unknown, it should appear as an assumption rather than disappear from the proposal.
No numeric rate, minimum commitment or discount is published on this page. Those values must come from the current written proposal and its stated validity period. This prevents an old web figure from being mistaken for a binding offer and keeps exceptions visible to both sides.
- Use one scope table shared by commercial and technical reviewers.
- Define every metric used to calculate a variable charge.
- Separate included support from separately approved work.
- Record taxes, currency and payment assumptions in the proposal.
- Compare total responsibilities, not only the headline rate.
Pair the proposal with the integration brief and acceptance criteria so priced scope and launch scope remain aligned.