Quant8
Book a briefing

Forward deployed teamForward deployedGovernance reviewGovernanceCost reviewCost

A working application on your own data.

Forward deployed means two Quant8 engineers join one of your operating teams. They find the decision that costs the most and build an application for it. The people who asked for it use it.

Book a briefing See how it runs

What you get

A decision note first. Then software in use.

Every week you also get a status note with the same five measures, each marked green, amber or red.

Instead ofA role and a rateTickets closedA requirement through four pairs of hands

How it runs

From one decision to software in use.

Most delivery separates the people who understand the problem from the people who build the answer. Here they are the same people. Each stage ends in something you can read or use.

Frame

Agree the decision

We agree the sponsor, the operating team, the decision in question and what better would look like.

Sit with the work

A decision note

The engineers work beside the operators. They watch the decision being made, read the data behind it, and find the rules that no requirements document holds. The note asks the sponsor to decide.

Build

A working first version

It reaches the operators early, on real data. They use it and say what to change. We say plainly which is an early version and which is ready for daily use.

Put it into use

An application in daily use

We count who uses it and record what it changed.

Hand over and widen

A handover file

We write down how it works and how to run it. With the sponsor, we size the next use cases.

Stay or step back

A team plan

The Quant8 lead stays while a larger team builds out, or your own team takes it on.

Does it fit

Five signs that a team fits.

Tick each one that is true where you work.

0Signs present, of five

  1. Fewer than threeStart with the briefing. We say plainly when a team is not the answer.
  2. Three or moreA forward deployed team fits. Name the decision and we start there.

Send these answers with a briefing request

Where it fits

Who it is for, and what it needs.

Who it is for

The head of an operating function who owns a decision. In a utility, that is vegetation, outage response, asset investment, new connections or customer operations. Also the CIO or chief data officer.

What it needs

A named sponsor who owns the decision. Time with the operators each week. Access to the data, under your own security rules.

Which platform

The one you run. On Palantir Foundry we bring the depth: most of our engineers came from Palantir. On Databricks, Azure, AWS or Google Cloud we work beside your platform engineers.

What it leaves

The application and its documents, on your platform and under your accounts. The next use cases, each one sized, and a build that a larger team can take on.

Where it does not fit

Nobody owns the decision.

You want a fixed specification delivered.

The engineers may not talk to the operators.

Nobody is allowed to read the data.

What it is not

Not staff augmentation. We do not take a seat and wait for tickets.

Not a strategy study. The result is software in use.

Not a platform sale. We build on what you run.

How we keep it safe

Four rules on every engagement.

One sponsor, one decision

We do not start without both.

Honest status

Every weekly note says where the work stands, in the same words each time.

Your rules

We work inside your security, your change control and your data handling.

Nothing in one head

What we learn is written down as we go.

Questions people ask

Six answers about the team.

What does forward deployed mean?

Our engineers work inside your operating team, beside the people who make the decision, until the application is in daily use and handed over. Nobody writes a specification for somebody else to build.

Do the engineers work on site?

When the work calls for it. Forward deployed means close to the operation and the people who run it, in the room or on a call. The engineers work with your operators every week, and the written scope says where.

Is this staff augmentation?

No. We start from a decision, not from a role and a rate. You get a decision note first, then an application in use.

We do not run Foundry. Does it still work?

Yes. The team works on the platform you already run, beside your platform engineers.

How do we know it is working?

Every week you get a status note with the same five measures. We count who uses the application, and record what it changed. The plain test: if it were switched off tomorrow, would your operators notice before lunch?

What happens when the team leaves?

The Quant8 lead stays while a larger team builds out, or your own team takes it on. The handover file says how it works and how to run it.

Name one decision.

Tell us the decision you must defend this year, or the Foundry platform you want an answer on. We start there.

Book a briefing James replies to you himself.

Book a briefing

Name the decision or the platform you have in mind. James replies to you himself.