AI-Native Strategic Management Office.

Company Profile

A Supply Chain Data and Risk Management Company with deep roots outside healthcare, standing up two new product lines for the healthcare market: consumable inventory and supply chain readiness for hospitals and state emergency-preparedness programs, and high-value surgical asset tracking for surgical vendors and IDNs. Data-fluent organization with almost no AI exposure inside the building at engagement start.

The Challenge

The company knew supply chain and canonical data models. It did not know how to leverage AI to augment it’s current workforce to scale them as they prepared to enter a completely new “line of business.”

The work would have demanded a full PMO staffed by one to three full-time resources per workstream. An AI-native Strategic Management Office stood up instead, with humans serving as the quality check and external customer-facing support.

• External opportunity flow. RFPs across state procurement portals, federal grants, GPO bid boards, conference attendee tracking, and partnership signals across two product lines.
• Internal coordination across functions. Product, sales, IT security, hardware provisioning, and customer success each pulling in different directions, all touching the same healthcare-entry workstreams.
• Cadence reporting. Monthly executive-sponsor and customer-ELT updates, quarterly internal board cycles, and customer-facing deck production at 8–10 hours per week of senior time.

Ongoing AI Stewardship

3PS stood up a Strategic Management Office (SMO) instead of a traditional PMO. The SMO is an AI-native function that sits inside every meeting, every email thread, and every project plan across both product lines, with humans serving as the quality check and external customer-facing support.

Week 1: Diagnose

Stakeholder interviews and a data and tool inventory. Workflow shadowing across product, sales, IT security, hardware provisioning, and customer success. A commercial-landscape map covering the RFP, grant, and partnership universe across both product lines. A sales-plan overlay showing exactly where the SMO would feed sales ops reps. An AI readiness baseline of existing data systems, document repositories, communications platforms, and security posture. By end of Week 1: a six-workflow build plan with human-in-the-loop checkpoints designed.

Weeks 2–3: Build

The build was deliberately split. Three workflows pointed outward at the market: RFPs and state grants, conferences and attendee tracking, and market-entry and partnership opportunities. Three workflows pointed inward at the company: a silent meeting participant, cross-functional coordination and risk surfacing, and board-and-customer deck generation.

Each workflow stood up with a defined human-in-the-loop checkpoint so the organization could trust the output and teach the system where it was wrong. Document repositories were instrumented for RFPs, grants, conference intel, partnership notes, project plans, board decks, and customer-facing materials. A shared SMO command surface (built on Notion, Granola, and Claude) let the PMO lead, sales ops, and executive sponsor see status across both product lines in one place.

A teaching layer captured every human correction and reapplied it: corrections to action-item routing, opportunity scoring, risk-register language, and deck framing all fed back into prompts, skills, and reference data so the system got sharper each cycle.

Operate: Week 4 Onward

The SMO runs as a silent participant across both product lines. Sales, product, IT security, hardware provisioning, and customer success coordinate through the SMO layer in place of standing meetings.

• Daily. Scans for RFPs, grants, and conferences. Meeting participation and recaps. Project plan and risk register updates.
• Weekly. Partnership and market-entry digest to the executive sponsor. Cross-functional coordination review with the PMO lead. Outreach drafts to sales ops reps.
• Monthly. Executive sponsor and customer-ELT deck materials, generated from the operating state.
• Quarterly. Internal board deck refresh. Sales-plan overlay refresh. ICP and source-list tuning. Retrospective on what the human-in-the-loop layer corrected most often, with those corrections feeding back into the system.

Results

Functional Areas Touched

The SMO is a cross-functional coordination layer. By design it touches almost every function that interacts with the healthcare-entry program. The map below shows a typical operating structure for a Supply Chain Data and Risk Management Company. Highlighted nodes are where this engagement created downstream impact.