How a buyer can evaluate the product
Merge Unified Launch includes three production linked accounts at no charge, then publishes a paid Launch tier for up to ten. Documentation and sandbox access support a selected-integration test before a larger contract.
The buyer must choose a category and provider, map required objects and fields, confirm permissions, decide whether passthrough is acceptable, handle webhooks and resyncs, and own UI or support when a customer connection fails.
The current Unified page publishes a Launch step and routes Professional and Enterprise to contract pricing. Other Merge products use different units, so Agent Handler or Gateway pricing should not be combined with Unified linked-account economics.
Sources: Merge Unified pricing · Merge documentation · Merge integrations
Evidence a buyer can inspect
| Buyer question | Public evidence | How to use it | Source |
|---|---|---|---|
| Is the named provider listed? | Integration pages identify supported providers by category. | Confirm the exact provider and authentication method. | Integrations |
| Are required fields normalized? | Common-model docs enumerate objects and fields. | Map every must-have read/write field. | Common models |
| What happens outside the common model? | Passthrough can access provider-specific endpoints. | Assess portability and extra maintenance. | Passthrough docs |
| What creates the bill? | Unified Launch is organized around production Linked Accounts. | Forecast active customer connections and growth. | Unified pricing |
Sources: Merge Unified pricing · Merge documentation · Merge integrations · Merge common models
How to use this in your own materials
The best proof for an integration platform is a completed coverage matrix for one commercially important provider. Catalog size establishes breadth; it does not answer field fidelity, write support, permissions, latency or who fixes provider-specific breakage.
Method and limits
We read the listed first-party pages on 2026-09-08 and compared them with our notes from a July 2026 review. We looked at what a technical buyer can verify before contacting sales. We did not test the product or check customer results the vendor reports.
- We did not connect a live third-party account.
- Provider APIs and supported fields can change after the review date.
- Professional and Enterprise minimums, support and overage terms were not public.
Sources: Merge Unified pricing · Merge documentation · Merge integrations · Merge common models
Sources and dates
- Merge Unified pricing ↗Reviewed 2026-09-08
- Merge documentation ↗Reviewed 2026-09-08
- Merge integrations ↗Reviewed 2026-09-08
- Merge common models ↗Reviewed 2026-09-08
Found an error or a changed source? Send a correction.
Apply this to your company
Draft your next buyer document from approved claims.
Briefs and decks from approved facts, every claim sourced.
See the demo →