Skip to content
AI Product · Enterprise Workflow · Design Engineering

PrintCore Campaign OS

An AI-enabled campaign operations platform that helps enterprise marketing teams create, review, benchmark, and improve campaigns in one connected workflow.

View live prototype ↗
PrintCore Campaign OS Launch-ready step showing the final email, launch package metrics, and pre-launch checklist
Project overview
Role
Lead Product Designer
and Front-End Prototyper
Timeline
2026
Platform
Responsive web application
Ownership
Independently designed and built end to end.
Scope

Product strategy, information architecture, AI workflow design, UX/UI design, design system, and front-end implementation

The problem

Slow, agency-dependent campaign execution, with hard-won knowledge lost between handoffs.

My approach

One operating system that runs a campaign from brief to launch, then learns from it.

The solution

A governed workflow plus a four-agent intelligence layer connecting feedback to the next campaign.

01 · Problem

Campaign execution was slow, expensive, and difficult to improve over time.

A B2B printer company already had strong customer targeting through CRM and Databricks. The real bottleneck was downstream: turning strategy and customer data into approved, launch-ready materials without losing momentum to repeated agency handoffs and review loops.

Just as costly, nothing carried forward. What worked in one campaign was scattered across emails and agency files, so every new brief started from scratch instead of from evidence.

Production cycle 5 to 7 weeks

Traditional time from initial brief to final campaign rollout.

Agency spend $750K to $1.25M annually

Recurring cost of routine campaign production work.

Campaign knowledge Fragmented across handoffs

Learnings lived in emails and agency files, so each campaign started from scratch.

Current-state workflow

Where the process slows down

5–7 weeks from initial brief to rollout

01
Campaign Brief
Internal alignment and brief drafting
Week 1 to 2
02
Customer Targeting
CRM and Databricks identify target accounts
03
Sales Validation
Sales confirms list relevance and freshness
04
Agency Production
Creative development and first draft
Bottleneck
05
Revision Loops
Multiple back-and-forth reviews
Bottleneck
06
Testing and Launch
Formatting, links, tracking, personalization, rollout
Week 5 to 7
Primary bottleneck

Downstream production, repeated handoffs, and knowledge lost across emails and agency files.

Design question How might we reduce production time and routine agency dependency without removing the human review, governance, and quality controls an enterprise marketing team requires?
02 · Strategy

Design one operating system for execution and continuous learning.

I structured PrintCore around two connected layers: an operating layer that moves a campaign from brief to launch, and an intelligence layer that turns each campaign's signals into recommendations for the next one.

Strategic principle Automate repeatable production, not accountable decision-making.
Product architecture

Two layers, one feedback loop

Campaign Operating Layer
Brief
Audience & Sales Validation
Content
Compliance & QA
Launch Readiness
Knowledge Repository
Agency Benchmarking
1 · Signals captured after launch
Sales feedbackReview decisionsCampaign performanceMarket signals
2 · Recommendations for the next brief
Stronger briefsBetter targetingBetter contentEarlier risk preventionSharper positioning
Campaign Intelligence Layer
Sales Objection Mining
Revision Root Cause
Performance Learning
Competitive Intelligence

Operational signals become reusable recommendations for the next campaign.

03 · Operating model

Move from brief to launch readiness in one connected workflow.

Campaign Studio runs the whole process as one connected workflow, making each stage's inputs, ownership, AI assistance, review status, and next action visible as work moves toward launch.

Campaign Studio Brief stage showing success criteria, audience logic, and grounding context

Brief

Ground the campaign before generation.

Connect the business goal, audience logic, success criteria, message strategy, and product proof before downstream work begins.

Audience selection and sales validation gate showing the refined account list and sales approval status

Audience

Validate the target list before content production.

Refine exported CRM and Databricks sample data and require sales confirmation before the team invests in content creation.

Content stage showing subject line and CTA options alongside a live email preview

Content

Turn approved strategy into editable content.

Generate subject line, CTA, and email options from approved context while keeping every output reviewable and editable.

Compliance and QA stage showing policy checks and the human approval chain

Compliance

Catch risk before stakeholder review loops.

Run first-pass policy and launch checks while keeping human approval as the final gate.

CRM and Databricks are represented through exported sample data, not a live production integration. Compliance runs a first-pass review; human sign-off remains the final gate to launch.
04 · Knowledge & intelligence

Ground AI in reusable knowledge, then learn from every campaign.

Ground and evaluate

Knowledge Repository

Centralizes customer data, brand guidance, product proof, past campaigns, agency work, and intelligence signals so AI output is grounded in reusable organizational knowledge.

Campaign Knowledge Repository showing customer data, brand guidelines, products, past campaigns, and intelligence signals

Agency Benchmarking

Compares AI and agency work through shared criteria and blind scoring before routine production moves in-house.

Agency Benchmarking decision frame showing the agency baseline selector and blind mode toggle
The learning loop

Every campaign feeds the next one.

Four agents read the signals each campaign produces and turn them into recommendations for the next brief.

Projected AI versus agency performance across open, click-through, conversion, and unsubscribe rates, with Performance Learning Agent recommendations for the next brief
Projected AI versus agency performance as the repository grows, with the Performance Learning Agent turning results into next-brief recommendations.
The performance model is illustrative, not measured production data.
Sales Objection Mining

Reads CRM notes and sales validation comments to sharpen brief angle, subject strategy, and CTA rationale.

Revision Root Cause

Reads approval and rejection decisions to improve brief quality, claim specificity, and stakeholder ownership.

Performance Learning

Reads open, click, and conversion data to guide targeting, subject ranking, and CTA choice.

Competitive Intelligence

Reads market and competitor signals to shape positioning, offer framing, and creative direction.

Phase 2 is a fully designed and prototyped intelligence layer, not an unbuilt roadmap. It does not represent live production data connections.
05 · Impact & reflection

A proposed path to faster execution and lower routine production costs.

The proposed operating model targets a shorter campaign cycle, lower routine agency spending, and earlier risk detection within one governed workflow.

Projected value
Speed~2.5-week target campaign cycle
Cost~50% reduction target in routine agency spend
GovernanceFirst-pass QA before stakeholder review
Learning4 AI agents connecting feedback to the next campaign
Illustrative targets and prototype capabilities, not measured production outcomes.
Reflection

What I learned

This project reinforced that a successful AI product is not defined by how much work it automates. It is defined by how clearly it establishes context, ownership, review, and trust.

The strongest solution was not an autonomous campaign generator. It was a governed operating system that connected creation, sales validation, human approval, agency comparison, and continuous learning.