Publishing · Financial Planning · Community Impact · Media Production · AI Orchestration · Microsoft-Native · GPO Registered · SAM.gov Active · Legacy by Design · Columbus, OH · Publishing · Financial Planning · Community Impact · Media Production · AI Orchestration · Microsoft-Native · GPO Registered · SAM.gov Active · Legacy by Design · Columbus, OH ·
Operating Model
Built for people. Governed for permanence.
Every system at J Merrill One exists because a person needed something to last. This page is for clients, partners, donors, and stakeholders who want to understand how JM1 stays coordinated behind the scenes.
How J Merrill One stays consistent.
The operating model matters because people should not have to start over every time a need moves from one division to another.
JM1 uses one shared model so communication, accountability, and follow-through stay aligned across publishing, financial planning, community impact, and productions. The technical pieces support that promise; they are not the reason the promise exists.
How the Model Supports People
Three shared layers. One coordinated experience.
These layers help JM1 stay organized, responsive, and consistent so the people we serve experience clearer handoffs and better follow-through.
DV
Layer 01
Unified
Data Layer
Microsoft Dataverse as the single source of truth. One contact record. One relationship model. Every client is known across all four divisions.
One contact record across all divisions
Shared relationship intelligence
Lifetime value made visible
Cross-brand opportunity detection
AI
Layer 02
AI
Orchestration
A governed agent operating system with dedicated AI support for Publishing, Financial, Marketing, and Executive decisions within the JM1 governance framework.
Division-specific AI agents
Enterprise governance layer
Canon-aligned decision support
Azure AI Foundry integration
PA
Layer 03
Cross-Division
Execution
Power Automate routing that detects cross-brand opportunities in real time — every client touchpoint becomes enterprise-wide intelligence and action.
Publishing → Financial routing
Financial → Foundation pathways
Productions amplifies all divisions
Real-time opportunity detection
Governance Model
Centrally governed. Divisionally executed.
JM1 holds the shared standards so people encounter one level of care, clarity, and accountability. Each division still has room to serve its own audience well.
JM1 Controls
Domain structure and subdomain assignment
Master color palette and typography
Homepage architecture and section order
Canonical copy and WHY language
Technology stack decisions
AI usage standards and agent governance
Data schema and Dataverse structure
Cross-brand routing logic
Divisions Control
Service catalogs and pricing
Division-specific copy and testimonials
Marketing execution within their domain
Client-facing workflows and intake
Division-specific content strategy
Appointment and consultation scheduling
Technology Stack
Microsoft-native. Azure-powered.
These tools matter because they help JM1 keep records cleaner, handoffs smoother, and follow-through more reliable across every division.
Web
FrameworkNext.js 14+ (App Router)
Web
StylingTailwind CSS with JM1 design tokens
Cloud
HostingAzure Static Web Apps
Web
RenderingHybrid SSR/ISR (performance + SEO)
Data
Data LayerMicrosoft Dataverse
Data
CRMDynamics 365 Sales Enterprise
Data
FinanceDynamics 365 Business Central
Auto
AutomationPower Automate
AI
AI InfrastructureAzure AI Foundry (post-launch)
Ops
BookingsMicrosoft Bookings
Sec
IdentityMicrosoft Entra ID
Lang
LanguageTypeScript
AI Roadmap
Leading the industry. By design.
AI is part of how JM1 improves follow-through, not the reason JM1 exists. As the platform matures, automation supports faster routing, cleaner handoffs, and better decision support across divisions.