One AI Workflow Across Two Dozen Applications: How Lineate Uses Claude for Rosen Publishing

2026-07-07

Rosen Publishing's digital portfolio spans more than two dozen branded web applications plus mobile apps, built over years on whatever stack fit at the time. Java and PHP on the backend; React, Vue, and server-rendered HTML from Java on the frontend. For most teams, that diversity is a tax on every change. For Lineate, it became the proving ground for our Claude-based engineering discipline: one workflow that holds across every stack in the estate.

Share:

Service:

  • AI Product Development

Got a project?

Lineate designs and builds the data pipelines, governance, and infrastructure that power AI.

Contact Us

Problem

An estate this varied punishes specialization. An engineer fluent in the React applications slows down in the Vue ones, and the server-rendered Java pages follow different patterns entirely. Routine work like a shared feature rollout or a security update means context-switching across frameworks, conventions, and years of accumulated decisions. Ramping engineers onto unfamiliar corners of the portfolio consumed senior time, and no single person held the full picture.

The usual answer is to standardize the stack, a multi-year rewrite nobody funds. The better question: can the delivery process be standardized instead, even if the technology never is?

Solution

Lineate embedded Claude into daily delivery across the Rosen portfolio using our artifact-driven workflow. For any non-trivial change, Claude produces an implementation plan covering what changes and why, the files affected, and a rollback path. A senior engineer approves the plan before code is written, and every stage after, from tests through release notes, produces an artifact in version control.

Claude's fluency across the whole stack is what makes this work at Rosen's scale. The same agent that plans a change to a Java backend can carry it through a React frontend, a Vue application, and server-rendered pages, keeping conventions consistent within each codebase while the workflow stays identical across all of them. Engineers stop being bottlenecked by which framework they know best and spend their judgment where it matters: reviewing plans and approving what ships.

Result

  • One consistent, auditable delivery process across two dozen applications and four frontend and backend technologies

  • Engineers work productively across unfamiliar parts of the portfolio, with Claude carrying the framework-specific detail

  • Senior review gates on every plan and every release, so speed across the estate never outruns oversight