Who we are
Vincent Vantrappen
Co-founder
Master Industrial Engineering
Expertise: Data, GxP, Automation
Background: Consulting
Thomas Boogaerts
Co-founder
Master Mathematical Engineering
Expertise: Generative AI, Full-stack & mobile development, Marketing
Background: Co-founder HabitBull
Ward Homan
Co-founder
PhD Astrophysics
Expertise: Numerics & algorithms, Distributed systems, Communication
Background: Academia
Before Feldspar, our team worked on projects at:
Origins and shared insight
Feldspar started because Ward, Vincent, and Thomas kept seeing the same pattern in industrial operations: inbound information arrives scattered across email, EDI, portals, and paper, and teams spend their days rekeying, cross-checking, and chasing exceptions before anything can move forward.
Ward and Vincent's track record
Ward began in academia before moving into data science and data engineering; Vincent came through IT consulting and ended up in the same space. When they crossed paths, they started collaborating almost immediately, switching between hands-on work (building the data flows that keep operations moving) and the bigger context around it (enterprise architecture, data governance, getting teams aligned). As a freelance duo, they repeatedly built custom fixes for the kind of inbound frictions that standard automation doesn't cover.
Thomas's parallel angle
Thomas went through a few startups and later moved into IT consulting with a focus on Generative AI products, where he kept seeing the same gap between what the tools promised and what actually held up in daily operations — especially around the exception handling and deviations that never fit the happy-path demos.
How we came together and committed
The spark to do it together came from an informal chat between the cousins Vincent and Thomas at a family gathering. Soon after, the three of us met for the first time in late 2025, for a few hours in the lobby of the Crowne Plaza in Zaventem, roughly halfway between our homes. By January we had wrapped up our freelance contracts and committed full-time.
What we're building and how we're approaching it
We started with open discussions about where the real pain sits, then decided to focus. Inbound — from capture to verified system entry — is where operational friction compounds fastest and where standard automation tends to stop short. We're building a compact platform that stays quiet and reliable on the happy path, and keeps the flow moving when reality deviates from plan.