Axton Group LTD Japan and Fluyenta Partner to Bring Enterprise Automation to Japan

The article at a glance

The Axton Group LTD Japan × Fluyenta partnership is focused on helping organizations connect fragmented systems, automate multi-step business processes, create secure interfaces for external stakeholders, and introduce AI into governed operational workflows.

For Japanese companies, the objective is not simply to add another software product. It is to identify critical processes where people, existing systems and data are disconnected, and then build a practical route toward a more integrated operation.

Why enterprise automation matters for Japan now

Digital transformation in Japan has moved well beyond the question of whether companies should adopt digital tools.

The harder question is now: how do those tools work together to create measurable business change?

IPA’s DX Trends 2026 found that AI adoption continues to expand among Japanese companies, particularly large enterprises. At the same time, much of the value currently being realized remains concentrated around operational efficiency and faster work; expansion into broader value creation and business transformation remains more limited.

Legacy technology remains part of the challenge. METI’s Legacy Systems Modernization Committee reported that existing systems continue to hinder the introduction of newer digital technologies at Japanese companies and emphasized the need to move toward more flexible, modern environments capable of responding to business change.

This is an important distinction.

A company may already have an ERP, CRM, document system, cloud applications, spreadsheets, databases and now several AI tools. Yet employees may still be copying data between them manually, waiting for approvals by email, checking status by telephone, or asking multiple departments for the same information.

Buying more software does not automatically solve that problem.

Often, the missing layer is orchestration: connecting people, systems, decisions and data into an end-to-end process.

That is the area the Axton × Fluyenta partnership is designed to address.

What enterprise automation means

Enterprise automation is broader than automating individual repetitive tasks.

A simple automation may move information from one application to another. Enterprise automation has to deal with a much wider operational reality: multiple departments, different systems, approvals, exceptions, external stakeholders, security rules, human decisions, audit requirements and sometimes AI.

Consider a procurement process.

A purchase request may begin with one employee, require budget approval from a manager, involve procurement and accounting, require information from a supplier, create or update information in an ERP, generate documents, trigger notifications and eventually need to be visible to management.

If each step is handled separately, employees become the integration layer.

An enterprise workflow instead coordinates those steps as one process while allowing existing systems to continue doing the jobs they were designed to do.

Fluyenta describes its platform around workflow automation, integration, governed AI, data management, API connectivity, monitoring and enterprise controls. It emphasizes human approval and override within automated processes rather than treating automation as the removal of human oversight.

Axton and Fluyenta: complementary strengths

The partnership combines two complementary strengths.

Axton Group LTD Japan brings the Japan-side business context. Our role is to understand the operational problem, communicate with Japanese stakeholders, help translate business requirements into a workable automation opportunity, and maintain the local customer relationship.

Fluyenta brings the enterprise automation technology and experience. Fluyenta describes itself as the current company behind RunMyProcess and says its current platform builds on more than two decades of enterprise process-automation experience. The company’s history includes the RunMyProcess business founded in Paris in 2007, its acquisition by Fujitsu in 2013, acquisition by Akorbi Digital in 2021, and its current ownership under AK Digital.

This allows Axton to approach Japanese digital transformation differently.

Instead of beginning with:

“Which software should we sell?”

we can begin with:

“Which business process is creating friction, and what needs to connect for that process to work better?”

That is a much more useful starting point.

Five connected capabilities

Our enterprise automation discussions can broadly be understood through five connected capabilities: Integrations, Automation Flows, External Portals, AI Native capabilities, and Collaboration.

Integrations connect the systems a company already depends on—such as ERP, CRM, databases, cloud services, legacy applications and APIs.

Automation Flows coordinate the actual sequence of work: submissions, validations, approvals, decisions, escalations, notifications and updates.

External Portals give suppliers, subcontractors, customers or other outside stakeholders a controlled way to participate without exposing internal business systems.

AI Native capabilities place AI inside governed workflows where it can assist with activities such as document processing, classification, summarization, information extraction, routing and decision support.

Collaboration keeps people involved where judgment, approval or intervention is required.

This is particularly important as organizations move from experimenting with AI toward embedding it in real operations. AI becomes more useful when it knows what process it is part of, what information it is allowed to use, what happens next, and when a human must make the decision.

Fluyenta’s current platform positioning similarly emphasizes combining workflows, integrations, AI and governance within one controlled environment.

We will explore these five capabilities in greater detail in a separate article.

What processes can improve?

The problems do not need to begin as enormous “digital transformation programs.”

They can begin with a process employees already know is painful.

Imagine a construction company coordinating subcontractor documentation. A subcontractor might send insurance documents, certificates, worker information and project documents through email. Someone then checks the files, another person approves them, the project team needs to know the result, and information may ultimately need to be entered into an internal system.

That process could instead become:

Submission → validation → internal review → approval → notification → system update → auditable record

The internal ERP or project-management platform does not necessarily have to be discarded. The workflow layer can coordinate the process around it.

A similar approach can apply to procurement approvals, maintenance requests, quality-control workflows, customer onboarding, field operations, employee processes, compliance workflows, document review and supplier management.

Fluyenta / RunMyProcess partner experience

One publicly documented RunMyProcess case describes a building-materials retailer whose supplier onboarding relied heavily on email and telephone communication. The resulting issues included slow approvals and limited visibility across branches.

The solution introduced structured data collection, automated approval routing and real-time visibility into onboarding status. The published case reports faster onboarding, improved internal efficiency and a smoother supplier experience, while keeping the client identity anonymous.

This is Fluyenta/RunMyProcess partner experience, not an Axton-completed customer project. We make that distinction deliberately.

What makes the example relevant for Japan is not the industry name. It is the pattern:

Manual communication + fragmented information + repeated approvals + poor visibility.

Those same patterns appear across many organizations.

Do existing systems need to be replaced?

Not necessarily.

For many companies, replacing a major ERP or legacy system is expensive, disruptive and difficult to justify when that system still performs important functions.

METI’s work on legacy-system modernization recognizes the need for environments that can evolve more flexibly with changing business requirements.

Enterprise orchestration offers another option: modernize the process around existing systems while progressively improving the underlying architecture where necessary.

Fluyenta specifically positions integration across ERP, CRM, APIs, cloud applications and legacy environments as a core part of its approach.

Sometimes replacement will still be the correct decision.

But “replace everything” should not automatically be the starting assumption.

How should AI be used?

The same principle applies.

AI should not be added simply because a company wants to say it uses AI.

A better question is:

Where in the process can AI reduce effort or improve decision-making without removing necessary accountability?

For example, AI might extract information from submitted documents, summarize a long report, identify a category, detect missing information or prepare a recommendation.

The workflow can then route that output to an employee for review or approval before the next action occurs.

This approach is particularly relevant as Japanese organizations increase AI adoption while still working through governance, organizational and value-creation questions identified in IPA’s 2026 research.

The goal is not “AI everywhere.”

The goal is useful AI inside a controlled business process.

Useful improvement in weeks, where appropriate

Another principle we share with Fluyenta is that useful digital improvement should not automatically require an endless implementation cycle.

Fluyenta’s current product material emphasizes rapid low-code delivery and moving appropriate workflow projects from idea toward production in weeks rather than traditional long development cycles.

That does not mean every enterprise project can or should be completed in a fixed number of weeks.

Security reviews, integrations, data availability, procurement, process complexity and organizational approvals all affect delivery time.

The important principle is different:

Start with a clearly defined operational problem, reduce unnecessary development overhead, produce something useful early, learn from real users, and improve from there.

A transformation program becomes easier to manage when value is delivered incrementally rather than postponed until the end of a multi-year project.

How a project should begin

A sensible enterprise automation project should begin with discovery rather than software configuration.

The first conversation should establish the current process: who is involved, what systems are used, where delays occur, what information moves between teams, which decisions require human judgment, and what a successful outcome would actually look like.

From there, the organization can identify a workflow that is important enough to matter but contained enough to implement and evaluate.

The initial path will generally be:

Understand the process → identify friction → map systems and stakeholders → define the target workflow → validate feasibility → build and test → measure → expand where justified

This prevents automation from simply making a badly designed process run faster.

When a conversation is worth having

A conversation about enterprise automation is worth having when employees repeatedly move information between systems manually; approvals are difficult to track; important processes depend on email, telephone or spreadsheets; suppliers or subcontractors need to participate in internal processes; management lacks visibility into workflow status; legacy and modern systems need to coexist; or AI experiments need a safer route into actual operations.

The starting point does not have to be a technology specification.

It can simply be:

“This process takes too much effort and we know there must be a better way.”

What the partnership means for Axton

For Axton, this partnership significantly expands the scale of digital problems we can help Japanese organizations address.

Our existing work across IT, engineering and business operations gives us exposure to the environments in which digital systems must actually function. Through Fluyenta, we can now bring a deeper enterprise automation and orchestration capability into those conversations.

That is particularly relevant to areas where Axton already has strong business context, including construction and infrastructure, while also creating opportunities across manufacturing, supply chains, agriculture and sustainability, healthcare, and public-sector operations.

We do not believe every organization needs the same platform or the same automation roadmap.

We do believe many organizations have valuable processes trapped between disconnected systems, manual communication and institutional knowledge.

Finding those processes—and improving them pragmatically—is where we intend to begin.

Start with one process

If your organization is considering workflow automation, system integration, an external supplier or customer portal, or governed use of AI, you do not need to begin by planning an enterprise-wide replacement project.

Begin with one process.

Map what happens today.

Identify where people are waiting, copying information, chasing approvals or compensating for systems that do not communicate.

That conversation usually reveals where automation can create genuine value—and where it cannot.

Axton Group LTD Japan is now available to discuss these operational challenges with organizations in Japan and explore where the Axton × Fluyenta partnership can provide a practical path forward.

Frequently Asked Questions