Prepared for Radisys Marketing Operations · Prepared by RevOps Global · 2026-05-19
A full year of partnership that takes Marketo from sender to revenue system. Audit, hygiene, scoring, lifecycle, attribution, and leadership reporting, sequenced against Radisys's stated priorities and gated quarterly.
This rebuilds the engagement from a Phase 1 audit into a full 12-month partnership. Phase 1, as scoped on 2026-05-19, becomes the first 30 days of Q1. Phase 2 and Phase 3 collapse into Q1 as well, since the 30 / 60 / 90 work covers what's strictly necessary to make the rest of the year possible.
Quarters 2 through 4 take the 504 hours currently sitting in the Deferred column of the Radisys 30/60/90 plan and sequence them against Radisys's stated priorities and the business outcomes Marketo can produce once the foundation is in place.
Phase 1 draft remains operational scope for Days 1-30. The 2026-05-19 Phase 1 proposal draft continues to govern day-to-day execution for the first month. This document supersedes it as the contracting frame.
After six years of Marketo running under-resourced, the conditions that held the prior cadence in place have closed. The window to convert Marketo from a sender into a revenue-generation system is open.
Radisys now has an executive-backed marketing operations owner with a clear mandate to fix Marketo. The accountability gap that defined the past six years has closed.
The prior cadence of ~5 hours per month kept the instance on life support. The work required to make Marketo a revenue-generation system, not just a sender, is multiples larger than that cadence allowed.
The marketing roadmap, the reporting expectations from leadership, and a potential rebrand cycle all sit on a 12-month arc. This proposal matches the same horizon Radisys is already planning against.
The engagement scales from the prior ~5 hours / month to ~50 hours / month. Dedicated senior RevOps capacity, sequenced against the work Marketo needs to produce real pipeline.
The 12-month arc honors these priorities. Day-by-day execution within Q1 is sequenced by dependency and deliverability risk, not strict priority order, so the Priority 1 templates ship safely on Day 21.
Five deliverables ship in the first 30 days. Sequenced by dependency and deliverability risk, not strategic priority order: suppression has to land before templates so new sends don't hit a poisoned database, and templates wait on Adobe admin access. The earlier days unblock Priority 1.
Every new campaign from Day 7 is reportable. Stops the legacy mess from growing.
6,693 dead contacts stop receiving sends. Deliverability protection from week 2.
Radisys's stated #1 priority shipping inside the first three weeks. New content can ship the day it lands.
Every form fill from Day 28 has clean source data, ending the attribution gap.
Hard numbers on legal exposure, ready for the executive team conversation.
These are early signals of value, not the foundation itself. The audits and operational rebuild work continue underneath through Day 90, producing the platform Q2 depends on.
Each quarter builds on the last. Foundation gives way to execution, execution gives way to scale, scale gives way to optimization and leadership reporting.
The platform Marketo should have been. A clean, compliant, governed instance with templates live, segmentation working, and source attribution flowing.
Marketo running as a revenue system. Scoring produces real MQLs, lifecycle flows route them, and the first leadership-facing ROI report ships.
Marketo plus Salesforce running ABM at modest scale. Buying group surfaced, target list mirrored, nurture in market, attribution model live.
A measurable, maintainable revenue engine with leadership-grade reporting. Year 2 conversation starts from a position of strength.
Year-1 planned scope is ~640 hours, ~$105,600. The retainer is structured against 600 hours / year ($99,000) with a 40-hour ($6,600) buffer line that absorbs the planned overage and cross-quarter shifts. Monthly billing keeps cash predictable; quarterly envelopes keep work properly sequenced.
Representative mockups from analogous RevOps Global engagements. Final outputs ship in Radisys brand, against Radisys data, in your Marketo and Salesforce instances.
Header, hero, body, CTA, and regional footer blocks compose any Radisys email. Drag-in modules, no HTML edits required.
| Segment | Count | Action |
|---|---|---|
| Hard bounces (180d) | 4,892 | Suppress |
| Role-based addresses | 1,203 | Suppress |
| Unsubscribed | 598 | Suppress |
| Never engaged (>2y) | 12,440 | Review |
| Active subscribers | 64,887 | Keep |
Every record sorted into suppress, review, or keep. Reason codes, counts, and one-click actions. Deliverability protection starts week 2.
Consent coverage, opt-in status, and EU residency gaps as hard numbers. The document that drives the executive conversation with legal.
Every stage transition is defined, instrumented, and recoverable. Wait, exit, and re-entry logic replaces six years of drift.
| Campaign | MQLs | Pipeline | ROI |
|---|---|---|---|
| 5G RAN Webinar | 142 | $1.2M | 8.4x |
| Open Telecom Brief | 89 | $680K | 4.7x |
| MWC Booth Follow-up | 54 | $310K | 2.1x |
| Q1 Newsletter Refresh | 23 | $45K | 0.6x |
Every campaign tied to SF opportunity, source taxonomy intact, ROI computed end-to-end. The number the Radisys exec team has been waiting for.
Two-axis grid surfaces MQL-ready accounts. Behavior scoring weighted against ICP fit; rules + decay + validation against historical pipeline.
Each lead carries a product-interest score per Radisys line. Routes the right lead to the right specialist team. Closes the 82% data gap.
Subscribers pick topics and cadence. Replaces all-or-nothing unsubscribes; rebuilds list health by retaining engaged contacts who just wanted less mail.
Multi-stakeholder B2B is the Radisys reality. This surfaces decision makers, champions, influencers, and economic buyers per account.
Decision-tree nurture replaces blast email. Each branch is observable; underperforming paths get tuned at the quarterly review.
Every channel weighted across the full buyer journey. Replaces single-touch models that under-credit nurture and over-credit demo requests.
SF-side target list mirrors the Marketo target list. Each tier has its own play, its own resourcing, and its own measurement.
Standardizes the L2C flow so SDR and AE handoffs are clean. Every step has an SLA, every conversion is logged, every drop-off is visible at the gate review.
Database to opportunity, top to bottom. Source-attributed, scored, lifecycle-driven, and refreshed on a schedule the board can plan around.
Sourced and influenced pipeline, deal velocity, and average deal size. The single page the CMO walks into a board meeting with.
The waterfall that proves the function, from pure mkt-sourced to influenced revenue. Closes the loop the executive team has been asking about.
Operational view for marketing operations and demand gen. Stalled stages surface before the QBR, not in the QBR. Filters by source, segment, and rep.
Once a year of clean work has accrued, the instance gets restructured to match how it is actually used. Folder convention, owner tags, archive policy.
These are illustrative mockups, not screenshots from past Radisys work. Final deliverables ship in Radisys brand, against Radisys data, against the Marketo and Salesforce instances you already operate.
The current 30/60/90 plan, executed as continuous work instead of a probation period. Phase 1 (Days 1-30, $13,200) is the first half; the second half rolls directly into Days 31-90 without a re-contracting break, because every deliverable in Q2+ depends on the data and structure built here.
A clean, compliant, governed Marketo instance with templates live, segmentation working, source attribution flowing, and an ICP that supports the scoring work in Q2.
Scoring, lifecycle, attribution and the first leadership-facing ROI number. Q1 made the data trustworthy. Q2 makes Marketo a revenue system on top of it.
Marketo running as a revenue system: scoring produces real MQLs, lifecycle flows route them, source attribution proves which channels work, and a first leadership-facing ROI report goes to the Radisys executive team.
ABM at modest scale, the first nurture program in market, multi-touch attribution, and a Salesforce-side target list that mirrors the Marketo target list. The data needed for Q4 leadership dashboards now flows.
Marketo + Salesforce running ABM at modest scale (buying group surfaced, target list mirrored), nurture in market, attribution model live. The data needed for the Q4 leadership dashboards is now flowing.
Marketo plus Salesforce as a measurable, maintainable revenue engine with leadership-grade reporting. The Year 2 conversation starts from a position of strength.
Marketo + Salesforce as a measurable, maintainable revenue engine with leadership-grade reporting. Year 2 conversation starts from a position of strength.
Radisys marketing operations and RevOps Global sit the review together. Three outcomes from each. Everything delivered to date is transferable: documentation, templates, scoring models, dashboards, audits.
Approve the next quarter as scoped. Work continues without a re-contracting break.
Adjust the next quarter's priorities based on what the prior quarter surfaced.
Take everything delivered to date and run it internally or with another partner. All work-product is transferable.
Phase 1's gate (Day 30) and the Day-90 review both remain, even though the engagement is continuous. They become check-ins inside Q1, not contract-renewal moments.
These are deliberately excluded from the Year-1 retainer. The Year-2 conversation starts at the Q4 review.
A flat monthly retainer at $165 per hour, structured against 600 hours per year (~50 hours per month). Predictable cash flow, with a 40-hour cross-quarter buffer that absorbs the planned overage and any mid-year shift.
Hours flex month-to-month within the quarterly envelope. Unused capacity does not roll past the quarter; over-runs are surfaced at the gate review before they bill.
Monthly billing keeps cash predictable; quarterly envelopes keep work properly sequenced. Each gate review can re-balance the next envelope without restarting the contract.
From signature to kickoff, in five business days.
Approval frames Year 1. The Phase 1 draft remains the operational scope for Days 1-30.
Phase 1 prerequisite, still pending Adobe custom-role resolution. Required to ship the Email Template Framework on time.
Within 5 business days of approval. Aligns the team on Q1 sequencing, dependencies, and weekly cadence.
Both held even though the engagement is continuous. They become check-ins inside Q1, not contract-renewal moments.
Questions or scope changes go to Greg at greg@revopsglobal.com. Source plan: Radisys Martech and RevOps Maturity Plan, 30/60/90 Day Plan V2. This document supersedes the 2026-05-19 Phase 1 proposal draft (now Q1 Days 1-30 scope).