Product System / Portfolio Ready

Capital

Private financial command center for account state, cash flow, spending intent, and net worth.

Private product / public case studyStrongAppPublished record

Project Dossier

Portfolio ReadyStrong
Category
Product System
Type
App
Status source
Project model

A structured read on the build.

The page uses approved project data and keeps current-state boundaries visible.

Portfolio Ready

Capital is a private, single-owner finance application that combines connected account data, a manual monthly ledger, recurring analysis, alerts, and digest reporting in one operating interface.

Stack, status, evidence, and public actions are rendered from the typed project record.

Capital synthetic financial overview with net worth, liquidity, investments, liabilities, and account health

Category

Product System

Type

App

Priority

Strong

Overview

What this project is

Capital is a private, single-owner finance application that combines connected account data, a manual monthly ledger, recurring analysis, alerts, and digest reporting in one operating interface.

FintechData systemsProduct designAutomation

Problem

Why it matters

Personal financial context is fragmented across institutions, statements, notifications, and separate planning tools, making it difficult to explain what changed and why.

Solution

Approach

A server-first command center that unifies account state, transactions, intentional monthly planning, recurring behavior, historical trends, net worth, and scheduled summaries for one authenticated owner.

Architecture

System shape and stack

Product Model

Explain change, not just balances

The product connects balances and transactions to manual spending intent, recurring patterns, cash-flow trends, net-worth history, and digest reporting so the owner can understand movement across the whole system.

Architecture

Server-first financial operations

Next.js routes and server services coordinate Supabase Auth and Postgres, Plaid synchronization, webhook handling, alert evaluation, Resend email, Web Push, and authenticated Vercel Cron work.

Security Boundary

Narrow owner access

There is no public sign-up. User-facing data is owner-scoped, privileged provider work stays server-side, and Plaid access tokens are encrypted before persistence.

Presentation

Public proof, private product

The public case study contains privacy-reviewed synthetic screenshots and technical documentation. The connected app, source, credentials, and production deployment remain private.

  • TypeScript
  • Next.js
  • Supabase Auth
  • Supabase Postgres
  • Plaid
  • Vercel Cron
  • Resend
  • Web Push

Technical Highlights

Visible technical signal

  • Plaid synchronization with encrypted provider token storage
  • Owner-scoped Supabase data model with server-only privileged paths
  • Responsive analytics, manual ledger, alerts, and digest workflows

What It Proves

Builder signal

Full-stack product ownership across a high-trust data model, third-party integrations, financial analysis, privacy boundaries, and a distinctive responsive interface.

Boundaries

Context that should stay visible

Capital is personal finance software, not a public banking product or financial institution. The screenshots use fictional synthetic data from an isolated read-only presentation build.