Work / WeddingDock
WeddingDock
- Client
- Own company
- Year
- 2026
- Role
- Development, automation and finance
- Question
- Planning a wedding is a project with dozens of loose threads, and there was no tool that helped the way I needed it to.
- Approach
- Built a tool for my own wedding and kept developing it throughout the year leading up to it, with the wedding itself as the test.
- Result
- A running business, set up from day one as an AI-first organisation.
The situation
WeddingDock started as a tool for my own wedding. No market research, no proposition on a napkin — just a problem I had myself, in a year in which I ran into it every day.
That’s a luxury you rarely have: a whole year with one user who knows exactly what isn’t right, and a hard deadline by which it had to work. Everything that wasn’t right, I noticed myself.
What I did
I build the tool and the automations, and I handle the finances.
It’s an AI-first organisation: set up with AI tooling as the starting point rather than as an afterthought. That’s also why it works with a very small team.
What came of it
A running business, out of a problem I had myself.
But the real return is what it teaches me, and I use that in my work for others: how to get from a problem to a solution very quickly with AI tooling, then make that solution scalable, and turn it straight into a business. Not as theory — here I have complete freedom to just do it, and I also see what goes wrong when you do.
That’s the difference between advising on working AI-first and having done it yourself.