How do I estimate the cost of a batch of web tasks?

Run a small, representative batch, check actual browser usage, and use it to estimate your expected workload. Choose a plan that also covers the concurrency you need.

Lexmount plans apply to a project. Concurrency determines how many browser sessions can run at once; Browser hours is the browser time allowance included in the plan. If your tasks call a model API you configure separately, include those model costs in your budget too.

1. Choose representative tasks that cover typical login, page loading, and interaction flows.
2. Compare browser usage before and after the trial, and record model costs and retries.
3. Estimate the budget for your expected task volume, then compare regional plans against your concurrency needs. Close sessions promptly when tasks finish.

Login waits, page loading, and retries affect trial results. Check the console for actual usage and your regional pricing page for renewal and upgrade options.