Step 1
Name one decision
We agree the sponsor, the operating team and what better would look like.
Forward deployed teamForward deployedGovernance reviewGovernanceCost reviewCost
Two Quant8 engineers sit with your operators and ship an application they use every day. Two independent reviews answer for the Palantir Foundry platform you already run. Most of our engineers came from Palantir, and Quant8 is independent of it.
Where you are
Find the one you are in. Each leads to what you hold at the end.
Forward deployed team
Two engineers sit with the people who make it and build an application for it on your own data.
How the team works
Forward deployed team
The team starts from the decision that date rests on. The sponsor holds a decision note first.
See whether a team fits
Governance and security review
One signed result, with the evidence behind every score.
What the review covers
Governance and security review
An independent account of what you take on: every control scored, every gap owned and dated.
Ten questions to ask first
Governance and security review
The review tests what each agent can read, and whether it can act without a person approving it.
The eight domains
Cost review
A cost map that matches what you pay. Then one change at a time, each saving measured.
How a saving is proven
Forward deployed team
Start here when a decision that matters still runs on a spreadsheet.
Forward deployed means our engineers work inside your operating team, beside the people who make the decision. Two of them find the decision that costs the most, build an application for it on your own data, and stay until it is in daily use and handed over.
The problem, the evidence and the proposal. The sponsor decides before anything is built.
Built on your own data, on the platform you already run.
A larger team can run and extend the work. Nothing stays in one head.
Instead ofStaff augmentationA strategy studyA platform sale
Governance and security review
Start here before an audit, a renewal or the first automation that acts by itself.
An independent review against 32 controls in 8 domains. One result that you can show a board, an auditor or a regulator.
A score for each of the 32 controls, with the evidence behind it.
Each one has an owner and a date.
A second test, after its due date, shows the gap is closed.
Instead ofA self-assessmentAssurances by emailAnswers nobody signed
Cost review
Start here when the cost of Foundry is rising, or a renewal has a date.
We find the settings that spend compute for nothing, change them one at a time, and count a saving only after we measure it.
By kind of usage and by resource.
Through your own change control, each with a rollback written first.
A saving counts only when it is measured, with every service level held.
Instead ofForecast savingsCuts with no rollbackEstimates nobody measured
How you start
A team starts from a decision that matters to an operator, never from a role and a rate.
Step 1
We agree the sponsor, the operating team and what better would look like.
Step 2
The engineers work beside your operators and read the data behind the decision. You get a decision note.
Step 3
A first version reaches the operators early, on real data. Then it goes into daily use.
Step 4
We write down how it runs, and size the next use cases with the sponsor.
The standard
Four areas, on every engagement, written the way you would check them.
If scope, dates or quality move, you hear it from us first, and early.
All 19
We can tell you how many people use each tool, for what, and whether the number is rising.
All 19
We know each day that the pipelines ran and the data is fresh. Nothing fails in silence.
All 19
Our knowledge is on paper. A new engineer could take over tomorrow.
All 19
On the way
The waiting list is open.
Questions people ask
It depends on the scope, so we set the price after the briefing. You see the scope and the price in writing before any work starts.
The dates are part of the written scope. We set them once we have seen the decision or the platform.
Yes. A forward deployed team works on the platform you already run. The two reviews are for organizations that run Palantir Foundry.
Named Quant8 engineers lead it. They work beside your own people, and what they learn is written down as they go.
It stays where it is. We work inside your security, your change control and your data handling.
No. Most of our engineers came from Palantir, and Quant8 is independent of it. The first is why we know the platform. The second is why you can rely on what we find. We sign a certificate only for a platform that we did not build and do not run.
Yes. AIP is the set of AI tools that Palantir adds to Foundry. A forward deployed team builds with it where the decision calls for it. When AIP runs in production, the governance and security review tests what each agent can read, and whether it can act without a person approving it.
Yes. Your consultancy holds the contract and the relationship, and named Quant8 engineers lead the work.
James replies to you himself and you agree a time. On the call we ask five questions and say which of the three fits, or that none does. Then you get a scope in writing.
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.