eZbreZ

Your money, made easy — with a little help from Bree.

Inspiration

For a lot of young women, the first paycheck shows up long before anyone explains what to do with it. You're a first-year student or a brand-new grad juggling money, career decisions, and independence all at once and often you're the first person in your family navigating it this way, with no roadmap to inherit. As first-generation earners and digital natives, we're expected to figure out finances on our own, right at the moment the stakes get real.

The problem isn't a lack of tools. It's that the existing ones assume you already speak the language. Spreadsheets assume discipline you were never taught. Banking apps show you what happened after it already happened. Budgeting software is built for people who already budget. None of them feel like they're on your side, and none of them meet a nervous 19-year-old at step zero.

We kept coming back to one question: what if managing your money felt less like a test you were quietly failing, and more like a conversation with someone who actually had your back? That question became Bree, and Bree became eZbreZ.

What it does

eZbreZ is a budgeting and financial-confidence tool built for early-career women making their first "money moves." It does three things, and it does them in plain language:

Visualizes your monthly budget so you can actually see where your money goes instead of guessing at it.
Offers financial planning assistance through Bree, a built-in assistant who talks through your situation like a knowledgeable friend rather than a banker.
Rates and tracks your financial decisions over time, so progress is visible and every choice has context.

Using it is as easy as 1-2-Bree:

Input your month's income and expenses.
Review your visualized budget.
Tell Bree what's on your mind - a big purchase, a tempting credit card offer, a "can I actually afford this?" gut check and get a grounded, judgment-free answer that's tied to your real numbers.

We designed it deliberately for the women who usually get left out of financial tools: those who fall for unexpected money traps and credit obligations before anyone thinks to warn them, and those who know they should budget but have no idea where to start. eZbreZ is built to meet both groups at the very beginning of the journey and make that first step feel doable.

How we built it

eZbreZ runs on a full-stack, polyglot architecture. We intentionally split the app across a Java backend, a Python intelligence layer, and a React frontend so each language could handle what it's best at, rather than forcing everything through one framework.

React (frontend) - The entire user-facing experience: the income/expense input forms, the visualized budget dashboard with its breakdown charts, and the Bree chat interface. We built the 1-2-Bree flow as a guided, low-friction path so a first-time user never hits a blank screen, and used component state to keep the budget view and the conversation with Bree in sync as numbers change. The UI leans into an approachable, encouraging design language on purpose, the opposite of an intimidating banking dashboard.

Java Spring Boot (backend / REST API) - The core of the system. Spring Boot exposes the REST endpoints the frontend talks to, and handles routing, the authentication handshake, budget math, expense categorization, and orchestration between the React client, the Supabase database, and the Python service. We structured it in the standard Spring layers - REST controllers, a service layer for business logic, and DTOs for clean data transfer - so budget calculations and decision-tracking logic live in one predictable, testable place.

Python (Bree's intelligence layer) - Bree lives here. A dedicated Python service takes the user's actual budget context plus whatever they've asked, structures a grounded prompt around their real income, expenses, and history, and calls a large language model to generate plain-English, context-aware guidance. Keeping Bree in Python let us handle the data shaping, prompt construction, and financial heuristics independently of the main API, and made it easy to iterate on how Bree "thinks" without touching the rest of the app.

Supabase (database + authentication) - Our Postgres backbone. Supabase stores users, income and expense entries, budget snapshots, and the decision history that powers the rate-and-track feature. We used Supabase Auth to manage accounts and lean on row-level security so a user only ever touches their own financial data - a non-negotiable when the whole product is built on trust.

Figma (design) — We designed the full product in Figma before writing a line of production code: the green, warm, approachable brand, Bree's persona and voice, and every screen in the 1-2-Bree flow. Prototyping the flows first let us pressure-test the experience for a nervous first-time user, and gave us a component library that mapped cleanly onto our React build.

Challenges we ran into

The biggest challenge was integration across a genuinely polyglot stack. Getting a Java Spring Boot backend, a Python service, and a React frontend to talk to each other cleanly — consistent data contracts, matching request/response shapes, sane error handling across language boundaries — took real work. A field that looked fine in Python didn't always deserialize the way Spring expected, and tracking those mismatches down ate more time than the individual features did.

Designing Bree was its own challenge. We wanted her to feel warm, specific, and genuinely helpful, but we also had to keep her grounded in the user's actual numbers instead of drifting into generic advice, and careful not to overstate herself as a licensed financial advisor. Getting the prompt to consistently reference real budget context — and to stay encouraging rather than preachy — took a lot of iteration.

Wiring Supabase auth and row-level security together with a Spring Boot backend also took some untangling, since we had two systems that both wanted opinions about identity and permissions. And as a small team on a deadline, the hardest ongoing decision was scope: constantly choosing which pieces of the vision to ship well now versus save for later.

Accomplishments that we're proud of

The thing we're proudest of is that Bree actually works. You enter your real income and expenses, ask her a real question, and she answers in plain language that's tied to your budget — not a canned tip pulled off the internet. Watching that loop close, from input to visualization to a grounded conversation, is the moment eZbreZ stops being a demo and starts feeling like a companion.

We're also proud that we pulled off a full, integrated stack across three languages as a team that was learning much of it along the way. Java, Python, and React all doing their real jobs, backed by a live Supabase database with proper auth, is a lot of moving parts to land.

And we're proud of the tone. eZbreZ doesn't lecture. The whole experience - the design, the copy, Bree's voice - is built to make a first-time earner feel capable instead of ashamed, and getting that feeling right mattered as much to us as any feature.

What we learned

We learned how much work lives between the pieces of a system. The hardest part of a full-stack build wasn't any single component - it was the seams: the API contracts, the auth handoffs, the data shaping between Python and Java. That integration layer is where the real engineering happened.

We learned that a language model is only as good as the context you give it. Bree got dramatically better the moment we started feeding her structured, grounded budget data instead of open-ended questions - the same lesson keeps showing up: good inputs beat clever prompts.

And we learned how much financial UX is really emotional UX. For an audience that's anxious about money, every design decision - a color, a piece of copy, whether a number feels like a judgment or a nudge - changes whether someone trusts the tool enough to keep using it.

What's next for eZbreZ

Going mobile with a community forum. We want eZbreZ to live in your pocket and add a forum feature, so the women using it can share knowledge and support each other — turning private budgeting into a community.
Linking to bank statements. Connecting monthly income and expenses directly to real bank statements, so the budget updates itself instead of relying on manual entry.
Bree fact verification. A verification layer so Bree's guidance is checked against reliable sources before it reaches the user - trust is everything in personal finance.
Two-factor authentication. Hardening account security as we move toward handling real, linked financial data.

Longer term, eZbreZ is meant to be an interactive, personable alternative to the cold, one-size-fits-all financial tools that exist today - one that grows with a young woman as her income, goals, and confidence grow.