Calculate GEO Tool Capacity: Prompts, Models, and Tracking Units
Use a 24-keyword, 24-prompt example to distinguish search tracking units from AI response counts. Compare taxes, billing periods, and add-ons consistently.
In this article
Keyword count alone cannot determine the right plan. Sum active search channels per keyword and calculate prompt/model workload separately.
Calculate search tracking units
Surfaze sums the selected search channels of each active keyword. Prompt runs across four AI models are separate from search tracking units. Provider API call count and customer-facing capacity are also different concepts.
A 123-unit example
| Targets | Count | Channels | Units |
|---|---|---|---|
| Korean keywords | 17 | Google/Naver desktop, mobile, and two AI channels: 6 | 102 |
| English keywords | 7 | Google desktop, mobile, AI Overview: 3 | 21 |
| Total | 24 | 123 |
Record AI responses separately
Twenty-four prompts across four channels once daily plan 96 observations per day, or 672 over seven days. Failures and missed runs reduce successful observations. These are not users or real customer query volumes.
Commercial comparison checklist
- Check keyword, search-unit, and prompt caps independently.
- Record models, projects, competitors, and team seats.
- Separate annual effective monthly pricing from monthly billing.
- Normalize Korean pre-VAT prices and international tax treatment.
- Check whether additional capacity is self-serve or sales-assisted.
Where to verify in Surfaze
Inspect active channels in keyword settings and compare them with the billing usage view. This example fits the Pro limits verified on September 10, 2026: 75 keywords, 75 prompts, and 300 units. Recheck the official plan when purchasing.
Build an eight-week usage table before reading price cards
Usage often grows in weeks three and four as the team finds new competitors, adds English prompts, and separates desktop from mobile. Forecast realistic usage with fifteen to twenty percent room, rather than pricing only the day-one setup.
Do not reserve capacity the owner cannot review. Three hundred prompts create no analytical value when the team can inspect only thirty original answers per week. Put collected volume and reviewable volume in adjacent columns.
| Period | Search | AI prompts | Human review | Expected change |
|---|---|---|---|---|
| Weeks 1–2 | baseline portfolio | 15–24 core questions | twenty changed answers | correct setup and labels |
| Weeks 3–4 | +10–15% | add comparison gaps | thirty purchase answers | discover competitors and sources |
| Weeks 5–6 | hold steady | split languages or markets | answers tied to edited pages | validate content changes |
| Weeks 7–8 | remove unused units | retire duplicates | recurring patterns | choose next-quarter capacity |
Agencies should model the largest client, not the average
Five clients with twenty prompts each look like one hundred prompts, but one client spanning three markets and four models can hit a project or model limit first. Model the largest client, several typical clients, and one small client separately.
Seats and permissions also affect cost. Decide whether clients receive read access or a delivered report, and verify where client-level separation becomes available in the plan.
A low subscription can create high operating cost
Time the workflow during the trial. A product that creates an assigned task in thirty minutes can be cheaper than one requiring two hours of Friday reconciliation, even when its invoice is higher.
| Hidden cost | Test | Monthly estimate |
|---|---|---|
| Recreating answers | Can the answer and sources be opened directly? | manual minutes × labor rate |
| Cleaning failures | Are failures separate from missed mentions? | weekly cleanup × four |
| Combining reports | Where do search and AI data meet? | export and spreadsheet time |
| Additional access | Are reviewers and client users included? | seats × price |
| Execution features | Do content or agents consume credits? | expected actions × credits |
Define both upgrade and downgrade conditions
Consider an upgrade when important questions or channels must be removed repeatedly. Consider reducing the portfolio first when prompts go unread, models never enter a report, or search surfaces duplicate no real customer journey.
At the plan review, compare active keywords, tracking units, prompts, normal answers, and original responses actually reviewed. If collection grows while human review remains flat, the operating model may be the constraint. Read Surfaze's plans beside its tracking-unit guide and apply the same calculation to every vendor.
Frequently asked questions
Do seventy-five keywords always equal seventy-five tracking units?
No. Each keyword can consume capacity across active engines, devices, or result surfaces. Sum the combinations you will actually use.
Can AI answer volume be added to search tracking units?
They are different units. Calculate keyword-channel observations and prompt-model-market runs separately, then apply each to the relevant plan limit.