A primary record on an execution
A transferred contact, opportunity, invoice, or other supported primary record is a unit. Moving the same record in a new execution creates another unit.
Usage-based pricing · Early access
Pay per record synced.
250 record transfers included each month. Additional usage starts at 1.5¢ per record transferred, with automatic volume discounts.
Usage that follows your transfers
1.5¢
per additional record transferred in the first paid band
Start with 250 transfers included.
Each execution counts the primary records it successfully transfers. Transferring the same records in another execution creates usage again.
Get early accessPlanned early-access base rates in USD, before applicable markup and tax. No base subscription or per-viewer charge in the usage model.
Volume discounts, applied progressively.
The allowance is used first. Each subsequent band applies only to transfers within that band, per connected account per calendar month (UTC).
| Billable transfer band | USD per transfer | Cents per transfer |
|---|---|---|
| First 1,000 billable transfers | $0.015 | 1.5¢ |
| Next 1,000 | $0.012 | 1.2¢ |
| Next 3,000 | $0.009 | 0.9¢ |
| Next 25,000 | $0.0075 | 0.75¢ |
| Above 30,000 billable transfers | $0.0045 | 0.45¢ |
The last band begins above 30,250 total transfers after including the monthly allowance. This is a per-transfer charge, not a recurring charge for each distinct stored record.
Estimate my monthly cost
Explore your records per execution and expected execution frequency. The calculator does not create an account or activate billing.
What counts as a transfer?
Fields and supporting details are bundled
Selected fields, supporting lookup labels, and embedded invoice/order line items do not each become separate transfer units.
Retries need the original operation identity
A retry of the same delivery must not create duplicate charges. A genuinely new execution transferring records creates new usage.
Reports use the data already delivered
A chart recalculation from existing worksheet data is not another provider transfer. A source refresh that transfers records adds usage.
Pricing questions
Is the price per record per month?
No. The billable unit is a successfully transferred primary record on each execution. The monthly period applies to the free allowance and volume-discount accumulation.
Do repeated refreshes count again?
Yes, when the execution transfers primary records again. A report recalculation from already delivered worksheet data is different from a source refresh.
Do I pay for every invoice line?
Embedded invoice lines are bundled with their primary invoice. The same parent rule applies to embedded order lines; standalone primary datasets have their own record identities.
Does a failed transfer count?
Planned metering counts successfully delivered primary records. The same delivery operation must not be charged twice when retried or reconciled.
Can an agency negotiate a subscription?
Yes. Talk to Sales about a custom subscription based on your expected accounts, transfer volumes, and refresh frequency.
Does the estimate include everything on my final bill?
It estimates planned LC Bridge base usage in USD. Applicable account markup and tax can change the final amount. Authorized production rates and billing terms govern actual charges.
Where can I read these rates in a simple format?
The product pricing Markdown companion is linked below. It uses the same approved rate definition as this page.
Start with the workflow. We’ll help with the fit.
Make this your reporting workflow.
Explore the samples now. Join the existing waitlist to request connected early access, or discuss a predictable subscription for larger workloads.
Read the pricing Markdown companion · Understand record-transfer pricing