Okta credibility
Activate tier + OIN listing
Use the Okta relationship as factual trust proof: Activate tier, published Okta Integration Network listing, and Partner Community access.
View partner proof →Partner growth center
Assets, campaigns, and customer tracking that move pipeline.
Butterfly partners need more than a logo and a handshake. This page defines the asset library, campaign center, customer/contact fields, and training queue that turn identity recovery interest into proof, pilots, and paid work.
Launch packet
Public-safe assets partners can use immediately.
This packet is designed for first conversations and warm forwarding. It includes the customer-facing deck, one-page handout, demo, and Okta-owned proof links. Internal call scripts, named prospect notes, pricing nuance, and objection strategy stay out of the public partner hub.
Sharing boundary
Partners can share these assets as Butterfly materials. Partner badges, reseller status, delivery certification, discounts, and production access still require written approval.
PPTX↗
Okta field deck
Short forwardable deck for SE, CS, partner, and customer recovery conversations.
Open assetDOCX↗
Sales handout
One-page overview for buyers who need the recovery story, proof links, and next step.
Open assetWeb↗
Product demo
Public demo route for prospects who want to see the recovery workflow before a call.
Open assetOkta↗
OIN proof
Okta catalog proof for the Butterfly API Service integration.
Open assetOkta↗
SSO/SCIM proof
Okta catalog proof for the Butterfly SSO/SCIM integration.
Open assetDesign kit pattern
The asset center is a reusable growth surface, not a file dump.
Every card in this system exists to move a buyer or partner to the next proof point: install, validate, scope, drill, certify, or hand off evidence.
Partner assets
Collateral tied to action
Every asset maps to a motion: first conversation, audit evidence, implementation, co-branded campaign, competitive response, or certification.
Open assets →Marketing center
Campaign plays with metrics
Campaigns define audience, action, and success metric so partner marketing drives pipeline instead of decorative content.
Start a campaign packet →Customers and contacts
Pipeline records built for proof
Track account, buyer, need, stage, owner, evidence, commercial path, and written authorization so partner-led work is auditable.
Register customer motion →Brand rule: Butterfly can reference its Okta Activate tier, OIN listing, and Partner Community access. Do not imply Okta endorsement, resale authorization, or customer approval unless separately confirmed in writing.
Partner assets
Every asset exists to create the next customer action.
Partner content should not be a file dump. Each collection has a job: open the conversation, prove the gap, scope the work, reduce procurement friction, or certify delivery.
Recovery-first sales kit
Open the first customer conversation around identity recovery risk, not generic backup.
- ✓One-page partner overview
- ✓Recovery-first pitch deck
- ✓Executive email opener
- ✓No-slides discovery script
Audit readiness kit
Help security and GRC buyers connect restore proof to audit evidence.
- ✓SOC 2 / HIPAA / PCI / NIST / ISO / CIS mapping
- ✓Restore drill evidence checklist
- ✓Signed audit-pack explainer
- ✓Board-ready risk summary template
Implementation kit
Give delivery partners a repeatable path from OIN install to first validated backup.
- ✓OIN install checklist
- ✓Backup coverage worksheet
- ✓SSO/SCIM validation worksheet
- ✓Workflows recovery inventory
Co-branded campaign kit
Let partners launch campaigns without waiting on bespoke copy or design.
- ✓Partner landing-page copy blocks
- ✓LinkedIn post set
- ✓Webinar abstract
- ✓Email sequence
Competitive response kit
Answer why Butterfly is different when buyers compare audit-only, backup-only, or enterprise-only tools.
- ✓Why change / why now / why Butterfly
- ✓Common objections
- ✓Competitor comparison worksheet
- ✓Procurement FAQ
Certification kit
Move delivery partners from interest to trained, evidenced, and reviewable execution.
- ✓Training path checklist
- ✓Replica Okta lab blueprint
- ✓Capstone evidence rubric
- ✓Delivery guardrails
Marketing center
Campaign plays partners can launch without waiting.
Each campaign ties audience, message, call to action, and success metric together so partners can measure movement instead of just publishing content.
Okta restore drill offer
- Audience
- Okta admins, IAM leads, CISOs, GRC teams
- Action
- Offer a fixed-scope restore drill with before/after evidence.
- Success metric
- Booked drill or readiness assessment
Audit evidence sprint
- Audience
- Companies approaching SOC 2, HIPAA, PCI, ISO, NIST, or CIS review
- Action
- Lead with evidence gaps, audit-pack output, and recovery proof.
- Success metric
- Audit-pack request or security review call
SCIM and access continuity review
- Audience
- Teams rolling out SSO, SCIM, Lifecycle Management, or app assignment changes
- Action
- Package setup validation with backup coverage and deprovisioning evidence.
- Success metric
- SSO/SCIM scope request
Incident-response retainer attach
- Audience
- IR firms, MSSPs, vCISOs, cyber insurers
- Action
- Add identity recovery checks to existing incident readiness work.
- Success metric
- Managed resilience pilot
Workflows continuity review
- Audience
- Okta Workflows customers with fragile automations
- Action
- Inventory automations that would be painful to rebuild under pressure.
- Success metric
- Workflows recovery map
Executive resilience briefing
- Audience
- CIOs, CTOs, CISOs, boards, regulated operators
- Action
- Turn technical backup posture into recovery time, audit risk, and control evidence.
- Success metric
- Executive follow-up or design-partner intro
Customers and contacts
Track the fields that turn partner activity into revenue.
Customer and contact records are useful only if they drive the next action. Butterfly tracks buyer context, evidence, stage, consent, and commercial routing so partner-led work stays clean.
Minimum useful record
Account, buyer, need, stage, next action, evidence link, partner owner, and written authorization status.
Account
Company name, domain, industry, region, Okta/Auth0 footprint, and regulated environment.
Buyer
Primary business owner, technical owner, economic buyer, partner owner, and approval path.
Need
Restore gap, audit deadline, implementation project, incident concern, or managed-service motion.
Stage
New, qualified, discovery, scoped, proposed, pilot, closed, held, or partner-delivered.
Next action
Meeting, demo, OIN install, SSO/SCIM validation, backup run, restore preview, or audit pack.
Evidence
Screenshots, backup IDs, restore-preview IDs, audit logs, scope docs, and approval notes.
Commercial
Package, plan, estimated value, referral eligibility, partner fee, close date, and renewal owner.
Consent
Customer authorization, partner-of-record approval, data handling boundary, and written change control.
Operating loop
The portal pattern is simple: record, route, prove, govern.
1. Register the customer context
Capture the account, buyer, identity provider, urgency, partner motion, and first requested outcome.
2. Attach the right assets
Match the account to a sales kit, campaign play, service package, integration checklist, or certification path.
3. Prove technical progress
Move from conversation to OIN install, backup run, restore preview, SSO/SCIM validation, or audit-pack evidence.
4. Keep partner status clean
Separate referral, reseller, delivery, certification, production access, and customer-change authority.
Training queue
Assets teach. Certification proves.
Partner training should be visible, staged, and connected to the capstone. Marketing teams learn how to position recovery. Delivery teams prove they can operate safely.
Recovery-first positioning
OIN install and scope model
Backup and restore-preview workflow
SSO/SCIM validation
Workflows recovery mapping
Compliance evidence generation
Replica Okta capstone
Customer handoff and claims guardrails
Butterfly ↔ partner communication
One async record for every partner motion.
Communication between Butterfly and partners should be guided, evidence-based, and repeatable. The request record becomes the starting packet; follow-on updates use the same structure so sales, delivery, certification, and managed-service motions stay aligned.
1. Submit the packet
Use the guided request as the Butterfly ↔ partner communication record: motion, customer domain, scope, evidence links, owner, and requested next step.
2. Keep the thread async
Use the same guided request path for updates, scope changes, pilot context, capstone artifacts, or deal-registration changes so the record stays auditable.
3. Continue with assets
The submitter can keep moving through public docs, demo, service catalog, trust artifacts, and capstone prep without waiting for a person.
4. Gate authority separately
Reseller rights, certification badges, discounts, production access, and customer-change authority still require written terms and evidence.