VTEX Marketing — Shared Action Plan

Eight projects. One executable plan.

A shared view of what each project will deliver, where collaboration is required and what must land over the next 1, 3 and 12 months.

8
projects
6
first-month outcomes
5
cross-project dependencies
3
decisions required
Explore the planView immediate prioritiesLast updated · 20 August 2026

Executive overview

Now

First 30 days

Define, validate and launch the first shared deliverables

Next

By 3 months

Connect channels, journeys and data

Later

By 12 months

Consolidate scalable experiences

Operating cadence

Biweekly and quarterly

Track commitments and remove blockers

Execution principle

Every collaboration must have one leading project, a concrete output, a deadline and a measurable result.

Start here

Immediate priorities.

The four commitments that carry the plan in the first 30 days. Each one has a leading project, contributors, a concrete output and the evidence that proves it landed.

Priority 1

VTEX Club launch experience

Lead · VTEX ClubVCCReputation & DataVTEX.com

A defined Club content and communication journey, supported by personalized HubSpot flows and dedicated website experiences.

First-month deliverables
  • Launch content strategy defined
  • Email cycles and HubSpot flows mapped
  • News and events page requirements defined
  • Content tags and member preferences defined
Success evidence
  • Approved content and communication journey
  • Active email flows
  • Clear audience and content segmentation
  • Club interactions measurable across HubSpot and VTEX.com
Priority 2

Unified editorial model

Lead · VCCOFFBoundsVTEX.comISVsEmployer Branding

Every channel has a defined role, audience and content purpose, reducing duplicated or disconnected publishing.

First-month deliverables
  • VTEX.com's first two navigation levels proposed
  • VTEX News placement and naming defined
  • OFFBounds content divided into public, internal and exclusive Club formats
  • H2 2026 Employer Branding coverage calendar created
  • Recurring VCC–ISV editorial sync established
Success evidence
  • Approved channel roles
  • Shared editorial calendar
  • Content consistently adapted to the intended audience
  • Reduced duplication between VTEX.com, Club, VCC and internal newsletters
Priority 3

ISV activation

Lead · ISVsAcademyVCCVTEX.comOFFBounds

ISVs become discoverable, contribute content and participate in commercial and educational opportunities.

First-month deliverables
  • Categorized ISV list by region and capability
  • Two ISVs sponsoring Master Architect Training
  • ISV content opportunities identified
  • Important industry events shared with the ISV team
  • Recurring VCC–ISV content meeting established
Success evidence
  • Updated ISV inventory available to participating projects
  • Two confirmed MAT sponsors
  • Published or scheduled ISV stories
  • Traceable engagement opportunities created from content or events
Priority 4

Battle of Bats activation

Lead · Battle of BatsVCCVTEX ClubVTEX.comOFFBoundsAcademyReputation & Data

Battle of Bats becomes a measurable VTEX-owned brand and audience activation platform — not an isolated event.

First-month deliverables
  • Final target list delivered to VTEX Club
  • Rules established for publishing major milestones on VTEX.com
  • VTEX point of view and social formats defined with VCC
  • Academy recording from the AI/Agentic Conference published
  • User journey and login integration requirements mapped
Success evidence
  • Major milestones published through VTEX-owned channels
  • Target audiences invited to Club experiences
  • Content reused across social, website and Academy
  • Journey, engagement and lead data captured

Execution board

Project by project.

Eight projects, their commitments and what each one owes the others. Open a card for the full mandate, milestones, indicators and blockers.

Cross-project enabler

Employer Branding

Not a ninth project. A horizontal support layer available to every project on this board.

Culture and valuesTone of voiceCauses and social agendaGlobal event planningCorporate content guidance

Timeline

What lands, and when.

Only tangible outputs. Switch between the project view and the deadline view.

19 deliverables

First 30 days

Now

  • Battle of Bats target list delivered to Club

    Club can activate the right audiences around the event.

    Battle of BatsVTEX ClubConfirmed

    Dependency · Audience criteria

    Evidence · Target audiences invited to Club experiences

  • Club launch content strategy approved

    A defined Club content and communication journey.

    VTEX ClubVCCReputation & DataVTEX.comConfirmed

    Dependency · Audience and launch definition

    Evidence · Approved content and communication journey

  • Club email cycles and HubSpot flows defined

    Personalized member communication running on HubSpot.

    Reputation & DataVTEX ClubConfirmed

    Dependency · Segments and communication rules

    Evidence · Active email flows

  • OFFBounds newsletter formats, tags and audiences defined

    Public, internal and exclusive Club content clearly separated.

    OFFBoundsVCCVTEX ClubVTEX.comConfirmed

    Dependency · Channel roles decision

    Evidence · Every format has a defined audience and channel

  • VTEX.com news and events requirements defined

    A public destination for news, events and ecosystem content.

    VTEX.comVCCOFFBoundsVTEX ClubConfirmed

    Dependency · Editorial ownership of VTEX News

    Evidence · Approved requirements document

  • VTEX.com first two navigation levels proposed

    Clear content navigation for every ecosystem project.

    VTEX.comVCCConfirmed

    Dependency · Channel and editorial decisions

    Evidence · Approved channel roles

  • Categorized ISV list consolidated

    ISVs discoverable by region and capability.

    ISVsVTEX.comOFFBoundsConfirmed

    Dependency · Regional and capability data

    Evidence · Updated ISV inventory available to participating projects

  • Two ISVs confirmed as MAT sponsors

    Master Architect Training funded and co-owned with partners.

    ISVsVTEX AcademyConfirmed

    Dependency · Sponsor proposition

    Evidence · Two confirmed MAT sponsors

  • H2 2026 Employer Branding coverage calendar created

    Culture and people content planned alongside the editorial model.

    VCCVTEX.comProposed

    Dependency · Employer Branding guidelines

    Evidence · Shared editorial calendar

  • Academy certification-link integration validated

    Certifications can surface inside the Club member area.

    VTEX AcademyVTEX ClubVTEX.comConfirmed

    Dependency · Masterdata validation

    Evidence · Validated integration path

  • Academy Battle of Bats / Agentic Conference recording published

    Event content reused as durable educational material.

    VTEX AcademyBattle of BatsVCCConfirmed

    Dependency · Recording and rights approval

    Evidence · Recording live and distributed

By three months

Next

  • Employer Branding communication guidelines available

    Consistent culture, tone and causes across every channel.

    VCCVTEX.comVTEX ClubProposed

    Dependency · Editorial model approval

    Evidence · Guidelines adopted by participating projects

  • Battle of Bats login and audience journey integrated

    Event audiences become identified, measurable CRM records.

    Reputation & DataBattle of BatsVTEX.comConfirmed

    Dependency · Site and identity requirements

    Evidence · Journey, engagement and lead data captured

  • Academy certifications visible in the Club member area

    Learning recognition becomes a Club member benefit.

    VTEX AcademyVTEX ClubVTEX.comConfirmed

    Dependency · Masterdata validation

    Evidence · Certifications rendered in the member area

  • Shared website, content, social and reputation measurement model operating

    One agreed way to read performance across projects.

    Reputation & DataVCCVTEX.comVTEX AcademyProposed

    Dependency · Metric ownership decision

    Evidence · Shared model adopted — Baseline required

  • Recurring editorial and cross-project routines operating consistently

    Collaboration becomes a cadence, not a series of one-offs.

    VCCISVsOFFBoundsVTEX.comVTEX ClubConfirmed

    Dependency · Accountability for maintaining the plan

    Evidence · Biweekly updates submitted by every project

By one year

Later

  • Academy content consolidated into the VTEX.com experience

    One public home for education and ecosystem content.

    VTEX.comVTEX AcademyProposed

    Dependency · Navigation model approved

    Evidence · Academy discovery from VTEX.com — Baseline required

  • Club members can access nominal learning benefits or coupons

    Membership carries tangible, recognizable value.

    VTEX ClubVTEX AcademyReputation & DataProposed

    Dependency · Certification and identity integration

    Evidence · Benefit redemption — Baseline required

  • Shared operating model reusable by new projects

    New projects join without rebuilding integrations and governance from scratch.

    Reputation & DataVCCVTEX.comVTEX ClubVTEX AcademyISVsOFFBoundsProposed

    Dependency · Ownership of the shared action plan

    Evidence · A new project onboarded using the existing model

Dependencies

Who is waiting on whom.

Every field is editable so the table can be revised live during the biweekly review.

Cross-project dependencies
DeliverableLeadContributorsDependencyDeadlineStatus

Decisions required

Unresolved, and blocking.

These decisions sit above the projects. Until they close, dependent deliverables stay in Defining.

  • What belongs on public VTEX.com versus the exclusive Club newsletter?

    Decision owner
    Required contributors
    Target decision date
    Resolution

  • Who has final editorial ownership of VTEX News?

    Decision owner
    Required contributors
    Target decision date
    Resolution

  • Who owns each shared metric and its data quality?

    Decision owner
    Required contributors
    Target decision date
    Resolution

  • What is the canonical source for ISV information?

    Decision owner
    Required contributors
    Target decision date
    Resolution

  • Which team owns ongoing HubSpot workflows after implementation?

    Decision owner
    Required contributors
    Target decision date
    Resolution

  • How will Battle of Bats users authenticate and connect to CRM records?

    Decision owner
    Required contributors
    Target decision date
    Resolution

  • Which project is accountable for maintaining the shared action plan?

    Decision owner
    Required contributors
    Target decision date
    Resolution

Operating model

The cadence that keeps it true.

Every two weeks

Each project updates:

  • What landed
  • What lands next
  • Current blocker
  • Decision required
  • Team needed

Every month

Review:

  • Overdue deliverables
  • Cross-project dependencies
  • Performance evidence
  • Scope changes

Every quarter

In-person or extended review to:

  • Confirm outcomes
  • Resolve ownership gaps
  • Reprioritize shared deliverables
  • Add or remove commitments