GW
HomeWorkAboutNotesStackLab
Experience atOmnicom Group

Driving financial systems and automation across global teams.

Builder ofEnterprise AI Systems

AI agents, audit workflows, and decision intelligence at scale.

Based inNew York City

Building systems for enterprises around the world.

HomeNotesWorkAboutStackLabPartners
XLinkedInGitHubEmailllms.txt
© 2026 · New York City
All enterprise work

Finance operations case study

Workforce planning connection.

A controlled connection between approved workforce inputs and finance planning scenarios.

Workday logoWorkday HCMFP&ARole-based access
Ask the project copilotGrounded in this public-safe case study.

Business problem

What people needed to solve.

Finance scenarios drift from reality when workforce inputs, role and cost definitions, and access rules sit outside the planning model and are refreshed by hand. Headcount changes then reach the forecast late, and sensitive people data is either overshared or missing.

Decision frame

Questions the work needed to answer.

  • Which approved people data belongs in finance planning?
  • How do workforce movements change the scenario?
  • Who is allowed to view or update the detail?
Interactive operating flowSelect any node for context or ask the AI guide.

Selected Operating layer

Workforce planning connection

Connected approved HCM inputs to finance planning by mapping people data into planning dimensions, aligning workforce movements with scenario logic, and setting role-based access boundaries around the planning workflow.

Implementation

From the business problem to a working operating model.

Connected approved HCM inputs to finance planning by mapping people data into planning dimensions, aligning workforce movements with scenario logic, and setting role-based access boundaries around the planning workflow.

  1. 01

    Mapped approved HCM inputs into planning dimensions.

  2. 02

    Aligned workforce movements with finance scenario logic.

  3. 03

    Designed access boundaries around the planning workflow.

Controls, approvals, and delivery constraints

The work around the work.

Enterprise systems change only when data, access, testing, ownership, and evidence move together.

  • Employee data is protected through role-based access.
  • Finance and HR definitions are aligned before downstream use.
  • The portfolio does not show workforce data or employee-level views.

Prior art

How leading teams approach this.

Public references for the same class of problem, so this work can be read against how other organizations are building it.

Anaplan

Connected Planning Supports Healthy Growth at Penumbra

Penumbra links workforce plans to its recruiting and HRIS systems and drives headcount off revenue and demand forecasts, the same connection between approved people data and finance planning built here.

Workday

Sales Capacity & Headcount Planning Software

Workday links workforce plans to financial models with real-time headcount and cost, with approved positions created back in HCM, illustrating a governed HR to finance planning connection.

Anthropic

Inside Claude's rapid expansion across corporate finance

Reports finance teams tying headcount forecasting to hiring plans and cost decisions with reconciliation and context files, reinforcing that workforce inputs belong inside the planning frame, not beside it.

Public-safe outcome

Workforce changes flow into finance scenarios on a defined path with aligned definitions and controlled access, without exposing employee-level detail in reporting or in the public portfolio.