Show us how the task works today.
We discuss a typical task, the systems involved and common follow-up questions.
AI for mid-sized freight forwarders
Less routine work.More time for your customers.
We are developing Freyta to automate routine tasks across email, TMS and freight billing — built around your processes.
Typical time sinks
Where routine work slows your team down.
A missing weight, a delivery time that does not fit or a document that has been missing for days: these four friction points show where Freyta could gradually take routine work off your team’s desk.
Four common friction points from day-to-day forwarding work.
Development concept · Sample dataF-1042 · München → Hamburg
The transport order has arrived. Weight and collection time are missing.
Email · Inbox
Inbox2
Transport order Munich–Hamburg
Customer · New message
Please provide a curtain-side trailer tomorrow for 24 pallets. Delivery the following day.
Attachment
Transportauftrag.pdf
Email and attachment are matched to the same case.
01 / 05Read order
The work your team could hand over
Identify missing details, ask targeted questions and match the reply to the order — this is the work Freyta is intended to handle.
Your team handles cases that remain unclear after follow-up.We shape these workflows with development partners around their existing TMS and inbox structures.
Your task is not among the examples?
Customer quotes, order changes and freight invoice checks could also be starting points. What matters is where your team repeatedly has to find, transfer or follow up on information.
How we start working together
Start with a task from your day-to-day work.
Together, we identify where recurring work takes up your team’s time and what support would be useful.
We develop an initial approach.
Using selected examples, we assess results, rules and exceptions — and the work that would remain for your team.
Decide together on a limited test.
If the approach looks useful, we agree the scope, responsibilities and criteria for reviewing the results.
Your team sets the rules.
For future operational use, we agree clear boundaries with the people responsible for the process.
- Business requirements
- Which data sources, requirements and thresholds apply to the workflow.
- Automation and approvals
- Which standard steps may run independently, and when a question, approval or stop is required.
- Clear ownership
- Who owns the process, receives exceptions and decides on changes or pausing automation.
Your TMS and inbox remain part of the workflow.
Freyta is intended to support recurring work across your existing systems. Together, we assess the connections needed and how results feed back into your existing workflow.
The first development partners pay no licence fee. Objectives, scope and any setup or data-preparation effort are agreed transparently in advance.
Your direct contact
Developing Freyta with you.
I am Martin Gardemann. Over the past nine years, I have worked on supply-chain, fulfilment and B2B software, most recently as Head of Product at everstox. At Freyta, you speak directly with me. Together with your team, I want to find out where the software can reduce day-to-day workload.
Previous roles: everstox, Amazon and Westwing
Common questions
Before our first conversation.
What can I view today?
This page shows possible workflows using sample data. Freyta is not yet a product proven in customer operations. Together with freight forwarders, we want to understand which tasks actually create workload and develop suitable support. The interfaces and channels shown illustrate a target workflow, not existing integrations.
Does our TMS need to be connected or replaced?
Your TMS stays in place. Depending on the task, documents or exports may be enough for initial tests. We assess whether and how email, TMS or other systems should be connected for the selected process. An existing integration is not a prerequisite.
Who decides which steps Freyta may execute?
Your company agrees responsibilities, rules and approvals with us. The first test produces results for comparison only; Freyta does not send messages or make bookings. For later use, we agree which standard steps may run independently and when your team needs to be consulted.
What data is needed for a test?
You need no data export or written procedure for the first conversation. For a later test, we select suitable examples together. Before live data is processed, processing terms, providers, access and deletion periods are agreed in writing. You receive the DPA and subprocessor list before data access.
How does working together start, and what does it cost?
The first conversation is free. We discuss a recurring task and assess whether a closer look would be useful. The first development partners pay no licence fee. Development scope and any setup or data-preparation effort are agreed transparently in advance.
Which task takes too much of your team's time?
In our first conversation, we discuss a typical process and assess whether working together would make sense.