ButterflyOS Logo
Before IT defined what was possible
Now Business drives · AI executes
Platform Overview · June 2026

The System of Intention.
Business drives.
AI executes.

AI can now code faster than humans can think. The new bottleneck is structured business intent — not development speed. ButterflyOS Chrysalis turns strategy, OKRs and business knowledge into validated requirements and connects them to SAP® Cloud ALM, SAP Signavio®, Digital Discovery Assessment (DDA), SAP Joule Studio™ and your systems of record.

Category
Requirements Intelligence Platform
Core Flow
OKR Cascade → User Journeys · User Stories · SAP Scope Items → Code
Audience
Enterprises implementing SAP S/4HANA® · SAP Partners · Enterprise Architects · CIO · CDO
Use Case starten → Book a demo
Interactive demo

From document to structure

Experience how Chrysalis turns a functional spec into an actionable story map — user journeys, process steps and user stories with SAP fit context.

📄

Upload functional spec

Select a specification (e.g. Market to Lead) to start automatic generation.

Discover the methodology

From document to structure

Market to Lead — user journey, process steps and user stories generated from one functional spec.

Market to LeadLIVE BOARD

Activity · User journey
Market to Lead
Campaign & lead capture Customer & product Opportunity Quotation Quote to order
Lead capture & qualification
As a marketing manager I want to capture leads from campaigns…
Standard
Customer & product master
As a sales rep I need customer and product context in one view…
Standard
Opportunity & forecast
As a sales manager I want pipeline visibility by segment…
Config
Quotation & pricing
As a sales user I want to create quotes with approved pricing…
Config
Quote to order
As a sales operations user I want to convert accepted quotes…
Extension
“Needed in the market immediately — for customers and consultants.”

Lead Solution Architect at an SAP partner company

Experienced SAP solution architects confirm: the transition from unstructured functional concepts to clean S/4HANA user stories is the biggest bottleneck in project delivery.

Chrysalis · Fit-to-SAP

One story. One trace. Many targets.

Chrysalis routes validated intent to the right platform — and proves the decision before anything is built.

The Vision
Why ButterflyOS exists
ERP systems are the System of Record. SAP Joule™ (SAP’s AI execution layer) becomes the System of Execution. ButterflyOS becomes the System of Intention.
Enterprises spend millions on strategy. Then they spend millions on SAP. What happens in between — the translation of intent into scope — still lives in Excel, PowerPoint, and the heads of senior consultants. ButterflyOS replaces that gap with a system. Not another tool on top — the missing layer between decision and delivery.
System of Record
SAP® ERP software
Stores enterprise reality: customers, orders, invoices, deliveries, master data and financial records.
System of Intention
ButterflyOS · Chrysalis
ButterflyOS is the platform. Chrysalis is the Fit-to-SAP product — scope, fit, and architecture trace. Jarvis is the dialog assistant that helps business users express intent in plain language.
System of Execution
SAP Joule™ & delivery
SAP Joule Studio™ and other SAP® execution tools run validated intent — agents, workflows, project tasks and implementation artefacts.
Coding is becoming faster than thinking.
The value is no longer in generating code. The value is in generating the right intent.
The Problem
Where transformations fail today
The pain rarely starts in implementation. It starts earlier — before scope is stable, before architecture decisions are documented, and before AI or delivery teams know what should actually be built.
Without ButterflyOS
  • Customer documentation is interpreted manually and inconsistently.
  • Requirements lose context at every handover.
  • Scope Items and dependencies are identified too late.
  • Architecture decisions are not traceable.
  • AI agents may build fast — but in the wrong direction.
  • Go-live does not stop new requirements from arriving every week.
With ButterflyOS
  • Customer language becomes Story Maps, User Journeys and User Stories.
  • Scope decisions are continuously improved throughout the SAP Activate® methodology.
  • Standard, Configuration and Extension decisions are transparent.
  • Architects review and confirm high-impact decisions.
  • Business Intent Packages prepare handoff to SAP Joule Studio™.
  • Continuous Requirements Engineering supports operations after go-live.
Core use case
From document to user journey — in minutes
The original ButterflyOS entry point: upload functional specs, process models or workshop notes. Jarvis captures business language; Chrysalis structures it into user journeys, process steps and user stories — with SAP fit signals before the first workshop.
Documents
.md · .bpmn · .csv · PDF
›
Jarvis
Dialog · capture intent
›
User Journey
Story map · activity
›
Process steps
Columns · releases
›
User stories
With context
›
Fit-to-SAP
Chrysalis · GO/NO GO
Input
What you upload
Functional specs, BPMN, company journey maps, workshop notes, OKRs, regulation and customer requirements — no SAP expertise required in the business department.
Chrysalis
What gets structured
Canonical discovery model, user journeys, process steps, user stories, scope proposals per line of business — ready for SAP Activate® and your SAP® toolchain.
Outcome
What you decide faster
Standard vs. configuration vs. extension per story — with confidence and evidence. Architects review; the board is decision-ready before Explore workshops.
From document to structure — not from workshop chaos to Excel.
Try the interactive demo with a Market to Lead functional spec.
Use Case starten → Demo ansehen
Use Cases · Chrysalis in Action

Every SAP project type.
One intelligence layer.

ButterflyOS Chrysalis adapts to the transformation context — from clean Greenfield starts to complex multi-OpCo harmonizations to continuous post-go-live improvement. Jarvis understands the difference and responds accordingly.

Chrysalis-Fit: high
Chrysalis-Fit: medium
Chrysalis-Fit: foundational
3
Brownfield · Multi-OpCo
Process Harmonization
Multiple business units with diverging processes → unified SAP standard
Fit: very high

Multiple OpCos or business areas each run their own processes — often in legacy SAP ECC. The goal: converge on a single SAP S/4HANA® standard without losing critical business-specific requirements. This is the hardest transformation type: top-down from Signavio meets bottom-up from OpCo documentation. Jarvis holds both layers simultaneously and finds the meet-in-the-middle.

Input to Chrysalis
OpCo-specific functional specs
Process models per business unit
Signavio To-Be target architecture
Delta requirements from workshops
OKR cascade from group strategy
Jarvis Intelligence
Cross-OpCo conflict detection
Standard vs. exception classification
Fit: STANDARD · CONFIG · EXTENSION · GAP
Decision Trace per story
Confidence Score + Evidence
Output to SAP Toolchain
Harmonized backlog → Cloud ALM
Scope Items confirmed → DDA
Architecture decisions → LeanIX
Process links → Signavio
Handoff package for SAP Joule Studio™
Core use case for Chrysalis — highest Jarvis value. Complex requirements landscape, multiple stakeholders, maximum need for structured intelligence.
Get started
Which project type is yours?

Start a use case and see how Chrysalis maps your requirements — before your first workshop.

Use Case starten → Book a demo
For Enterprise · CIO · CDO · Transformation Lead
Your starting situation

Where are you right now?

Select the transformation context that matches your project. Chrysalis adapts — from a first public cloud pitch to post-go-live continuous delivery.

Chrysalis-Fit: high
Chrysalis-Fit: medium
Chrysalis-Fit: foundational
Pick your situation

All use cases in detail →

The Core Flow
The Paradigm Shift

IT used to define what was possible.
Now business defines what gets built —
and AI executes.

The AI coding revolution has inverted enterprise IT. Speed is no longer the constraint — structured business intent is. Every enterprise has strategic objectives. Every enterprise runs systems of record. The new bottleneck is the translation layer between them. Chrysalis is that layer.

Strategy
OKR Cascade
Company → Division → Department → Team objectives
Chrysalis
Requirements Intelligence
OKRs → User Stories → Fit Classification → Validated Scope
Architect
Decision
GO / NO GO — with full evidence and decision trace
Handoff
Validated Package
Cloud ALM · DDA · SAP Joule Studio™ · ready to build
Execution
Systems of Record
SAP · Dynamics · Salesforce · Custom Code
Works with your systems of record
SAP S/4HANA®
Microsoft Dynamics
Salesforce
Custom · FastAPI · Python
SAP Joule Studio™
More coming
~20%
cost reduction
Measurable Impact · Per Project
Every SAP project costs less
with Chrysalis.

The ~20% consulting cost reduction comes from three compounding effects:

Fewer workshops — Fit-to-SAP is done before the first session. Explore phase shrinks from weeks to days.
Structured handoffs — No translation loss between business and IT. Requirements arrive validated, classified, and ready for Cloud ALM.
Less rework — Wrong requirements caught before they enter development. Change requests evaluated in minutes, not weeks.
New requirements move fast — Post-project changes no longer wait weeks in Excel queues. Every new requirement is assessed and handed off immediately.
A · In Projects
🏗
SAP Transformation · SAP S/4HANA® Implementation
Structured from day one.
Delivered faster.

Every SAP project starts with the same problem: unstructured documents, unclear scope, weeks of workshops to figure out what is standard and what needs custom work. Chrysalis solves this before the first meeting — and keeps requirements structured throughout the entire project lifecycle.

⚡
Fit-to-SAP before the first workshop
Chrysalis maps business requirements to SAP Scope Items automatically. Your team walks into Explore already knowing what is standard, what needs configuration, and what requires custom development.
8–12 weeks → days
📋
Structured backlog from day one
Every user story comes with a fit classification, confidence score, and decision trace. Your Cloud ALM backlog is populated before the first sprint — no manual entry, no translation loss.
Ready for Cloud ALM · DDA · SAP Joule Studio™
🔍
Every decision is traceable
Why EXTENSION? What evidence? Chrysalis documents every reasoning step — no more "I think we decided this in a workshop three months ago." Full audit trail, always.
Full audit trail · zero guesswork
🚀
New requirements move immediately
Mid-project change requests don't derail timelines. Every new requirement is evaluated instantly: fit class, impact on existing scope, clean core risk. Structured answer in minutes.
Impact analysis in minutes
🏛
Clean Core by design
Extensions are flagged before they enter development. Alternatives in SAP standard are proposed automatically. Your SAP S/4HANA® stays upgrade-safe — not by accident, but by architecture.
Risks flagged before build
🗺
OKR cascade → SAP scope
Strategic objectives flow directly into Chrysalis. Jarvis translates company-level OKRs into department requirements and maps them to SAP scope — from boardroom to backlog, without a manual translation layer.
Strategy → Requirements → Code
Without Chrysalis
8–12 weeks of manual fit-to-standard workshops
Requirements in Excel, Word, PPT — no structure
Scope decisions undocumented — "I think we decided..."
Clean Core violations discovered late — expensive rework
OKRs never reach the development team
New requirements wait weeks for evaluation
Knowledge disappears when the project ends
→
With Chrysalis
Fit-to-SAP done before the first workshop
Structured User Stories with Scope Item mapping
Every decision traced — evidence per story
Clean Core monitored — risks flagged before build
OKR cascade directly into SAP scope
New requirements evaluated and handed off in minutes
Knowledge captured in catalog — grows permanently
B · In Operations · Regelorganisation
♾️
Post Go-Live · Continuous Delivery · IT Operations
Go-Live is not the end.
It is the beginning.

After go-live the business keeps moving. New regulations arrive. OKRs change. Markets shift. Each change generates new requirements — and without Chrysalis, they pile up in emails and Excel until someone manually translates them into IT tickets weeks later.

"Coding now goes faster than thinking. The bottleneck is no longer the developer — it is the quality of the requirement. Chrysalis ensures what gets built is what the business actually needs. Not just once, but permanently."
Continuous Input
What triggers new requirements
New OKRs from quarterly strategy review
Regulatory changes — CSRD · LKSG · Tax
Customer and market requirements
SAP 2-year release cycle updates
M&A: new entities to integrate
Internal process improvement initiatives
Jarvis in Operations
What Chrysalis does continuously
Evaluates every new requirement — Standard or Extension?
Assigns to correct wave for next release
Checks impact on existing scope and architecture
Monitors Clean Core — flags risks before build
Feeds validated backlog continuously into Cloud ALM
Prepares SAP Joule Studio™ handoff for next development cycle
Instead of Today
Without Chrysalis in operations
Requirements collected in department Excel sheets
Forwarded by email — context lost in translation
IT ticket created weeks later — requirement already changed
Developer interprets without business context
Wrong thing built — expensive rework cycle
Knowledge never captured — repeated every cycle
The Enterprise Catalog
Your knowledge — permanently structured
Every decision captured in your enterprise catalog
Each project enriches the catalog — compounding value
New requirements matched against existing decisions
Industry best practices injected by your SAP partner
Jarvis gets smarter with every engagement
Your IP stays yours — catalog belongs to your enterprise
🔄
Permanent requirements intelligence
Chrysalis does not switch off after go-live. Every new requirement — from any source — is evaluated, classified, and handed to IT in a structured way. Operations run on intelligence, not on Excel.
Always on · always structured
📈
SAP release readiness
SAP releases major updates every two years. Chrysalis evaluates every new feature against your existing requirements and flags which extensions can now be replaced by standard — keeping your clean core intact over time.
Every release evaluated automatically
⚖️
Regulatory compliance built in
CSRD, LKSG, new tax rules — when compliance requirements arrive, Chrysalis maps them to affected SAP processes, identifies gaps, and generates requirements for your compliance backlog. No manual translation.
Regulation → requirement → backlog
Ready to start
Close the gap between strategy and code.

From your first OKR to a validated handoff to SAP Joule Studio™ — in projects and permanently in operations.

Use Case starten → Book a demo
SAP Activate® methodology
One requirement base that improves phase by phase
Chrysalis on ButterflyOS creates one requirement foundation from day one — and hardens it across every Activate phase. User stories become more accurate, relevant and traceable. The same intent feeds your SAP toolchain without re-translation.
Discover
Existing documents become Story Maps, User Journeys and initial User Stories — plus early cloud-fit signals.
Prepare
Stakeholders refine priorities, epics, waves and governance context — aligned with SAP Signavio® scope framing.
DDA
Scope, Line-of-Business and license-relevant decisions become transparent — ready for SAP® Cloud ALM solution and Explore.
Explore
Fit-to-Standard workshops start with validated stories, scope candidates and SAP Signavio fit/gap context.
Realize
Validated intent flows into SAP Cloud ALM, implementation teams, tests and handoff to SAP Joule Studio™.
Run
Continuous requirements from regulation, customers and operations — structured, not ad-hoc in Excel.

Inputs → Chrysalis → SAP toolchain: per Activate phase, what enters ButterflyOS, what Chrysalis produces, and how SAP Signavio®, SAP Cloud ALM, DDA, SAP LeanIX and WalkMe receive structured handoffs — instead of Excel and email chains.

One requirement base across Discover, Prepare, Explore, Realize and Run — DDA and CBC consume the same structured scope before and during Explore.

One intent. Many outputs.
The same business intent can feed SAP® Cloud ALM solution, Digital Discovery Assessment, delivery workstreams and handoff compatible with SAP Joule Studio™. No duplicate PowerPoint-to-Excel-to-Jira translation.
Compatible with SAP Joule Studio™
Chrysalis is not another agent builder
SAP Joule Studio™ (an SAP offering) can generate agents, workflows and code. On the ButterflyOS platform, Chrysalis (with Jarvis as dialog assistant) determines what should be generated, why it matters, whether it fits SAP standard and whether it is architecturally responsible — before handoff to SAP execution tools.
Jarvis
Plain language
›
Chrysalis
User journey · Fit
›
Fit Review
Standard · Config · Extension
›
Business Intent Package
Traceable handoff
›
SAP Joule Studio™
SAP AI execution
Requirements before agents
Before AI builds, Jarvis and Chrysalis clarify business value, affected journeys, scope, governance and architecture.
Human-in-the-Loop by design
Architects, business owners and product owners confirm high-impact decisions before execution moves forward.
Honest STOP logic
If a requirement is not fit for standard/configuration or needs custom development, Chrysalis stops the handoff.
Future-ready handoff
The goal is a validated Business Intent Package and handoff ready for SAP Joule Studio™, not uncontrolled prompt-to-agent delivery.
Effective Catalog
One brain, two outputs
Chrysalis (Fit-to-SAP) and execution handoff to SAP Joule Studio™ share the same business truth on ButterflyOS: the Effective Catalog. It combines global SAP® knowledge, partner expertise and customer-specific context.
Butterfly Core
Global SAP Baseline
  • Scope Items and Process Steps
  • Capabilities and Fit Signals
  • SAP Fiori® master data and patterns
  • Public Cloud baseline knowledge
Partner Overlay
Private Industry Expertise
  • Industry signals and preferences
  • Capability templates
  • Validated delivery patterns
  • Partner IP remains protected
Enterprise Overlay
Customer-Specific Truth
  • Terminology and legacy aliases
  • Project decisions and suppressions
  • Governance rules
  • Customer-owned context
Effective Catalog
One business truth
›
Fit-to-SAP
Scope · Fit · Impact
›
AI handoff
Business Intent Package → SAP Joule™
Partner Network
Why partners join ButterflyOS
Partners do not simply buy software. They build assets. Every customer project strengthens their private knowledge base and increases their ability to win future projects.
Win more projects
Show customers Story Maps, User Journeys, Scope Candidates and Fit-to-SAP analysis before implementation starts.
Scale industry expertise
Transform senior consultant knowledge, industry patterns and lessons learned into reusable Partner Overlays.
Differentiate from generic competitors
Show real industry journeys and scope mappings instead of generic capability slides.
Create new roles for juniors
Junior consultants curate industry knowledge, validate mappings and improve capability templates instead of producing disposable documents.
Knowledge becomes a scalable asset.
In the future, customers will not only ask how many consultants a partner has. They will ask what knowledge the partner brings. ButterflyOS makes that knowledge visible, reusable and commercially valuable.
Current Focus
Where ButterflyOS is going next
The platform starts with SAP, but the pattern is broader: Strategy → Intention → Requirements → Architecture → Execution.
Now
Chrysalis · Fit-to-SAP
Stabilize Public Cloud use cases, story mapping, scope mapping and SAP Activate® alignment — powered by Jarvis.
Next
SAP Joule™ handoff
Business Intent Packages and handoff compatible with SAP Joule Studio™ — plus partner capability templates.
Later
Strategy-to-Code
Integration with strategy, OKR and transformation systems — including Salesforce, Microsoft and Oracle paths over time.
The mission for June 2026
Win five founding industry partners, start two enterprise pilots, stabilize Fit-to-SAP, validate handoff to SAP Joule Studio™ and grow the Effective Catalog every day.
See ButterflyOS in action.

Book a 30-minute walkthrough — Chrysalis (Fit-to-SAP), Jarvis, partner overlays, and handoff to SAP Joule Studio™.

Book a demo
Contact

Leave a message

Questions about Chrysalis, partnerships or your S/4HANA project? Send us a note — we typically reply within one business day.

By submitting, you agree that we process your details to handle your request (Privacy policy).

Prefer a call? Use Jarvis for a callback, or +49 170 786 26 73.

Book a demo