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 →Okta professional services
Fixed-scope implementation, recovery drills, SSO/SCIM setup, and audit evidence for teams that need Okta backup and restore to work in production – not just look good in a demo.
These services are narrow on purpose. We are not trying to be a generic IAM consultancy. Butterfly focuses on Okta disaster recovery, restore proof, SSO/SCIM correctness, Workflows continuity, and compliance evidence.
Partner-enabled services
Okta credibility opens the door. The asset kit, campaign plays, and customer/contact records help partners turn service interest into scoped recovery work.
Okta credibility
Use the Okta relationship as factual trust proof: Activate tier, published Okta Integration Network listing, and Partner Community access.
View partner proof →Partner assets
Every asset maps to a motion: first conversation, audit evidence, implementation, co-branded campaign, competitive response, or certification.
Open assets →Marketing center
Campaigns define audience, action, and success metric so partner marketing drives pipeline instead of decorative content.
Start a campaign packet →Customers and contacts
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.
Service catalog
Inventory Okta apps, groups, policies, admin roles, Workflows, SCIM dependencies, and recovery gaps. Ends with a ranked remediation plan and Restore Readiness Score baseline.
Deliverables
Install Butterfly from the Okta Integration Network, grant required scopes, configure schedules, validate backup coverage, and run restore previews against approved fixtures.
Deliverables
Configure SAML or OIDC SSO plus SCIM 2.0 provisioning for Butterfly. Validate fail-closed behavior, assignment flows, deprovisioning, and administrator access controls.
Deliverables
Map critical Workflows, backup folders and flows, document dependencies, and define recovery steps for automation that moves users, groups, or access decisions.
Deliverables
Run a tabletop or controlled technical drill. Capture before/after evidence, dry-run output, operator notes, audit logs, and an executive-ready recovery report.
Deliverables
Quarterly restore drills, monthly readiness review, policy drift review, backup schedule checks, and incident-response support when identity changes go sideways.
Deliverables
Delivery model
The operating model mirrors the way Butterfly is built: every claim needs an artifact, every artifact needs a path back to a command, screenshot, API response, or audit log.
We define the Okta orgs, environments, compliance constraints, mutation boundaries, and the proof required to call the engagement done.
We capture current state: connection health, scopes, backups, SSO/SCIM posture, Workflows coverage, restore readiness, and audit evidence gaps.
We configure Butterfly, schedules, SSO/SCIM, restore previews, operator runbooks, and any approved remediation tasks.
Every engagement ends with explicit artifacts: command output, screenshots, API responses, audit logs, report files, and a handoff checklist.
Enterprise service standard
Butterfly should feel like a specialist recovery partner: scoped work, controlled access, dry-run proof, and handoff artifacts that IT, security, procurement, and audit teams can all read.
Scope
Customer domain, Okta orgs, environments, access roles, safety boundaries, acceptance criteria, and success evidence are recorded before production work starts.
Validate
Backups, diffs, restore previews, SSO/SCIM lifecycle checks, and Workflows recovery steps are validated before any customer-approved production change.
Evidence
Handoffs include backup IDs, restore-preview IDs, screenshots, API responses, audit logs, report files, open risks, and a completion checklist.
Operate
Every services motion ends with owners, escalation paths, operating runbooks, next-review cadence, and the proof needed for audit or incident review.
Start with one scoped outcome
We will turn it into a fixed-scope statement of work with deliverables, access requirements, safety boundaries, and the evidence needed to call it complete.