Launch BOM: CloudBees Unify
Tier: 1 (Strategic bet) · Primary objective: Pipeline / Revenue · Date: 2026-07-30 (reconstructed from the May 2025 launch)
This is a retroactive Tier 1 BOM built from the actual Unify timeline (competitive signal in early Feb 2025, launch May 20, 2025, executive-narrative rebuild October 27, 2025), reconstructed as the project plan that would have been briefed on day one, if the project had been scoped as a formal launch plan rather than run live.
RACI (generalized roles)
R = Responsible (does the work) · A = Accountable (owns the outcome, signs off) · C = Consulted (input before it ships) · I = Informed (told after)
| Workstream | PMM | Exec Sponsor (VP PMM / CPO) | Product | Analyst Relations | Sales Enablement | Sales (AE/SE) | Corporate Marketing (Comms/PR/Brand) | Demand Gen | Customer Success |
|---|---|---|---|---|---|---|---|---|---|
| Positioning & messaging house | R | A | C | I | I | I | I | I | I |
| Message validation (buyer testing) | R | A | C | — | — | — | — | — | — |
| Analyst briefings (MQ / Wave submissions) | R | A (delivers briefings) | C | R | — | — | I | — | — |
| Sales enablement (course, plays, mini SKO) | R | C | C | — | R | C | — | — | — |
| Champion program (top reps) | R | I | — | — | C | C | — | — | — |
| Funnel instrumentation & win-rate scoring | R | I | — | — | — | C | — | — | — |
| Press release | C | A | I | — | — | — | R | I | — |
| Launch-day moment (press event / brand activation) | C | A | I | — | — | — | R | I | — |
| Launch blog (exec byline) | R (narrative) | R (byline) | C | — | — | — | C | I | — |
| Webinar series | C | I | I | — | I | I | I | R | — |
| Campaigns & outreach | C | I | — | — | — | I | I | R | — |
| Field cadence (biweekly/weekly syncs) | R | I | C | — | C | C | — | I | — |
| Customer reference conversion | C | I | I | — | — | C | — | — | R |
| Executive-narrative rebuild (fast-follow) | R | R (byline) | C | — | — | I | C | I | — |
Note on Analyst Relations: at CloudBees this sat inside PMM (Drew led the MQ/Wave submissions and prepped the VP of PMM to deliver the briefings), so the column above is really "PMM wearing the AR hat." Kept as its own column because a Tier 1 launch at a company with a dedicated AR function would staff it separately.
TL;DR
Unify was a category-reframe launch (control plane vs. platform) triggered by a competitive signal, built on a 16-week clock, and executed with an awareness-grade spectacle (press, a Nasdaq/Times Square activation, a webinar series). But the metrics that actually governed it, Stage 1→3 conversion, deal size, referenceable customers, were Pipeline/Revenue metrics, not awareness metrics. That mismatch is the retroactive lesson this BOM is built to correct: had the objective been declared Pipeline/Revenue on day one instead of implied by the metrics chosen later, funnel instrumentation and sales enablement would have been critical path from T-16 weeks, not backfilled after a quarter of "great impressions, no pipeline."
Bill of Materials
Critical path (blocks launch)
| Deliverable | Owner (suggested) | Depends on | Target timing |
|---|---|---|---|
| Positioning & messaging house (control plane framing) | PMM | Competitive signal, product truth from Product | T-16 to T-12 weeks (early-mid Feb 2025) |
| Message validation (Wynter test against real buyers) | PMM | Draft messaging house | T-12 weeks |
| Analyst briefings (Gartner MQ, Forrester Wave submissions) | PMM / Analyst Relations | Validated messaging | T-10 weeks (long-lead, briefings have fixed submission windows) |
| Funnel instrumentation (Stage 1→3 tracking, Gong pitch-relevance scoring) | PMM | Primary metric declared as Stage 1→3 conversion, not campaign volume | T-6 weeks (must be live before launch, not added after Q1 showed no pipeline) |
| Sales enablement (SDLC 101 course, sales plays, mini SKO) | PMM + Sales Enablement | Validated messaging | T-6 to T-2 weeks |
| Champion program (top reps, biweekly) | PMM + Sales | Enablement shipped | Launch week, ongoing |
| Biweekly AE/SE cadence | Sales + PMM | Enablement shipped | Launch week, ongoing |
Standard (ship it)
| Deliverable | Owner (suggested) | Depends on | Target timing |
|---|---|---|---|
| Launch blog (CPO byline, architect audience) | Exec Sponsor + PMM | Positioning locked | T-2 weeks draft, publish launch day (May 20) |
| Press release | Corporate Marketing | Positioning locked | T-4 weeks draft, launch day |
| Launch-day activation (Nasdaq / Times Square) | Corporate Marketing | Creative + positioning locked | T-10 weeks (long-lead production) |
| Weekly market-intel newsletter to field | PMM | Launch shipped | Launch week onward, ongoing |
| Customer reference program | Customer Success + PMM | Early adopting accounts | Post-launch, ongoing through fiscal year end |
| Webinar series | Demand Gen | Positioning + enablement | Post-launch fast-follow |
| Executive-narrative rebuild (CIO/security audience) | Exec Sponsor + PMM | Win/loss data showing the architect-first version wasn't reaching economic buyers | T+22 weeks (October 27, 2025) |
Optional / stretch
| Deliverable | Owner (suggested) | Why it's optional here |
|---|---|---|
| Paid social amplification | Demand Gen | Top-of-funnel volume was never the constraint; the funnel data proved this within one quarter |
| Additional analyst content beyond MQ/Wave | Analyst Relations | Two flagship submissions covered the credibility bar this launch needed |
| SE demo sandbox automation | PMM + SE | Valuable deal-cycle accelerant, but a mid-cycle enhancement, not a launch-day dependency |
Messaging focus
- Lead with the reframe (coordinate vs. consolidate), not a feature list. The "control plane" language was claimed in February, before the market had the term, specifically so CloudBees defined it rather than answered it.
- Two audiences, two pieces of copy, sequenced: architect-first at launch, CIO/security economic-buyer version as a deliberate fast-follow once win/loss showed the first wasn't reaching the people who sign.
- Keep the SDLC lifecycle claim honest: Unify credibly played in Test/Release/Deploy/Govern, not Plan/Code. Don't let campaign copy overreach into stages the product doesn't touch.
Sequencing notes
- Analyst submissions and the launch-day activation are the two genuine long-lead items; both need to start by T-10 weeks or they slip the date, not the launch.
- Funnel instrumentation has to exist before launch, not get added after a quarter of vanity metrics. That's the single change this retroactive plan makes versus what actually happened: promote it from an afterthought to critical path.
- The executive-narrative rebuild is a planned fast-follow, not scope creep: it depends on data (win/loss) that doesn't exist until after a full sales cycle post-launch, so it can't be pulled earlier no matter how the plan is sequenced.
What we're deliberately NOT doing
- Not treating campaign impressions or asset-delivery counts as a launch KPI. They were explicitly rejected in favor of Stage 1→3 conversion, and the one quarter they were allowed to stand in as a proxy is exactly when the launch looked like it was working and wasn't.
- Not running a full-lifecycle campaign (Plan through Govern). Scoping the narrative to the stages the product actually wins keeps sales honest about what closes.
- Not over-investing in paid/social amplification. Top-of-funnel was healthy on day one; the constraint was always further down the funnel.