Data engineering
Architecture, pipelines, hiring.
← All services
Vertical · Data & product leadership support
Beyond the geospatial: leading the data and the product.
20 years at the crossing of data, product and management. For organisations that need to frame their data or their product before committing, whether the subject is geospatial or not.
0 → 7
size of the multidisciplinary team led
4 disciplines
data, UX/UI, back end, front end, managed directly
Board
direct line to founders and investors
Strand 1
Leading the data, deciding the product
Founding data hire: stack architecture, technical decisions, a direct line to the board. But also, and above all, leading a multidisciplinary team : beyond data engineers and analysts, I recruited, managed and grew UX/UI designers and back-end and front-end developers, from the first hire to a team of 7.
UX/UI
Managing designers, product consistency.
Back-end development
Technical decisions, architecture review.
Front-end development
Prioritisation, quality, delivery.
Strand 2
Product Ownership
Is your SaaS platform, your data product or your WebGIS short of a product vision? Framing the screens with business users, writing epics and user stories, arbitrating the backlog: I carry the product vision of a tool as much as the data that feeds it, with the technical and business reading that 20 years at this crossing gives you.
Product ownership: holding the roadmap and the calls
Over the past five years, most of my work has not been producing analysis but deciding what to build, in what order, and making it hold over time. I am the link between users, technical teams and management: I frame the need, I write the specifications, I arbitrate the backlog, and I measure what was actually delivered.
Framing and discovery
User interviews, a map of how the tool is really used, sorting what is asked for from what is needed.
Roadmap and arbitration
Cut into deliverable increments, explicit prioritisation, decisions owned and documented rather than endured.
Specifications and work with the technical teams
User stories, acceptance criteria, testing, and turning the business need into something that can be built.
Measuring what ships
Instrumentation planned from the design stage, adoption indicators, an explicit decision to carry on or to stop.
Data treated as a product
Interface contracts, quality, documentation, identified users: a dataset has customers, just as a feature does.
Ways of working together
- Product framing before a project starts
- Data function audit and roadmap
- One-off support on an architecture or backlog decision
Where I have held this role
A B2B SaaS scale-up in retail
Product owner for the product: framing with business users, backlog prioritisation, specifications and acceptance criteria, user testing, then measuring real usage once in production. This is where I spent most of my time in this role.
A second product, still in development
Same role, on a product still being built and not public at this stage. I am glad to talk it through in person, within what I am free to say.
Two local authorities · working WebGIS
On both projects I held the role without the title: framing the interfaces, arbitrating features, back and forth with the staff who use them, through to going live.
Product analytics pipeline
A Modern Data Stack architecture: ingestion, warehouse, versioned transformation, exposure.
A product analytics pipeline built on an engagement · architecture illustration
This diagram illustrates a standard architecture. It does not reproduce any particular client’s set-up.
Engagement formats
Two formats from the catalogue
From €4,000 excl. VAT
Product framing for a SaaS or data platform
A testable PRD, scope arbitrated in batches, a revenue model and the free / paid boundary, a test protocol with decision thresholds, a prioritised backlog.
The method was applied in 2026 to the full framing of a SaaS platform, from PRD to a prototype tested on real data.
From €3,200 excl. VAT
Ordered directly, with no prior advertising or tender.
Data function audit and roadmap
A picture of the data, the tools and the real usage, a reasoned target architecture, a hiring or outsourcing plan, a three-page note that works in a committee.
See also
The other GeoQriosity verticals
A data or product leadership gap to fill?
30 minutes to understand your context and see whether one-off or recurring support is the right format.