One connected customer hub

Haworth AI and Sales Forward

Revisit what we have explored, use the shared collaboration space, and shape the next seller, leader, and executive experiences together.

Now Seller-role and sales-process discovery
Next Two ready-now scenarios and one bounded proof
Measure Adoption, time value, data quality, and safe follow-through

Start here

Everything needed to continue the work

The current workspace, the latest meeting artifact, and the original Sales Premium experience are connected here so the engagement can move forward without losing prior work.

September 25 meeting

AI Business Process Connect transcript

This meeting was transcribed but not video-recorded. The transcript is available to the approved audience in SharePoint.

Open the transcript

Preserved prior work

Sales Premium customer hub

Return to the original seller-intelligence experience, demo recap, and supporting resources. Use the passphrase previously shared with the Haworth team.

Open the prior hub

Access: SharePoint resources require sign-in and are limited to the approved Haworth and Microsoft audience. The prior Sales Premium hub remains preserved at its original address.

What we heard

Start with the work, then choose the technology

The joint direction is to make the seller experience simpler, protect Dynamics 365 as the system of record, and prove value before expanding the solution.

Reduce seller administration

Capture signals once, remove unnecessary steps, and make safe follow-through easier from Outlook, Teams, mobile, and the flow of work.

Use the right layer

Begin with ready-now Copilot and Sales Agent value, use Cowork for justified cross-app orchestration, and extend only when a real gap remains.

Keep people in control

Ground experiences in approved data, keep proposed actions reviewable, and require confirmation for consequential updates.

Interactive vision guide

See the experience through each role

Choose a role to explore an illustrative end-to-end journey. These scenarios guide discovery; Haworth will validate the priorities, data, actions, and success measures before any pilot.

Seller experience

Spend more time with customers and less time reconstructing the deal.

Bring trusted account context, meeting preparation, capture, and reviewable follow-through into the seller's flow of work.

  • Prioritize the right customer and next action.
  • Prepare with approved CRM and Microsoft 365 context.
  • Review proposed follow-through before Dynamics 365 updates.

From vision to working proof

Move forward in bounded, measurable steps

The path separates what can be enabled now from what must be discovered, proven, and governed before scale.

1 · Align

Map roles and work

Choose priority seller personas, recurring tasks, friction, approved context, and outcome measures.

2 · Activate

Use ready-now value

Validate the Sales Agent, Copilot, environment, access, and support path for a bounded cohort.

3 · Prove

Test one orchestration

Run one cross-app scenario with explicit data, actions, human approvals, cost routing, and stop measures.

4 · Decide

Scale, adjust, or stop

Expand only when repeat use, usefulness, data quality, supportability, and cost evidence justify it.

Joint workstreams

One engagement, connected work

Each lane contributes to the same outcome: a practical, governed AI operating model that meets Haworth users where they work.

Discovery

Seller personas and processes

Document the priority roles, current work, D365 touchpoints, friction, approved actions, and success measures.

Launch planning

Sales Agent activation

Confirm the environment, cohort, access, scenarios, support, rollback, and baseline adoption measures.

Bounded proof

Cowork fit

Test one cross-app seller task and compare value, maintenance, governance, and cost with extension or custom paths.

Separate path

Executive activation

Choose leadership decisions and recurring tasks, then design a concise experience with trusted sources and a named sponsor.

Required foundation

Governance and operations

Resolve identity, data boundaries, monitoring, human approval, cost routing, support, and accountable ownership.

Evidence

Adoption and outcomes

Measure repeat use, time value, scenario completion, correction rate, data quality, and support burden.

Technical delivery set

Discovery-first technical direction

The current state is a customer journey and discovery guide, not a final production design. Haworth and Microsoft technical owners will close the decisions below before implementation.

Technical details

Readiness to confirm

  • Target environment and eligible users
  • Identity, roles, data, and licensing path
  • Support, monitoring, and rollback ownership
Architecture

Boundary to validate

  • Dynamics 365 remains the system of record
  • Copilot, Sales Agent, and Cowork use approved context
  • Connectors and actions are explicitly bounded
Solution design

Proof to define

  • One persona, task, trigger, and desired outcome
  • Human review for consequential actions
  • Acceptance, cost, stop, and scale measures

Decision owner: joint Haworth and Microsoft technical leads, informed by the seller-process discovery and the selected proof scenario.

Next checkpoint

Turn the sales process into two ready-now plays and one proof.

Use the focused seller-role and process session to choose the users, task, approved context, guardrails, outcome measures, and technical owners that will define the first working experience.

Continue in SharePoint