Dico Angelo

🧠Mission → Vision → Values → Objectives → R&R → Value-Add

The confidant's framing: “roles and responsibilities tied to objectives of the org, which are tied to the objectives of OUR company.” Below is that cascade — synthesized from the recruiter screen (2026-04-13) and Nebius public posture.

Values (recruiter-confirmed signals)

• Hyper-growth + hyper-scale — “the hyper growth and hyper scaling is definitely very real right now.”
• Builder culture — “really build and iterate and break things and fix them.”
• Startup-native velocity even at scale — explicitly named “startup vibe.”
• Cross-functional influence as a first-class skill — RevOps / Finance / Sales / Legal / Marketing alignment is baseline, not aspirational.
• Operational rigor over operational theater — centralized reporting is the gap to fix, not the brand to polish.

Strategic Objectives (this fiscal window)

⚡Operating Doctrine — Learning > Rate of Change

Nebius is hyper-growing. The role is being defined in real-time (manager hired 4–5 weeks ago, two new seats being hired, partner ops function taking shape). In that environment, only one thing protects the operator:

The rate at which I learn has to exceed the rate at which the organization changes.

• AI-native compounding: every conversation, transcript, and artifact feeds a persistent knowledge system. I don’t re-learn — I accumulate.
• Builder-independent operator: I ship without needing the org to hand me process. Process is something I build alongside the function.
• Cross-functional posture: RevOps / Finance / Sales / Legal seat-swaps at Contentsquare. The muscle is live.
• Compound feedback: every panel round becomes new intel into the same knowledge base.

🔗Role R&R vs Dico R&R — Tied to Each Nebius Objective

Crosswalk: what Nebius is hiring for, next to what I have already shipped. This is the “I hope you would agree I have much of the skillset you’re looking at” structure — objective by objective.

O1 — Launch Partner Portal (Salesforce-based)

Nebius asks for: roll out and maintain the new partner portal built in Salesforce.

Dico brings:

• Rocket Mortgage: co-built the partner portal connecting real estate agents and mortgage agents across Ontario. Salesforce admin privileges, power user.
• Contentsquare: assisted the OneCRM project unifying six-to-seven platforms onto Salesforce as SOT.
• Tie-back: I don’t ramp into portal rollout — I repeat a playbook I have already shipped twice.

O2 — Salesforce Migration

Nebius asks for: drive Salesforce migration execution alongside ongoing managers.

Dico brings:

• Contentsquare OneCRM: drove unification across Crossbeam, Reveal, PartnerStack, Google Sheets, AWS Partner Central, Microsoft Partner Center, Suger API bridge into Salesforce SOT.
• Cash-to-quote migration with RevOps — lived through the cross-functional sign-off phases (legal, revenue, sales).
• Tie-back: The exact reference architecture Nebius needs — multi-platform partner data unified to Salesforce with an API bridge pattern.

O3 — Centralized Reporting + Analytics (the named gap)

Nebius asks for: pull data from CRM, build dashboards, deliver to the teams that need to know.

Dico brings:

• 50+ dashboards in Looker Studio and Salesforce at Contentsquare feeding partner sales managers + AWS/Microsoft co-sell reps.
• AI-native power user — Claude Code, agentic orchestration, and terminal-level intelligence extraction. Dashboards that compound rather than go stale.
• Tie-back: The exact gap the team is missing is what I have been closing for six years, and the AI-native layer 10x’s delivery speed.

O4 — Scale Partner Ops to Nebius Hyper-Growth

Nebius asks for: independent builder who can scale the function while the org is shape-shifting.

Dico brings:

• 6 years in partner operations across two companies through merger/integration phases — scaled systems while the business was shape-shifting underneath them.
• Claude Code + agentic orchestration toolchain — ship dashboards and analysis in hours, not sprints. 58 production tools, 212 tests, 93.1% routing accuracy.
• Tie-back: Velocity that matches the hyper-growth + hyper-scaling pace the recruiter named.

O5 — Influential Support for Partner Alliances + Revenue Team

Nebius asks for: influential + supporting function — not just reporting, but shaping how partner ops takes shape.

Dico brings:

• Contentsquare: day-to-day AWS ACE owner + Microsoft Partner Center owner — direct operator relationships with both hyperscalers, co-sell attribution and referral flows.
• Partnership Leaders community member — active in the partner ops ecosystem, not just an internal operator.
• Tie-back: An existing rolodex + pattern library at the two hyperscaler partners the recruiter named as the biggest nice-to-have.

✅Crosswalk — Nebius Asks / Dico Brings

📅30/60/90 — Partner Ops Execution Plan

Concrete first-90-days plan, anchored to O1–O5. This is what I commit to in the offer conversation.

Days 1–30 — Ground Truth + Quick Wins

• Audit the Salesforce instance: objects, permissions, data model, integration points, reporting structure. Document current state.
• Shadow the hiring manager + sibling partner ops manager. Understand the partner portfolio: AWS, Azure, NVIDIA, GCP, regional SIs.
• Meet RevOps, Finance, Sales, Legal, Marketing points of contact. Map the cross-functional seats.
• Inventory the existing reporting — what exists, what’s stale, what’s missing.
• Day-30 deliverable: 3 foundational dashboards (partner pipeline, deal reg throughput, portal usage readiness) shipped to leadership.

Days 31–60 — Portal Launch + Reporting Backbone

• Co-own the Salesforce Partner Portal launch. Partner onboarding flows, tier eligibility logic, deal registration workflow, MDF request handling.
• Build the centralized reporting spine: partner-sourced vs partner-influenced revenue, co-sell attribution, marketplace pipeline, program health KPIs.
• Document Rules of Engagement across partner segments (direct sales, partner teams, cloud provider reps).
• Stand up the operating cadence: weekly ops review, pipeline review, monthly partner QBR template.
• Day-60 deliverable: Portal live with first cohort of partners. Reporting layer serving the revenue team.

Days 61–90 — Scale + Influence

• Migrate remaining partner data sources into Salesforce SOT. Deprecate shadow systems and spreadsheets.
• Automate 80% of manual deal reg + MDF + marketplace workflows (pattern from Contentsquare: 8 minutes → 30 seconds).
• Deliver forecasting + capacity modeling inputs into annual planning cycle.
• Begin AI-native layer: agentic reporting, automated partner intelligence briefings, self-healing data pipelines.
• Day-90 deliverable: Partner ops function running on centralized reporting, cadenced operations, and 50%+ reduction in manual touch-time.

⭐STAR Portfolio — 7 Wins That Map to Nebius

Situation / Task / Action / Result. Each story maps directly to at least one of O1–O5.

📈Take-Home Simulation — HubSpot→Salesforce Cutover

Full simulated take-home for this role. Built against a synthetic-but-realistic 4-CSV dataset (43 partners, 200 opps, 54 deal-regs). Every artifact is production-grade, not an outline. Open the interactive dashboard first — everything else supports it.

📊Headline Numbers

📃Deliverables

🔑The Thesis

Every rule in this package is downstream of one governance gate: Deal_Registration__c.Origin_Flag__c, locked at Stage=Propose, gated by a T-14 freeze window. Name the gate before the rule. That's the difference between a partner-ops program that scales with 547% YoY growth and one that dies at the next parallel-run.

📊Neocloud Competitive Context

Nebius is competing with a small number of AI-native infra challengers. Understanding that landscape is table stakes for the partner ops seat — partner positioning is how neoclouds win or lose the ISV/model-builder ecosystem.

The Neocloud Cohort

🎯Where Partner Ops Wins the Category for Nebius

• Co-sell discipline with hyperscalers: Nebius sits adjacent to AWS, Azure, GCP. A working AWS ACE + Azure Marketplace motion is a moat the pure-GPU players don’t operate yet.
• NVIDIA alignment operationalized: NVIDIA is already a partner — the question is whether partner ops turns that into deal reg throughput and co-sell pipeline.
• ISV + model-lab ecosystem: The category winner will be the neocloud whose partner program is easiest to build against. Program design, deal reg, and MDF matter.
• Regional SI network: The next phase is regional SI coverage — exactly the segment where my Rules of Engagement and governance design experience applies.

🔌Partner Ecosystem Thinking — Tiers & Motions

A working partner program separates by tier and by motion. At Contentsquare I designed this from scratch. Here’s how I’d start at Nebius.

Rules of Engagement (the governance layer)

• How direct sales, partner teams, and cloud-provider reps coordinate on overlapping accounts.
• Deal reg precedence rules — who gets credit when a deal touches multiple motions.
• Approval thresholds: MDF disbursements, promo credits, tier exceptions.
• Escalation path for channel conflict — documented, repeatable, enforced.
• Conflict minimization across segments is where partner programs succeed or fail at scale.

💬Questions for the Nebius Panel

The confidant's direction: after the alignment story, invite them to speak. Ask — then shut up. Let them share their version of the fit.

Value-Add Framing Questions

• “I hope you would agree I have much of the skillset you’re looking at. Given our conversation, how do you see my skillsets being able to add value to the mission of the organization? I’d really like to do that.”
• “Where do you see I can add value within the organization — beyond what’s in the job description?”
• “From your side of the team, what would the ideal version of this seat look like six months in?”
• “If I don’t yet see it — where else do you see that I can contribute? I’d look forward to exploring that as a builder.”
• “What does being a strong team member + team player look like inside this team specifically?”

Operating Questions

• What’s the current Salesforce maturity — greenfield build or replacing an existing system?
• What’s the internal launch milestone cadence for the Partner Portal?
• Who are the named partner alliances the team is prioritizing this fiscal window?
• How is the RevOps / Partner Ops boundary drawn today?
• What would “centralized reporting done right” look like to this leadership team?

Close — What I Commit To

• Rolling out + maintaining the new Salesforce partner portal from day one, using Rocket Mortgage + Contentsquare playbooks as reference architecture.
• Standing up centralized reporting as the first deliverable — the gap the recruiter explicitly named.
• Driving the Salesforce migration alongside the managers, acting as systems/analytics lead while they own team/strategy.
• Owning AWS ACE + Microsoft Partner Center integrations from day one — no ramp-up on the two biggest nice-to-haves.
• Bringing AI-native toolchain velocity — dashboards, automations, agentic workflows — to 10x the function’s throughput as Nebius scales.

“Thanks very much. I really look forward to meeting those objectives and adding value to the mission of the organization — looking forward to Nebius.”

Partner Operations Roadmap

"The best way to predict the partner channel of 2027 is to build the operating system for it in 2026. Salesforce is the substrate; the portal is the surface; reporting is the steering wheel — together they are the channel engine that lets Nebius scale partner-sourced revenue without scaling the partner-ops headcount."

🎯The Thesis

Nebius is mid-flight on the most leveraged moment in its GTM history: a 547% YoY clock, the Meta $27B + Vera Rubin window, and a 5-week-old Partner Operations function that owns three of the highest-impact deliverables on the company roadmap — Salesforce cutover, partner portal launch, and centralized reporting.

This roadmap is not a 90-day plan. It is the answer to: what does the Partner Operations function look like in 12 months if Dico runs the systems & analytics seat?

• Q2 2026 — Cutover: Land the HubSpot → Salesforce migration without losing partner attribution.
• Q3 2026 — Portal: Ship the partner portal as the single ingress point for deal-reg, MDF, and co-sell.
• Q4 2026 — Reporting: Centralized partner-sourced/influenced reporting on Snowflake + Tableau, SOX-auditable.
• Q1 2027 — Engine: Channel engine running on autopilot. Partner-ops headcount stays flat while partner-sourced revenue compounds.

⚡Phase 1 — Cutover (Days 1–90)

Theme: Land Without Losing Attribution.

DELIVERABLE: SF SOT live. Partner-attribution preservation rate ≥ 99.5%. Zero forecast disruption.

Honest probability: 80%+ on-time if Candace clears the governance lane in week 1. 50% if SI dependencies block.

🌐Phase 2 — Portal (Days 60–180)

Theme: One Door, Every Partner Motion.

DELIVERABLE: Portal GA. >70% partner adoption by Day 180. Deal-reg cycle time cut by 60%.

Honest probability: 70% on-time. Build-vs-buy decision (Experience Cloud vs Impartner) is the critical-path swing.

📊Phase 3 — Reporting (Days 150–270)

Theme: Steering Wheel for the Channel.

DELIVERABLE: Single source of truth for partner revenue. Exec confidence in partner-channel attribution at 95%+.

⚙️Phase 4 — The Engine (Days 270–365)

Theme: Compound Without Scaling Headcount.

📈Honest Metrics — The 12-Month Scorecard

🚀The Three-Year Arc

Year 1 builds the engine. Years 2–3 are where Nebius pulls away from CoreWeave / Lambda / Crusoe on partner-channel leverage:

• Year 1 (2026): Cutover → Portal → Reporting → Engine. The operating substrate.
• Year 2 (2027): Channel becomes the primary growth lever. Marketplace & NCP co-sell drive 35%+ of net-new ARR. Tier-gating on Rubin/Blackwell allocations becomes the alliance flywheel.
• Year 3 (2028): Nebius is the partner-friendliest neocloud at scale. Agentic partner-ops handles the long tail; humans focus on top-20 alliance economics. Partner channel runs at hyperscaler-grade rigor with neocloud-grade speed.

"The Ingram Micro of AI infrastructure" — not as a slogan, as a functional reality. The Partner Operations function is the load-bearing wall.

🔧Tech Stack Reality — What Nebius Has vs. What Ships Next

Synthesized from recruiter signals + job-req language + Salesforce Enablement Trainer posting + public LinkedIn signals. Gaps below are the Phase 1–2 build surface.

📊Partner Data Model — The Object Graph I'll Build

Every deal-reg workflow, attribution rule, and SOX touchpoint lives or dies on this object graph. Built once at Contentsquare, ready to ship again.

💰License Math — Login vs. Member-Based Break-Even

Partner Community licensing is the hidden unit-economics lever. Wrong choice at 500 partners = $600k/yr burn. This is a Day-30 decision.

🔒Sharing Architecture — Partner Data Isolation Without Fragmenting SSOT

Partner A cannot see Partner B's deals. Alliance manager must see both. SOX auditor must see all. This is solved with OWD + Sharing Sets + ARDSR — not custom code.

🔥Why I'm the Right Operator for This Roadmap

• Already shipped this exact playbook once: One-CRM at Contentsquare unified HotJar + CSQ + a 3rd company onto SF SOT via Sugar API bridge. Same migration shape, same attribution-preservation problem.
• Already runs the partner-portal motion: Day-to-day owner of AWS Ace + Microsoft Partner Portal at Contentsquare. Knows the deal-reg, MDF, and co-sell mechanics from inside the partner-side experience.
• Already wired the data unification stack: Crossbeam + Reveal + PartnerStack + Sheets → SF, with attribution preserved across all four ingress paths.
• AI-native operator: Top 1% ChatGPT, 4-month Claude Code sprint, agentic orchestration in production. The Year 2–3 AI layer is not aspirational — it's the muscle I already train daily.
• Public-co change-management vocabulary: Governance pair, stage gates, SOX-auditable workflow design — speaks Candace's Prosci/ACMP language natively.

The Ask

Give me the Systems & Analytics seat, the SF Tower desk, top-of-band comp + RSU equity, and the runway to ship Phase 1 by end of Q2. The roadmap above is the return on that investment.

DICO ANGELO · PARTNER OPERATIONS · NEBIUS 2026

🧠Nebius Stack Quiz — Do I Actually Know What They Run?

15 questions pulled from the JD, recruiter screen signals, Salesforce Enablement Trainer req, Candace Jenum's hiring pattern, and comparable neocloud partner motions. Click an answer → reveal the evidence. Score persists in localStorage.

💰Comp + SF Relocation Strategy

Recruiter screen anchor was $180k base — under-represented vs. the posted band of $185–225k + OTE. This panel resets the anchor to top-of-band, layers SF Tower co-location as compounding value, and stacks equity + sign-on.

⚔1. The Anchor Reset

The $180k number was a screen-stage placeholder, not a final ask. Three signals justify the reset:

• Posted band ceiling: $225k base is on the JD — the company has already authorized it.
• Revealed scope: Salesforce cutover + portal launch + centralized reporting = three Q-shaped objectives, not one. That's senior-IC-plus-systems-architect territory.
• Velocity premium: Candace inherits a 5-week-old org. A candidate who can ship the Q1 cutover under SOX gates is buying her quarters of credibility — that's worth top-of-band.

NEW ANCHOR: $210–225k base · +30–40% OTE · equity refresh · SF relocation

🏛️2. SF Relocation Thesis

Nebius's main US hub is the SF Tower. Relocating there compounds value in ways remote-from-Texas cannot:

• Proximity to decision-makers: Laurelle Roseman (VP Global Partnerships), Dave Boroditsky (CRO), Dan Lawrence (GM Americas) are in-Tower. In-person hallway access shortens decision cycles 3–5x vs. async.
• Atmosphere = learning rate: The Rubin window + Meta $27B + 547% YoY clock all run hot in the SF building. Being inside that signal density beats any dashboard.
• Partner co-sell motion: NVIDIA HQ (Santa Clara), AWS SF, hyperscaler GTM teams, every NCP partner — SF is the center of mass.
• Recruiting + retention signal: Willingness to relocate for the role telegraphs commitment — counter-signal against the Texas/TN-visa friction story.

Frame: "I'd like to be in the SF Tower from Day 1. The cost of co-location pays back inside the first quarter on cutover velocity alone."

📊3. Comp Structure — The Full Ask

🎤4. Pitch Script — Raising It With Candace

"Candace — before we wrap, I want to be transparent about comp. The $180k I gave on the screen was my floor going in cold; now that I've seen the scope — cutover, portal, reporting, all under SOX gates — and learned more about the SF Tower as the GTM heartbeat, my real ask sits at the top of the posted band: $215–225k base, OTE that ties to the Q1 deliverables, an RSU grant that lets me compound with the IPO ramp, and a relocation package so I'm in-Tower from Day 1. I'd rather be expensive and inside the building than cheap and remote — the velocity delta is worth more than the spread."

⚠️5. Walk-Away Calculus

Hard floors — below these, the role doesn't pencil out:

• Base < $200k — below this, I'm taking a paycut vs. trajectory at Contentsquare with no offsetting equity story.
• No TN visa legal coverage — immigration cost shifted to me makes the move uneconomic.
• No annual RSU refresh commitment — a single sign-on grant without refresh = compensation cliff in year 3.
• Relocation gap > 30 days — if I can't be in-Tower by start date + 30, the SF thesis collapses.

Soft preferences (would accept trade-offs): exact OTE structure, sign-on size, equity vest schedule shape (back-weighted OK if grant size compensates).

📈6. Why This Lands

• Frame as investment, not cost: Every dollar above $180k buys cutover velocity Candace can't get elsewhere.
• SF relocation neutralizes the "remote Texas" objection: Removes the friction story before they raise it.
• Equity ask aligns with NBIS upside: Signals long-horizon belief in the Nebius thesis — the opposite of mercenary.
• Top-of-band is already authorized: Asking inside the posted band is not a stretch, it's reading the room correctly.

🎯Interview Walkthrough — Live Panel Script

How to navigate this battle station live during a 45-min panel. Each step = one tab, with opening line, what to show, and transition cue. Hit W anytime to return here. Use ← → discipline — never more than 90s per tab.

🎤Pre-flight (before share-screen)

• Theme check: Dark mode on for panel. Verify battle station loads without lag.
• Open tabs: (1) This site, (2) LinkedIn profiles of panelists, (3) notes scratchpad.
• Opener (before sharing): "Before I share, I built a living doc that maps every one of Candace's three Q1 priorities to evidence from my last role. I'll use it as a visual anchor — happy to drive or follow your lead."
• If they decline: Keep tab keys 1, 4, 5 memorized — verbal only, no screen.

📌Step 1 — Overview (key 1) · 90s

Open with: "Nebius is building partner ops from scratch inside a hyper-growth neocloud. That's exactly what I ran at Contentsquare — 3-person cloud alliance team, zero-to-$30M marketplace, $800M+ TCV. I don't ramp into this role; I repeat a playbook."

Show: Ecosystem Capability Stack diagram + Thesis card.

Transition: "Let me walk you through how my background aligns with your stated mission —" (press 2)

🎯Step 2 — Alignment (key 2) · 60s

Open with: "Your public mission is democratizing AI infrastructure. My translation: partner ops is the force-multiplier that turns GPU capacity into revenue velocity. Every row below is a line from my history that already did that motion."

Show: Confidant cascade; scroll through 3 alignment rows.

Transition: "Now to the R&R map —" (press 3)

📝Step 3 — R&R Map (key 3) · 90s

Open with: "This is where the fit gets literal. Left column: Candace's JD. Right column: what I already shipped. Green means I've done the exact thing at similar scale."

Show: 3 rows maximum — pick: Salesforce migration, Partner portal, Reporting layer.

Transition: "If we fast-forward to day one —" (press 4)

📅Step 4 — 30/60/90 Plan (key 4) · 90s — hero tab

Open with: "Here's my 90-day plan. Days 1–30: ground-truth the cutover, shadow deal-reg, no code changes. Days 31–60: ship the partner portal MVP on Experience Cloud. Days 61–90: stand up the reporting layer with SOX-auditable attribution."

Show: Full plan timeline. Let them read.

Transition: "To ground that in evidence —" (press 5)

⭐Step 5 — STAR Wins (key 5) · 60s + on-demand

Open with: "These are my three strongest receipts. I'll drop one in full when it's relevant to a question you ask — rather than prescribing which."

Show: Titles only; expand on question. Default hero: HubSpot→SF cutover with Sugar API parallel flow.

Transition: "On the market context —" (press 6 or skip to 8 if time tight)

⚔️Step 6–7 — Competitive + Ecosystem (keys 6 7) · 45s each

Only if Laurelle is in the room. Pivot on: "I've tracked CoreWeave, Lambda, Crusoe partner tier-gating; here's where I think Nebius's Rubin allocation wedge lands."

Transition: "I have three questions I'd love your take on —" (press 8)

❓Step 8 — Questions (key 8) · 10 min protected

Open with: "I've got three I'd like your perspective on. First — [tier-gating question to Laurelle] / [change-mgmt governance pair to Candace] / [portal build-vs-buy to Panelist 3]."

Show: Let them see the list — signals you prepared named questions.

Transition: Do NOT jump to negotiation unless they raise comp.

💰Step 9 — Negotiation (key 9) · only if asked

Trigger phrase: "What are your comp expectations?" → open tab 9, share screen. "$180k base is my anchor; SF relocation is on the table; TN sponsorship is the constraint."

If not asked: Don't open. Close with Contact (0) instead.

📤Close — Contact (key 0) · 30s

Close with: "Everything you just saw is at the URL in the chat. You can drill into any diagram at 4K. Follow-up deck comes within 24 hours tailored to whatever we didn't get to."

🔮Emergency Overrides

• Panelist goes deep on one thing: Abandon the walkthrough. Follow them. STAR wins (5) is your safety net — any answer can route there.
• Time pressure (<15 min left): Skip 6/7. Go straight 4 → 5 → 8.
• Screen-share fails: Tabs 1, 4, 5 are fully verbal — you know them cold.
• Curveball question: Press R — Roadmap reframes as vision. Press Q — Stack Quiz if they want to test tactical depth.

📧Contact

Dico Angelo — Candidate, Senior Partner Programs Operations Manager, Nebius Group.

Logistics Snapshot

• Full comp scope: $185K–$225K USD base + stock + OTE. Aiming for $200K+ all-in to anchor the SF relocation economics.
• Location preference: SF Bay Area preferred — ready to relocate to the SF Tower hub. Compounds value vs. remote-from-Texas (in-room with Candace, Laurelle, alliance ICs; faster portal-launch feedback loops).
• Visa: TN visa sponsorship required. Declared up front; recruiter confirming internally. SF relocation neutralizes the "remote Texas" friction story.
• Current base: Lavon, TX (Dallas-Fort Worth metro). Remote-first interim; SF move on offer signature.
• Relocation asks: 60–90 day temp housing, moving stipend, return-trip clause if TN visa lapses.
• Start: Ready to start — 2-week runway to SF on signed offer.

Panel-Round Checklist

• Dashboard demo rehearsed — Looker Studio + Salesforce walk-through, 7 minutes, one screen share.
• OneCRM architecture diagram printed — Salesforce as SOT, API bridges to Crossbeam / Reveal / PartnerStack / AWS Partner Central / Microsoft Partner Center / Suger.
• Rocket Mortgage portal story compressed to 90 seconds — lead with the business outcome, not the build.
• Confidant Framework quotes memorized — delivered in one breath, then silence.
• Three questions cued up for each of the three panelists.
• Thank-you email drafted in advance — sent within 6 hours of each panel round.

References Available on Request

• Matt Rivron — AWS Account Manager. Co-built the AWS Scale Cloud Alliance with Dico day-to-day at Contentsquare.
• Former manager, Contentsquare Cloud Alliances — direct partner ops leadership reference.
• Rocket Mortgage Canada product + Salesforce ops leads — portal co-build reference.
• Partnership Leaders community — peer references across AWS, Microsoft, GCP partner ops networks.
• Suger.io case study — published third-party validation of the OneCRM unification work.

Appendix A — Systems Architecture Reference

Detailed reference for the OneCRM + Salesforce SOT pattern I would bring to Nebius. Included for the hiring manager / systems round.

Data Flow Pattern

• Salesforce as the system of record for partners, opportunities, deal registrations, MDF, and co-sell events.
• AWS Partner Central → Salesforce via AWS Ace API and Suger bridge. Bi-directional deal reg sync.
• Microsoft Partner Center → Salesforce via PRACR ingestion + MACC linkage object. Monthly submission cadence.
• Crossbeam → Salesforce account overlap enrichment. Populates partner intelligence on opportunity records.
• Reveal → Salesforce as a secondary overlap signal, used for Americas segment.
• PartnerStack → Salesforce for referral attribution, commission calculation, partner portal identity.
• Google Sheets → decommissioned, replaced by Salesforce reports + Looker Studio dashboards.

Reporting Spine

• Looker Studio connected to Salesforce via BigQuery export + direct connector.
• Core dashboards: Partner Pipeline, Deal Reg Throughput, Co-sell Attribution, Marketplace Revenue, MDF Utilization, Portal Adoption, Program Health.
• Executive view: partner-sourced vs partner-influenced vs direct, YoY trend, ACV trend, attach rate on deals over $200K.
• Partner-facing reporting via the portal: deal reg status, MDF balance, co-sell motions, certifications.
• Weekly ops review pack generated from the reporting spine — one PDF, one view, shipped Monday 9am.

Appendix B — Comprehensive Metrics Ledger

Every quantifiable number referenced in the portfolio, with source context.

Revenue & Pipeline

• $800M+ TCV processed across the cloud alliance program at Contentsquare.
• $30M+ marketplace revenue generated from a $0 starting point in 30 months.
• 14x AWS YoY growth trajectory during tenure.
• 81% larger average deal size on partner-influenced opportunities.
• 26-day shorter average sales cycle on partner-influenced deals.
• 40% cloud marketplace attachment on deals over $200K.

Operational Throughput

• 2,500+ deal registrations processed with 97% approval rate.
• 600+ deal registrations per quarter at peak throughput.
• 50+ dashboards in production across Looker Studio and Salesforce.
• 3K+ partner records validated during PartnerStack UAT.
• 10+ integration test cases executed before OneCRM production rollout.
• Deal registration cycle time: 8 minutes → 30 seconds after automation.
• 90% of manual partner ops workflows automated.

Financial Impact

• $222,750 annual cost savings across product ops (Rocket Mortgage).
• 7,425 hours per year recovered through process automation (Rocket Mortgage).
• $28K+ in MDF disbursements managed through AWS Payee Central.
• 98% accuracy on automated workflows.
• 90% user satisfaction on new feature rollouts.

AI-Native Toolchain

• 58 automation tools across 2 production MCP servers.
• 212 tests passing on the multi-agent orchestration framework.
• 93.1% routing accuracy on the agent coordination layer.
• 9,153 autonomous repairs executed by the self-healing routing engine.
• 94% error coverage in the production observability layer.
• 30 repositories, 10,871 commits shipped in a 4-month build sprint.
• 12.15M knowledge graph links across 7,100+ captured items.
• 270,000+ AI interactions captured and indexed.

Awards & Validation

• 2x Microsoft Partner of the Year (Contentsquare).
• Suger.io published case study on OneCRM unification.
• Master Cloud Marketplace Partner Insights webinar co-host.
• Partnership Leaders community — active contributor.

Appendix C — AI-Native Operating Layer

Detail on the toolchain that will accompany me into the Nebius seat. This is the 10x velocity layer.

Agentic Orchestration

• Multi-agent router coordinating specialized sub-agents for research, reporting, documentation, and operations.
• Context prefetcher that reads session history and pre-loads relevant knowledge before tasks begin.
• Cognitive bridge for cross-session memory — learnings compound across weeks, not sessions.
• Self-healing routing engine with 94% error coverage and 9,153 autonomous repairs logged.

Reporting Acceleration

• Dashboard scaffolding agents that generate Looker Studio and Salesforce reports from spec.
• Automated QBR narrative generation from pipeline data — human edits the final 10%.
• Partner intelligence briefings refreshed daily, delivered to named owners via Slack / email.
• Anomaly detection on partner pipeline — alerts when deal reg throughput diverges from forecast.

Portal Operations

• GoMotion — AI-powered partner sales platform with MEDDPICC scoring and CRM integrations.
• Integration surface: Salesforce, HubSpot, Crossbeam, Slack, Gmail, Google Calendar.
• Pattern for Nebius: embed the same intelligence layer inside the Salesforce partner portal so partners self-serve on deal reg, MDF requests, and co-sell motions.

Appendix D — Objection Handling

Likely objections from the panel, and how I will respond.

“You don’t have AI-infra domain experience.”

Correct — and the role is partner ops, not infra engineering. The operating patterns (deal reg, co-sell attribution, MDF, portal design, Salesforce SOT, Rules of Engagement) are the same across SaaS and infra. What’s different is the ecosystem: NVIDIA alignment, hyperscaler adjacency, model-lab ISVs. I close that gap by week two — the sovereign cloud research I have already done is the starting point.

“You’ve only been at two companies in partner ops.”

And both of them were through merger / integration phases where the systems were shape-shifting underneath us. Depth over breadth. Six years of compounding the same playbook makes me faster at the things Nebius needs shipped in the first 90 days.

“The AI-native framing is hype.”

Happy to run the demo live. 58 tools, 212 tests, production servers. I’ll show the dashboard stack, the agentic orchestration, and the partner intelligence briefing flow. The artifact speaks louder than the framing.

“TN visa is friction.”

TN is one of the cleanest US visa paths — same-day adjudication at the border for Canadian citizens. I have the documentation pack ready, and my prior employer has sponsored the same path. Happy to walk through the logistics with whoever owns immigration at Nebius.

“$180K is above our band.”

Open to conversation on total comp — base, OTE, equity, sign-on. The anchor is backed by current comp history and the Bay Area / NYC comparable. I’m motivated by the mission and the builder environment, and willing to structure to fit.

Appendix E — Tool Landscape Fluency

Every partner ops tool I have operated in production.

CRM & Reporting

• Salesforce — admin + power user. Flow, Process Builder, Apex trigger awareness, Lightning record pages, permission sets.
• Looker Studio — primary dashboarding tool at Contentsquare. 50+ dashboards in production.
• Tableau — used for executive reporting at prior engagements.
• Google Data Studio — predecessor to Looker Studio, same skill set.
• BigQuery — data warehouse layer behind the reporting spine.

Partner Platforms

• AWS Partner Central / AWS ACE — day-to-day operator, deal reg throughput, co-sell motions.
• Microsoft Partner Center — PRACR submissions, MACC linkage, Partner of the Year processes.
• Google Cloud Partner Advantage — deal reg and marketplace motions.
• NVIDIA Partner Network — exposure through ecosystem research and co-sell planning.

Ecosystem & Intelligence

• Crossbeam — account mapping, ecosystem intelligence, partner overlap enrichment.
• Reveal — secondary overlap signal for Americas segment.
• PartnerStack — referral attribution, commission calculation, partner portal identity layer.
• Suger.io — marketplace billing bridge, API integration pattern for OneCRM.
• Common Room — community intelligence (exposure).

Marketplace & Billing

• AWS Marketplace — private offers, CPPO (consulting partner private offer), channel resell.
• Azure Marketplace — MACC-eligible listings, private offers, co-sell offers.
• GCP Marketplace — private offer flow awareness.
• AWS Payee Central — MDF disbursement operations.

Ops & Collaboration

• Slack — workflow automation, partner ops channel governance.
• Notion / Confluence — playbook documentation, Rules of Engagement, SOPs.
• Google Workspace — core collaboration.
• Zapier / Workato / native Salesforce flows — automation fabric.

Appendix F — Additional STAR Depth

Supplementary stories beyond the seven headline STARs, for panelists who want to go deeper.

Appendix G — Partner Ecosystem Deep Dive

Tier-by-tier deep dive on the partner ecosystem design I would propose for Nebius. Built on the Contentsquare program design plus the Rocket Mortgage portal pattern.

Hyperscaler Alliance Layer — AWS

• AWS ACE deal registration motion — operational cadence, approval SLA, status sync into Salesforce.
• AWS Marketplace listing — private offers, CPPO, and consulting partner resell.
• AWS co-sell motion — opportunity engagement, partner solution finder, joint account planning.
• MDF flow through AWS Payee Central — disbursement operations, documentation, reporting.
• Target: partner-influenced revenue attached at 40%+ on deals over $200K (Contentsquare benchmark).

Hyperscaler Alliance Layer — Microsoft

• Microsoft Partner Center PRACR submissions on a monthly cadence.
• MACC linkage — Microsoft Azure Consumption Commitment — customer eligibility on every deal.
• Azure Marketplace listings — MACC-eligible offers, private offers, co-sell offers.
• Partner of the Year awards motion — submission, case studies, validation (Dico has done this twice).
• Target: active co-sell pipeline inside Microsoft Partner Center every quarter.

Hyperscaler Alliance Layer — NVIDIA

• NVIDIA Partner Network positioning — Nebius already has alignment. Operational depth is the gap.
• Joint reference architectures — publish with NVIDIA on GPU cluster patterns.
• NVIDIA co-sell motions — inference + training use cases routed to Nebius capacity.

Regional SI Layer

• Identify top 10 regional SIs by geography — North America, EMEA, APJ.
• Tier into Advanced / Select / Premier based on certification, committed volume, delivery capability.
• Rules of Engagement — direct sales, SI-led, co-sell, channel-through.
• Enablement layer — technical certification, deal reg training, portal onboarding.

ISV / Model Lab Layer

• Model labs running inference on Nebius — the most strategic tier for the next 24 months.
• Deep technical validation — joint reference architectures, performance benchmarks, migration playbooks.
• Co-marketed case studies — the Suger.io pattern, repeated across the model lab ecosystem.
• Program design — credit programs, migration MDF, joint GTM motions.

Referral Layer

• Introducers — lead-only, no delivery. Low-friction onboarding.
• PartnerStack or equivalent for attribution and commission.
• Simple incentive: fixed percent of first-year ACV, paid quarterly.
• Target: referral partners contribute a measurable slice of net-new pipeline by quarter 2.

Appendix H — Board-Level KPIs I Would Track

The KPIs I would commit to surface to leadership on a weekly cadence. Every one of them exists in the Contentsquare playbook.

Pipeline KPIs

• Partner-sourced pipeline — dollars and logo count, weekly delta, quarter-to-date trend.
• Partner-influenced pipeline — same cuts, separated by motion (co-sell, referral, resell, marketplace).
• Partner-sourced vs partner-influenced vs direct mix — board-level metric.
• Pipeline conversion rate by partner motion — identifies the motions that actually close.

Revenue KPIs

• Marketplace revenue by hyperscaler — AWS, Azure, GCP. Monthly recognition.
• Committed marketplace backlog — TCV remaining on active private offers.
• Partner attach rate on deals over $200K — proxy for co-sell muscle.
• Average partner-influenced deal size vs direct — the 81% lift number at Contentsquare.

Program Health KPIs

• Deal reg throughput — submissions per week, approval rate, time-to-approval.
• MDF utilization — budget committed vs deployed vs disbursed.
• Portal adoption — active partners, deal regs via portal vs email, onboarding completion rate.
• Certification coverage — partner technical certifications by tier.
• Partner NPS — quarterly pulse survey.

Team Health KPIs

• Seller NPS on partner ops — are partner motions making or hindering sales cycles.
• Cross-functional SLA adherence — legal, finance, marketing turnaround on partner workflows.
• Partner ops cycle times — deal reg, MDF request, contract execution.

Appendix I — Hiring Manager Round Prep

The hiring manager joined Nebius 4–5 weeks before the recruiter screen. The partner ops function is being built up right now. This is the fit narrative tuned for that round.

What a founding partner ops hire should bring

• Willingness to own the first draft of every document, SOP, and dashboard.
• Comfort operating without a playbook hand-off — you are writing the playbook.
• The instinct to ship the 80% version and iterate, not wait for perfect spec.
• Cross-functional credibility — RevOps, Finance, Legal, Marketing take your calls.
• AI-native velocity as a multiplier, not a hobby.

How I show up in the first 90 days

• Monday week 1: audit doc published — current Salesforce state, reporting gaps, partner portfolio.
• Friday week 2: first three dashboards in production, shared with leadership.
• Week 4: cross-functional RACI signed with RevOps, Finance, Legal, Marketing.
• Week 6: portal launch readiness checkpoint — risks, dependencies, owner list.
• Week 8: portal live with first cohort, reporting spine serving the revenue team.
• Week 12: automation layer live, deal reg cycle time cut by 50%+, weekly ops cadence running.

What I need from the hiring manager

• Clarity on the partner portfolio priorities this fiscal window.
• Named cross-functional counterparts in RevOps, Finance, Legal, Marketing.
• Decision rights: what I can commit to without escalation, what needs the manager.
• First-month milestone alignment — so we agree on what “shipped” means.
• Air cover during the first 30 days while I ground-truth before committing.

Appendix J — Operating Doctrine Expanded

Learning > rate of change.

The single operating principle that carries the role through the hyper-growth phase. Everything else is tactics.

AI-native compounding in practice

• Every conversation is transcribed, indexed, and searchable across sessions.
• Every artifact — dashboard, doc, playbook — is tagged into a knowledge graph.
• Context prefetcher surfaces relevant prior work before new tasks begin.
• Cognitive bridge synchronizes learnings across multiple concurrent sessions.
• The result: I do not re-learn. I accumulate.

Builder-independent operator

• I do not wait for process to be handed to me — I write the first draft, then iterate.
• Documentation is a first-class deliverable, not a follow-up.
• Automation is the default — if I do something twice, I automate the third time.
• The operating model scales without me becoming the bottleneck.

Cross-functional posture

• RevOps — data model and attribution are shared territory, not contested.
• Finance — MDF and marketplace billing are joint ownership, not hand-offs.
• Legal — partner contracts and data processing agreements move faster when I own the tracker.
• Sales — partner motions help sales cycles, not hinder them. That trust is earned weekly.
• Marketing — co-marketed case studies, joint campaigns, measured attribution.

Compound feedback loop

• Every panel round becomes new intel into the same knowledge base.
• Every partner manager conversation sharpens the next partner manager conversation.
• Every dashboard iteration informs the next dashboard iteration.
• The flywheel gets faster, not slower, as the org scales.

Appendix K — Risk Register & Mitigations

Honest list of risks I see in the seat, and how I would mitigate each.

Portal launch slips

Risk: Salesforce partner portal launch target is early fiscal window. Risk of scope creep, dependency on Salesforce admin bandwidth, partner data quality.

Mitigation: Ship a minimum viable portal — deal reg, MDF request, document library. Defer nice-to-haves. Phase 2 after first cohort validates the flow.

Salesforce migration stalls

Risk: OneCRM-style migrations stall when cross-functional sign-off (legal, revenue, sales) takes longer than forecast.

Mitigation: Start cross-functional alignment on day one. Weekly unblock meeting. Scope the migration in phases — partners first, then opportunities, then MDF, then marketplace.

Reporting layer gets bypassed

Risk: If leadership does not use the centralized reporting, the function becomes theater.

Mitigation: Ship the weekly Monday ops pack from week 1. Make it the default artifact for ops review. Iterate based on the questions that get asked in the meeting.

RevOps boundary fuzzy

Risk: Partner ops and RevOps overlap on data model, attribution, and reporting. Unclear boundary creates friction.

Mitigation: Week 1 conversation with RevOps lead. RACI on shared objects (partner, opportunity, quote). Joint ownership where it makes sense, clear hand-off where it does not.

Hyperscaler co-sell motion atrophies

Risk: If AWS ACE + Microsoft Partner Center motions do not have a named operator, they decay.

Mitigation: I own them from day one. Monthly cadence on PRACR, weekly cadence on AWS ACE. Status reported to leadership every Monday.

Partner NPS drops during migration

Risk: Portal launch + Salesforce migration is disruptive. Partners may lose visibility or experience friction during the transition.

Mitigation: Proactive partner communications. Named partner manager owner for every top-tier partner. Office hours during the launch window.

Appendix L — Themes from Recruiter Screen (2026-04-13)

Direct signals from the recruiter conversation, mapped to panel-round posture.

Build-from-scratch signal

Recruiter used builder language four different ways — build, iterate, break, fix. Build the program. Build operational processes. Build the team.

Panel-round implication: lead with builder anecdotes. Rocket Mortgage portal, OneCRM design, AI-native toolchain sprint. De-emphasize maintainer framing.

Greenfield urgency

Salesforce migration + portal launch by early fiscal window is a near-term high-stakes deliverable.

Panel-round implication: come in with a 30/60/90 that assumes I land mid-project. Show I have done the exact work under the exact time pressure.

Hyperscale stage

“Hyper-growth and hyper-scaling is very real right now.”

Panel-round implication: match velocity in the conversation. Crisp sentences. No long monologues. Ship, then verify.

Centralization gap

Team explicitly lacks a centralized reporting function.

Panel-round implication: own this as the wedge. Pair every claim with a specific Contentsquare or Rocket Mortgage anecdote. Bring the dashboard demo.

Recent formation

Manager hired 4–5 weeks ago. Two new seats being hired. Team assembling now.

Panel-round implication: founding-team dynamics. Ambiguity tolerance. The seat is being defined in real time — I bring shape to the function, not shape to myself.

Friction signals to manage

• Visa: not pre-cleared. Recruiter doing internal check. Panel should not assume this is resolved.
• Comp: $180K base not confirmed in-range. Could be in or above band.
• Recruiter is new herself — bonded answers may shift after hiring manager conversation.

Panel-round implication: lead with fit and value, let logistics follow. Do not re-open visa / comp in the technical rounds — those are recruiter-to-recruiter conversations.

Appendix M — Confidant Framework Reminder

The verbatim lines — memorize, deliver, then shut up.

“I HOPE YOU WOULD AGREE I HAVE MUCH OF THE SKILLSET YOU ARE LOOKING AT.”

“WHERE DO YOU SEE I CAN ADD VALUE?”

Then: LET THEM SHARE WITH ME HOW THEY SEE MY FIT.

DOCTRINE: Learning > rate of change.

The full delivery sequence

1. Open with the alignment cascade — mission, vision, values, objectives, R&R.
2. Tie my R&R to O1–O5, one objective at a time, with the Contentsquare / Rocket Mortgage proof.
3. Deliver the first Confidant line: “I hope you would agree I have much of the skillset you are looking at.”
4. Deliver the second: “Where do you see I can add value?”
5. Shut up. Let them share their version of the fit.
6. If they do not elaborate on team fit: “What does being a strong team member + team player look like inside this team specifically?”
7. Close with: “Thanks very much. I really look forward to meeting those objectives and adding value to the mission of the organization — looking forward to Nebius.”

Appendix N — Expanded Metrics Ledger (Contentsquare + Rocket Mortgage)

Every number I cite on a panel call has a source. This is the ledger behind the claims.

OneCRM Salesforce Migration — Contentsquare

• 6–7 source systems unified: Crossbeam, Reveal, PartnerStack, Google Sheets, AWS ACE, Microsoft Partner Center, Sugar CRM via API bridge.
• Migration window: multi-quarter, overlapping the cash-to-quote redesign.
• Cross-functional sign-offs shepherded: Legal (data processing), Revenue (attribution), Sales (workflow), Finance (marketplace billing).
• Salesforce-native data model: Partner object, Partner Contact, Partner Opportunity, Partner MDF Request, Partner Certification.
• API bridges: Suger.io for AWS Marketplace, native integrations for Microsoft Partner Center PRACR.
• Dashboard migration: 50+ reports rebuilt in Salesforce reporting + Tableau, with canonical KPI definitions.
• Partner communications: phased rollout with office hours, training videos, and office-hours support during cutover.
• Post-migration partner NPS: held flat through the transition (the usual dip was mitigated).

Deal Registration Cycle Time

• Pre-automation: 8 minutes per deal reg across three systems (Salesforce, AWS Partner Central, Suger).
• Post-automation: 30 seconds — 16x compression.
• Volume: ~600 deal regs per quarter across hyperscaler motions.
• Seller time reclaimed: ~75 hours per quarter, or roughly 1.5 FTE-weeks returned to selling.
• Quality dividend: data-integrity errors dropped materially because manual copy-paste was eliminated.

Partner-Influenced Revenue Lift

• 81% larger average deal size for partner-influenced vs direct-only motions (Contentsquare benchmark, year-over-year).
• 40%+ partner attach rate on deals above $200K TCV.
• Referral partner contribution: measurable share of net-new pipeline within two quarters of program launch.
• Microsoft Partner of the Year: two awards cycles Dico operated through (Contentsquare wins).

Rocket Mortgage Partner Portal

• Co-built the portal connecting real-estate agents and mortgage agents across Ontario.
• Salesforce admin privileges, power user on the build side — not just the operator side.
• Partner count onboarded: scaled from cohort 1 to steady-state without the build team bottlenecking.
• Deal submission cycle: partner-self-serve via the portal, with routing rules for mortgage agent assignment.
• Reporting: shared dashboards to partner managers + leadership, canonical KPIs for portfolio health.

AWS ACE Day-to-Day Ownership

• Operational cadence: weekly opportunity hygiene, monthly co-sell review with the AWS partner team.
• Named AWS counterparts: Matt Rivron (Account Manager — confirmed internal ally for future roles).
• AWS Partner Network tier progression: navigated certification requirements, partner path enablement.
• Marketplace motion: private offer design, CPPO flow, consulting partner resell mechanics.

Microsoft Partner Center Day-to-Day Ownership

• Monthly PRACR submissions (Partner Recognition and Co-Sell).
• MACC linkage validation on customer-facing offers.
• Azure Marketplace offer operations — private offers, MACC-eligible offers.
• Partner of the Year submissions drafted and shepherded through.

Appendix O — AI-Native Toolchain Deep Dive

The operating layer that multiplies every other deliverable. Not a hobby, not a buzzword — the actual stack I bring to Nebius day one.

Claude Code (Agentic Orchestration)

• Primary terminal-native agent environment: plan, execute, review across files and shells.
• Parallel background agents for decomposed tasks — research, implementation, review.
• Skill system for reusable procedures — battle-station generation, PR review, transcribe pipelines.
• Result: dashboards and automations delivered in hours, not sprints.

Cognitive Bridge

• Persistent context layer spanning sessions and projects.
• Every artifact is captured, indexed, and retrievable in the next session.
• Project-level memory so the agent stops asking the same orientation questions.

NotebookLM (Research Synthesis)

• Long-form research synthesis across transcripts, decks, papers.
• Studio artifacts — slide decks, briefings, audio summaries — generated from source corpora.
• Cognitive curation loops — auto-curation, enrichment, cross-notebook queries.

OpenViking (Context Database)

• Semantic search across user memory, agent patterns, research, decks, ecosystem docs.
• Viking URI system — addressable context blocks reusable across sessions.
• Ingestion pipeline for new corpora (transcripts, research notes, playbooks).

ResearchGravity

• Python MCP server for research coordination.
• Status protocol, URL logging with tier and relevance, research archive management.
• Context packs and prefetcher — intelligent context selection across sessions.

UCW (Universal Context Wallet)

• Long-horizon capture of every AI interaction, tagged and graph-linked.
• Current snapshot: 12.15M graph links, 7.1K items, 270K+ interactions across 5 platforms.
• The compounding substrate — what makes “Learning > rate of change” real, not aspirational.

Why this matters for Nebius

• Dashboard delivery: hours not sprints. The reporting gap closes faster than traditional hiring assumes.
• Playbook reuse: partner portal launch patterns, STAR libraries, objection handling — all pre-loaded.
• Cross-functional artifacts: legal tracker, RevOps RACI, finance MDF ledger — generated and iterated on in-session.
• Knowledge compounding: every Nebius conversation becomes indexed context for the next Nebius conversation.
• Builder-independent velocity: I do not need a team to ship the first draft of any artifact.

Appendix P — Partner Ops Tool Landscape (Detailed)

Every tool in the partner ops stack, what it does, and where I have operated it.

Salesforce (CRM + Partner Portal)

• Power user + admin privileges at Rocket Mortgage.
• Participant in OneCRM build at Contentsquare — data model, flows, reports.
• Experience with Experience Cloud (partner portal), Sales Cloud, Service Cloud fundamentals.
• Nebius application: net-new partner portal build, as-built-twice playbook.

Crossbeam (Partner Data Overlap)

• Day-to-day operator at Contentsquare.
• Account overlap analysis, partner-with-partner mapping, signal generation for co-sell.
• Integration into Salesforce for pipeline enrichment.

Reveal (Partner Data Overlap, EU-leaning)

• Complementary to Crossbeam, stronger footprint in EU partners.
• Same operational discipline — overlap analysis, co-sell signal.

PartnerStack (Referral / Reseller PRM)

• Referral program operation — partner onboarding, attribution, commissions.
• Low-friction tier: good for introducer programs before partners graduate to SI or ISV tiers.

Suger.io (Marketplace Automation)

• API bridge between Salesforce and AWS Marketplace.
• Deal reg automation, private offer orchestration, status sync.
• Case study partner at Contentsquare.

AWS Partner Central + ACE

• Day-to-day operator — ACE deal reg, opportunity engagement, partner path.
• Marketplace operations — private offers, CPPO, consulting partner resell.

Microsoft Partner Center

• Day-to-day operator — PRACR submissions, MACC validation, co-sell motions.
• Partner of the Year operational history.

Tableau / Google Data Studio

• Custom dashboards serving partner sales managers + hyperscaler co-sell reps.
• Canonical KPI definitions, weekly ops pack, leadership-level summaries.

Salesforce Native Reporting

• Reports + dashboards as the default layer — lives next to the data, lowest-friction operational adoption.
• Canonical KPI layer is built here first, then exported to Tableau for leadership views.

Supporting SaaS

• Slack — partner ops channel architecture, cross-functional routing.
• Notion / Confluence — partner ops wiki, playbook library, onboarding docs.
• DocuSign — partner contract execution tracking.
• Workato / Zapier — lightweight integrations between partner tools when full Salesforce builds are overkill.

Appendix Q — Proposed Weekly Operating Cadence

The week-in-the-life of partner ops once the function is up. Proposed cadence I would propose inside the first 30 days.

Monday — Ops Pack + Leadership Sync

• 07:00 ET: refresh data, regenerate weekly ops pack (pipeline, revenue, program health, team health).
• 09:00 ET: partner ops leadership sync — walk the pack, flag the three things that changed, name owners on the risks.
• 10:30 ET: RevOps weekly — data model + attribution alignment.

Tuesday — Hyperscaler Motions

• AWS ACE weekly: opportunity hygiene, approval queue, partner manager escalations.
• Microsoft Partner Center: PRACR pipeline, MACC eligibility review, co-sell motion status.
• NVIDIA alignment: active deals, joint reference architecture progress.

Wednesday — Partner Manager 1:1s + Portal Ops

• Rolling partner manager 1:1s — what is blocked, what do they need from ops.
• Portal ops: deal reg approvals, MDF queue, new partner onboarding.
• Support ticket triage for partner-facing issues.

Thursday — Cross-Functional Rhythms

• Legal sync: contract queue, data processing agreements, edge cases.
• Finance sync: MDF disbursement, marketplace billing reconciliation, quarterly close prep.
• Marketing sync: co-marketed campaigns, case study pipeline, event planning.

Friday — Build + Reflect

• Deep work on automation, dashboard iterations, playbook updates.
• Partner-facing comms drafted and queued for Monday send.
• Week retrospective — what worked, what did not, what changes next week.
• Archive captured learnings into the cognitive bridge for compound use next week.

Appendix R — First-Week Questions I Would Ask Leadership

The audit questions I would run in the first week. Ground truth before action.

Partner Portfolio

• Who are the top 10 partners by revenue influence today?
• Which partners are active in the current Salesforce vs legacy system?
• What is the tier structure today — formal or informal?
• Which alliances are under contract vs verbal agreement?

Salesforce State

• What is the current Salesforce data model for partners?
• Who has admin rights today?
• What is the current reporting vs what does leadership actually consume?
• What migrations are in flight and what is the sequence?

Cross-Functional Map

• Named counterparts in RevOps, Finance, Legal, Marketing — who do I call first?
• What SLAs exist today and which are binding?
• Where are the recurring friction points?

Leadership Priorities

• What does “win” look like for partner ops at 90 days? At 180 days?
• What metrics does the CRO actually look at for partner revenue?
• Where is the board pushing the hardest — growth, margin, hyperscaler attach?

Appendix S — Canonical FAQ (Self-Generated)

Questions I expect to get, with the prepared answer. Rehearsal substrate.

Q: Why Nebius?

A: The neocloud thesis is where infrastructure compounds next. Nebius sits at the intersection of AI-native demand and sovereign compute — exactly the layer where partner operations become a strategic moat. Beyond the thesis: the job description is a mirror of the last six years of my operating life. Salesforce partner portal, migration-to-SOT, centralized reporting, AWS + Microsoft motions. I do not ramp into this — I repeat a playbook.

Q: Why leave Contentsquare?

A: Contentsquare was a multi-year compounding experience — I scaled with the org, landed OneCRM, owned the hyperscaler motions. The next rate of change is higher at Nebius because the function is being built from scratch in a hyper-growth neocloud. Learning > rate of change — that ratio is better here.

Q: What is your weakness?

A: I over-invest in tooling and automation when a manual stopgap would unblock the team faster. I have learned to ship the manual version first, then automate once the pattern stabilizes — but the instinct to build is there and I have to govern it.

Q: How do you handle a partner manager who disagrees with a process change?

A: First, listen — the disagreement is usually data I do not have. Second, separate preference from principle — if it is preference, adjust the rollout. If it is principle, escalate to the partner ops lead with both sides laid out. Third, commit to the decision once made, even if it was not my preferred path.

Q: What do you do when you do not know the answer?

A: Say I do not know. Commit to a timeline for the follow-up. Ground-truth via the system of record, not from memory. Return with the answer and the source.

Q: Describe a conflict with a colleague.

A: Cash-to-quote migration at Contentsquare — RevOps and partner ops disagreed on partner attribution at the quote object. I ran a whiteboard session with both sides, mapped the data model implications, agreed on a joint definition, documented it, and got legal and revenue sign-off. The relationship strengthened because the disagreement was productive, not positional.

Q: How do you stay current?

A: Partnership Leaders community, Crossbeam / Reveal community slack, AWS and Microsoft partner ecosystem newsletters, hyperscaler re:Invent and Ignite content. Plus the AI-native toolchain — research synthesis at the velocity of Nebius-style hyper-growth requires NotebookLM + Claude Code.

Q: Why should we hire you over another candidate?

A: Two things: the exact-match playbook (Salesforce portal + hyperscaler motions + centralized reporting), and the AI-native velocity layer that most candidates will not bring. The first is table stakes for this role. The second is the differentiator.

Appendix T — Closing Narrative

The single paragraph I would deliver as the panel close. Tested, rehearsed, owned.

Nebius is building the neocloud that the next generation of AI builders will run on. The partner operations function is the load-bearing layer for how that ecosystem compounds. I have built this exact function twice — Rocket Mortgage portal, Contentsquare OneCRM and hyperscaler motions — and I bring an AI-native velocity layer that compresses every deliverable. The role as described is a mirror of the last six years of my operating life. I hope you would agree I have much of the skillset you are looking at — and I would be grateful for your read on where else you see me adding value inside the organization. Thank you for the conversation. I am looking forward to Nebius.

Appendix U — Nebius Market Context

The neocloud landscape as I understand it going into panel rounds. Calibrated to Dico's sovereign cloud index thesis.

The neocloud category

• Purpose-built AI infrastructure providers — GPU-dense, training and inference optimized.
• Category defined by three operational primitives: GPU availability, cluster reliability, and software/tooling velocity.
• Differentiated from hyperscalers by pricing discipline, GPU procurement advantage, and AI-native product surface.
• Differentiated from bare-metal brokers by software depth and partner ecosystem maturity.

Competitive set (observed)

• CoreWeave — hyperscaler-scale GPU supply, public-company trajectory, enterprise sales motion maturing.
• Lambda Labs — strong developer brand, on-demand + reserved capacity, SMB-to-enterprise motion.
• Crusoe — vertically integrated (energy-to-compute), infrastructure-first narrative.
• Together AI — model-lab-adjacent, inference-heavy positioning.
• Nebius — global footprint, sovereign AI positioning, ex-Yandex technical depth, builder-culture velocity.

Partner ecosystem implications

• AI-native ISVs are the strategic tier — model labs, inference platforms, agent frameworks.
• Hyperscaler co-sell via AWS / Azure / GCP remains a pipeline source, even for neocloud competitors.
• NVIDIA alignment is baseline, not differentiator — everyone has it.
• Regional SIs matter more for sovereign / regulated segments (EU, APJ, government-adjacent).
• Marketplace presence (AWS, Azure) is a billing consolidation play for enterprise buyers.

Why Nebius positioning resonates

• Sovereign cloud narrative is timely — geopolitics, regulation, and data locality are tailwinds.
• Hyper-growth in AI compute demand is real, not speculative.
• Builder culture maps to how fast the partner ecosystem needs to mobilize.
• Founding-team partner ops seat is a rare compounding opportunity for an operator who has done it before.

Appendix V — Partner Program Blueprint

The default program design I would propose inside Nebius during the first 90 days. Adjusted after ground-truth, not before.

Tier structure

• Registered — low-friction entry, portal access, deal reg rights, baseline enablement.
• Advanced — certified technical delivery, minimum committed volume, co-sell access.
• Premier — joint GTM plans, dedicated partner manager, MDF access, marketplace offers.
• Strategic — named alliance tier, executive sponsorship, bespoke program design.

Partner motions supported

• Referral — lead-only, introducer incentive, PartnerStack-style attribution.
• Co-sell — joint opportunity engagement, shared pipeline visibility, shared comp plans.
• Resell — channel-through motion, discount structure, resell agreement framework.
• Marketplace — AWS / Azure private offers, consolidated buyer billing, MACC eligibility.
• Technical / ISV — joint reference architectures, integration certification, co-marketed assets.

Operational primitives each partner gets

• Named partner manager (for Advanced tier and above).
• Portal access with deal reg, MDF request, document library, certification tracking.
• Defined enablement path — training, certification, solution architect access.
• Reporting dashboard — partner-specific pipeline and revenue view.
• Quarterly business review cadence for Premier and Strategic tiers.

Program economics

• Deal-reg discount schedule by tier and motion.
• MDF allocation model — committed, earned, discretionary.
• Incentive accelerators for net-new logos, marketplace volume, strategic use cases.
• Commission structure integrated with Finance — no parallel shadow systems.

Governance

• Monthly partner council for Premier + Strategic.
• Quarterly program review with leadership — tier movements, health metrics, economics.
• Annual program redesign anchored in audited outcomes, not assumptions.

Appendix W — Salesforce Data Model Proposal

The default Salesforce data model for Nebius partner ops — derived from the OneCRM + Rocket Mortgage reference architectures.

Core objects

• Partner Account — master partner record, tier, motion mix, regional footprint, named managers.
• Partner Contact — portal users, named counterparts, role + seniority tags.
• Partner Opportunity — shared with the core Opportunity object via a partner attribution junction.
• Partner MDF Request — lifecycle from request to disbursement with approval workflow.
• Partner Certification — technical + sales certifications by contact.
• Partner Engagement — QBRs, joint planning sessions, enablement events.

Attribution model

• Partner-sourced: partner brought the lead, tagged at Opportunity creation.
• Partner-influenced: partner contributed to a deal not originally sourced by them.
• Partner-delivered: partner is involved in technical delivery or implementation.
• Marketplace-transacted: deal flowed through AWS / Azure marketplace — separately tagged.
• Every opportunity can have multiple attribution tags; reporting surfaces the breakdown.

Data quality controls

• Validation rules on tier transitions.
• Required fields at each stage — partner manager, motion type, attribution flags.
• Duplicate management at Partner Account level (company + domain match).
• Weekly data hygiene report — stale partner records, missing attribution, incomplete onboarding.

Integration surface

• Suger.io for AWS Marketplace.
• Native integrations for Microsoft Partner Center PRACR.
• Crossbeam / Reveal for account overlap enrichment.
• PartnerStack for referral program attribution.
• Slack alerts for deal reg status changes, tier transitions, MDF approvals.

Appendix X — Partner Portal Launch Checklist

The detailed launch checklist I would run for the Salesforce-based partner portal — proven at Rocket Mortgage, refined at Contentsquare.

T-8 weeks: foundation

• Data model confirmed and validated against leadership priorities.
• Cross-functional RACI signed with RevOps, Finance, Legal, Marketing.
• Portal scope locked for v1 — deal reg, MDF request, document library, certification tracking.
• First-cohort partner list curated — top 20 partners across tiers.

T-6 weeks: build

• Portal navigation and branding finalized.
• Permission sets and sharing rules designed and tested.
• Workflow automation — deal reg routing, MDF approval, notification cadence.
• Reporting baseline — partner-facing dashboards configured.

T-4 weeks: validation

• Internal UAT with partner managers — every flow walked end-to-end.
• Data integrity checks — partner records, contacts, opportunities, certifications.
• Security review with IT / legal — PII handling, data processing, access controls.
• Comms plan drafted — partner announcement, training deck, office hours schedule.

T-2 weeks: partner soft launch

• First cohort invited — 3–5 friendly partners as the alpha.
• Office hours running twice per week.
• Issue tracking live — dedicated Slack channel + Salesforce case queue.
• Daily ops standup — portal team + partner managers + Salesforce admin.

T-0: general launch

• All Advanced+ partners onboarded.
• Training deck published to partner library.
• Weekly office hours continue for first 30 days.
• Portal adoption dashboard live — weekly leadership review.

T+30 days: stabilization

• First iteration batch shipped — priority fixes and quick wins.
• Partner NPS pulse survey fielded.
• Portal adoption baseline reported to leadership.
• Phase 2 roadmap locked.

Appendix Y — Negotiation Posture

Compensation, visa, and logistics — what was committed, what is open, and how I show up if the topic lands in a technical round.

Compensation

• Anchor number on the table: $180,000 USD base.
• Open to OTE layer on top — willing to meet quota demands.
• Recruiter did not confirm range — pending internal calibration.
• Panel-round posture: if raised, defer politely back to the recruiter. “Happy to align with {recruiter} on comp — the panel conversation is about fit.”

Visa

• TN visa requirement declared up front.
• Recruiter doing internal feasibility check (ref: Dave).
• Status: pending.
• Panel-round posture: open about the requirement if asked. Do not re-open if not asked.

Location

• Based in Texas.
• No pushback from recruiter on location.
• Comfortable with remote-first, willing to travel for team offsites and partner events.

Process

• If visa + comp align: panel of 3 conversations, 30–45 minutes each.
• Goal of the panel: assess team dynamics and implementation build-out.
• Recruiter handles visa internal check, comp range confirmation, profile share to hiring team.
• Communication channel: email.

Appendix Z — Post-Panel Follow-Up Playbook

What I send after each round, to whom, when, and what it says. Executed consistently across every panel.

Within 2 hours: internal capture

• Capture the panel conversation into NotebookLM / cognitive bridge.
• Tag the names, roles, signals, and open threads.
• Flag the two or three follow-ups I committed to (“will send the dashboard demo,” “will share the Contentsquare case study”).
• Identify the one question I wish I had answered better — draft a refined answer for the next round.

Within 24 hours: thank-you email per panelist

• Short — three paragraphs.
• Paragraph 1: thank them, reference one specific topic we explored.
• Paragraph 2: deliver any follow-up I committed to (dashboard link, case study, doc).
• Paragraph 3: one-sentence reiteration of the alignment + invitation to continue the conversation.

Within 48 hours: recruiter update

• Quick note to the recruiter: how each round went from my side.
• Any logistic follow-ups (visa, comp, scheduling) kept on the recruiter channel.
• Signal readiness for the next round.

If offer lands: evaluation cadence

• 48-hour no-decision window to think clearly.
• Comp review against $180K anchor.
• Visa terms reviewed with cross-border tax counsel.
• Start-date alignment — respecting Nebius urgency and Dico's current obligations.

If no offer lands: learning loop

• Capture the gap — where did I not convert?
• Feed the gap back into the cognitive bridge for the next panel round.
• Maintain the relationship with the recruiter — partner ops market is small.
• Move forward — Nebius is one index point in a sovereign cloud thesis that has other chapters.

Appendix AA — Reference Architecture (Narrative)

System design narrative for the Nebius partner operations stack. Text form — whiteboard-ready.

System of Record

• Salesforce as SOT for partners, partner contacts, opportunities, MDF, certifications.
• Experience Cloud as the partner portal surface — Salesforce-native, branded.
• Native reports + dashboards for operational workflows.
• Tableau as the leadership-consumption layer for cross-functional views.

Inbound integrations

• Crossbeam / Reveal — account overlap enrichment into Partner Account object.
• PartnerStack — referral attribution into Partner Opportunity.
• AWS Partner Central via Suger.io — deal reg round-trip, private offer orchestration.
• Microsoft Partner Center — PRACR round-trip, MACC validation.
• NVIDIA Partner Network — manual at first, integrated as volume warrants.

Outbound surfaces

• Partner portal (Experience Cloud) — partner-facing deal reg, MDF, docs, certification.
• Slack alerts — ops team, partner managers, cross-functional channels.
• Weekly ops pack — leadership, partner managers, revenue team.
• Quarterly board cut — partner-influenced revenue, marketplace backlog, attach rate.

Governance + observability

• Weekly data hygiene report — stale records, missing attribution, incomplete onboarding.
• Monthly partner NPS pulse.
• Quarterly program review with leadership.
• Annual program redesign cycle.

Automation layer

• Salesforce Flow for deterministic workflows (deal reg routing, MDF approvals, tier transitions).
• Workato / Zapier for lightweight cross-SaaS integrations.
• Custom agentic layer (Claude Code skills) for high-judgment tasks — partner manager summaries, co-sell opportunity scoring, case-study drafting.

Appendix BB — Glossary

Shorthand vocabulary in partner ops. Listed so there is no ambiguity in panel-round language.

Motions

• Referral — partner brings a lead, takes no delivery role.
• Co-sell — partner + vendor jointly engage an opportunity.
• Resell — partner transacts the deal on their paper.
• Marketplace — deal transacts through AWS / Azure / GCP marketplace.
• Technical / ISV — partner integrates product into their own stack.

Attribution

• Sourced — partner brought the lead.
• Influenced — partner contributed to a deal not originally sourced by them.
• Delivered — partner executes part of the technical implementation.

Hyperscaler constructs

• ACE — AWS Partner Central engagement and deal reg.
• CPPO — Consulting Partner Private Offer (AWS).
• PRACR — Partner Recognition and Co-Sell (Microsoft).
• MACC — Microsoft Azure Consumption Commitment.

Program constructs

• MDF — Market Development Funds.
• QBR — Quarterly Business Review.
• RACI — Responsible, Accountable, Consulted, Informed.
• NPS — Net Promoter Score.
• SOT — System of Truth.

Appendix CC — Day-One Playbook

What I execute in the first 24 hours on the job. Concrete, not aspirational.

Hour 0–2: system access

• Salesforce login validated, permission set confirmed.
• AWS Partner Central + Microsoft Partner Center access requested with business justification.
• Slack channels joined — partner ops, RevOps, finance-ops, legal-ops.
• Email distribution lists subscribed — partner operations, GTM leadership.

Hour 2–5: 1:1 schedule

• Hiring manager 30-minute sync on priorities.
• Sibling partner ops manager intro.
• Partner Managers (named counterparts) introduction rounds.
• RevOps lead intro request.

Hour 5–8: document ingest

• Current partner portfolio inventory.
• Existing Salesforce data model documentation.
• Any prior partner program design docs.
• Board decks mentioning partner revenue or attach.

End of day: commit artifact

• Draft audit doc: what I learned, what I still need to know, first-week questions queued.
• Shared with hiring manager + sibling manager.
• Anchors the week-one ground-truth cycle.

Appendix DD — Stakeholder Map (Proposed)

The stakeholders I would identify and the cadence I would build with each. Proposed before landing — adjusted after week 1 ground truth.

Direct line

• Hiring manager — daily async, weekly 1:1, monthly strategic review.
• Sibling partner ops manager — weekly coordination, shared ownership of the function design.
• Partner Managers — rolling 1:1s, shared Slack channel, weekly ops sync.

Cross-functional (critical)

• RevOps lead — weekly sync, joint ownership of data model and attribution.
• Finance (partner + marketplace) — weekly sync, joint ownership of MDF, marketplace billing, commission structure.
• Legal (partner contracts) — weekly ops meeting during high-volume windows, on-demand escalation otherwise.
• Marketing (partner marketing) — bi-weekly sync, shared campaign calendar, joint case studies.

Leadership exposure

• CRO — monthly program review, quarterly board cut preparation.
• Head of Partnerships — weekly pipeline + program health review.
• COO / CFO — quarterly exposure on marketplace revenue, partner economics.

External counterparts

• AWS partner team — named PDM, monthly co-sell review, quarterly business review.
• Microsoft partner team — named partner development manager, monthly co-sell cadence.
• NVIDIA alliance — quarterly touch-point.
• Top 10 named partners — rolling QBR cadence driven by the partner manager, ops on the support line.

Appendix EE — Dashboard Catalog

The dashboards I would stand up in the first 60 days, in sequence, with consumer and cadence.

Week 2 ship list

• Pipeline Health — partner-sourced and partner-influenced pipeline, weekly delta. Consumer: CRO, Head of Partnerships.
• Deal Reg Operations — submission volume, approval rate, time-to-approval. Consumer: ops team, partner managers.
• Partner Portfolio — tier breakdown, motion mix, active vs dormant. Consumer: partner managers, leadership.

Week 4 ship list

• Marketplace Revenue — monthly marketplace bookings + backlog by hyperscaler. Consumer: Finance, CRO.
• MDF Utilization — committed / deployed / disbursed by partner + motion. Consumer: Finance, partner managers.
• Co-Sell Motion Health — AWS ACE pipeline, Microsoft PRACR pipeline, deal progression. Consumer: alliance leads.

Week 8 ship list

• Partner Attach Rate — attach on deals over $200K, trend by quarter. Consumer: CRO, Head of Partnerships, board prep.
• Partner-Influenced Deal Size Lift — average deal size partner vs direct. Consumer: CRO, sales leadership.
• Portal Adoption — active partners, deal regs via portal vs email, onboarding completion. Consumer: ops team, product + partner portal stakeholders.

Week 12 ship list

• Quarterly Board Cut — partner-influenced revenue, marketplace backlog, attach rate, named strategic alliance health. Consumer: board prep, CRO.
• Data Hygiene Monitor — stale records, missing attribution, incomplete onboarding. Consumer: ops team.
• Partner NPS Pulse — quarterly score, open comments, trend lines. Consumer: Head of Partnerships, CRO.

Appendix FF — Case Study Bank

Pre-written talking tracks for the highest-leverage case studies.

Contentsquare + AWS: private offer at scale

We stood up the AWS Marketplace motion as a revenue channel for enterprise customers who preferred consolidated billing. Suger.io bridged Salesforce to AWS Partner Central so private offers were authored, approved, and tracked in the system of record. The motion went from “case by case” to “default for deals over $200K TCV” within two quarters.

Contentsquare + Microsoft: Partner of the Year

The Microsoft co-sell motion operationalized around monthly PRACR submissions and MACC linkage validation. Two Partner of the Year award cycles ran during my tenure — the submissions packages were anchored on hard pipeline data that the Salesforce reporting layer surfaced.

Rocket Mortgage partner portal

The portal connected real estate agents and mortgage agents across Ontario. Salesforce-native build, partner-self-serve deal submission, automated routing rules for mortgage agent assignment. The build was co-owned — Dico had admin-level ownership alongside the Salesforce team.

OneCRM unification

Six-to-seven source systems collapsed into Salesforce as the single source of truth. Crossbeam, Reveal, PartnerStack, Google Sheets, AWS ACE, Microsoft Partner Center, Sugar CRM via API bridge. The migration ran alongside the cash-to-quote redesign and shipped without an attribution data loss.

Deal reg automation

Manual 8-minute deal reg process compressed to a 30-second flow. Salesforce as the submission point, Suger.io as the API bridge to AWS, bi-directional status sync. At 600 deal regs per quarter, this reclaimed ~75 hours of seller time every quarter.

Appendix GG — Self-Critique

The honest weaknesses I know about, and the working countermeasures.

Over-building the automation before validating the manual workflow

Countermeasure: ship a manual version of every workflow first, then automate on the third repetition. Automation is earned, not assumed.

AI-native framing running long

Countermeasure: lead with one crisp sentence, offer to deep-dive on request. The panel does not want a monologue — it wants crisp exchange.

“Top 1%” language without an artifact

Countermeasure: pair every AI-native claim with a tangible artifact — dashboard demo, battle station, agent output.

Sovereign cloud index reference unpacked

Countermeasure: a two-sentence definition rehearsed. “The sovereign cloud index is a thesis that geopolitics + regulation + data locality make regional AI infrastructure a structural growth category. Nebius sits at the intersection of that thesis and AI-native demand.”

Tendency to front-load context before the ask

Countermeasure: lead with the ask, then layer context only if requested. The panel's time is the constraint.

Appendix HH — Why Nebius (30-Second Version)

The rehearsed 30-second answer to “why Nebius.”

Nebius sits at the intersection of the sovereign cloud thesis and AI-native demand. The partner ops function is the load-bearing layer for how the ecosystem compounds — Salesforce portal, hyperscaler motions, centralized reporting — and it is being built in real time. That is the exact playbook I have run for six years at Rocket Mortgage and Contentsquare, and I bring an AI-native velocity layer on top. The rate at which Nebius is scaling is the match for the rate at which I want to learn — Learning > rate of change.

Appendix II — Why Me (30-Second Version)

The rehearsed 30-second answer to “why you.”

Two things. First, the playbook match — I have built the Salesforce partner portal, operated the hyperscaler motions, and owned the centralized reporting function twice across Rocket Mortgage and Contentsquare. The role description is a mirror. Second, the AI-native velocity layer — Claude Code, cognitive bridge, compounding context. I ship in hours what traditional operators ship in sprints, and the function compounds learning across every partner manager conversation. Those two together are what I bring that the next candidate probably does not.

Appendix JJ — Panel Energy Management

Three 30–45 minute panels in a single day is a cognitive load. This is the energy plan.

Pre-panel (24 hours out)

• Deep sleep 8 hours minimum.
• Panel pack re-read once, not memorized — the Confidant lines are the only memorization target.
• Water intake elevated for the day before.
• No new research 12 hours before — consolidation, not accumulation.

Pre-panel (2 hours out)

• Light meal, protein-forward, no caffeine spike.
• 10-minute walk for oxygenation.
• Review the Confidant lines, nothing else.
• Tech check — camera, mic, lighting, backup network.

Between panels

• 5-minute stand-up stretch.
• Water reset.
• 30-second note to self — what landed in the prior panel, what to carry forward.
• No doom-scroll, no email.

Post-panel

• Capture into cognitive bridge within 2 hours.
• Thank-you emails within 24 hours.
• Rest the evening of the panel — no new deep work.
• The learning loop closes the next day with refined answers for the next round.

Appendix KK — Extended Q&A Library

Questions beyond the canonical FAQ, with prepared answers.

Q: How would you handle a partner who is missing their commitments?

A: Data first — pull the commitment, pull the actuals, identify the gap. Then partner manager conversation, not escalation. If the gap persists, structured remediation plan with tier implications. Graceful offboard if the pattern does not reverse. Partners respect clarity more than tolerance.

Q: How do you prioritize competing asks from three partner managers?

A: Triage against revenue impact and strategic alignment. Communicate the prioritization transparently — “this gets done this week, this gets done next week, this goes into the backlog with a quarterly review.” Never drop asks into a silent queue.

Q: How do you evaluate a new tool or platform?

A: Three filters. First, does it solve a problem we have today, or a problem we think we will have? Second, does it integrate cleanly with Salesforce as SOT? Third, is the operational overhead reasonable relative to the pain it removes? If any filter fails, it stays in the backlog.

Q: What is your approach to documentation?

A: Document as a first-class deliverable, not an afterthought. Every process gets a one-page SOP in the partner ops wiki. Every data model change gets a changelog entry. Every dashboard gets a canonical definition attached. If it is not written down, it does not scale.

Q: How do you recover from a visible failure?

A: Own it fast — do not wait for the post-mortem to acknowledge. Diagnose with the team, not at the team. Ship the fix, then capture the learning. Use the failure as a forcing function for the process improvement that was already needed.

Q: What do you do in your first 30 minutes of every day?

A: Refresh the weekly ops pack, scan the Slack partner ops channels, triage any overnight deal reg or MDF escalations, and write a three-item day plan. The pattern holds across both Contentsquare and the AI-native build phase.

Q: How do you measure your own performance?

A: Three lenses. One: did the program metrics move in the right direction (pipeline, attach rate, cycle time). Two: did I compound knowledge (dashboards and SOPs that survive me). Three: did cross-functional partners become stronger because I was there. If all three trend positive, the quarter worked.

Q: What is your relationship to uncertainty?

A: Uncertainty is the working condition, not the exception. My operating posture is ground-truth first, commit to the 80% version, iterate from production feedback. I do not stall for perfect information — but I also do not pretend I have information I do not have. Uncertainty gets named, not hidden.

Appendix LL — Network and References

The ecosystem touchpoints and reference landscape.

Active communities

• Partnership Leaders — the primary community of partner ops operators.
• Crossbeam Slack community.
• Reveal community for EU-partnered operators.
• AWS Partner Network events + Microsoft Inspire / Ignite.

Named AWS counterpart

• Matt Rivron — AWS Account Manager, internal ally from the Contentsquare co-build of the AWS SCA.
• Referral-ready into AWS-adjacent partner motions.

References available on request

• Prior hiring managers at Contentsquare and Rocket Mortgage.
• Cross-functional counterparts — RevOps, Finance, Legal — who can speak to the cross-functional operating posture.
• Named partner managers who worked the portfolio alongside.

Appendix MM — Final Panel-Round Checklist

The night-before and hour-before checklists.

Night before

• Panel pack re-read once.
• Confidant lines out loud, three repetitions.
• 30-second “why Nebius” + “why me” out loud, two repetitions.
• Dashboard demo tech-check — loads, logs in, renders.
• Camera frame, lighting, mic confirmed.
• Sleep 8 hours.

Hour before

• Water.
• Walk.
• Confidant lines once more.
• Three 30-second rehearsals: why Nebius, why me, close.
• Open the panel pack to Appendix M and Appendix HH.
• Close Slack, email, notifications.

In the panel

• Listen first, respond crisp.
• Pair every general claim with a specific anecdote.
• Deliver the Confidant lines when the moment opens.
• Ask, then SHUT UP.
• Close with gratitude and forward motion.

Appendix NN — Objection Handling Deep Library

The specific objections I have heard or expect from Nebius panelists, with drafted responses.

Objection: You have never worked in neocloud or AI infrastructure.

Response: The ecosystem is different, the operations are not. AWS ACE + Microsoft Partner Center are the two motions Nebius is leaning into, and I have operated both daily for years. The vertical context I will absorb fast — the operational discipline is already resident.

Objection: Contentsquare is a mature SaaS, Nebius is hyper-growth infrastructure.

Response: I have scaled partner ops systems through a Contentsquare OneCRM migration that reshaped six-to-seven tools into Salesforce SOT. The build-while-moving muscle is already live. The velocity layer — AI-native toolchain — is the multiplier that matches Nebius pace.

Objection: The AI-native framing feels like a pitch.

Response: It is a working operating system, not a pitch. I can demo the dashboard build, the battle station, the cognitive bridge. Every artifact I have described was built with it. Happy to walk the panel through a live workflow in two minutes.

Objection: You are applying for a role where the manager started 4–5 weeks ago.

Response: That is why I want the seat. A founding-team partner ops function compounds fastest when the operator brings shape to the function and lets the function bring shape to itself. I have the playbook to draft the first version of every artifact the team needs.

Objection: Tell me about a time you failed.

Response: Contentsquare — I under-communicated a tier transition to a Premier partner because I was heads-down on the OneCRM migration. The partner heard the change through a deal reg rejection rather than a partner manager outreach. I owned it within 24 hours, flew to the partner for the apology, rebuilt the communication cadence, and added a “tier transition comms” gate to the SOP. The partner stayed and grew. The lesson: partner-facing changes need the comms ahead of the system change, not after.

Objection: How do we know you will stay through the build?

Response: I am choosing this role because the compounding opportunity is rare — a founding-team partner ops seat inside a neocloud at hyper-growth pace. The commitment is not abstract — it is what makes the role desirable. And I have six-year tenures behind me; I do not move for arbitrage.

Appendix OO — Execution Rigor

The discipline layer that keeps a founding-team function from going sideways.

Weekly operating pack — never skipped

The Monday 09:00 ops pack is the ritual. It gets shipped whether the week was smooth or chaotic. Skipping the pack is how functions drift into theater.

Commitment ledger

Every commitment to a partner manager, cross-functional counterpart, or leadership gets logged. Weekly review of the ledger — outstanding, at-risk, completed. No silent drift.

Document-first decisions

Any non-trivial decision gets a one-page doc — context, options considered, decision, owner. The doc is the artifact, the meeting is the ratification.

Quarterly retrospective

End of every quarter: what shipped, what slipped, what compounded, what needs redesign. The retrospective becomes the plan for the next quarter.

Escalation discipline

Escalate early, not late. An unresolved blocker does not get better by waiting. The escalation is not a failure — it is the operating contract with leadership.

Appendix PP — Final Reminder

“I HOPE YOU WOULD AGREE I HAVE MUCH OF THE SKILLSET YOU ARE LOOKING AT.”

“WHERE DO YOU SEE I CAN ADD VALUE?”

Then: LET THEM SHARE WITH ME HOW THEY SEE MY FIT.

DOCTRINE: Learning > rate of change.

Close: “Thanks very much. I really look forward to meeting those objectives and to adding value to the objectives of the organization — looking forward to Nebius.”

Appendix QQ — Session Notes

Meta — how this portfolio was built, which is itself a demonstration of the AI-native velocity layer.

Input corpus

• Recruiter screen transcript (2026-04-13).
• Confidant framework session notes — the Mission/Vision/Values/Objectives cascade.
• Six years of Contentsquare + Rocket Mortgage operational artifacts.
• Nebius public positioning + sovereign cloud index thesis research.

Build pipeline

• Claude Code agentic orchestration — session plan, tab structure, card authoring, appendix expansion.
• Research synthesis layer from NotebookLM / cognitive bridge.
• Battle station pipeline skill — 8 research files to single-file HTML mission control.
• Template base: prior battle-station template, brand-remapped to Nebius cyan / indigo / navy.

What this demonstrates

• A single operator shipped a panel-ready operating brief end-to-end.
• The AI-native toolchain is not decorative — it is how this document exists.
• The same pipeline runs on partner ops artifacts: dashboards, playbooks, SOPs, reports.
• Learning > rate of change, demonstrated rather than asserted.

Appendix RR — 30/60/90 Expanded Narrative

The 30/60/90 plan written out in prose form, past the headline bullet list. Calibrated for the founding-team partner ops seat.

Days 1–7: ground truth

The first week is listening and mapping. I meet the hiring manager and the sibling manager on day one and frame the cadence for the coming 30 days. I meet every partner manager in the first week to understand what is blocking them and what their named partners expect from ops. I meet the RevOps lead, the finance partner-ops counterpart, and the legal contract owner to scope the joint territory.

At the same time I am reading: the current Salesforce data model, the existing reporting, board decks that reference partner revenue, any prior program design docs, and the last quarter of Slack history in the partner ops channels. The product of the week is a published audit document — what exists, what is missing, what I recommend we prioritize, what I still need to learn.

Days 8–30: wedge shipping

Weeks two through four I ship the wedge — centralized reporting. By end of week two there are three production dashboards: pipeline health, deal reg operations, and partner portfolio. These get attached to the Monday ops pack, and the pack becomes the default artifact for leadership review. By end of week four there are three more dashboards: marketplace revenue, MDF utilization, and co-sell motion health. The RACI with RevOps, Finance, Legal, and Marketing is signed and circulated.

In parallel I am writing the partner portal launch plan — scope locked for v1, cross-functional dependencies named, first-cohort partner list curated. The portal is not live yet at day 30, but the readiness checkpoint is in place.

Days 31–60: portal launch + migration discipline

The portal soft-launches around day 45 with the first cohort. Office hours run twice per week. Issues land in a dedicated Slack channel and a Salesforce case queue. The general-launch cutover lands around day 55. Partner NPS holds flat through the cutover — the proactive comms plan did its job.

The Salesforce migration runs in parallel — phased scope, legal and revenue sign-offs tracked weekly, cash-to-quote touch-points coordinated with RevOps. The attribution model is preserved through the migration. I am also owning AWS ACE + Microsoft Partner Center from day one — weekly ACE hygiene, monthly PRACR submissions.

Days 61–90: automation + compound

Weeks nine through twelve the automation layer comes online. Deal reg automation cuts cycle time by 50%+ (my Contentsquare number was 16x — the Nebius number will calibrate to the volume). MDF disbursement moves into the portal. Marketplace private-offer orchestration is Suger-bridged where AWS is the transaction layer.

The weekly operating cadence is live: Monday ops pack + leadership sync, Tuesday hyperscaler motions, Wednesday partner manager 1:1s + portal ops, Thursday cross-functional rhythms, Friday build + reflect. By day 90 the function is operating as a system, not a person, and the compounding layer is accruing for the next quarter.

Beyond 90 days: what “mature function” looks like

Partner NPS is measured quarterly with open-comment analysis. The program design is published and ratified by leadership. Hyperscaler alliance QBRs are on the calendar. Board cuts are automated from the weekly ops pack with one-click export. The sibling partner ops manager and I are co-owning a scale plan for the next hiring cohort. The function is load-bearing for Nebius's hyper-growth, and the partner ecosystem is compounding pipeline faster than the direct sales motion is growing headcount.

Appendix SS — First-Meeting Agenda Templates

The agendas I would walk into the first cross-functional meetings with. Published artifacts, not improvised conversations.

RevOps first meeting (30 minutes)

• 5 min — introductions, operating posture.
• 10 min — current Salesforce data model state: what exists, what is owned by whom.
• 10 min — partner attribution model: sourced / influenced / delivered definitions, joint ownership.
• 5 min — cadence set: weekly sync, shared Slack channel, escalation path.

Finance partner-ops first meeting (30 minutes)

• 5 min — introductions.
• 10 min — MDF budgeting, allocation, disbursement current state.
• 10 min — marketplace billing reconciliation: AWS + Azure flows.
• 5 min — cadence set, reporting expectations.

Legal partner contracts first meeting (30 minutes)

• 5 min — introductions.
• 10 min — contract queue state, active agreements, data processing agreements.
• 10 min — SLA expectations, escalation path, tracker ownership.
• 5 min — cadence set.

Marketing partner-marketing first meeting (30 minutes)

• 5 min — introductions.
• 10 min — current campaign calendar, co-marketed assets, case study pipeline.
• 10 min — attribution on co-marketed campaigns, partner-sourced MQL quality.
• 5 min — cadence set.

Hyperscaler alliance first meeting (AWS, 45 minutes)

• 10 min — introductions, named counterparts, current joint pipeline.
• 15 min — AWS ACE operational cadence, approval SLAs, escalation path.
• 10 min — marketplace motion: private offers, CPPO, consulting partner resell.
• 10 min — co-sell cadence, joint account planning, 30-day commitments.

Hyperscaler alliance first meeting (Microsoft, 45 minutes)

• 10 min — introductions, named PDM, current joint pipeline.
• 15 min — PRACR cadence, MACC linkage validation.
• 10 min — Azure Marketplace motion, private offers, MACC-eligible offers.
• 10 min — co-sell cadence, Partner of the Year planning if applicable.

Appendix TT — Skills Crosswalk (JD to Dico)

Line-by-line mapping from the job description signals to the Dico operating history.

JD: “Roll out and maintain new partner portal in Salesforce”

Dico: Rocket Mortgage partner portal co-built + Salesforce admin. Contentsquare OneCRM partner portal contributions. Two portals shipped on Salesforce — this is repeat work, not ramp work.

JD: “Own supporting analysis, pull data from CRM, create dashboards”

Dico: Custom dashboards at Contentsquare serving partner sales managers + AWS/Microsoft co-sell reps. Tableau + Google Data Studio + Salesforce-native reporting. Canonical KPI definitions authored and maintained.

JD: “Drive Salesforce migration execution”

Dico: Contentsquare OneCRM — six-to-seven systems unified into Salesforce as SOT. Cash-to-quote migration cross-functional sign-offs. This is the exact reference architecture.

JD: “Cross-functional teaming with ongoing managers”

Dico: Six years of cross-functional operating partner at Contentsquare — RevOps, Finance, Legal, Sales, Marketing. The muscle is live.

JD: “Establish influential + supporting function”

Dico: Partnership Leaders community presence, named AWS account manager, named Microsoft partner team. The seat is not just internal — it is plugged into the ecosystem.

JD: “Work independently”

Dico: AI-native builder-independent operator. Four months of build sprints generated agentic orchestration, custom dashboards, cognitive bridge, terminal intelligence extraction. This is above bar, not at bar.

JD: “AWS or Microsoft partner motion experience” (nice-to-have)

Dico: Day-to-day operator of both at Contentsquare. Not nice-to-have — core.

JD: “Tableau or similar dashboarding” (nice-to-have)

Dico: Tableau + Google Data Studio + Salesforce native. Not nice-to-have — core.

Appendix UU — First-Quarter Deliverable List

The concrete artifacts I would ship in the first 90 days, named.

Week 1

• Published audit doc.
• Named 1:1 map with hiring manager, sibling manager, partner managers.
• Draft Slack channel architecture for partner ops.

Weeks 2–4

• Three production dashboards live (pipeline, deal reg ops, partner portfolio).
• Monday ops pack shipping weekly.
• Cross-functional RACI signed with RevOps, Finance, Legal, Marketing.
• Three additional dashboards live (marketplace revenue, MDF, co-sell health).

Weeks 5–8

• Partner portal launch readiness checkpoint published.
• Portal soft-launch with first cohort.
• Office hours running twice per week.
• Deal reg automation scoped with Suger bridge design.

Weeks 9–12

• Portal general-launch cutover complete.
• Deal reg automation in production, cycle time cut.
• Weekly operating cadence fully live.
• Quarterly retrospective published.
• Partner NPS baseline measured.

Supporting artifacts all along

• Partner ops wiki seeded with SOPs.
• Commitment ledger running in Salesforce.
• Cognitive bridge captures every partner manager conversation.
• Weekly one-page status note to hiring manager.

Appendix VV — Operating Identity

How Dico operates, in one page, for a panelist who wants the signature rather than the resume.

Builder, not maintainer

I would rather ship a rough first draft than wait for a perfect spec. The second draft is faster because the first draft exists. Iteration is the operating loop, not a phase.

Ground truth before commitment

I do not claim system state without verifying it. The audit precedes the plan. Commitments are tied to evidence, not hope.

Documentation as deliverable

If it is not written down, it does not scale. Every process gets an SOP. Every dashboard has a canonical KPI definition. Every cross-functional boundary gets a RACI.

Cross-functional first

Partner ops is a connective tissue function. My first week is relationships, not reports. The reports work because the relationships work.

Learn faster than the org changes

Hyper-growth means the company ships a new state every week. The operator who learns slower is always a week behind. The AI-native toolchain is how I run faster than the rate of change.

Close the loop

Every commitment is tracked. Every escalation is resolved. Every partner manager gets the follow-up they were promised. The commitment ledger is the operating honor system.