Division 01 · PublishingJ Merrill One ↗
Platform
Enterprise Roadmap

The future publishing stack
for J Merrill Publishing

The flagship website is only the visible layer. The next platform phase connects web content to Dataverse records, Dynamics workflows, BI reporting, and governed AI agents so the publishing experience can scale without losing polish.

Roadmap Modules

Four implementation phases.
One operating direction.

These are the architectural modules the web experience is being prepared to support.

Phase 1

Dataverse author graph

Unify author, title, package, imprint, and lifecycle records into one governed publishing data model.

Outcome

One source of truth for every relationship and every title.

Phase 2

Dynamics onboarding orchestration

Route inquiries, consultations, package decisions, and production handoffs through structured business workflows.

Outcome

Premium onboarding with less operational drag and more consistency.

Phase 3

Power BI catalog intelligence

Surface performance by title, channel, imprint, and campaign in executive, team, and author-friendly dashboards.

Outcome

Faster decisions and clearer visibility into publishing performance.

Phase 4

AI publishing agents

Deploy governed assistants for package guidance, metadata enrichment, launch prep, and relationship follow-through.

Outcome

A more intelligent publishing experience without sacrificing human trust.

What the site must support

The web layer is now prepared
for deeper systems integration

This architecture makes room for content, forms, and journeys that can later be powered by enterprise systems instead of static assumptions.

Structured content and relationship data across authors, titles, packages, imprints, and lifecycle milestones.
Dynamics-driven inquiry routing and onboarding orchestration for a higher-touch front-end experience.
Dashboard-ready catalog intelligence for team operations, executive oversight, and future author reporting.
Governed AI assistance that improves speed and insight without weakening human editorial judgment.
Next build implication

The homepage and route architecture now have dedicated places for catalog, onboarding, platform, and relationship content. That gives the future data layer somewhere clean to land when live integrations begin.