Flutter People OS

North-star workshop presentation

Federated / global / regulated / channel-native

Act I / the promise

What if every people workflow at Flutter began in one calm conversation?

The north star is not another HR portal. It is a presentation-grade people operating layer where employees ask once, managers act in-channel, and HR teams supervise recruiting, contracts, onboarding, and policy from one mission control surface.

Download deck
Active agents
8
Human interventions
1
Resolution window
< 2 min
Ask layer Web / WhatsApp / Telegram Orchestration Knowledge + workflow graph Control Mission control for HR and shared services
Live scenario Employee day: one answer, one action path
Current posture AI-guided, policy-cited
Target outcome < 2 min

01

The future should feel like one conversation, not one more system.

Today, knowledge, approvals, policies, onboarding steps, and contract work are fragmented. The north star is a calm, channel-native experience for people and a visible orchestration layer for HR.

Today

Fragmented portals, tickets, PDFs, and handoffs

Portal
PDF
Inbox
Ticket
Manager ping
Spreadsheet

The employee or recruiter rebuilds context every time the workflow crosses a boundary.

North star

One ask layer with context, source, and action built in

What policy applies to my mobility request?
Here is the rule for your market, your role, and your contract. I can start the flow now.
Manager brief created. Local approval path attached. Sensitive cases escalate automatically.

02

Design the day, not just the tool.

The workshop should anchor on the lived rhythm of work: what the employee experiences, what the employer or people team experiences, and where the system quietly absorbs complexity.

Three real-life chapters

Tell the story through people, not technology.

For the workshop, these chapters make the future easy to understand. Each one is a realistic Flutter people moment: an employee needs an answer, a leader needs to hire, and a new joiner needs a smooth start.

Employee day

Priya wants one answer, one source, and one next step.

  1. 09:10
    Ask in channel

    Priya asks in WhatsApp instead of searching across internal systems.

  2. 09:11
    Resolve context

    The system already knows her brand, office, manager, country, and contract type.

  3. 09:12
    Start action

    The answer includes the policy source and the ability to launch the real workflow.

  4. 09:13
    Escalate only if needed

    If the case is sensitive or conflicting, HR receives a summary with the relevant trail attached.

Employer day

Marco wants one supervised flow for hiring, contracts, and onboarding.

  1. 10:35
    State the need once

    Marco defines the role outcome and the system maps it to architecture, market, and approvals.

  2. 11:20
    Let agents move standard work

    Recruiting, contract assembly, local clauses, and signature prep move without manual chasing.

  3. 14:10
    Intervene on the edges

    Humans step in only for compensation breaches, legal exceptions, or local entity conflicts.

  4. Day 1
    Hand off into onboarding

    Signed contracts trigger payroll, IT, workspace, manager nudges, and onboarding flows automatically.

03

One system, many local realities.

Flutter needs a federated architecture: one people operating layer that respects brand, market, entity, employment type, and local policy from the start.

People OS

Ask Orchestrate Govern
Employees
Managers
Recruiting
Knowledge graph
Workflow graph
Local policy packs
HRIS / ATS / payroll
Shared services

Ask

Channel-native entry

Employees and managers start in web, WhatsApp, or Telegram, not in a maze of internal tools.

Orchestrate

Knowledge and workflow graph

The system resolves the right source and launches the next step with the relevant context already attached.

Govern

Mission control for people teams

HR, Recruiting, and Shared Services supervise confidence, SLAs, risk, and interventions from one layer.

04

Then make the operating model tangible.

The interactive layer below is not the vision by itself. It is the proof that the vision can adapt to real employee, recruiter, and onboarding flows.

Interactive demo

Click through the chapters and show how the same system adapts.

Chapter 1 / Employee question

Priya needs to understand what applies to her move from Dublin to Lisbon.

Instead of searching through policy pages or waiting for HR, Priya asks one question in channel and the system resolves the right answer for her exact context.

What the person says “What policy applies to my move, and can you start the process for me?”
What this sells in the room Less searching. Less waiting. Fewer tickets. More confidence in the answer.

Mission control

Employee day: one answer, one action path

Context-aware service

Mission objective

Find the right document, process, or policy without searching five systems.

The experience understands the employee's Flutter brand, market, contract type, office, manager, and role before answering or launching a workflow.

System posture

AI-guided, policy-cited

Answers clearly when rules are known. Escalates ambiguity, sensitivity, or market-specific edge cases.

Context graph

Brand, market, role, policy

    Agent fleet

    Guided autonomy

      Playback

      Employee question to resolved action

      09:10 local

        Self-serve resolution

        87% Employees find the right answer inside the first conversation.

        Time to contract

        48h Standard recruiting and contract work moves without manual chasing.

        Day-one readiness

        95% Signed contracts trigger coordinated onboarding before quality breaks.