Ausbiz Capital Financial Platform

What problem did the Ausbiz Capital platform need to solve?

I joined the Ausbiz Capital project with an incomplete codebase that needed refactoring before it could support production use. The application combined public investment content, subscriber access, pricing rules, and scheduled market-data imports. Those responsibilities were spread across Sanity, Supabase, FTP files, an XML feed, and HubSpot.

The engineering problem was not simply building pages. I needed to define clear boundaries between editorial content, subscriber data, imported financial records, and access-control decisions.

How did I structure the application?

Next.js handled public and authenticated experiences

I used Next.js and React for the application layer. Public editorial pages could be generated efficiently, while authenticated routes could request subscriber-specific data and enforce access rules.

Sanity owned editorial content

Sanity stored the content that editors needed to change without a deployment. I modeled reusable content structures so the team could create pages from approved sections rather than asking engineering to hard-code each layout.

Supabase owned application data and authentication

Supabase provided PostgreSQL storage and OAuth-based authentication. The frontend queried Supabase for imported records and user-specific data, while Sanity remained focused on editorial content.

How did the financial-data pipelines work?

I implemented two scheduled ingestion paths:

1. An FTP job downloaded Excel files containing stock-analysis data, transformed each file into application records, and stored the results in Supabase PostgreSQL.
2. An XML job fetched structured news content and mapped it into Sanity documents for editorial display.

I also connected application logic to HubSpot contact properties. Those properties helped determine pricing conditions and subscriber access. This kept commercial rules out of the presentation components.

What did I deliver?

I refactored unstable areas of the inherited codebase, built React components that consumed both Sanity and Supabase data, and connected the application to its scheduled data sources. The result was a maintainable foundation for editorial pages, authenticated investment content, and recurring market-data updates.

The Ausbiz Capital website remains the public reference for the product. This case study describes my engineering scope during the 2024 implementation, not every feature added afterward.