This is why I'm building Lunch Flow.

Problem

After relocating to the UK, I faced the challenge of managing spending across multiple currencies. As a staff engineer in fintech, I was familiar with financial tools but couldn't find one that elegantly solved multi-currency management. I discovered Lunch Money, which helped, but its automated bank sync was limited to US & Canada through a single provider. Living in the UK, I saw an opportunity to enhance the experience through European open banking technology.

Solution

I created Lunch Flow to bridge this gap - not just for myself, but for the entire Lunch Money community. By leveraging open banking APIs, Lunch Flow automates transaction imports and reconciliation for users outside North America, eliminating manual data entry and reducing financial admin time. The goal is simple: give people back their time while providing clearer insights into their finances across currencies, regardless of where they live.

Community-Driven

The adoption and feedback from the community have been incredibly motivating. Each suggestion and feature request shapes the product's evolution. You can see this commitment in action through our public feedback board where user ideas directly influence our roadmap, and our changelog which documents improvements based on community input.

I've also recently launched a Discord server as another channel for users to connect and share ideas. It's early days, but I'm excited to grow this space together with the community.

I'm expanding beyond the initial use case to serve a larger audience through Google Sheets integration and extending coverage beyond the EU. This journey is collaborative - I'm only a message away if you have ideas or feedback.