What is a Climate Pipeline Discovery and how is it different from a regular consulting call?

A Climate Pipeline Discovery is a fixed 2-week paid engagement (€5-7k). I audit your existing climate scoring pipeline, map risks and duplication, and deliver a 10-15 page technical note with a scoped remediation plan. It’s the entry point for clients who want to commit budget seriously and avoid a fuzzy consulting call.

Do you write original climate models from scratch?

No. I work with the climate scientists already on your team. I challenge their model choices through comparative studies and I industrialize the models they ship, turning prototypes into reliable, modular production pipelines.

Is there a guarantee on the code you deliver?

Yes, the Code Quality Guarantee. Any major bug in production on code I shipped, within 30 days of handover, I fix for free. No questions. Major bug = any malfunction preventing the pipeline from producing expected outputs, or producing reproducibly incorrect outputs.

Available · 2-3 new engagements per quarter

Ship your next climate peril in 8 to 16 weeks, without recruiting in-house.

I’m the senior data engineer parametric insurers call when their climate scoring pipelines need to bridge climate science and DevOps, without recruiting a €120k/year hire.

Ex-Raincoat · 10+ countries · 15+ years satellite & reanalysis · PhD

Book a Discovery Call

Trusted by research & industry

10+ countries served at Raincoat
2 years operating production climate pipelines
6 peer-reviewed publications

You’ve shipped one peril. The next three are 9 months out.

Your data scientists prototyped climate models that work. Your DevOps team runs Kubernetes for the product. Nobody in the team bridges the two, and every new peril takes 6 months instead of 6 weeks.

This is what I see in most parametric insurtechs I talk to: climate scoring pipelines built fast, then bolted together. Code duplicated between perils. Datasets that quietly change calibration in the middle of the night. New geographies that look like a new project every time, not a configuration change.

The board refuses a new full-time hire at €120k+/year for what they perceive as a punctual need. But the next three deals depend on shipping that next peril before the next renewal cycle.

I close that gap.

For nearly 2 years at Raincoat, I operated production climate pipelines across 10+ countries spanning LatAm, SEA, and Africa. I maintained drought and precipitation, built water balance from scratch to production, brought heat stress to a ready-to-deploy state, ran dev/ops solo at the end of the contract, and delivered a modular architecture roadmap for next-perils scaling.

Before that: 15+ years in satellite remote sensing at IFREMER. PhD in Marine Ecology. 6 peer-reviewed publications. 2 CRAN R packages.

I’m the senior who can sit between your climate scientists and your DevOps team: challenge model choices with comparative studies, ship production code that won’t wake your team at 3am, build the operational dashboards your team actually uses, and document everything so you can run new perils without me.

Climate Science

15+ years in satellite remote sensing. Production experience with CHIRPS, IMERG, ERA5-Land, Copernicus CDS, and WEkEO.

DevOps

Nearly 2 years operating production climate pipelines at Raincoat. Built water balance from scratch to production. Modular architecture roadmap delivered.

Scientific Dialogue

PhD in Marine Ecology. 6 peer-reviewed papers. 2 CRAN packages. I challenge model choices through comparative studies.

Three ways to work together

Full audit of your existing pipeline, risk mapping, scoped remediation plan.

10-15 page technical note
Risk mapping of duplication, fragility, calibration drift
Datasets & scientific methodology audit
Production readiness assessment
Scoped remediation plan with budget & timeline
2 debrief calls

Book Discovery

Code Quality Guarantee

Any major bug in production on code I shipped, within 30 days of handover: I fix it for free. No questions.

Major bug = any malfunction preventing the pipeline from producing expected outputs, or producing reproducibly incorrect outputs.

What clients say

Steph is a seriously talented engineer with a rare combination of skills. He’s just as comfortable building scientific algorithms and doing deep data analysis as he is shipping polished frontend dashboards — and he does all of it at a high level. What stood out most was how independently he operated: you could hand him a complex project and trust him to run with it, communicate clearly along the way, and deliver something that genuinely moved the needle for the company. I’d recommend him to anyone in a heartbeat.

Jan Paral Head of R&D and Co-Founder Raincoat LLC

His coding skills are unparalleled, producing efficient and well-documented codes. His ability to translate our needs is exemplary, and he excels in proposing innovative solutions that go beyond the initial objectives. Stéphane embodies excellence and will be an invaluable asset to any organization.

Kelig Mahé Head of Unit, Fisheries Resources, Channel & North Sea IFREMER

I worked with Stéphane at the beginning of my PhD, and I am still grateful — without his recommendations I would work and troubleshoot much less efficiently. He always takes time to explain, and never loses his sense of humor even after the nth error message.

Carolin Neven Ph.D. Student IFREMER

Ready to ship that next peril?

Two ways to start:

1. Get the free Reality Check PDF

5 lessons from industrializing pipelines across 10+ countries, plus the 12-point checklist I use on every mission. No call, no pitch, just useful content.

2. Book a Discovery Call

15 min, free, to see if a fixed Discovery mission (€5-7k, 2 weeks) makes sense for your context.

Book a Call