Skip to content
Butterfly
A production facility in the holding sector
Industries · Holding Companies

In Holdings, Each Company Has Its Own Path, but the Group Must Move in One Direction.

When group companies in different lines of business run on different ERPs and applications, managing shared processes and achieving group-wide visibility can become difficult. Butterfly brings procurement, payment, customer and management processes together on a single orchestration platform while each company keeps its own way of working. It provides permissions by company and business unit while creating a shared group-wide management structure.

Request a Demo
Organizations that trust Butterfly
VodafoneFloReebokNine WestMetro IstanbulDoğuş MediaTypekuvazNTVDiscoveryTLCKoleksiyonLumberjackGQVogueDeva Holding CompaniesKoray KimyaPuhu TVDMAX

Different companies come together in a shared management rhythm.

A payment approval in one group company, a customer record in another or a shared procurement process may run on different systems. This fragmentation makes group-wide decisions and process comparisons harder. Butterfly brings shared processes and data together without disrupting each company’s own operating structure. The result is both company-level control and group-wide visibility.

TodayScattered tools break the group’s rhythm.
With ButterflyButterfly brings the group into a single management rhythm.
Group managementOne rhythm
Company A

Each company sets up its own tool.

Shared processes run on one platform with company-level permissions.

Company B

Payment approvals wait in different systems.

Threshold-based approvals move through a single flow.

Company C

The same customer sits in separate records across brands.

Customer records are deduplicated across brands.

Company D

Management cannot see the group on one screen.

The group dashboard shows approval and cash status on one screen.

Every payment reaches
the right desk based on its amount.

Threshold rules are defined once for the whole group; each company keeps its own permission structure. A reason is required for rejections and revisions.

Company A · ₺85,000Completed with unit manager approval
Company C · ₺420,000Unit manager → Group finance
Company B · ₺1.8MUnit manager → Group finance → Senior management
One rule set for all group companiesCompany-level permissions and workspacesEvery decision recorded with its reason

Shared process management across group companies

Group companies operate in different lines of business and on different ERPs. Without a shared process platform, each company builds its own tools and ways of working.

The flow with Butterfly

  1. Processes outside the ERP are managed group-wide on a single platform.
  2. Connections are made to different ERPs and databases; separate workspaces and permissions are defined by company and business unit.
  3. A shared group-wide process standard is created while each company’s own workflows and ways of working are preserved.

Payment approvals and management visibility

Payment requests, pending approvals, overdue payables and cash indicators are tracked in different systems. Management cannot see the group-wide financial picture from one place.

With Butterfly Threshold-based payment approval flows are set up across unit, finance and senior management stages. A reason is mandatory for rejections and revisions. Pending payments and due dates are tracked on management dashboards fed by ERP data.

Management can track the payment approval cycle and financial indicators from a single screen.

₺1.8M → awaiting senior management approval

Pending payment approvals and due dates of group companies on one dashboard; approval chain based on threshold rules. Sample data.

A shared customer view across brands

The same customer may exist as separate records across the group’s brands. This makes it harder to view customer history as a whole and to build joint campaigns.

The flow with Butterfly

  1. Customer records across brands are compared and deduplicated with rule-based scoring.
  2. Based on merge rules, a shared group-wide customer view and target audiences are created.
  3. Customer data becomes more consistent across brands, making group-wide campaigns and customer management easier.

Controlled rollout of low-code processes

There is a search for a low-code platform for indirect procurement and internal processes. As the number of users grows, license costs, scalability and governance become more important.

The flow with Butterfly

  1. A priority process such as indirect procurement is modeled end to end in a proof of concept.
  2. Technical analysis, scope and acceptance criteria are defined; tests are run and an evidence-based results report is prepared.
  3. The platform decision rests on results validated on a real process, not just on screen demos.

Group-wide process inventory and visibility

Company processes often live in people's knowledge and experience. There is no complete picture of which steps run in the ERP and which run in Excel or over email.

The flow with Butterfly

  1. A living process map is drawn, from main processes down to subprocesses and individual steps.
  2. Who performs each step, where and how is identified; manual steps and automation rates become visible.
  3. Transformation priorities are set based on a measured process inventory, not assumptions.

Processes managed end to end
across the holding

Butterfly
Indirect procurementRequests and approvals across group companies
Management dashboardsCEO and finance; threshold-based payment approvals
Shared customerCross-brand deduplication and group campaigns
Process inventoryA living map from main process to individual step
Group HR and auditE-signed approvals, digital archive, internal audit
Service deskRequest and ITSM processes
Butterfly orchestration layer
Indirect procurementRequests and approvals across group companies
Management dashboardsCEO and finance; threshold-based payment approvals
Shared customerCross-brand deduplication and group campaigns
Process inventoryA living map from main process to individual step
Group HR and auditE-signed approvals, digital archive, internal audit
Service deskRequest and ITSM processes

Regulatory and corporate requirements

  • Personal data access and permissions across group companies under KVKK (Turkish Personal Data Protection Law)
Frequently asked

Quick answers about Holdings.

Frequently asked questions about Butterfly in holding processes.

Can each group company keep its processes separate?
Yes. Each company or business unit can work in its own workspace with defined permissions. Processes and management dashboards that should be run jointly across the group can be shared centrally.
Can our companies that use different ERPs connect to the same platform?
Yes. Butterfly can work with different ERPs and databases through APIs and other suitable connection methods. Group-wide processes can then be managed on a shared platform without changing each company’s existing system. The connection method is determined by the technical characteristics of the systems in use.
Where should a holding start its transformation?
First, the processes and existing applications of the group companies are mapped. Processes that are run manually, repeated across companies or that require management visibility are identified. Then a priority process is selected and a pilot with defined scope and acceptance criteria is carried out.

The same orchestration
creates value in every industry.

Explore how Butterfly creates value across industries.

Let’s decide where to start, together.

In a discovery call, let’s talk about your existing systems and your priority process, and define the right starting area for you together.