← All work

01Fintech · 2025

Tidex

End-to-end product build for a fintech MVP: onboarding, bank connections, cash-flow views, and an admin layer founders could run without engineering support.

Role

Lead full-stack engineer

Timeline

10 weeks

Team

Founder, 1 designer, 2 engineers

Status

In production

Laptop showing a financial analytics dashboard interface

Onboarding completion

68% → 89%

Time to first insight

< 4 min

Weekly active teams

120+

P0 incidents (90d)

0

The problem

Small business owners were exporting spreadsheets from three tools to understand runway. The startup needed a credible first release that could handle real accounts, daily usage, and fast iteration after investor demos.

The solution

Shipped a Next.js web app with a normalized ledger model, role-based access, and dashboard views tuned for operators—not accountants. Onboarding was reduced to four steps with clear recovery when bank linking failed.

What I owned

  • Owned system design, API contracts, and frontend architecture
  • Built auth, billing hooks, and bank-ingest pipeline with idempotent jobs
  • Partnered on design system tokens and accessible form patterns
  • Set up CI, preview deploys, and error monitoring before launch

Stack

  • Next.js
  • TypeScript
  • PostgreSQL
  • Prisma
  • tRPC
  • Tailwind CSS
  • Vercel
  • Plaid
  • Stripe

Engineering highlights

  1. 01

    Ledger-first data model

    Mapped messy bank transactions into a small set of event types so reporting stayed fast and audits stayed traceable.

  2. 02

    Resilient bank linking

    Retries, user-visible states, and support tooling for failed connections—reducing drop-off without hiding errors.

  3. 03

    Operator dashboards

    Server-rendered overview pages with chart data cached per workspace; kept TTFB low on mobile networks.

How we shipped it

  1. 01

    Discovery & scope

    Mapped jobs-to-be-done with founders, defined MVP cut line, and wrote a technical brief with risks (compliance, ingest SLAs).

  2. 02

    Foundation

    Auth, org model, design tokens, and CI. Established API patterns and preview environments the whole team could use.

  3. 03

    Core product

    Onboarding, transactions pipeline, dashboards, and exports. Instrumented funnels before opening beta.

  4. 04

    Launch & iteration

    Hardened observability, runbooks, and weekly release rhythm with feature flags for risky areas.