• -World Emblem does not need a prettier dashboard. It already has the operating discipline: Hoshin, FMDS, Standard Work, and an 8-step problem-solving method.
• -The gap is that the operating model and the data live apart. Business Central, NetSuite, HubSpot, Power BI, Microsoft 365, the workflow tracker, and WMS each carry a piece of the truth.
• -T3 still asks people to assemble the week by hand: pull the KPI, find the owner, add the commentary, then remember what changed since the last meeting.
• -When a KPI goes red, Randy has to ask twice. The first ask finds the problem. The second ask finds the explanation. Leadership OS should collapse that into one loop.
• -Randy's judgment layer, including Hoshin priorities, meeting habits, decision heuristics, and Claude memory exports, needs to become institutional context every agent can read from.

One agentic layer over the systems and operating model, delivered by a senior Supernal pod over twelve months.

• -Track A, The Vault: Week 1 source map, vectorized data layer, read-only integrations, meeting and document ingestion, entity graph, operating-principles capture, decision history, and audit layer. 13 deliverables.
• -Track B, App: the executive room for KPI cascade, Standard Work, Hoshin, T3, follow-ups, and role-based access. 6 deliverables.
• -Track C, AI CEO: Randy's morning desk, inbox triage, T3 prep, executive briefings, role-time tracker, and decision surface. 6 deliverables.
• -Track D, AI COO: backlog trajectory, plant-by-plant status, logistics and shipping intelligence, and late-order escalation. 4 deliverables.
• -Commercial model: one flat Leadership OS engagement at $10,000 per month for 12 months, with monthly sequencing reviewed with Randy before the next work begins.

• -Randy stops asking the same question twice because red KPIs and late orders already have an owner, an explanation path, and a posted resolution.
• -The operating model runs the agents. Hoshin, FMDS, Standard Work, and the 8-step method shape what the system flags and how it explains the work.
• -Leadership context becomes institutional. Decisions, reasoning, source data, and Randy's operating principles are logged instead of trapped in meetings or memory.
• -Each leader sees the surfaces tied to their actual job: dashboards, agents, approvals, follow-ups, and access scoped to their role.
• -The v1 foundation can cascade below the executive layer later without pretending this Order Form includes every future workflow.

• -T3 runs end-to-end in the system: prep, meeting capture, action extraction, owner assignment, follow-up wall, and repeated-item flags.
• -When a KPI goes red, the system notifies the owner, gathers the explanation, posts the resolution, and makes time-to-resolution visible.
• -Randy's inbox shows only what needs his judgment. Routine items route to owners, replies draft for approval, and email operations time shows up in the role-time tracker.
• -Leadership can answer who owns this, what was decided and why, and what is slipping without calling a side meeting.
• -Hoshin objectives get a weekly heartbeat so drift is visible while there is still time to act.

• -After Order Form signature, Week 1 is already practical: access, architecture, operating-principles capture, and the first sequencing decision.
• -Provision read-only access within 10 business days for Business Central on-prem and cloud, NetSuite, HubSpot, Power BI, Microsoft 365 via Graph API, WMS, and leadership KPI sheets.
• -Run the Week 1 data architecture workshop with Randy Carr, Eric Freeman, and Jim Cozell, with Phil available for technical sign-off on integrations.
• -Client shares Hoshin objectives, Leader Standard Work, FMDS source documents, role and KPI definitions, master prompt, and Claude co-work memory exports.
• -Executive meetings are recorded by default for the Vault: T3, financial review, Hoshin review, and project meetings. Month 1 ends with a sequencing review before the next deliverable set begins.