Case Study

Kaspit

A personal finance PWA (Hebrew for "little cash box") built to make tracking savings and recurring spend feel like maintenance, not a monthly chore.

Visit Live Site Back to Projects
Status
Live · Actively Evolving
Role
Solo Builder — Product, Full-Stack, Backend Schema
Stack
Installable PWA · Supabase · Vercel
The Problem

Budgeting apps get abandoned within weeks

Most personal-finance tools demand a lot of upfront setup — categorize every transaction by hand, tag every expense — and the habit rarely survives past the first few weeks. The friction of maintaining the tool ends up bigger than the friction of the problem it was meant to solve.

The Goal

A straight answer to "where did my money go"

Build a lightweight, installable money tool that gets out of the way — clean tracking with no spreadsheet energy — while making sure the underlying data model could support recurring bills and savings goals from day one, not as a bolted-on feature later.

Architecture

An installable PWA on a proven backend

Kaspit ships as a Progressive Web App — a real manifest.json and service worker — deployed on Vercel, so it installs and feels native without an app-store build. The backend reuses the same Supabase + Vercel pattern already proven in Profity, rather than re-deciding the stack from scratch.

The Postgres schema has dedicated migrations for recurring transactions and categories and monthly savings contributions — the recurring-bill tracking and savings-goal logic runs off real schema, not a mockup screen.

Installable PWA Supabase (Postgres) Vercel Service Worker
What I Built

Data model first, so features aren't a rewrite later

Reusing Profity's backend pattern meant most of the early build time went straight into the savings and recurring-transaction data model, instead of re-litigating infrastructure choices — the schema for recurring bills and savings contributions was designed to support real engagement features (streaks, goals) before those features existed.

Challenges

The data is ready; the habit loop isn't — yet

Kaspit already has what it needs to support the kind of streaks and missions that make Profity sticky — recurring transactions, savings contributions — but doesn't have that engagement loop built on top yet. It's the single most concrete, identified next step: porting Profity's gamification mechanics (missions, streaks, a leaderboard) into Kaspit's savings goals, rather than designing an engagement system from scratch.

Result

Live, with real infrastructure ahead of most MVPs

Kaspit is live at kaspit-yuval.vercel.app with a real backend and schema — further along than a typical side-project prototype at this stage. The next milestone is exactly the gamification transplant from Profity described above.