Events
Summits, labs, roadshows, and private SE days built for people who deliver — agendas, tiers, prep, and what you leave with. Not a badge calendar.
Registered partners see the live calendar in the portal. Public product webinars stay under /webinars/ — different audience, different bar.
Why this calendar exists
Every product page embeds running software. Partner events are where practitioners learn that same build — not a parallel demo universe. Labs cancel if the app will not open. Roadshows require a registered opportunity when SE time is on the agenda.
Badge-only attendance without delivery people wastes seats operators need. We cap theatre and keep keynotes short, labs long. Summit awards celebrate delivery outcomes, not registration volume.
Formats
Pick the format that matches the job — discovery, certification, architecture, or co-sell.
| Format | Length | Who | You leave with |
|---|---|---|---|
| Partner Summit | 2–3 days in person | All tiers · practitioners preferred | Roadmap notes, lab certs, co-sell intros, awards context |
| Enablement week | 3×90 min virtual | Consulting + resellers | Demo cert attempt, motion checklist, battlecard links |
| Architecture lab | Half day virtual | SIs · Advanced+ | Sandbox pattern, identity notes, extension guidance |
| Roadshow clinic | 1 day regional | Firms with live opps | SE feedback on a registered deal, next-step plan |
| Distributor forum | 1 day regional | Distributors + top resellers | Train-the-trainer pack, recruitment bar, MDF shape |
| Premier SE day | 1 day private | Premier · joint plan | Named SE agenda on a real account |
| Operator evening | 3 hours invite | Customers + delivery partners | Shared stories — no pitch deck theatre |
| Public webinar | 45–60 min | Anyone | See Webinars — not partner-only |
Access by tier
Core enablement is included for Registered. Depth and private time concentrate as you progress.
| Access | Registered | Advanced | Premier |
|---|---|---|---|
| Portal calendar + self-serve labs | Yes | Yes | Yes |
| Monthly enablement weeks | Yes | Yes | Yes · priority seats |
| Demo certification sprints | Yes | Yes | Yes |
| Summit seats | Standard | Priority | Priority + awards track |
| SI architecture labs | Waitlist | Yes | Yes |
| Roadshow co-sell clinics | Case by case | Yes with reg opp | Priority with joint plan |
| Private named SE day | — | — | Yes on joint plan |
| Early roadmap briefings | — | Summary | Detailed + SE notes |
Calendar
Dates in the portal win when they conflict with this page. Request a seat with path and region so we route correctly.
Roadmap, awards, multi-product labs (CRM, Desk, Books, Platform), co-sell clinics, Premier dinner. Practitioners required — badge-only seats are limited.
Pipeline design, quote-to-cash, forecast hygiene, demo certification for consulting and resellers. Ends with a live tenant exercise.
Co-sell clinics with CEDX SEs. Bring a registered opportunity. Architecture office hours after lunch.
Identity, entitlements, data plane, Builder/API extensions. Sandbox breakouts. Bring a real multi-product problem.
Train-the-trainer packs, MDF shape, reseller recruitment quality bars, local enablement calendars.
Joint operator stories. No hard pitch. Customers and delivery partners only — sales theatre stays outside.
Close checklist, ASC 606 schedules on real contracts, multi-entity board pack export. Controllers welcome.
One ticket from intake to truck; parts, skills, and SLA on the job. Dispatch + field roles in the same room.
Listing bar, identity contracts, sandbox-to-prod promotion, support ownership split with platform.
Named SE lab on a joint plan account. Agenda agreed one week prior. Not a free discovery tour for cold logos.
Scripted flagship motions matching live product pages. Pass/fail practical — not a slide quiz.
Security pack walkthrough, questionnaire shortcuts, shared responsibility. Bring a live RFP section if you have one.
Summit shape
Illustrative. Final agenda publishes in the portal six weeks prior.
Registration, partner success office hours, optional Premier dinner.
State of the estate, roadmap, identity and platform bar. Short keynotes only.
Track labs: Revenue, Service, Finance, Platform. Live tenants. Cert attempts.
Co-sell clinics, deal registration hygiene, MDF and marketing rules.
Industry breakouts, awards for delivery outcomes, office hours with SEs.
Recording links for keynotes only. Lab materials in portal. Follow-up joint plans for Premier.
Lab shape
Enablement weeks are three ninety-minute virtual blocks across a week, not a single webinar with a quiz. Block one is work design and checklist. Block two is live product on a demo tenant. Block three is certification attempt or co-sell scenario with peer review.
Come with a laptop, portal login, and one real customer-shaped problem. Mute theatre. If you only need a high-level product tour, use public webinars instead.
Who should go
Consultants, SEs, and implementers who will live in the product on Friday. Primary audience for labs and certs.
Owners of methodology, SOWs, tier evidence, and who gets staffed on which motion. Summit + forums.
Distributors and reseller recruiters. Forums and roadshows — not every product deep lab.
Co-brand and MDF sessions only. Do not fill lab seats that practitioners need.
Evenings and joint stories. Not partner-only labs unless the session is labeled open.
Marketplace ISV day and architecture labs. Bring sandbox proof, not only a pitch.
Before you attend
Approved partner login, primary path set, branding kit acknowledged.
One Academy module for the motion. Public tracks are free — finish before the lab.
For roadshows and SE clinics: registered opp with products, stage, and close date.
Laptop that can run the demo tenant. Headphones for virtual labs. Camera on for cert attempts.
At least one practitioner per firm for product labs. Practice lead for Summit strategy blocks.
Write architecture or delivery questions in advance. Office hours reward prepared partners.
After the session
Log cert results, download kits, update internal enablement tracker.
Run the motion on your sandbox with a second practitioner watching.
Apply to a live registered opportunity or internal dry-run SOW.
Attach lab attendance and certs to tier progression evidence.
Delivery
If enablement does not change how you staff and deliver, you attended the wrong sessions — or sent the wrong people.
Year map
| Quarter | Focus | Primary events |
|---|---|---|
| Q1 | Onboard + first motion cert | Enablement weeks, demo cert sprints, security clinic |
| Q2 | First delivery proof | Roadshow clinic, Field/Desk or CRM lab, architecture lab for SIs |
| Q3 | Second family or region | Books/Revenue lab, Marketplace ISV day, distributor forum |
| Q4 | Tier review + Summit | Partner Summit, Premier joint plans, awards |
Related
FAQ
Straight answers before you book travel or clear a calendar.
Most enablement is included by tier. Summit travel is on you unless a co-funded plan says otherwise.
Usually no. Joint customer evenings are separate and invite-based.
Registered partners see the portal calendar. Public webinars are under /webinars/.
Public webinars often yes. Partner labs and Premier private days usually stay internal.
No. Strongly recommended for Advanced and Premier progression evidence. Registered partners may attend within seat limits.
You can, but product labs prioritize practitioners. Marketing-only firms get less from enablement weeks.
Usually for live attendees in the portal. Not public. Cert blocks may require live presence.
Through partner success with a joint plan account and a written agenda one week prior.
Retake on the next sprint. Progression waits on pass, not on attendance alone.
On the partner unless a co-funded plan says otherwise. Portal lists host hotels near Summit.
No unless the session is labeled joint. Use operator evenings or public webinars.
Portal calendar is authoritative. Summit lock ~8 weeks prior; monthly labs ~2 weeks prior.
Program charter
CEDX ships as one operating estate with shared identity and a shared customer graph across revenue, service, finance, commerce, people, and platform products. Most customers do not configure that estate alone on day one, and they should not have to invent delivery methodology while learning a new queue design. Partners exist so implementation quality, training, hypercare, and multi-product architecture remain professional after procurement signs.
The program is written for finance and delivery leads, not only for partner marketing teams collecting badges. Paths, tiers, deal registration rules, co-sell definitions, and enablement ladders are published so both sides know what the partnership purchased. Vanity badges without evidence are not a tier, and annual review can step benefits down with notice after remediation fails.
Consulting firms implement and run managed services on single-motion pilots and multi-quarter estate programs. Resellers sell with registration, demo tenants, and certified motions that match the live product pages. System integrators own identity, multi-product architecture, entitlements, and Builder or API extensions that must not invent a second login.
Distributors scale regional coverage with train-the-trainer enablement and reseller recruitment playbooks that keep quality local. Marketplace ISVs extend the estate under identity and data contracts after security review. The PRM product at /partners/ is software for managing your own channel; the program at /partner-program/ is how you sell and implement CEDX — keep those URLs separate.
Co-sell model
Register opportunities in the portal with products in scope, stage, and close date so conflict detection has something real to evaluate. CEDX confirms or flags conflict within the published SLA rather than leaving registrations in limbo. Multi-product estates get joint discovery; complex architecture gets SE time; cold logo drops without footprint do not get co-sell theatre.
Protection windows widen with tier so Advanced and Premier investments in pipeline are not free-ridden by last-minute registrations. Spam registrations and stale pipeline rows are cleaned because dirty portals poison forecasting for everyone. Portal hygiene is part of Advanced and Premier annual review, not an optional courtesy.
Customers always choose CEDX-led, partner-led, or hybrid delivery after an intro shortlist of two to three firms. Forced placement is not the model because forced matches become failed implementations. When no partner fits region, product, or compliance constraints, we say so and discuss CEDX-led or hybrid options where available.
Multi-product deals are where co-sell pays for itself: CRM with Desk, Books with Revenue, Field with inventory and voice on one job record. Single-SKU transactional resale still uses deal registration without automatic Premier SE hours. First-year patterns for serious firms usually look like onboard and demo-ready motion in Q1, first registered or delivered opportunity in Q2, second product family or region in Q3, and tier review with outcomes in Q4.
Enablement ladder
Every product page embeds running software so demos and implementations share one truth with marketing. Battlecards link to live motions instead of outdated screenshot packs that age out between quarterly refreshes. Academy modules end in checklists and product opens; webinars cancel if the app will not open.
Registered unlocks portal access, core kits, flagship demos, and self-serve Academy for work design basics. Advanced adds full estate sandbox, live workshops, enhanced margin, and featured directory placement after quality review. Premier adds named SE hours, priority co-sell pipeline reviews, early roadmap notes, and a joint business plan reviewed annually.
The core benefits matrix is shared across consulting, reseller, SI, and distributor paths so finance can compare apples to apples. Path-specific SPIFs, architecture labs, and train-the-trainer packs sit on top without rewriting the matrix every quarter. Margin schedules are published so partnership models survive internal CFO review without a fog layer of verbal promises.
Public Academy stays free so evaluation is not gated behind certification theatre that blocks operators from learning the work. Partner labs after approval are certification-shaped practice in demo tenants with practitioners who will deliver. Sales kits, implementation playbooks, security packs, and co-brand guidelines track live product builds rather than a parallel marketing universe.
Governance
Progression uses delivery proof, practitioner activity in product, portal hygiene, and customer outcome notes rather than raw registration counts alone. Volume without quality does not purchase Premier, and Premier without a joint business plan does not renew on autopilot. Quality review can remove inactive directory listings so customers are not introduced to ghosts.
Branding non-compliance blocks marketing assets until fixed because inconsistent marks erode trust in co-branded pursuits. Deal registration disputes follow written rules with examples in the portal guide so partner managers are not inventing policy mid-quarter. Security packs and shared-responsibility notes exist for procurement questionnaires; do not invent architecture answers in RFPs.
If annual review fails, benefits step down with notice and a remediation plan before removal whenever recovery is realistic. The goal is a healthy channel of firms that deliver, not a vanity headcount of logos on a slide. Before you apply, read a path page, the tiers matrix, and one customer scenario in your industry, then submit a two-minute application with motion and region truth you can staff.
Partner success exists to unblock enablement and co-sell operations, not to write your SOWs or staff your bench. Bring practitioners to Summit and labs; badge-only attendance wastes seats operators need. Questions that are truly product defects still route through Support with estate context; do not open duplicate threads across every channel.
Commercial packaging
Customers rarely buy 'the estate' as a single SKU on day one. They buy a motion: revenue operations that forecast from live stages, service operations that keep jobs and tickets on one record, finance operations that close without three exports, or commerce operations that stop promising stock that does not exist. Partners package those motions as Foundation, Expansion, and Estate programs with written success metrics, retire lists, and hypercare exit criteria so procurement is not buying a vague transformation slogan.
Foundation scopes land one product family with data cutover, role-based training on the live apps, and weekly metric reviews until the Friday number is trusted. Expansion scopes add a second family on the same identity plane — CRM plus Desk, Books plus Revenue, Field plus inventory — without inventing a second customer graph.
Estate programs run multi-quarter architecture: identity lifecycle, entitlements, multi-entity structure, integration on the estate bus, and operating model for who owns config after hypercare. These programs are where Premier co-sell and SE time concentrate because architecture risk is real and the commercial value is multi-product.
Managed services retainers keep configuration healthy when the customer does not want a permanent internal admin bench for every product surface. Define RACI in the SOW so Support tickets route correctly and partners are not surprised by platform-only escalations that should have been delivery work.
Price books, rate cards, and SOW templates remain the partner's commercial paper; CEDX provides non-binding samples and playbooks, not a mandate to underprice delivery. Margin and incentives follow the published tier table so finance can model partnership economics without verbal side deals.
Security and procurement
Enterprise buyers ask about identity, access reviews, audit exports, data processing, and shared responsibility before they care about your demo polish. Use the partner security pack for architecture overviews and questionnaire shortcuts; escalate gaps to partner success instead of inventing answers that create liability.
SSO, lifecycle provisioning patterns, and entitlement models should be discussed in the estate map, not buried in an appendix nobody reads until week six of implementation. Partners who lead with security fluency win regulated and multi-entity deals that pure product demos lose.
Illustrative scenarios on the website are honest about being composites; do not present them as audited case studies in an RFP response. When a named public case is approved, it will be labeled as such — until then, use scenarios as evaluation narratives with live product proof.
Data migration plans need an authoritative customer graph owner, a retire list, and a freeze window; partners who skip this create double-write disasters that look like product bugs in Support. Write migration scope into the SOW with acceptance tests operators can run without a consultant standing over their shoulder.
Procurement comparison matrices miss seams. Teach buyers to open three apps on one user and follow one customer record; that test separates estate platforms from glue stacks faster than a hundred feature rows. Bring that test into every serious pursuit, including co-sell reviews with CEDX.
Geographic and industry coverage
Region truth is coverage you can staff with practitioners, not a list of countries on a capability slide. Distributors exist to densify local coverage when a single SI cannot be everywhere; they do not exist to rubber-stamp inactive resellers into the directory.
Industry focus speeds time-to-value: retail and wholesale motions differ from cold-chain field service, which differs from multi-entity subscription finance. Partners should pick two verticals they can defend with reference-shaped work rather than claiming every industry on earth.
Language, on-site requirements, and compliance regimes belong in directory intro requests and in deal registration notes. Missing constraints waste SE time and produce shortlists that fail in the first customer call.
Roadshows and regional forums exist to put co-sell and enablement where partners already operate. Propose host cities when opportunity density justifies logistics; vanity events without pipeline waste everyone's calendar.
Global accounts with multi-region rollout need wave plans and a single identity strategy; do not sell six disconnected regional tenants as an estate. SIs who own multi-entity identity patterns are the right path for those pursuits.
Operating cadence with CEDX
Keep portal pipeline stages honest; stale opportunities poison protection windows and destroy trust in co-sell forecasting. Register early enough that conflict detection is meaningful, not as a last-minute claim on a deal already verbally committed elsewhere.
Send practitioners to enablement; practice leads own methodology artifacts and tier evidence for annual review. Badge-only attendance at Summit without delivery people is a signal that the partnership is marketing-led, not delivery-led.
After each customer pilot, write outcome notes: what metric moved, what was retired, what broke, what you would change in the playbook. Those notes become progression evidence and improve the next Foundation package you sell.
Route product defects to Support with reproduction; route co-sell and enablement to partner success by tier; do not spray the same issue across five channels. Fragmented threads slow response and create contradictory guidance to customers.
Quarterly, review your joint plan if Premier, or your progression checklist if Advanced, against actual delivery quality — not only against registration volume. Volume without outcomes does not survive review and does not help customers.
Premier partners book named SE labs against a joint plan. Everyone else starts with the public partner calendar after approval.
