Tekst Targets the Work Between Email and SAP

SAP may hold the order, invoice, or procurement record, but the instructions behind that transaction often arrive elsewhere. Customer requests, approvals, and exceptions move through inboxes and other applications before an employee translates them into an SAP action.

Tekst is building a process-intelligence layer for that work between systems. Its platform connects communications, documents, ERP, and CRM activity to map how a process operates, then supplies that context to AI agents that can route requests, validate documents, process orders, and update enterprise applications. Tekst explicitly lists Outlook-to-SAP automation among its use cases.

The Belgian company recently raised €11.5 million ($13.5 million) to expand the platform, its integrations, and its international operations. The investment will support Tekst’s expansion into governed execution across core enterprise processes.

SAP Records the Result, Not the Entire Process

An SAP transaction rarely tells the full story of how work reached that point. A customer may change an order by email, attach revised terms, or request an exception that requires approval before anyone updates the ERP record. Employees must interpret that information, find the right context, and decide what should happen next.

Tekst is designed to reduce that manual coordination. It follows the request across communications and business systems, connecting the information employees use to make a decision with the transaction eventually recorded in SAP. In quote-to-cash, that could mean linking a customer message with the opportunity in CRM, the applicable commercial terms, and the resulting order.

Tekst calls the resulting process model a context graph. Its practical purpose is to help an AI agent understand not only what a request says, but where it belongs in the business process and when an exception or approval requires human attention. The company argues that this operational context can support faster handling without forcing employees to reconstruct the same process across several systems each time.

Tekst Moves From Routing Work to Completing It

Once Tekst has enough process context, its agents can take over portions of the work employees currently coordinate by hand. An incoming request can be matched to the relevant customer or order, checked against the available information, and moved into the appropriate business system. The value lies in shortening the path between a message and the action it requires.

The clearest public evidence comes from high-volume communication workflows. Tekst says Securex receives 2.3 million emails annually and that testing improved routing accuracy from 50% to 90% within weeks. Securex aims to route 85% of messages automatically. Milcobel uses a shared inbox integrated with Outlook and SAP to handle 250,000 emails annually; Tekst reports a 200% improvement in first-response speed.

These deployments show how better interpretation and routing can reduce the delays that occur before work reaches the right employee or application. Tekst is now extending that model further into process execution.

At Becton Dickinson, Tekst says its platform handled 90% of the work autonomously within three weeks on one process, although the company has not disclosed the process or how it measured autonomy. The result suggests Tekst is beginning to move beyond organizing communications and into completing the operational work that follows.

Customer Readiness Will Influence Tekst’s Expansion

Tekst’s expansion will depend on how easily customers can connect its process-intelligence model to the way their own operations are organized.

The new funding will support product development, additional integrations, international growth, and a planned increase in headcount from 35 to 70 employees by the end of 2026. That gives the company more capacity to move beyond communication-heavy workflows and support broader enterprise processes.

Organizations considering Tekst should first identify where employees repeatedly move information between SAP, email, documents, and other applications. Processes with high volumes, clear ownership, and measurable delays offer the clearest place to begin.

Organizations should also define which decisions remain with employees before introducing agent execution. A Tekst deployment will be easier to scope when process owners understand the systems involved, the information required for each decision, and the points where approval is mandatory.

Tekst’s next phase will depend on how effectively it helps customers identify the handoffs around SAP that are ready for automation and turn them into repeatable workflows. As Tekst expands, it has an opportunity to make process intelligence a practical layer for SAP-centered work while keeping ownership and approvals clear.

What This Means for SAPinsiders

• Communication-heavy processes provide the clearest entry point. High-volume inbox work gives organizations a contained environment to improve routing, test process ownership, and identify where judgment remains necessary before agents begin updating core systems.
• Clear decision boundaries make automation easier to scale. Teams should define required information, approval thresholds, and exception ownership before deployment. That clarity helps Tekst connect process context with SAP actions without obscuring accountability.
• Operational value extends beyond routing accuracy. Cycle time, rework, manual intervention, and exception resolution show whether automation removes friction or merely shifts it elsewhere. Those measures provide a stronger basis for deciding what to automate next.