Ontology design and data integration
The object model that makes Foundry useful: your deals, policies, claims, counterparties and the pipelines that keep them current. Built with the people who own the data, not just the people who own the platform.
Palantir builds, sized to fit.
You don't need a forty-person programme to get Foundry and AIP working. Senior Treefrog engineers lead focused, fixed-scope builds you can see working in weeks — and we have worked out how to make building on AIP dramatically faster than the out-of-the-box experience.
What we build on Palantir.
Workshop applications and operational dashboards
Front-line tools in Workshop that your underwriters, claims handlers and finance team actually open every morning, shaped by a Living Requirements Document before they are built.
AIP agents and LLM-powered workflows
Agents that summarise submissions, triage claims, draft responses and route work, with the guardrails, evaluation and human review that make them trustworthy in a regulated business.
Extension of existing estates
Already on Foundry and not getting the value? We look at what is there, find what is not working, and extend it with focused builds rather than starting again.
How a Foundry build takes shape
From three systems to one ontology, and the apps on top.
Foundry earns its keep when the ontology matches how the business actually thinks: policies, claims, counterparties and brokers as objects, linked the way your underwriters link them in their heads. Get that right and a Workshop app or an AIP agent grounded in it becomes a matter of weeks.
The last frame is the part nobody else shows you: the same five changes to a Workshop app, made two ways. Anyone who has waited on AIP's own tooling will recognise the left-hand side.
Before the ontologyThree systems, three truths
policies_export.csvPolicy admin · nightlyPOL_NO, INSD_NM, BRK_CD, INCEPT, EXP, PREM_GWPINSD_NM spelled 4 ways
claimsSQL Server · liveClaimId, PolicyRef, Insured, Loss_Date, Reserve, PaidPolicyRef ≠ POL_NO format
Counterparties.xlsxFinance · monthlyName, Rating, Rating Date, Limit, ExposureRatings 6 weeks stale
Questions the business asks every week
Which counterparties have open claims over $1m?3 days, 2 spreadsheets
Has any rating moved on an insured with a live claim?Nobody knows
What is our exposure through Harbour MGA, all lines?Ask finance
The same five changes to the Workshop appSame afternoon · same engineer
Standard AIP tooling00:47:12
Add counterparty filter✓Rating-change badge…Export to Excel…Claims drill-down…Mobile layout…
● Still generating change 2 of 5…Treefrog way of working00:11:40
Add counterparty filter✓Rating-change badge✓Export to Excel✓Claims drill-down✓Mobile layout✓
● Five changes shipped. Engineer in control throughout.The 30-second version
Why a small senior team ships Palantir work faster
Our animated short announcing the Palantir practice. Thirty seconds, no slides.
Why a small senior team wins on Palantir.
We make AIP fly
Anyone who has built on AIP knows the wait: a simple change can take the platform's own AI tooling the better part of an hour. We have developed a way of working that turns those changes around in minutes, with the engineer still in control. It is the single biggest reason our Palantir builds land in weeks. Ask us about it on a call.
Weeks, not quarters
A fixed-scope first build is typically live in six to twelve weeks. Large programmes are still staffing the proposal.
Two kinds of senior on every build
Our Palantir practice launched in 2026. Every engineer on it has at least ten years of software development behind them, and they have been shipping Foundry and AIP work since the practice began. Alongside them is our founder, with 27 years building pricing, portfolio and claims systems for the (re)insurance market, who oversees the design so the ontology reflects how the business really works.
Domain first
Twenty-plus years in (re)insurance, ILS and funds. The ontology we build reflects how underwriters actually think, because we already speak the language.
Your tenancy, your ownership
We build in your Foundry instance, document everything and hand over. Nothing is held hostage.
Independent and honest about fit
We are not a Palantir partner or reseller, so we have no reason to recommend the platform when it is the wrong tool. If it is, we'll say so and build on your stack or ours instead.
How a Palantir engagement runs
The same four stages, on Foundry.
- 01WorkshopA remote workshop with your team to design the system they actually want on Foundry, and map the data it depends on.
- 02Prove itA thin, end-to-end slice: real data in the ontology, one Workshop app or AIP agent your users can click.
- 03BuildFixed scope, weekly demos, built in your tenancy by the engineer who scoped it.
- 04Hand overDocumented, tested, owned by you, with FlexTech support available if you want it.
Questions we get asked
Do we need to be a Palantir customer already?
To build in Foundry you need a Foundry tenancy. If you have one, we build in it. If you are evaluating Palantir, we will tell you honestly whether it fits the problem before you commit.
Is Treefrog a Palantir partner?
No. We are an independent consultancy, not affiliated with or endorsed by Palantir, and not a reseller. We build on the platform in your tenancy and give you a straight answer about it.
How long does a first Foundry or AIP build take?
A fixed-scope first build — an ontology slice plus one Workshop application or AIP agent — is typically live in six to twelve weeks, with weekly demos throughout.
How experienced is your Palantir team?
Our Palantir practice launched in 2026. Every engineer on it has at least ten years of software development behind them, with design oversight from our founder, who has 27 years in (re)insurance systems. That gives every engagement engineering depth and domain depth, plus a way of working that makes AIP builds dramatically faster than the standard tooling.
How do you make AIP builds faster?
Anyone who has built on AIP knows a simple change can take the platform's own AI tooling the better part of an hour. We have developed a way of working that turns the same changes around in minutes with the engineer in control. We explain it on a call rather than on a web page.
Can you work with an existing Foundry estate that is underused?
Yes. We look at what is there, find what is not working, and extend it with focused builds rather than starting again.
Have a Palantir build in mind?
Thirty minutes with the team behind our Palantir work. You'll leave with a scoped first build and a straight answer on whether Foundry is the right tool for it.
Palantir, Foundry and AIP are trademarks of Palantir Technologies Inc. Treefrog Consulting is an independent consultancy and is not affiliated with, endorsed by or a partner of Palantir.