A gateway contract outlasts the demo. Once your first sender goes live, every later sender, every payload change, and every Guidewire release runs through the choice you make now.
Most evaluations spend their hours on feature lists. The questions that decide the outcome sit elsewhere: who reviews the mappings, what happens to incomplete data, and who carries the work when something changes.
This article gives carrier CTOs, CIOs, and Guidewire integration architects ten questions to ask, grouped into five areas. Each one comes with what a complete answer sounds like.
Start With Scope and Fit
The first two questions settle whether the provider covers your Guidewire footprint and how it sits beside what Guidewire already ships. Get these answered before you spend time on anything else.
The ten questions fall into five groups. Use this table to keep the review organized.
Group | Questions | What it settles |
|---|---|---|
Scope and fit | 1 and 2 | Which Guidewire applications are covered and how the gateway relates to Guidewire’s own tooling |
Mapping | 3 and 4 | Who maps, who reviews, and how instance-specific fields are handled |
Data quality and testing | 5 and 6 | What gets rejected and what senders can test |
Change and scale | 7 and 8 | Payload changes, Guidewire releases, and large payloads |
Senders and terms | 9 and 10 | Which senders connect, who owns what, and what is in writing |
Question 1: Which Guidewire applications do you send data into today?
Ask for the list by application, not a general statement about Guidewire support. A provider with real coverage names each application and the data type that flows into it.
Submission and policy data lands in PolicyCenter, so ask for a live example of a policy payload arriving there.
Claims data such as FNOL lands in ClaimCenter, and billing data lands in BillingCenter. Ask for one live example of each.
Question 2: How does your product relate to Guidewire’s own Integration Gateway?
The two products share a name and do different jobs. Guidewire’s Integration Gateway is a developer framework that your engineers build with.
A carrier-side data exchange gateway sits beside it and faces your senders. Ask how the provider fits beside the cross-platform Guidewire solutions your team already operates.
Then ask what the provider adds on top. A complete answer names a mapping step the sender completes once, a self-service portal, and a test harness.
Pin Down Who Maps and Who Reviews
Mapping decides which sender field lands in which Guidewire field. Two questions show whether the provider treats that step with care.
Question 3: Who creates each mapping, and where does a person review it?
Mapping is where AI-assisted field mapping earns trust or loses it. The model drafts the match, and a person must approve it before any real data moves.
A provider that cannot name the review step is describing a decision made without you. Ask to see the mapping editor, the reviewer’s view, and the point where approval happens.
Question 4: How do you handle fields that are specific to our Guidewire instance?
Every carrier extends Guidewire differently. Your mandatory fields and valid values will not match the next carrier’s.
This is multi-tenant integration in practice: one sender, many carriers, each with its own fields. Ask whether tenant-specific mapping keeps your extensions in your tenant, so that no one forks the integration to support them.
Test What Arrives and What Gets Rejected
Clean data is the point of the gateway. These two questions cover what the gateway stops and what senders can prove before they send real data.

Question 5: What happens when a sender’s data is incomplete?
Incomplete data should be rejected at the gateway, before it reaches an underwriter or an adjuster. Ask what the sender sees when a payload fails.
Then ask who defines complete. The answer should be you, through your mandatory fields and valid values.
Question 6: Can senders test before real data arrives?
Senders need a safe place to try a payload. A complete answer includes a sandbox, a test harness, and a self-service portal where the sender works without waiting on your team.
Ask for a live walkthrough of the test harness. Request a sample payload run through the sandbox, including one deliberately incomplete payload.
Plan for Change and Volume
A gateway earns its place after go-live, when payloads change and volume spikes. These two questions test the provider against both.
Question 7: What happens when a payload or a Guidewire release changes?
Senders add fields, and Guidewire ships releases on its own schedule. Ask who edits the mapping in each case, and what your team does compared with what the provider does.
Ask how the provider handles the differences between on-premises and cloud Guidewire APIs. Senders see one gateway, while your instance sits on one or the other.
Question 8: How do you move large payloads?
Catastrophe FNOL files and bulk policy files are too large for an API body. A complete answer describes sending large payloads by file location, where the sender passes the location of the file instead of the file itself.
Ask what the sender does, what the gateway does, and how a person reviews the mapping for a file format the gateway has not seen before.
Check Senders, Support, and Terms
The last two questions move from the product to the relationship. They tell you who else depends on the provider and what you own once the contract starts.

Question 9: Which kinds of senders connect today?
Your senders will not look alike. Ask for the sender types the provider supports, starting with the ones that matter most to your book.
Ask whether the provider supports underwriting workbench vendors that send submissions into PolicyCenter.
Ask the same about rating and pricing vendors, and about MGAs, brokers, and TPAs.
Question 10: What do we own after go-live, and what is in the commercial terms?
Get ownership in writing. Ask who maintains mappings, who supports senders, and who answers when a payload fails at midnight.
Ask the provider to state what drives the price and what the term covers. Then ask for references from carriers and for the provider’s partners, so you can check the answers from the other side.
How InsOps Helps
InsOps builds Yazh (Yaal), the InsOps Integration Gateway. A sender maps its payload once, and Yazh translates it to each carrier’s Guidewire format. LiLa, our insurance-trained model, assists the mapping, and a person reviews every mapping before it is used.
Yazh sends data inbound into PolicyCenter, ClaimCenter, and BillingCenter. It includes a self-service portal for senders, a test harness, and a sandbox. It rejects incomplete data, handles changes to a payload or a Guidewire release, moves large payloads by file location, and applies tenant-specific mapping.
Guidewire’s own Integration Gateway is a developer framework. Yazh adds the sender-facing layer beside it, so your Guidewire team is not building and maintaining a separate connector for every partner.
If you are evaluating how to take on the next sender without a new connector build, contact us to walk through these ten questions against your own Guidewire setup.
Frequently Asked Questions
What is an insurance integration gateway?
It is a carrier-side layer that receives policy, claims, and billing data from senders in their own formats and translates it into the carrier’s Guidewire format. Senders map once, so the carrier does not build a connector for each sender.
What should a carrier look for in an insurance integration partner?
Look for coverage of the Guidewire applications you run, human review of every mapping, rejection of incomplete data, and a test environment for senders. Also look for a clear answer on who maintains mappings after go-live. The ten questions above turn each of these into a request for evidence.
How is a carrier-side gateway different from Guidewire’s Integration Gateway?
Guidewire’s own gateway is a developer framework that your engineers build with. A carrier-side data exchange gateway adds sender-facing pieces such as a portal and a test harness, so senders map and test on their own.
Why does a gateway need a person to review mappings?
A mapping decides which sender field lands in which Guidewire field, and a wrong match corrupts the record. The model drafts the match, and a reviewer approves it before any real data moves.
How should a carrier test a gateway before signing?
Ask the provider to walk a sample payload through the sandbox and test harness, including one deliberately incomplete payload. Confirm that the incomplete payload is rejected and that the complete one reaches the right Guidewire application.
What happens to sender integrations when Guidewire ships a release?
Ask the provider to explain this before you sign. With Yazh, changes to a payload or a Guidewire release are handled at the gateway, and a person reviews each mapping before it is used.
Which Guidewire applications can Yazh send data into?
Yazh sends data inbound into PolicyCenter, ClaimCenter, and BillingCenter.

