Begin with accepted outcomes
The relevant unit is usually an accepted business result: a verified export, a correctly prepared draft, or a reconciled record. A cheap attempted run is not necessarily a cheap completed task. Our editorial cost model therefore separates attempted runs, accepted outputs, retries, and manual interventions before applying any vendor rate.
Use the structured pricing snapshots on this site for current public inputs. Their dates and units matter. Do not mix a subscription entry price with a per-hour infrastructure rate or assume included credits cover your entire workload. A missing public unit price is an unknown input, not zero.
Build a layered estimate
Model spend depends on the requests and observations consumed across the run. Runtime spend depends on session duration and any minimum billing increments. Proxy or data-transfer charges may be separate. An agent service may add its own fee. Include storage and operational review if they are material to the workload.
Write down whether each term is included in another plan. Double-counting a bundled model charge overstates cost; omitting an external model key understates it. A calculator should show assumptions, units, and excluded costs so a reader can adapt it rather than mistake it for a quote.
Use your pilot distribution
Measure a sample of representative runs and keep both the median and slower cases. Login delays, unfamiliar layouts, large files, and approval waits may extend sessions. Distinguish browser time spent actively executing from time held open while waiting for a person, because the provider’s billing rules may treat both as session duration.
Estimate accepted outcomes from the pilot rather than a generic benchmark percentage. If a job needs multiple portal visits, evaluate the whole job, including partial completion. A component benchmark does not establish your end-to-end cost per accepted result.
Control spend without hiding failures
Set per-run time, step, and cost limits. Stop repeated navigation that produces no new evidence. Close unused sessions and avoid sending redundant observations where the integration permits it. Before adding concurrency, check the application’s access policy and whether parallel work can create conflicting updates.
Our calculator is a planning tool. It cannot promise a monthly bill or measured return on investment. Reverify rates before procurement and rerun the estimate when task shape, model choice, included allowances, or success criteria change. Keep failed-run costs visible; removing them makes a spreadsheet look better while making the decision less useful.