Vision · Architecture · Roadmap

Vinci

Creative Studio

Vision document · Architecture overview · Roadmap

Origin & Problem

Why Vinci exists

·Hundreds of asset requests per week across onsite, CRM, marketing, and social
·All routed through JIRA, executed manually, delayed by unclear briefs
·Difficult to use for stakeholders · AI leverage is difficult · No centralised rules based on brand repository of what worked in past

10+

Banner formats in scope

Languages per asset (EN + AR)

Self-serve paths (before Vinci)

∞

JIRA tickets, no system

Where Vinci sits

The broader creative pipeline

Vinci is one part in a larger content production chain. Understanding where it sits · and what it doesn't own · is critical to scoping it correctly.

Event Calendar

Curie

Campaign triggers: Ramadan, Black Friday, category sales

→

Page Layout

Curie

Defines page structure: hero slots, carousels, tile rows

→

Asset Generation

▶ Vinci

Generates banners & tiles in EN + AR per spec

→

Asset Storage

▶ Vinci

GCS bucket → page assembly and publishing

→

Onsite / CRM

Live

Customer-facing placements across channels

Curie handles the upstream decision of what goes on a page and where. Once a page layout is confirmed Vinci takes over and produces the visual asset. In a future state, Curie can invoke Vinci programmatically, making the entire flow event-driven.

Evolution

Past → Present → Future

Before

Manual era

Manual, ticket-driven design

·JIRA ticket → brief interpretation → manual Figma build → export
·Limited AI, no templates, no feedback loop
·Every asset bespoke, even when it didn't need to be

JIRA-gatedNo self-serveManual Figma exportNo performance data

Shipped

Designer-led AI generation

·3-step brief: format · vibe · review
·Figma guidelines + approved assets as generation context
·Hero banners + category tiles, EN + AR, all ratios
·Composites hero images or SKUs without distortion

Hero banners EN + ARCategory tiles EN + ARDesktop formatsAll format sizes

Full asset coverage + stakeholder self-serve

·JIRA removed · category, DM, and CRM teams self-serve directly
·Full banner ratio coverage + DM and CRM creatives
·Logo and brand assets with design system accessible in vinci
·Usage analytics: request logs, model breakdown, daily cost, time-in-funnel
·Built-in eval QCs output against the original brief

[V1]Built-in evalsDesktop bannersLogo and brand assetsDesign guidelinesStakeholder self-serve

V3+

Long term

Creative Studio for noon

·Single source of truth for all brand assets, logos, and guidelines
·Curie integration · page-layout decisions auto-trigger asset generation
·Emailer, translation pipelines, and SKU-level image generation in-house
·Design Head to manage the Design system used in Vinci
·"Suggest Me" mode for campaign-ready work with minimal input
·Shared creative infrastructure across noon Food, noon minutes

[V1+V2]Usage analyticsAdmin logsCurie integrationEmailerCross-verticalChatbotSuggest Me mode

Architecture

How Vinci is built

Modular pipeline · each layer upgrades independently without touching the others.

Brief Interface

3-step input: format · vibe · review. SKU/URL, custom uploads. Brand constraints enforced invisibly.

Intent Decoder

Translates brief into a generation spec: dimensions, language pair, hero subject, background, overlays, CTA.

Rules Engine

Figma-sourced tokens: fonts, spacing, radii. Rulebook for CTAs, offer tags, and standard elements.

Asset Repository

Approved assets with performance metadata. Few-shot context so new outputs inherit past top-performers.

Generation Layer

Composites hero onto background, applies text and elements. EN + AR from a single brief.

Eval + Storage

QC against brief + guidelines before surfacing. Stored on GCS. Performance feedback loops into rules engine.

User Evolution

Who uses Vinci, and when

The tool's user base expands in deliberate phases · each stage unlocking a new group while the previous one remains supported.

Phase

Primary User

What they can do

● Now (V1)

noon Core Designers

Generate EN + AR banners and category tiles from a guided brief. Download PNG. Refine with feedback.

● V2

Category, Onsite, DM & CRM Teams

Submit asset requests directly · no JIRA ticket, no design team intermediary. Full asset coverage.

● V3+

All noon verticals

Access Vinci as shared creative infrastructure. noon Food, noon minutes, external marketing teams.

The Vision

Where this goes

Vinci is not a banner generator. It is the creative infrastructure that lets noon operate at the speed of commerce · where a campaign brief becomes a production-ready, brand-consistent, bilingual asset in minutes, not days.

· Vinci Product Vision · 2026

The long-term bet is that design bottlenecks in noon are a solved problem. Any team, for any campaign, in any language, gets production-ready creative in minutes · not days. The design team's role shifts from execution to governance: owning the rulebook, curating the repository, and setting the creative direction that the system executes against.

Vinci's integration with Curie is the final unlock: a world where a category manager creates an event, Curie lays out the page, and Vinci auto-generates every asset in the layout · all without a single JIRA ticket.