Foyla
For enterprises and mid-market companies

Custom AI automation for the processes that run your business.

We redesign your processes around what AI makes possible. Then we build the systems that run them. Deterministic where results must be stable, AI where judgment is needed. Every build is measured against your KPIs: cost, cycle time, revenue.

Built inside your company, on your data Working software reviewed with you every week Internal processes with no ready-made solution
What we build

Deterministic where it can be. AI where it has to be.

First we redesign the process around what AI now makes possible. Then we build it. AI can play two separate roles in an automated process. We keep them apart:

Level one · AI builds the system

Our engineers use AI to build it. Once complete, the system runs as plain code, with no AI in the loop. The same input gives the same output, every time. The build takes weeks, not quarters.

Level two · AI works inside the system

A language model takes only the steps that need judgment: reading a messy document, weighing an unusual case, writing to a customer. The deterministic core stays in place. The model works within limits you set, and its output can be reviewed before it takes effect.

You choose how far to go. The result is an automation that is cheap to run, stable in production, and worth the investment.

Where we focus

We build for internal processes where no ready-made solution exists. They depend on thousands of data points spread across your systems, and on real-world operations that still run by hand. That is why we do our best work in data-heavy and asset-heavy businesses: fleets, plants, dealerships, industrial groups, portfolios of any kind. Where a specialized vendor is the better option, customer support for example, we will tell you. We support where we add the most value.

What we build · Examples

Three kinds of work, one way of building.

One example per category, drawn from systems we have built. Open any of them for the full story.

01

Run the process

A whole flow, automated end to end.

Example · Pricing automation for rental cars
Level one · AI builds the system

Thousands of data points from five systems, priced every morning. Exceptions go to your team.

Level two · AI works inside the system

A language model watches for what the data does not contain yet.

02

Build the data, then decide

Information locked in documents, turned into a structured decision.

Example · Tender and supplier bid evaluation
Level one · AI builds the system

A structured database built from documents, and the comparison your team already uses.

Level two · AI works inside the system

A language model evaluates each bid and adds what the documents leave out.

03

Equip the team

One team, one assistant built on its documents and systems.

Example · Service technician assistant for an industrial group
Level one · AI builds the system

Manuals, service history, and parts in one searchable tool. Every number from the source system.

Level two · AI works inside the system

The technician asks in plain language and gets the answer with the evidence.

How we work

We build inside your organization, from day one.

A small team embedded in your organization, working in your systems and to your standards, using AI tooling to build several times faster.

Build

Forward-deployed engineers

Engineers work directly in your environment: data foundations, core systems, integrations. Building starts in week one.

Translate

AI deployment strategist

Translates your domain logic into system behavior and results into decisions. The bridge between your team and the build.

Deliver

Delivery lead

One accountable owner for timeline, milestones, and your satisfaction. Weekly review with your team and a direct line at all times.

The Foyla model
Two parties
One embedded team
What you receive
Your sideDomain knowledge and decisionsprocess owners · data access · priorities
FoylaEngineering and AI toolingengineers · strategist · delivery lead
Business and engineering in one team, iterating with AI WEEKLY BUILD · SHIP · MEASURE
Working software, in productionShown every week
Captured valueMeasured in your KPIs

Typical timeline Redesign in week 0. Weekly builds from week 1. Live on your work by week 10. Optionally we stay on for the next process.

Team

Built by operators who have run these processes.

We spent years inside tech startups and large companies, building, running, and automating the processes we now specialize in. We know what it takes for a system to work in daily operations, and what a team needs before it trusts one.

Philipp Goentgen
Philipp GoentgenCo-founder, CEO

Leads client work, scoping, and delivery.

Konstantin Hegestweiler
Konstantin HegestweilerCo-founder, CTO

Leads architecture and engineering.

FAQ

Questions we get in the first call.

Which of our processes are worth automating first?

The ones that repeat daily, pull data from several systems, and end in a decision someone makes by hand: pricing, approvals, allocation, evaluations, reporting. In the mapping phase we walk through your candidates with the people who run them. We rank them by hours saved, error cost, and how much of the data already exists. You see the ranking before you commit to a build.

Our process runs on spreadsheets and five different systems. Where do you start?

With the data, not the interface. First we connect the sources and bring them into one clean, versioned dataset, with every figure linked to where it came from. Then we rebuild the steps on top of that. Most of the value in a process like this is created in the first two weeks, when the data is joined for the first time.

How do you decide what runs as code and what uses AI?

If a step can be written as a rule, it runs as code: same input, same output, at almost no cost per run. If a step needs reading, weighing, or writing, a language model does it within limits you set and with a review step where it matters. We map every step of your process to one of the two before we build, and you see the split.

Part of the process depends on one person's experience. Can that be automated?

Usually more than expected. We sit with that person, turn what can be written down into rules, and give the model the rest with their past decisions as examples. What stays is the genuine judgment, and the system routes exactly those cases to them, with the evidence attached.

How do we know it works before it touches live operations?

It runs in shadow mode first: the system produces its decisions next to your team's, every day, and we compare them together in the weekly review. It goes live only when the match is where you want it. An evaluation suite keeps checking it against known cases after every change.

Our process changes every few months. Will the automation keep up?

Yes, because the rules and limits are configuration your team can see and change, not logic buried in code. Larger changes go through the same weekly cycle as the original build. If we stay on after go-live, adjusting the system as the process evolves is part of the agreement.

What does our team do once the process runs on its own?

They handle the exceptions and the judgment the data cannot show. In the pricing example, buyers approve the routine offers in seconds and spend their time on the unusual cases. The system tells them what changed and why, so the review is fast.

What does an engagement cost, and what do we get?

Each phase is a fixed scope with one deliverable: working software that meets acceptance criteria we agree on up front. The mapping phase is scoped on its own, so you decide on the build with a full plan in hand. You get a deployed system in your environment with monitoring and an audit log. You also get the source code, documentation, and an IP assignment for everything built for you.

Talk to us

Tell us about one process.

The one that costs your team the most time, or the one you think cannot be automated. In a 30-minute call we walk through it with you and lay out the options.

Where the data livesWhich systems and documents the process depends on, and what already exists.
Code or AIWhich steps can run as plain code, and where judgment is needed.
What a redesign could look likeFewer hand-offs, exceptions handled once, and what your team would do instead.

You leave with a clear picture of the options, whether you work with us or not.