How I work
My work starts with figuring out what a product should be and where its value lies. That means understanding what is possible, what is likely to become difficult, and what today's decisions will mean further down the road.
At We Build Products, that responsibility carries through to the architecture, the team and the business around the product.
Think ahead. Build in stages.
Early choices shape what a product can become: who it serves, what it costs to operate and how readily it can change. Product and architecture need to be considered together, with an understanding of where the constraints will appear.
Demand needs testing before the scope grows. Establish where the value is, test the assumptions behind it and let what customers actually need guide the next investment. Building everything at once commits time and money before there is enough evidence to make those decisions well.
Better tools for financial services
People in financial services spend too much time working around their software. The ambition behind WBP is to make the hard parts easier: tools that people can use without a struggle, supported by dependable systems working behind the scenes.
That includes removing repeated work and unnecessary handoffs, so people have more time for decisions that need their judgement. Experience with financial institutions, regulation, security and audit informs how those systems are built and operated.
Building the business around the product
The same questions shape WBP itself: where the value is, how to reach customers, which capabilities the team needs and where to put our time and money. Product direction, hiring, culture and commercial decisions are all part of the work.
I've lived in Berlin since 2017. My focus now is growing WBP and building tools that make financial services easier to work in.
Get in touch
For a conversation about building a product or backing WBP: