VILLACRUSIS LABS.

Case study · SOLE FRONTEND ENGINEER

AU Wage-Advance Fintech Frontend

Sole frontend engineer for a regulated Australian wage-advance platform: customer app with bank linking and KYC, internal ops portal and public site.

React 19TypeScriptViteAWSBank linkingKYC

The business and the problem

An Australian fintech lets employees access part of their earned wages before payday. It is a regulated lending product: every customer must be identified, their income verified from bank data, and every advance and repayment recorded and reconciled. The company needed all three of its production surfaces — the customer app, the internal operations portal and the public website — built and maintained, and it needed them from one engineer.

What was built

The customer app

A web app where a customer signs up, proves who they are, links their bank account, and requests an advance. The hard part is the onboarding: a multi-step identity-check flow that has to survive a customer switching from a phone to a laptop half-way, coming back three days later, or failing a step and needing to retry without starting over. Bank linking runs through two Australian data providers, with fallbacks when one is unavailable, and the income assessment has to explain to the customer why a limit is what it is.

The internal operations portal

The staff side: reviewing applications, processing payments and repayments, handling exceptions, and reading embedded analytics without exporting to a spreadsheet. Built so that a new operations hire can be productive on day one, with roles that keep sensitive actions behind the right people.

The public website

The marketing site and its SEO surface, kept consistent with the app's design system and fast enough that a customer on a phone does not bounce before the sign-up button.

What changed

The company ran three production surfaces with a frontend team of one, which is only possible when the same person owns the design system, the forms, the error handling and the release process end to end. Onboarding flows that used to lose customers at the identity step were rebuilt to resume where the customer left off.

What this means for an SME project

Most Philippine SME projects do not need bank linking or a compliance regime. They do need forms that never lose a customer half-way, admin screens that staff can use without training, and a public site that loads fast on mobile data. Those are the same skills, applied to a smaller problem. If a regulated lender trusted one engineer with all of it, a booking system or an inquiry funnel is well within reach. That is the work behind the custom CRM and web app service and, at the smaller end, a business website with forms that behave; NudgeNow shows the same discipline applied to a Philippine product.

Stack

React 19 and TypeScript, built with Vite, deployed on AWS. Bank data via two Australian open-banking providers; identity checks via a multi-step KYC flow.

Building something similar? Tell me about it.

Most SME projects are a fraction of this size, which is why they ship in weeks. The same care goes into a landing page as into a fintech platform.