Your S/4HANA transformation starts with your business model.
Not with SAP.
From your strategy, your goals and processes comes a validated SAP scope – with augmented intelligence. Everything on one data foundation: A single journey step simultaneously drives scope mapping, license need, and Clean Core. Agents prepare, your architects decide.
Journey Compare is the shared decision layer for the business, the architect, and agents.
- 20+ years of SAP transformations worldwide
- Member of the SAP PartnerEdge Open Ecosystem
- Runs on SAP BTP · synced with Cloud ALM
- Piloted on S/4HANA Public Cloud
Partners and technology suppliers
Your transformation is prepared more precisely — people decide.
Architects and project teams approve. Agents prepare and explain.
From Business Intent to Delivery.
ButterflyOS Manifesto
12 principles for better transformation
-
Human-in-the-loopAI prepares. People decide.
Agents can search, read, structure, compare, analyse and develop alternatives. Consequential architecture and transformation decisions belong in the hands of experienced people. That is Augmented Intelligence for us.
-
We start from your business reality – not from the SAP catalog.
Transformation begins by understanding how a company works today, what it wants to achieve and what makes it distinctive. Only then do we build the bridge to the SAP standard.
-
Transformation is more than software.
Technology alone does not transform a company. Successful transformation connects method, platform and people. That is why ButterflyOS is software and transformation method at once — accompanied by experienced transformation professionals.
-
Business intent comes before execution.
Before we ask how something will be implemented, we want to know why it should change. Strategy, OKRs, regulatory requirements, operational problems and business value give the transformation its direction.
-
A requirement needs a reason.
Requirements are the engine of change. A requirement without a traceable origin loses its context. That is why we connect requirements to strategy, OKRs, business intent, processes, decisions, delivery and tests.
-
Standard where standard makes sense. Differentiation where it creates value.
Clean Core is an important architecture principle — but not a dogma. Companies may deliberately be different. What matters is making deviations visible and deciding consciously about their business value and consequences.
-
Good experts should think — not chase information.
Consultants and architects should talk to people, understand context and make decisions. Not search hundreds of documents, copy Excel lists and re-document the same information again and again.
-
Every phase must build on the previous one.
Discover, Prepare, Explore, Realize, Test and Delivery are not separate worlds. What is created at the start becomes more precise and more robust as the program progresses. Don’t restart. Increase confidence.
-
Knowledge must not disappear with the workshop.
Why was something decided? Which alternative was discarded? What evidence was on the table? Transformation creates valuable enterprise knowledge. That knowledge belongs in corporate memory — traceable and reusable for people and agents.
-
The agentic toolchain must not become a gigantic toolchain.
More agents and more tools do not automatically fix fragmentation. Butterfly does not want to be just the next tool in the chain. We connect business intent, processes, SAP scope, requirements, decisions and delivery — and integrate specialised systems where they add value.
-
Transformation must become faster and more efficient — without becoming worse.
Our goal is not to replace as many consulting days as possible with AI. Our goal is to reduce unnecessary work and raise the quality of the human work that remains: better requirements → better decisions → better specs → better delivery → better tests → better outcomes.
-
A transformation belongs to the enterprise.
Processes, requirements, decisions, experience and transformation knowledge are enterprise IP. After the project they must not disappear into decks, consultants’ heads or single tools. Your transformation. Your knowledge. Your IP.
- Your processes
- User Journey
- SAP Reference
- Scope Items
- Requirements
- Architect Decision
One companion from the first idea – all the way to operations.
Butterfly OS follows the phases of SAP Activate. What is created in Discovery carries through the whole program: Explore does not start from zero, but with ready user journeys, scope items and requirements.
-
Understand how the company works today and where it wants to go.
Butterfly delivers- User journeys from the customer’s legacy processes
- Mapped against the SAP standard
- First scope items, requirements and license needs
-
Set up the program and settle the scope.
Butterfly delivers- Final scoping as the basis for the project contract
- Scope baseline reconciled with the DDA
- License structure that matches the scope
-
Harden requirements and adapt processes where needed. Explore starts with finished user journeys instead of empty workshops.
Butterfly delivers- Hardened requirements on the process step
- Process adjustments where the standard falls short
- Test cases straight from the stories
- Synced with SAP Cloud ALM
-
Build what was decided, with people and agents.
Butterfly delivers- Approved stories and test cases in SAP Cloud ALM
- Intent and context handed straight to implementation and test agents Roadmap
- Support for configuration and app development Roadmap
-
Go live and keep evolving without losing the thread.
Butterfly delivers- New requirements follow the same path
- Linked to strategy and OKRs
- Decisions stay traceable
- User journey
- Requirement
- Scope item
- Test case
- Context for agents
Migration is mandatory. Transformation is the opportunity.
SAP mainstream maintenance for ECC ends in 2027. Every company on ECC is now choosing a path, and most choose the fastest one instead of the best one.
Large programs rarely fail on technology. They fail on decisions made too late, too implicitly or without the business at the table. If you take the time, you take the Bluefield route: keep what makes your business different and adopt the SAP standard for everything else.
Lift & Shift
Fast technical move. Old processes, new platform.
Example A retail company moves ECC onto HANA and leaves Z-transactions and custom code untouched — go-live in a few months, Clean Core deferred.
Brownfield
System conversion. History preserved, legacy too.
Example A machine builder converts ECC 1:1 to S/4HANA including document history and modifications — regulatory continuity yes, hidden complexity and legacy debt also.
Greenfield · Public Cloud
Clean start on the standard. Existing know-how is easily lost.
Example A growth-stage group restarts sales and finance on S/4HANA Public Cloud and deliberately retires local custom developments — standard-first, but only if business know-how travels with it.
Bluefield
RecommendedKeep what sets you apart from competitors. Everything else moves to the SAP standard.
Example A pharma company moves core processes onto the SAP standard and selectively keeps differentiating manufacturing and quality flows — fit-to-standard with a conscious decision per scope item.
More on the SmartBluefield MethodIntent in — governed blueprint out.
Describe your program in your own words. The studio reads the intent, matches a scenario and returns a first executive answer with evidence, gaps and confidence — not an open-ended AI chat. The more context and outside-in you bring, the more robust the preparation becomes.
Three knowledge sources — the fuller, the better- ACorporate memoryYour own knowledge: processes, decisions and lessons from earlier projects.
- BOutside-inThe view from outside: SAP Best Practices, industry references and release updates.
- CAIConnects memory and outside-in, proposes and explains. You and your partner decide.
What do you want to transform today?
Describe the transformation intent. This demo returns a first governed blueprint answer with memory signals, gaps and next actions — curated sample memory, not an open chat.
Pick a scenario or describe your intent — the answer appears here.
Transformation overview (demo preview)
AI assisted. Human validated. Corporate Memory approved.
More context and outside-in raise confidence. Book a demo — then we'll go into a session together in the Transformation Studio.
Your team, your SAP partner, one method.
You stay in charge of your transformation. Your SAP partner delivers it. Butterfly provides the method that keeps everyone aligned, and helps you apply it until your team runs it on its own.
Built into Butterfly OS
A transformation method from more than 20 years of SAP projects, tested in a pilot on S/4HANA Public Cloud. Your team works with it directly, from strategy and OKRs to scope, architecture and licenses.
- Story Maps from standard or your documents
- Fit-to-standard and scope decisions
- Requirements and license intelligence
- Customer portal on SAP BTP
Help when you want it
We help you get started and make sure the method works in practice. As much or as little as you need, with one goal: your team applies it with confidence.
- Getting the program started
- Choosing the right approach
- A first sprint together
- Training and coaching
Delivers the project
Your SAP partner and their architects bring the delivery experience. Butterfly gives everyone the same method and the same view of every decision.
- Works with the partner you already have
- Shared Story Maps and decisions
- Architects stay in charge of architecture
- Results visible in your SAP landscape
We help you apply the method, until you no longer need us.
A Public Cloud rollout across 40 countries looks different from a Bluefield program with a strong legacy core. The method stays the same, the way you apply it changes. We bring over 20 years of SAP consulting from elephant360 and practice built along SAP Activate, and think it through with you.
Getting started
Set up your program around the method: roles, workstreams and a clear way to reach decisions.
Choosing the approach
Greenfield, Brownfield, Bluefield or Public Cloud: we think it through with you and your partner.
Fit-to-Standard Sprint
Apply the method together on one process area, then carry on with your own team.
Architecture reviews
A second view on deviations from the standard, alongside your architects and your partner’s.
Scope and license planning
See scope options and their license impact before you decide.
Training and coaching
Your team and your partner learn the method and the platform on your own process, not on training examples. That way the knowledge stays with you.
The method in four steps
Your team runs these steps with your partner. The platform records each decision, so nothing depends on who was in the room.
- Understand the business intentStrategy, OKRs and the customer’s own terms
- Show the standard firstStory Maps from SAP scope items, presented live
- Capture and assess deviationsRequirements checked against standard and clean core
- Decide, publish, syncArchitect gate, then customer portal, then SAP Cloud ALM
The missing intent layer of the SAP agent-led toolchain.
Butterfly OS works upstream of SAP Cloud ALM, Signavio and the Digital Discovery Assessment and hands its results to them. It decides what should be built; your delivery tools and agents build it.
Butterfly turns legacy processes and business intent into customer journeys, compares them systematically with the SAP standard, and turns the deviations into decisions you can stand behind.
This is more than document analysis or process modelling.
From legacy reality to an architect-approved SAP standard journey.
Mapping legacy against the SAP standard is the marketable use case. The journey is the shared language.
- Understand the legacyDocuments, processes, custom code and workshops — the customer’s reality, not the catalogue.
- Translate into a journey the business can readA customer journey with activities and requirements, readable for the business, the architect, and agents.
- Place the matching SAP standard beside itSAP scope items and standard processes become the SAP standard journey. SAP has standard journeys — Butterfly sets them against the customer journey.
- Compare step by stepJourney Compare makes Fit-to-Standard a shared decision: Covered, Deviation, Gap, Local Only.
- Take the transformation decisionStandard, configuration, redesign, extensibility, not supported or unclear — with evidence and architect approval. Then dock to Signavio, Cloud ALM, DDA and delivery.
What Butterfly actually does
Strategy & OKRs
Business intent, process documents, customer language
Butterfly OS
Story Maps · Fit-to-Standard · Requirements Intelligence · Scope & licenses
Cloud ALM · Signavio · DDA
Validated scope flows into delivery
Delivery agents
Build what was decided
Journey Studio
Start from the SAP standard and present it live, or generate Story Maps from the customer’s own documents. Deviations are captured from the conversation.
Fit-to-Standard & Scope
Every process step mapped to scope items and classified as standard, configuration or extensibility, reconciled with the DDA.
Requirements Intelligence Engine
First checks whether a requirement fits the standard and clean core. If not, it proposes an architecture for the architect to decide on.
License Intelligence
Predicts license impact from requirements before implementation, not after go-live from usage data.
Customer Portal on SAP BTP
Customers see what has been approved as a living process map in their own SAP landscape, synced with Cloud ALM.
The AI layer across all modules
The agent proposes, prepares and explains. It never approves.
Requirements belong to the process step.
BPMN shows the flow. A journey shows one persona. A Butterfly Story Map shows which requirements hang on which process step, with every role, scope item and fit decision in one view.
- BPMN diagramflow
- Customer journeyflow + one persona
- Butterfly Story Mapflow + roles + requirements + scope + fit
Drop shipment, end to end
The number on each step counts the requirements attached to it.
Readable by people and by agents.
Every scope item knows which goal it serves.
Butterfly keeps one unbroken chain from your objectives to the SAP scope and the licenses it triggers. When someone asks why something is in scope, the answer is one click away.
- OKRObjectiveFaster order-to-cash in wholesale
- IntentBusiness intentShip directly from supplier to customer
- Story MapProcess stepReceive carrier notification
- RequirementRequirementIntegrate carrier platform via API
- ScopeScope & fitSide-by-side extension, architect approved
- LicenseLicense impactPredicted before implementation
Agents work.
Humans decide.
Domain experts, product owners, lead architects and module consultants keep the final say. Every proposal passes an architect gate before it reaches the customer, and every decision carries its rationale.
The architect reviews the agent’s proposal, corrects it if needed and approves.
- Scope item
- Confirmed
- Fit rationale
- Architect approved
The customer sees only what was approved, in their own SAP landscape.
Your partners deliver. The method keeps everyone aligned.
Butterfly works with a network of Butterfly partners: certified SAP partners and specialists in strategy, OKRs and other disciplines that support transformation. Enterprise customers are not limited to a single partner — partners can collaborate and complement each other on the same program. Customer, partners and architects share one view of every decision.
Bring your partners along — or meet ones who know the method.
Already working with an SAP partner or with specialists in strategy and OKRs? Butterfly fits into that setup. Several partners can work together on one program. Still looking? We can introduce partners who already work with the method.
Talk to usBring the method to your customers.
Whether you are a certified SAP partner or a specialist in strategy, OKRs and transformation: scope projects faster with standard-first presales, reusable Story Maps and a customer portal that makes your work visible. Includes platform access, enablement and joint go-to-market.
Join the networkPartner logos after written approval.
Built for small, mid-size and large programs.
Piloted on S/4HANA Public Cloud, where the standard is law. Designed for Private Cloud and on-premise, where the standard is the reference.
ECC to S/4HANA
Greenfield, Brownfield, Bluefield or Lift & Shift, with a clear fit-to-standard baseline.
Global Public Cloud rollout
One template, many countries: standard first, local deviations decided and documented.
Process harmonization
Compare how sites and countries really work and converge on one global template.
Clean-core readiness
Find which custom logic stays, which goes standard and which moves to side-by-side extensions.
Presales & pre-studies
Show the standard first, capture deviations live and scope before the program starts.
Beyond go-live
New requirements in the run organization follow the same path: from goal to story map to scope, tied to strategy.
Piloted with an SAP partner on a live S/4HANA program.
“The greatest gain from Butterfly OS is the traceability and structure of the requirements-management process, in every project phase and in the run organisation. That helps customers as well as architects and agents enormously. You can spare yourself many late requirements.”
from the first workshop before project start to the start of the realization phase, measured in the pilot and compared with projects without AI
- More transparency for customer and project team
- AI prepares decisions — people decide
Retail company · S/4HANA Public Cloud
Drop-shipment process across sales, purchasing, fulfillment and invoicing. Reviewed live with the customer and published in the BTP portal.
Read the caseYour process knowledge stays yours.
Built in Berlin for European enterprises. Every decision is logged with its rationale and approver.
SaaS or BYOC
Butterfly is available as Software as a Service (SaaS) or Bring your own Cloud (BYOC). Platform and customer portal on SAP BTP.
GDPR · DPA on request
Subprocessor list available on request.
Leading LLMs, including Claude (Anthropic), GPT (OpenAI) and Gemini (Google)
Customer data is processed only to deliver the agreed service. How language models and subprocessors are used is set out in the DPA.
Human approval by design
Architect gates, audit trail and rationale on every decision.
Member of the SAP PartnerEdge Open Ecosystem
Runs on SAP BTP, syncs with SAP Cloud ALM.
Status on request
No certification claim on this page.
What does your requirements process cost – without and with Butterfly OS?
Set lines of business, processes and day rate. The calculator compares effort for license estimate, requirements engineering and specification — and rework from requirements found late. Rough estimate, not an offer. The Butterfly OS license is not included.
Start with one process. Scale to the whole program.
You can be up and running within 24 hours. After you engage us, a dedicated Butterfly colleague is assigned to you: intensive support, onboarding and empowerment of your team. From your existing documents we generate selected processes per line of business.
You do not need to start a full project. Entry can be a single process — including in the pre-study. Or you begin in the Transformation Studio and jointly develop a project approach grounded in many successful implementations. Project phase and scope size stay flexible. In the Fit-to-Standard Sprint you get Story Maps, requirements, scope items and fit decisions; agents prepare, architects decide. What stands in one process area, you extend step by step to the whole program.
Documents, specs, SAP edition — and you have the comparison.
Not a months-long pre-project. Once we have your materials, we deliver in a few days:
- Customer journey
- SAP standard journey
- Journey Compare
- Deviations
- Open questions
- Proposed scope items
Fit-to-Standard Sprint
Fixed price on request
One process area, duration agreed per process area — without standing up the whole program: Story Maps, requirements, scope items, fit decisions and a license indication, published in the customer portal.
Start a sprintMethod support
As you need it
Intensive support with a dedicated contact — in the pre-study or mid-program: help getting started, a first process, architecture reviews or coaching. As much or as little as your team wants.
Talk to usButterfly OS license
On request
The method on the platform for your team and your SAP partner, per project or per year — as Software as a Service (SaaS) or Bring your own Cloud (BYOC). Modules can also be licensed individually.
Request an offerLet’s talk about your program.