What is a forward-deployed engineer? An engineer who builds inside your company rather than from a distance: on site, with the people who run the work, accountable for the result. It is not a consultant, and not a support desk.

# Engineers on site until it stands on its own.

A named engineer works on your premises with the people who run the process, builds the agent around your systems, measures it against your numbers and stays until your team runs it alone.

[Talk to the team](https://qantara.systems/contact) / [Read the thesis](https://qantara.systems/original/thesis)

The frame comes away, and the arch holds. The dashed frame is our engineers, there from the first week. The stones are what they build with you, set one by one; the orange keystone is the record. When it is set, the frame comes away and the arch stands on its own.

## The four steps: what happens in each, who is there, what is written down, and what you see at the end of it.

| Step | What happens | Who is there | What is written down | What you see at the end |
| --- | --- | --- | --- | --- |
| Embed | The engineer sits with the people who run the process and maps how it really runs | The engineer, and the people who run the work | How the work moves today, and the baseline | The baseline, agreed, and the process to start with |
| Build | The first agent is built around your systems and tried on real cases | The engineer and your team | The connections, the thresholds and the rules | The agent working on real cases |
| Scale | The next process is added on the same record | The engineer, your team and the next process's owner | The next process's map and thresholds | Two processes on one record |
| Measure | The numbers are read against the baseline | The engineer, your leadership and the people who run the work | The numbers against the baseline | What changed, in your own numbers |

Software fails at the last mile. We walk it with you, then hand you the keys.

## How the engineers work, step by step

### 01 Embed: Sit with the people who run the work

A named engineer works on your premises beside the people who run the process, writes down how it really runs, and records the baseline before anything changes.

- What was learned each day, written down for you
- How the work moves across your ERP, email, calls and messaging
- The baseline, agreed with you before anything changes

### 02 Build: Build the first agent on real cases

The engineer builds the agent around your systems and your thresholds, and your team tries it on real cases as it takes shape. Nothing in your systems changes.

- Connections built system by system
- Thresholds set with the people who approve
- Tried by your team on real cases

### 03 Scale: Add the next process on the same record

The second agent starts from what the first agent wrote, so it is built on what the record already knows. Branches and group companies follow, one at a time.

- The next process, chosen with you
- The same record and the same log
- Branches and group companies added one at a time

### 04 Measure: Read the numbers against the baseline

The numbers are read the same way as the baseline from the first week, and reviewed with the people who run the work. The agent is tuned until they move.

- The same numbers as the baseline, read the same way
- Reviewed with the people who run the work

## Who comes, and when we step away

The questions an owner asks before letting anyone in: who it is, for how long, when they leave, and what they are there for.

- **Who comes.** A named engineer for your company, from Muscat, on site for the embed and the build, with the Qantara team accountable alongside.
- **For how long.** For the embed and the build, then as often as the work needs, until your team can run it alone.
- **When we step away.** When your team can set a threshold, read the log and add a case without us. We train them for exactly that.
- **What we are not.** We are not the product. The record is. We are the frame that holds it while it is set.

## In Arabic and English

The engineer's note at the end of a day of the embed, as your team reads it, in both scripts.

The engineer's note, day two: "Orders reach the sales team on WhatsApp and are typed into the ERP by hand. Many need a call back for a missing item code."

## Someone has to be there at the start of the working day

Companies here buy on references and pilots, and a pilot tests how the people behind the software behave when something goes wrong as much as it tests the software. That is learned in the room, at the start of the working day, not from a distance.

## What owners ask about the engineers

**How long are you on site?** For the embed and the build, then as often as the work needs.

**Who is accountable?** One named engineer, and the Qantara team behind them.

**Can our IT team run it?** Yes. That is the condition for us stepping away, and we train them for it.

**Can we build the next agent ourselves?** Your team learns to add cases and set thresholds during the build. A new agent is work we do with you.

## Where the engineers have the most to learn

- [Automotive and heavy equipment](https://qantara.systems/solutions/automotive): Bookings, parts and customers followed up.
- [Distribution and trading](https://qantara.systems/solutions/distribution): Orders confirmed, delivered and collected.
- [Supplier follow-ups](https://qantara.systems/solutions/supplier-follow-ups): Deliveries chased before they are late.

## Someone has to build the bridge

We named the company after it. Tell us where to start.

[Talk to the team](https://qantara.systems/contact) / [Back to the overview](https://qantara.systems/platform)

Muscat and across the Gulf

---

This is the Markdown twin of the page at https://qantara.systems/platform/engineers