Ian Macabulos

Ian Macabulos

Full-Stack Developer

SubVantage

A Clearer View of Recurring Spending

SubVantage is a subscription-management dashboard that turns recurring expenses with different currencies, billing cycles, trials, and shared costs into one comparable financial view. It tracks active commitments, upcoming renewals, cancellation history, and spending patterns so recurring costs are easier to understand before the next charge.

Next.jsTypeScriptPostgreSQLPrismaNextAuth

The problem is not one subscription. It is the total.

One monthly plan is easy to understand. Add annual bills, different currencies, free trials, shared costs, staggered renewal dates, and paused or cancelled plans, and a list of individual prices stops answering the useful question: how much am I actually committed to each month? I built SubVantage around making those unlike costs comparable.

Different billing models need one financial baseline

Normalization starts with what belongs to the user: a positive personal split cost takes precedence over the full bill. That amount is converted to the preferred currency, then yearly plans are spread across 12 months. Only active, non-trial subscriptions contribute to paid monthly burn.

  1. Personal cost

    Read the record’s cost, currency, billing cycle, and trial state. Use the recorded split cost when greater than zero; otherwise use the full cost.

  2. Currency normalization

    Express that amount in the user’s preferred currency.

  3. Billing normalization

    Divide yearly plans by 12 for monthly comparison. Keep trials visible, outside paid monthly burn. Sum the normalized active, paid commitments.

A dollar plan and a peso plan still belong in the same total

Each subscription keeps its original currency. Aggregate values use exchange-rate normalization to express unlike costs in the user’s chosen base currency. External rates are fetched with hourly revalidation, with fallback rates when the request fails.

Preferences are part of the financial model

Onboarding and settings store the preferred currency and email notification preference. Changing currency affects the aggregated dashboard totals. Individual upcoming bills retain their original currency so the charge remains recognizable.

What a common baseline makes visible

Monthly burn

The normalized monthly cost of active, paid subscriptions, using the user’s share where recorded.

Annual projection

Monthly liability multiplied by 12: a simple annualized estimate from the current records.

Upcoming commitments

The next four scheduled bills are ordered by due date. Future start dates and billing cycles determine the next payment, shown in the subscription’s original currency.

Cancelled-cost history

Cancelled plans are summarized as estimated monthly recurring cost no longer active, separate from current spending. This is a comparison of recorded costs, not guaranteed savings.

A cancelled subscription should not disappear from the story

A plan can be paused, cancelled into the archive, or restored when needed. Keeping those choices separate from permanent deletion preserves the record and makes cancellation’s effect on recurring commitments visible.

Pause / resume
Pausing keeps the record while leaving it out of active spending.
Cancel / archive / restore
Restore an archived plan to Active without creating a new record. Stopping a recurring cost is part of its financial story too.

Renewal dates matter more before the charge happens

SubVantage can surface upcoming trials and renewals before they become another charge. Scheduled email checks look two days ahead for trial dates and through the next three days for active-plan renewals. Resend handles delivery requests; the renewal check records successful sends to reduce repeat notifications on the same day. The goal is to put the decision before the next charge.

Sometimes the useful insight is a duplicate hiding in plain sight

Duplicate vendor subscriptions

The dashboard groups active records by vendor and surfaces repeated services as a redundancy signal. A trial can still be part of a duplicate group while remaining outside its paid total. Two active subscriptions for the same service are worth a second look.

A review signal, not a cancellation decision

These are deterministic grouping rules. A repeated vendor name suggests possible redundancy, but separate plans may serve different needs. The dashboard flags the pattern; the user decides whether either commitment is unnecessary.

Subscription records stay scoped to the account that owns them

Subscription Server Actions require an authenticated session, scope vendor records to that user, and check ownership before editing. Updates and deletes use both the subscription ID and user ID. Those checks live on the server, beyond what the interface chooses to show.

Financial totals are only useful if the rules stay predictable

Vitest tests cover currency conversion, yearly-to-monthly normalization, personal split costs, and trial exclusion. Reminder tests mock the database and email service to check trial reminder sends and the no-trials case. Playwright scenarios cover sign-up/sign-in and subscription creation, archiving, and deletion. GitHub Actions builds the application and runs those browser scenarios. The calculation tests keep the core normalization rules explicit as the interface evolves.

Making recurring spending visible before it becomes background noise

SubVantage’s more interesting problem was making unlike costs comparable. Currency, yearly billing, trials, personal shares, renewal dates, and cancellation all change what a subscription means financially. Bringing those rules together turned a list of services into a clearer view of ongoing commitments.