bleu
Request a walkthrough

How bleu works

From scattered records to a clear next move.

bleu works across the systems you already use. It connects the customer, the asset or product, the conversation, and the open work—then shows what changed, why it matters, and who can act.

Your systemsKeep the source records
bleuConnects the story
Your teamSees the next move

Inside the experience

The business moves with you.

Explore a mobile moment: the change, its context, and the question behind it. Product illustrations show the possibility.

From signal to context
Product illustrations · Original evidence available
01 / NoticeThe signal. The specific car.

A business-wide view, with a direct path to the record behind it.

bleu.
Ryan Friedman Motor Carsemployee bleu
Product illustration
HubInventory attention
BUSINESS IN VIEW
$59.2Mon the floor

283 cars · 60.7% borrowed

BLEU NOTICEDAging inventory needs a closer look.
$25M98 cars past 90 days
Carrying cost isn’t available in this source.
Recreated from RFMC Hub + Ask · Modeled operating data

A real business example. A native illustration—not live inventory or a connected workspace.

RFMC Hub + Ask, redrawn for clarity · Modeled operating data

Log in to RFMC workspace

The operating model

A signal is not a decision.

One discrepancy visible in the RFMC Hub shows why context and human judgment have to travel together.

01 / WHAT BLEU NOTICEDOne car. Two different stories.
Carrier email · unverifiedDelivered
Inventory bookNo label

The Hub surfaces the disagreement. It does not silently change the record or pretend the carrier email is proof.

  1. 01

    Notice

    Keep both signals visible instead of treating either as the answer.

  2. 02

    Resolve

    Match the carrier message and the inventory record to the same vehicle.

  3. 03

    Review

    Put the discrepancy, sources, and owner in one place for a human decision.

  4. 04

    Remember

    Carry the verified outcome forward so the next person sees the current state.

The discrepancy is drawn from the RFMC Hub with modeled operating data. The four steps describe the governed workflow bleu is built to support, not an automated correction claimed to have happened.

Platform modules

Six modules. One governed system.

Each module has a defined job and a visible control boundary.

01

Relationship Context

Resolves the current relationship state above fragmented records.

Input
Authorized customer, product, asset, interaction, and work records.
Output
A current relationship view with identity, sequence, ownership, and source references.
Control boundary
Source systems remain authoritative for their records.
02

Decision Engine

Turns current context into a specific, inspectable recommendation.

Input
Relationship state, a new signal, business rules, and operating policy.
Output
A proposed decision with rationale, evidence, confidence, and required review.
Control boundary
A recommendation is not permission to execute.
03

Workflow Engine

Coordinates the people and systems needed to carry a decision through.

Input
An approved decision, routing rules, owners, and action scope.
Output
Assignments, approvals, system operations, status, and an execution receipt.
Control boundary
Work pauses when authority, required data, or policy is unresolved.
04

Experience Runtime

Delivers the same business state through the right surface for the moment.

Input
Current context, user role, channel, intent, and permitted actions.
Output
A customer, employee, or embedded experience with a clear next move.
Control boundary
Each surface reveals only approved context and controls.
05

Trust & Control

Makes authority and evidence part of the operating model.

Input
Identity, roles, policies, approvals, and source metadata.
Output
Access decisions, provenance, review states, and durable receipts.
Control boundary
Policy is enforced at decision and action time, not added as copy later.
06

Integrations

Connects bleu to the systems that hold records and execute work.

Input
Authorized APIs, events, files, and scoped operating interfaces.
Output
Normalized signals in; governed actions and outcomes back out.
Control boundary
Read and write scope is defined per system and deployment.

Product system

One platform, purpose-built ways in.

The surfaces meet each participant where the relationship actually happens.

customer bleu

Customer experience

A continuous front door that uses current relationship context to help a customer understand, decide, buy, and get help.

employee bleu

Employee workspace

A role-aware operating surface that brings the signal, account state, source trail, owner, and next step together.

bleu OS

Control plane

The governed foundation for context, decisions, workflows, policy, approvals, and execution receipts.

Ask bleu

Embedded intelligence

A question-and-answer surface grounded in permitted relationship context and its underlying evidence.

Heartbeat

Preview

Monitoring for defined changes that should reach an owner for review.

Private preview

Map one high-value relationship workflow onto the platform.

Request a walkthrough