All cases
YINCOMGAsNetherlands

One extranet, fifteen products in three months, marketplace across Yellow Hive.

How YINCO turned a volmacht extranet, a DIAS-synced product catalogue and a Yellow Hive marketplace into one place where 100 advisors quote, close and advise.

YINCO · Yellow Hive · cover
One extranet for the volmacht, live-synced with DIAS, marketplace across Yellow Hive.
~100Affiliated advisors
15 → 50Products live (3 months)
STPLive sync to DIAS
Country
Netherlands
Size
YINCO · ~100 affiliated advisors, part of Yellow Hive
Core stack
DIAS as volmachtparket, WeGroup as extranet and advice surface
Go-live
Three months from first product to fifteen live

The challenge

What was broken before WeGroup showed up.

YINCO is the volmacht for retail products inside the Yellow Hive group. Affiliated advisors run their own offices and intermediate YINCO products to their clients. Until recently they were switching between three or four tools to get from a risk question to a closed policy. The product catalogue lived in DIAS. The extranet was a separate surface. The advice flow lived somewhere else again.

Every product change had to ripple through each tool manually. Every advisor lost time on context switching for every client conversation. And the marketplace YINCO wanted, where products from different Yellow Hive volmachten would surface in one place, had no operational home.

We wanted our advisors to stop switching tools to get from a risk question to a closed policy. And the products we add to DIAS should show up in the flow the same day. Both of those, in one platform.

Director of volmacht operations, YINCO

What we built

WeGroup is the extranet YINCO advisors log into. The customer view is pulled straight from DIAS, and the product definitions in DIAS drive the application flows directly: define a product in the volmachtparket and its compare-and-apply flow goes live in the extranet, without a separate rebuild. Closed policies write back to DIAS for STP processing, and the same surface carries advice, applications, mutations and cancellations.

One extranet for the volmacht

Customer view, comparison, quote, close, and policy mutations and cancellations from one surface, with a login per advisor. The switching between tools to get from a risk question to a bound policy stops.

Live product sync with DIAS

The product definitions in the DIAS volmachtparket drive the application flows directly: add or change a product there and its compare-and-apply flow in the extranet follows, without a separate configuration project. Policies bound in the extranet flow back into DIAS and get STP-processed there.

Advice and brokerage in one platform

The advice module sits inside the extranet. A risk inventory leads into the calculation, the quote and the close, without leaving the platform.

Yellow Hive marketplace

Every product across every Yellow Hive volmacht is accessible from one marketplace surface. The advisor navigates to the right product, regardless of which volmacht owns it inside the group.

The numbers

What it produced, in numbers.

~100

Advisors on one extranet

Every affiliated YINCO advisor logs into the same surface, runs calculations and closes policies there, with DIAS staying the system of record.

15

Products live in 3 months

Fifteen volmacht products operational across the network in three months. Pipeline is heading toward fifty without changing the model.

STP

Live to DIAS

Every closed policy lands in DIAS for straight-through processing. No re-keying, no overnight batch, no parallel administration.

1

Yellow Hive marketplace

Products across every Yellow Hive volmacht surface in one marketplace navigation. Advisors stop knowing which volmacht owns which product.

The outcome

The advisor stops switching tools to get from a risk question to a closed policy. YINCO ships product changes in DIAS and they show up in the extranet the same minute. Fifteen products live in three months. Fifty is the next stop.

YINCO advisors now move from a risk question to a closed policy in one platform. Because the product definitions in DIAS drive the application flows directly, a new or changed product is live in the extranet without a separate configuration project, and the most-used retail products go first. Closed policies write back to DIAS and get STP-processed there. Fifteen products live in three months, and the model holds as the pipeline grows.

The marketplace is the harder part. With every Yellow Hive volmacht's products surfacing from one navigation layer, an advisor at a YINCO office can intermediate the right product from anywhere in the group without learning a different surface for each volmacht.

In their words

We needed our advisors to stop switching tools to get from a risk question to a closed policy. The extranet does that, and the products we add to DIAS show up in the flow the same day. Fifteen live in three months. We are heading for fifty.

YINCO

Director of Volmacht Operations

YINCO

Portrait will be added once the customer goes on the record by name.

Timeline

From first conversation to a marketplace-ready extranet in three months.

  1. Month 0

    Working session

    Joint session with YINCO and the Yellow Hive product team.

  2. Month 1

    First product live

    Extranet live with the first product, DIAS sync active.

  3. Month 3

    Fifteen products

    Fifteen products live, marketplace navigation across Yellow Hive.

Stack and integrations

DIAS stays the volmachtparket. WeGroup is the surface the advisors work from.

DIAS

Ready to run the same play on your operation?

45 minutes with our team is usually enough to see whether WeGroup fits on top of your stack.

Or email us at hello@wegroup.ai