Hi, I’m Philippe.
I live in Gent, and I’ve always been the person who takes things apart to see how they work.
[How you got into the web: the first site you built, the moment it clicked, what kept you there.]
[What you’re like outside of work: what you do when you’re not at a screen, what you’re curious about right now.]
[What you care about in the people you work with, in one or two sentences.]
What I do
I build websites, and AI systems that take the repetitive parts off the job, mine first.
I spent [X years] as a Webflow developer, building sites for [agencies, startups, brands]. It taught me what clients actually need: things that work, that their team can maintain, and that don’t come with a manual.
I still build websites. Now I also build AI systems that help people in their work, with the same rule as before: if the people it’s for can’t use it, it doesn’t count.
Path
- [Year] — NowWebsites & AI systemsWebsites, plus AI systems that help people in their work: assistants, automations, internal tools.
- [Year] — [Year]TransitionPython, ML fundamentals, LLM APIs. First AI features shipped inside client Webflow projects.
- [Year] — [Year]Webflow developerMarketing sites, CMS architecture, interactions and integrations for [clients].
Stack
These are the tools I reach for most, not a limit. With AI in the loop, picking up a new stack is a matter of days, so I happily work with whatever your team already runs. The stack is never the goal: how the result performs is.
Languages
- Python
- TypeScript
- SQL
AI
- LLM APIs
- Retrieval / vector search
- Agents & tool use
- Evaluation
Product
- Next.js
- Webflow
- Three.js / WebGL
Infra
- [Cloud provider]
- Docker
- Postgres
To end
Websites or AI, the job is the same in the end: understand how people work, then build something that makes their day a little easier.
I like problems that aren’t fully defined yet, and clients who want to think them through together. If you’re not sure what you need, that’s a fine place to start a conversation.
Let’s talk about
your project.