Geo-grid budget planner
Estimate the scan workload before you buy credits. Change the grid size, keywords, locations and monthly scan runs to see what drives usage.
Plan one month of scans
The formula is visible
Grid side² × keywords × locations × monthly runs = grid points. A 7×7 grid, five keywords, 20 locations and four runs uses 19,600 points. Optional analysis is charged per report in some products: keywords × locations × runs × analysis units.
Four runs means exactly four, not an average calendar month of weekly scans. Add a fifth run when your schedule needs one. Include extra locations for separately scanned competitors and repeat the calculation for additional platforms.
Changing from 7×7 to 9×9 raises the same workload from 19,600 to 32,400 points. A larger grid is useful only if it answers a real coverage question.
Points are not a universal price
Vendors define credits differently. Confirm exclusions, AI charges, API fees, billing period and expiry. This calculator assumes a square grid and one planning unit per grid point. It does not query Google, measure your ranking or promise equivalent results across tools.
The public Local Falcon pricing explanation describes point-based credits and optional per-report analysis. Check the current rules before mapping these numbers to a package. Inputs stay in this page; the calculator sends no inputs to a server. The site’s normal analytics and advertising still apply.
Turn the workload into a shortlist
- Compare geo-grid tools for reporting and scan requirements.
- Read the pricing reference for billing caveats.
- Local Falcon review for a scan-focused workflow.
- Semrush Local review when GBP operations and listings also matter.
Method: transparent arithmetic, reviewed 14 September 2026. Our editorial evidence standard.