Skip to content
Beta Multi-model support (OpenAI, Gemini, and more) launching soon.
RBA RBA Skills

partner-evidence-package

Installable Ships in case-study-writer — or copy the raw skill below.
Open Claude.ai

Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V.

ExperimentalNo security review

Partner Evidence Package

Produce a structured partner-tier evidence package that meets the validation requirements of Microsoft, Sitecore, or Optimizely partner programmes. Outputs customer reference forms, deployment proof narratives, and evidence checklists ready for submission.

When this skill applies

  • Microsoft Solutions Partner renewal or specialisation audit is approaching
  • Sitecore Gold/Platinum tier renewal requires verified customer references
  • Optimizely Gold/Platinum tier renewal requires proof of delivery capability
  • A new specialisation is being pursued and deployment evidence must be assembled

Skip for: public-facing case study → case-study-draft; award nomination → award-submission-writer.

Inputs

Parameter Required Default Notes
project-brief-or-notes Yes — File path or inline description of the project(s) to evidence
--partner Yes — Programme being renewed or applied for
--tier No gold Target tier or specialisation name
--renewal-date No — Surfaced in the output header; triggers urgency notes if within 60 days
--project No — Project name or code for internal tracking

Supported Partner Programmes

Microsoft Solutions Partner

Relevant solution areas for RBA:

  • Digital & App Innovation (Azure)
  • Data & AI (Azure)
  • Modern Work (Microsoft 365)
  • Security

Evidence types required:

  • Partner Capability Score (PCS): Microsoft auto-calculates from telemetry; this skill focuses on the narrative evidence components
  • Customer references: typically 5 references per solution area; each reference must include: organisation name, primary contact (name + email), deployment details, and a statement of the Microsoft technology deployed and business outcome achieved
  • Specialisation audit: for advanced specialisations, a third-party auditor reviews documentation; this skill produces the audit-ready evidence pack

Validation requirements (current):

  • References must be from the preceding 12 months
  • The Microsoft technology must be in active production use (not a PoC)
  • References must be in the required Microsoft Partner Center format
  • Each reference requires client contact who can be reached by Microsoft for verification

Sitecore Partner Programme (Gold / Platinum)

Tier requirements (indicative — check Sitecore Partner Portal for current year):

  • Gold: 2+ certified developers; minimum annual Sitecore licence revenue threshold; delivery track record with customer references
  • Platinum: 5+ certified developers; higher revenue threshold; demonstrated go-to-market engagement with Sitecore; innovation evidence

Evidence types required:

  • Customer reference form (Sitecore-provided template): project description, Sitecore products deployed, client contact, business outcomes
  • Certifications register: current Sitecore certification holders at RBA with expiry dates
  • Go-to-market evidence: Sitecore-co-branded activities, Partner Finder listing, case studies on Sitecore.com

Optimizely Partner Programme (Gold / Platinum)

Tier requirements (indicative — check Optimizely Partner Portal for current year):

  • Gold: 3+ certified practitioners; minimum Optimizely ARR contribution; delivery track record
  • Platinum: 5+ certified practitioners; higher ARR; demonstrated experimentation practice

Evidence types required:

  • Customer reference form: project description, Optimizely products used, client contact, quantified outcomes (experimentation results, personalisation lift, editorial efficiency)
  • Certifications register
  • Practice evidence: documented experimentation methodology, enablement delivered to clients

Workflow

Step 1 — Programme requirements check

Fetch current-year requirements if accessible:

  • Microsoft: https://learn.microsoft.com/en-us/partner-center/membership/
  • Sitecore: https://www.sitecore.com/partners/become-a-partner
  • Optimizely: https://www.optimizely.com/partners

Note: partner portal content may require authentication. If the page is not publicly accessible, fall back to the reference standards in reference.md and flag this in the output:

[NOTE: Programme requirements fetched from public pages. Verify against the authenticated
partner portal before submission — requirements may have been updated.]

Step 2 — Project evidence extraction

For each project provided, extract and structure:

Project name:         [internal code or descriptive name]
Client:               [name — confirm if this can appear in the partner reference]
Sector:               [sector]
Engagement type:      [migration / implementation / managed services / optimisation]
Contract type:        [fixed-price / T&M / retainer]
Go-live date:         [month/year]
Duration:             [months]
Team:                 [RBA headcount and roles; client team size]
Platform(s) deployed: [specific products and versions, not just vendor names]
Azure / M365 used:    [list specific Azure services if relevant to Microsoft evidence]
Primary contact:      [job title — do NOT include personal contact details until confirmed]
Business outcome:     [quantified result(s)]

Flag any fields that are missing and cannot be inferred. Do not fabricate contact details.

Step 3 — Customer reference document

For each project, produce a customer reference document using the target programme's structure.

Microsoft customer reference structure

## Customer Reference — [Client Name or "Reference available on request"]

**Organisation:**        [Legal name | sector | employee count (approx.)]
**Country/region:**      [Primary country of the deployment]
**Microsoft technology deployed:**
  - [e.g. Azure App Service, Azure SQL Database, Azure OpenAI Service]
  - [e.g. Microsoft 365 — SharePoint Online, Teams, Power Platform]
**Deployment status:**   Production (active as of [month/year])
**Go-live date:**        [month/year]
**Engagement type:**     [Implementation / Migration / Managed Services]

### What was deployed

[2–3 sentences: specific Azure/M365 services used, integration points, scale of deployment
(users, transactions, data volume). Be concrete — reference validators check that the
Microsoft technology is genuinely central to the solution, not incidental.]

### Business outcome achieved

[2–3 sentences: quantified result(s) tied to the Microsoft technology. Avoid generic
"improved efficiency" claims — state: what metric, what value, what timeframe.]

### Client contact for verification

[DO NOT include in this document without written client confirmation that they consent to
being contacted by Microsoft as a reference. Insert placeholder:]
[PENDING CONFIRMATION — BD lead to obtain client consent before submission]

Sitecore customer reference structure

## Sitecore Customer Reference — [Client Name or anonymised]

**Client organisation:**  [sector + size descriptor]
**Sitecore products:**     [e.g. Sitecore XM Cloud, Sitecore Personalize, Content Hub DAM]
**Sitecore version:**      [XM Cloud SaaS / XP 10.3 / etc.]
**Go-live date:**          [month/year]
**Environment:**           [SaaS / Azure hosted / hybrid]

### Project description (150 words max)

[Challenge → approach → result. Platform-specific: name the Sitecore features leveraged,
not just "Sitecore CMS".]

### Outcomes (bulleted, quantified)

- [Metric + delta]
- [Metric + delta]
- [Metric (delivery quality, if platform outcome metrics are limited)]

### Client contact

[PENDING CONFIRMATION]

Optimizely customer reference structure

## Optimizely Customer Reference — [Client Name or anonymised]

**Client organisation:**    [sector + size descriptor]
**Optimizely products:**    [e.g. CMS 12, Feature Experimentation, Data Platform]
**Go-live date:**           [month/year]

### Project description (150 words max)

[Challenge → approach → result. Emphasise experimentation or personalisation depth
if applicable — these are Optimizely's programme differentiators.]

### Quantified outcomes

- Experiments run (first 90 days post-launch): [n]
- Winning variant conversion lift: [%]
- Editorial velocity improvement: [%]
- [Additional metric]

### Client contact

[PENDING CONFIRMATION]

Step 4 — Evidence checklist

Produce a checklist of what must be gathered before submission:

## Evidence Package Checklist — [Partner] [Tier] Renewal

### Documents to produce (this skill)
- [ ] Customer reference: [Project A]
- [ ] Customer reference: [Project B]
- [ ] Customer reference: [Project C]
- [ ] Capability narrative (see Step 5)

### Assets to gather from internal sources
- [ ] Certifications register — current holders, certification names, expiry dates
- [ ] Project delivery metrics (if not already in references)
- [ ] Architecture diagrams for complex deployments

### Client confirmations required
- [ ] [Client A] — written consent to be named as reference and contacted for verification
- [ ] [Client B] — written consent
- [ ] [Client C] — written consent

### Portal submissions
- [ ] Upload references to [Microsoft Partner Center / Sitecore Partner Portal / Optimizely Portal]
- [ ] Confirm contact details are accurate in the portal
- [ ] Verify renewal date: [date] — submission window opens [date - 30 days]

Step 5 — Capability narrative (optional, for specialisation audits)

When a specialisation or advanced tier requires a capability narrative, produce a structured statement covering:

  • Practice area depth — team size, certifications held, years of delivery in this practice
  • Delivery methodology — how RBA approaches this type of engagement (discovery, design, delivery, hypercare)
  • Reference engagements summary — 3–5 engagements in 2–3 sentences each
  • Differentiators — what RBA does that most partners do not

Step 6 — Sensitivity and accuracy check

Before returning the package:

  • No personal contact details (name + email) included without confirmed client consent
  • Metrics are consistent with the source brief — no rounding that changes meaning
  • Microsoft/Sitecore/Optimizely product names are accurate and correctly versioned
  • [PENDING CONFIRMATION] placeholders mark every item requiring human action
  • Renewal date and timeline noted if provided

Reference and template files

  • reference.md — Programme requirement summaries, evidence standards, common rejection reasons
Technical details
Plugin
case-study-writer
Author
Dakota Smith
Skill name
partner-evidence-package
Maturity
experimental
Security review
No security review
Owners
  • business-development
  • strategy
Argument hint
<project-brief-or-notes> --partner microsoft|sitecore|optimizely [--tier gold|platinum|specialisation] [--renewal-date <date>] [--project <name>]
Allowed tools
  • Read
  • Write
  • Edit
  • Bash(find *)
  • Bash(ls *)
  • WebFetch(domain:learn.microsoft.com)
  • WebFetch(domain:partner.microsoft.com)
  • WebFetch(domain:www.sitecore.com)
  • WebFetch(domain:www.optimizely.com)
Source
plugins/case-study-writer/skills/partner-evidence-package/SKILL.md

Edit this skill on GitHub — opens GitHub's web editor. No git knowledge needed.