SaaS platform · Clubs & communities
Klubfunder
Software that helps clubs and community organisations manage fundraising, membership, payments and the practical work behind keeping a club running.
The engineering
Making complicated services feel straightforward.
Klubfunder is a multi-tenant platform with different needs across clubs and organisations. Some principally use membership, others fundraising, Lotto, shops, ticketing or a combination of services.
My involvement spans software architecture, full-stack engineering and product decisions. That includes backend services, relational data, payments, cloud infrastructure and web experiences.
Lotto and recurring fundraising
The Lotto service combines weekly draws, ticket entry and recurring subscriptions. The engineering goes beyond selecting numbers: entries must respect draw cutoffs, repeat subscriptions must be applied to the correct draw, and payments and ticket records need to remain consistent.
My work in this area spans relational data modelling, SQL procedures, draw and subscription logic and the financial workflows supporting recurring participation. Read more about the Lotto engineering ↗
Football predictions and Matchday6
I've also worked on Matchday6, a distinct football score-prediction product involving competitions, predictions, scoring and leaderboards, together with entry rules and payment-related workflows.
Payment integrations & recurring billing
One substantial part of my engineering work has been connecting payment providers to the platform in a way that makes sense for clubs and members. That includes Stripe Connect and connected accounts, recurring collection with GoCardless, and SumUp integration.
The challenging work sits behind checkout: order and transaction records, provider webhooks, subscription status and cancellation, and tracking what has actually been paid. I've also worked on the design of club settlement workflows, where accurate data and clear payment states are essential.
These integrations call for careful handling of duplicate provider events, mismatches between internal and provider state, and payment failures. I approach them as backend and architecture problems as much as user-experience problems.
Exploring AI agents with MCP
In a separate engineering spike, I exposed selected Klubfunder capabilities through a remote Model Context Protocol endpoint and connected it to ChatGPT. The prototype used OpenIddict for OAuth and scoped permissions, with the existing application remaining responsible for club data and business operations.
Read the MCP architecture and design case study ↗
The approach
There is rarely one perfect abstraction for every club. The challenge is to build shared foundations while keeping experiences flexible and understandable for different users and use cases.
It's an example of the kind of engineering I enjoy: designing useful products while considering performance, security, maintainability, operational cost and the people using the software.
This page describes my contribution and perspective, rather than presenting the platform as a solo project.