Affiliate Program Budget Calculator 2026: Grids & Template

A 12-month affiliate program budget totals $921,280 for 2,830 first-time depositors in the worked plan on this page, an all-in cost of $326 per FTD. Only 48% of that is commission: $476,000, or 52% of the budget, is platform, team and creative cost that would exist even if commission were zero. The grids below let a budget be assembled by lookup rather than by spreadsheet: expected FTDs at spend levels from $10,000 to $500,000, commission liability across 5 CPA and RevShare mix scenarios, operating cost lines by program size, a filled 12-month template, and ROI at 3 performance assumptions. Every number is derived from the stated assumptions and can be recalculated with the formulas provided.

Budget Summary: The Three Cost Blocks

Three blocks make up every affiliate program budget: acquisition commission paid per conversion, ongoing revenue share accrued against future NGR, and fixed operating cost covering the tracking platform, headcount and creative. Budgets fail when the second block is modelled as if it behaved like the first. CPA is a cash cost in the month of conversion and then stops; RevShare is a liability that starts small, compounds across cohorts, and is still accruing in year three. The summary below is the shape of a budget rather than a number, and it is the frame for every grid that follows.

The share column carries the most useful single insight on this page. In a first-year program ramping from 50 to 380 FTDs per month, operating cost is the majority of the budget and revenue share is barely a tenth of it. Both proportions invert by year three: operating cost flattens while commission scales, and the accrued RevShare book from three years of cohorts becomes the largest line. A budget built on year-one ratios and then scaled linearly will be wrong in both directions at once.

Grid 1: Expected FTDs by Monthly Spend and Cost per FTD

Expected FTDs equal acquisition spend divided by blended cost per FTD, which at $50,000 per month and a $200 blended cost gives 250 first-time depositors. The grid below precomputes that division across 6 spend levels and 6 cost points so a planning number can be read directly. Blended cost per FTD here means total commission paid divided by qualified FTDs delivered, including any CPA, hybrid uplift and RevShare paid within the period; it is not the headline CPA on the rate card, which is always lower.

Grid 2: Expected FTDs by Traffic Volume and Conversion Rate

Click-to-FTD conversion of 2% on 50,000 monthly clicks produces 1,000 first-time depositors, and that single line explains most disagreements between affiliate teams and finance. Grid 1 sizes the budget from money; Grid 2 sizes it from traffic, and the two should be reconciled before a budget is signed. Where they disagree, the traffic view is usually right, because partner inventory is finite in a way that budget is not.

Two reconciliation rules apply. First, take the lower of the Grid 1 and Grid 2 answers as the plan number, because a budget that assumes traffic which does not exist simply underspends and misses the target anyway. Second, keep click-to-FTD as one metric rather than decomposing it into click-to-registration and registration-to-FTD at the budget stage: the decomposed version belongs in the optimisation conversation, and the Track360 EPC and CPA reference covers the full funnel arithmetic.

Grid 3: Commission Liability by CPA and RevShare Mix

12-month commission liability per 1,000 FTDs ranges from $250,000 on a pure CPA program to $117,700 on a pure RevShare program, a 2.1x spread on identical acquisition volume. That spread is not a saving, it is a timing difference plus a risk transfer: RevShare defers cost and keeps accruing after month 12, while CPA settles the liability permanently at conversion. The grid below holds volume constant at 1,000 FTDs and varies only the share of those FTDs acquired on each model.

Extend the horizon and the ranking changes. The same cohort under 30% RevShare accrues about $143 per FTD by month 24 and roughly $155 by month 36, because cumulative NGR per player rises from $392 at 12 months to about $477 at 24 months under a 12% monthly decay assumption. A pure RevShare program therefore crosses a $150 CPA offer somewhere between month 24 and month 30 for this player profile. Which side of that crossover a program wants to sit on is a cashflow and certainty decision rather than a cost-minimisation one, and the Track360 RevShare versus CPA calculator carries the full breakeven grids for that specific question.

Grid 4: Platform, Team and Creative Cost Lines by Program Size

Non-commission operating cost runs $9,000 to $19,000 per month for a program under 100 active partners and $77,000 to $195,000 for a program above 500, which is where most first-year budgets are wrong by a factor of two. These lines scale with partner count and market count, not with revenue, so a program that doubles revenue without adding partners barely moves them, while a program that adds two languages and a compliance regime moves several at once. Ranges are Track360 estimates for 2026 planning purposes and should be replaced with real quotes and salary bands before a budget is approved.

Three lines are habitually missed. Payment processing, FX and payout fees look trivial as a percentage and are not: at 1.5% of a $700,000 annual payout book that is $10,500, more than a small program's entire platform spend. Compliance and fraud review is treated as a manager's spare time until the first clawback dispute, at which point it becomes a role. Localisation is budgeted once as a translation project rather than as an ongoing line, even though every new creative set, terms update and landing page needs the same treatment in every language the program runs.

The 12-Month Budget Template

A program ramping from 50 to 380 FTDs per month costs $921,280 in its first 12 months and delivers 2,830 first-time depositors, an all-in cost of $326 per FTD. The template below is filled with a 50/50 CPA and RevShare mix at a $250 CPA and 30% RevShare, $60 month-one NGR per player, and 12% monthly cohort decay. Replace the FTD column with a program's own ramp and the other columns recalculate from the formulas in the methodology section; the structure is the reusable part, not the specific figures.

Read the RevShare column carefully before reusing this template. It totals $91,530 across the year, only 21% of the $445,280 of commission booked, because a ramping program has almost no accrued cohort base in its early months. That column roughly triples in year two on the same acquisition volume, purely from cohorts carried forward, and a budget that treats year one as the steady state will understate year-two commission by a wide margin. Carry a forward-liability line for the accrued RevShare book into the following year's plan and reserve against it.

ROI Scenarios at Three Performance Assumptions

The same $1.2 million annual budget returns -19.2%, +30.7% or +114.1% at 12 months depending only on cost per FTD and 12-month NGR per player, which is the honest range a first-year program should be defended on. The scenarios below vary two inputs and hold everything else constant: $360,000 of the budget is non-commission operating cost in all three cases, leaving $840,000 of commission capacity. ROI here is 12-month NGR generated by the acquired cohort against total program budget, before any other marketing or platform cost outside the affiliate channel.

Three readings matter more than the headline percentages. First, the conservative case is negative at 12 months and roughly breakeven at 24, which is normal for a first-year program and is the reason affiliate budgets should be defended on a 24-month horizon rather than a fiscal year. Second, the gap between conservative and base is driven as much by NGR per player as by cost per FTD, so partner quality is worth at least as much attention as rate negotiation. Third, the 24-month columns show NGR from the same cohort without adding the second year of RevShare accrual against it, so they overstate true 24-month ROI for any program with a significant RevShare share; treat them as an upper bound. Benchmarks for what good looks like across verticals sit in the Track360 affiliate program ROI calculator and benchmarks reference rather than here.

How to Build Your Affiliate Program Budget: Step by Step

Nine steps turn the grids above into a defensible budget, and the order matters because each step constrains the next. Work top to bottom and resist the temptation to start from a target spend figure, which is how programs end up with a number that cannot be delivered by the partner base that actually exists.

1. Set the FTD target and its monthly ramp. Start from the commercial target the program is accountable for, then spread it as a ramp rather than a flat line, because month one cannot deliver month twelve's volume.
2. Fix the commission model mix. Decide what share of FTDs will be acquired on CPA, RevShare and hybrid, then read the 12-month liability off Grid 3. This is the single decision with the largest effect on cashflow shape.
3. Price the blended cost per FTD. Take the rate card, add hybrid uplift and expected RevShare paid within the period, and use that blended figure in Grid 1, not the headline CPA.
4. Reconcile against traffic. Run the same FTD target through Grid 2 at a realistic click-to-FTD conversion rate and take the lower of the two answers as the plan number.
5. Build the operating cost stack. Use Grid 4 to size platform, headcount, compliance, creative, localisation, events and payment fees for the program size you will be at in month twelve, not month one.
6. Lay it out month by month. Fill the 12-month template, letting RevShare accrue across cohorts rather than applying a flat monthly figure, so the back-loaded shape of the liability is visible.
7. Add a forward-liability line. Record the accrued RevShare book carried into year two as a separate commitment, and reserve against it in the same way a finance team reserves for any deferred obligation.
8. Stress test at three assumptions. Run conservative, base and aggressive cases on cost per FTD and NGR per player, and present all three, because a single-point budget invites a single-point challenge.
9. Add a contingency of 8% to 12%. Clawbacks, fraud writeoffs, FX movement on cross-border payouts and one unplanned market launch will consume it, and a budget without it is renegotiated in month seven.

Methodology & Assumptions

Six stated assumptions produce every figure on this page, applied to published formulas rather than to survey or third-party benchmark data. The assumptions are: a $250 CPA, a 30% RevShare rate, $60 of month-one NGR per referred player, 12% monthly cohort decay, a 50/50 CPA and RevShare mix in the template, and a ramp from 50 to 380 new FTDs per month. Expected FTDs equal acquisition spend divided by blended cost per FTD, or partner clicks multiplied by click-to-FTD conversion rate. Cumulative NGR per player over n months equals month-one NGR multiplied by the sum of the decay series, which produces $392 at 12 months, $477 at 24 months and about $516 at 36 months on these inputs. RevShare liability equals cumulative cohort NGR multiplied by the RevShare rate. Operating cost ranges are Track360 estimates for 2026 planning, built from platform pricing, salary bands and agency rates observed across iGaming, Forex and prop trading programs, and they are ranges rather than points for that reason.

Three limits are worth stating plainly. The grids assume partner supply exists at the modelled price, which becomes less true as spend rises. Cohort decay is modelled as a smooth monthly percentage, whereas real cohorts decay in steps around bonus expiry, seasonality and payout cycles. And no tax, licensing or jurisdictional cost is included: in high-tax markets the operator margin behind a given RevShare rate can differ by more than the rate itself, which the Track360 gambling tax rates by country reference covers. This page is reviewed quarterly (January, April, July, October), with assumptions restated whenever observed platform pricing or salary bands move materially. Last updated July 18, 2026.

What the Budget Depends on Operationally

Four operational controls decide whether a modelled budget survives contact with a live program, and every one of them is a tracking configuration rather than a strategy choice. Each one maps to a line in the grids above, and each one is a configuration question rather than a strategy question, which is why they are usually discovered late.

• Attribution and conversion capture: server-to-server postback integration rather than pixel-only tracking, so the FTD count the budget is built on matches the FTD count the platform pays on. A 5% attribution gap on a 2,830-FTD plan is 142 conversions of disputed liability.
• Qualification rules: minimum deposit, activity window and market eligibility conditions that decide when a commission event fires. Loosening a qualification rule mid-year is a budget change, not a marketing tweak, and it should be priced before it is approved.
• Fraud detection and clawback: incentivised traffic, multi-accounting and self-referral all inflate FTD counts and therefore CPA spend. The 8% to 12% contingency line exists largely for this, and a clawback policy that is not enforceable in the platform is not a policy.
• Partner portal and reporting cadence: super-affiliate relationships are negotiated on data, and a program that cannot show a partner their own EPC, conversion rate and pending commission in a partner portal pays a premium in every renegotiation. That premium never appears as a budget line but shows up in blended cost per FTD.

The most common affiliate budgeting error is not the commission rate. It is treating revenue share, which is barely a tenth of a first-year budget, as if it were a steady-state cost rather than a liability that triples in year two on the same acquisition volume.