What we heard
This is what we understood
you're trying to solve.
If anything here isn't right, tell us. Everything we propose is built on this.
"I don't want to see an HR agent and an IT agent and a Facilities agent."
One agent. One conversation. Your employees ask a question in plain language — they get a reliable answer with a source, regardless of which system it came from. That's the outcome. Everything else is detail.
The four problems you described
🗂

Information is scattered

Employees bounce between Insight, WorkWise, and WeConnect looking for answers that exist — they just can't find them. The friction is the problem, not the content.

⏱

Your teams answer the same questions every day

HR, IT, and Facilities are spending time on questions that have clear documented answers. That time has a real cost — and a better use.

✋

Finding isn't enough — employees want to act

Not just answers. Submit a request. Log a ticket. Start a process. From the same place they asked the question.

🔒

Personal data is non-negotiable

Payslips, leave balance, contract details. Zero tolerance for disclosure errors. The agent must show each person exactly what they're allowed to see — nothing more.

Three types of information — three levels of care
Level 1

Same for everyone

Company-wide policies, general procedures. Available to all employees. No restrictions.

e.g. parental leave policy, office access rules
Level 2

Depends on your role

Location-specific, role-specific, contractor vs employee. Shown only to the right person based on their position.

e.g. salary ranges by country, team-specific procedures
Level 3 · Zero tolerance

Personal to you

Payslips, leave days, contract details. Shown only to you — with absolute certainty of identity. No margin for error.

e.g. your payslip, your remaining leave balance
Access works the way it already does. The agent shows you what you can see today in your Microsoft 365 environment — based on your role and existing rights. No new permissions model to build or manage.
What you get
One day together.
A working agent.
A binding proposal within 48 hours.
1
The PoC Sprint day · Free
We build it together
Mid August 2026 · On-site · Free

We agree one use case in the room. Our engineers build a working demo agent — against representative content in a demo environment — so you can see exactly how it will behave: the conversation, the access tiers, the source references. This is a proof of direction, not a production system. That comes next.

PoC vs MWP — the PoC shows you it works and what it looks like. The Minimum Working Product is the production-ready, governed, integrated version built inside your environment. Two distinct things.
→
2
Within 48 hours · Binding
You receive a proposal
Based on what we built and heard

A scoped, priced, ready-to-sign proposal. Prioritised use cases. Recommended architecture. Timeline from September through to live pilot. No surprises.

→
3
When you're ready · Contract
We start building the real thing
From ~1 Sep · Once contract signed

The MWP engagement starts from the working agent we built together. Not from scratch. No translation layer. Your decision on when to proceed.

The one-day journey
IDEA the spark 1 KICKOFF 30 min Align on use case Review inputs. Agree what we build today. 2 DEFINE 20–30 min Use case workshop Map the employee journey. Identify the quick win. Agree scope for the build. 3 BUILD 1.5 – 2 hrs Build on-the-fly Demo environment. Representative content. 4 DEMO same day Live demo You see it working. Validate direction. Proposal in 48 hrs. ★ WORKING PoC same day not an MWP
PoC — proof of concept
A working demo in a demo environment. Shows you what it looks like and how it behaves. Built in a day. Free.
MWP — minimum working product
Production-ready. Built inside your environment. Governed, integrated, and ready for employees. Follows the PoC.
What the 48-hour proposal includes
📋

Prioritised use cases

Everything we identified on the day — ranked by value and effort. Quick wins, phased items, and anything that surfaced during the session.

🏗

Solution architecture

A clear recommendation based on your systems, your data, and your governance requirements. How everything connects. How access is enforced.

📅

Scope, timeline & investment

Phased if needed. Clear path from September to live pilot. Investment range. Ready to move to contract when you are — on your timeline, not ours.

Day 1
Working agent demo
Scope agreed · Free
+48 hrs
Binding proposal
Architecture · Ready to sign
Your call
Contract when you're ready
Build continues from PoC
Our approach
From the day we meet
to employees using it.
Mid-August PoC. Proposal within 48 hours. Contract by 1 September. Pilot before December.
Timeline
Mid Aug
Late Aug
1 Sep
September
October
November
Before Dec
PoC Sprint
PoC · Free
Binding Proposal
+48 hrs
Contract
~1 Sep
MWP Build
Minimum Working Product
Live Pilot
Employee Pilot — before December
Why this works
⚡

You see it working before you decide

The PoC Sprint means your go/no-go decision is based on a real, functioning agent — not a proposal. No commitment required until you've seen it.

🏗

Built on what you already have

Your 1,500 Microsoft 365 Copilot licences are the platform. Insight, WorkWise, WeConnect, and AFAS are the sources. No new systems. No new procurement.

🔒

Governance is in from day one

Data sensitivity tiers and access controls are part of the PoC — not a phase 2 add-on. When you see the demo, you see it working safely.

👤

One agent — always

Your employees see one agent. One conversation. The complexity behind it — multiple domains, governance layers, access controls — is ours to manage.

Who's in the room
Haskoning — your team
Business Sponsor
Overall initiative ownership, priorities, and decisions
Digital & Workplace Lead
Technical feasibility, platform ownership, and IT environment
HR Lead
HR use case, content ownership, and data governance
Communications Lead
Employee experience, content adoption, and rollout
IT / Tenant Admin
Microsoft 365 environment access and permissions
Avanade — our team
Lead Forward Deployed Engineer
On-site · builds the working agent with your team on the day
Advisory
Microsoft data governance, security architecture & ESS reference implementations
Account Lead
Commercial coordination and relationship management
Before we meet
Two things we need from you —
at two different moments.
Before the PoC Sprint day
What we need to start building
The lighter ask — enough for us to arrive prepared and build something meaningful on the day.
1
Your platform and systems overview — the deck you shared with Microsoft
So we arrive knowing your environment rather than spending the day mapping it.
2
Who owns content in Insight, WorkWise, and WeConnect?
One name or team per system — the person who knows what lives where and what's current.
3
Each team's top 10 most common employee questions
HR, IT, and Facilities each bring their most repeated questions. This is how we agree scope and pick the quick win on the day.
4
The right IT contact for tenant-level questions
Someone with Microsoft 365 admin access — we may need them on the day or shortly after.
Before the binding proposal · within 48 hrs of the PoC
What we need to scope and price accurately
These shape the architecture, the effort estimate, and the commercial model. Some will surface during the PoC day — others we may need to follow up on.
1
Which countries and locations need to be covered?
Affects data residency, regional policy variations, and whether content needs to be scoped by geography.
2
What languages does the agent need to support?
Dutch and English as a minimum? Other languages across your 25+ country footprint?
3
Is Haskoning running on a single global Microsoft 365 tenant, or multiple?
Single tenant is straightforward. Multiple tenants changes the architecture and phasing significantly.
4
How many of Haskoning's ~6,800 employees fall outside the 1,500 Copilot licences?
The majority are likely unlicensed. How we handle access for those employees affects architecture and the commercial model.
5
Does relevant content also live in OneDrive, shared team folders, Teams channels, or Viva products?
Content outside the three main systems (Insight, WorkWise, WeConnect) needs a different approach. Viva Engage, Viva Learning, Viva Connections — if these are in use, they may also be relevant surfaces or sources.
6
Do WeConnect (Ivanti) and WorkWise (Xoralia) have accessible APIs?
Determines what's achievable in the MWP without custom connector work, and what needs to be built.
You don't need answers to all of this before we arrive. Many of these will come out naturally during the PoC day. What matters most upfront is questions 1–4 in the first block — everything else we can work through together.