The problem behind a simple quote
NOW Finance is an Australian non-bank lender that describes its personal loans as no-fee, with an establishment fee applying to its vehicle loans. Its proposition depends on being easy to deal with, so customers need to get from a first question to a finished application online, without having to visit anyone.
Loan applications are not naturally simple. Behind one journey sit eligibility rules, repayment calculations, user management and analytics. Customers also need to trust what they are seeing, because they are sharing personal and financial details.
The frontend had to turn all of that into something clear, on any device, for customers and for the brokers who work with the lender. It also had to look like one brand across several systems.
What we knew before we built
No before-and-after baseline is published for this project, so this page does not offer an improvement figure. What can be stated is the context the work sat in, using NOW Finance's own public information.
- 2013
- The year NOW Finance was founded, as stated on its site
- 2min
- Time NOW Finance states for a personalised quote, as of November 2026
- 2
- Lending channels the frontend had to serve: direct and broker
That set three requirements for the work. A customer had to be able to check eligibility and get a quote with little effort. Several backend systems had to feel like one experience. And branding and financial services requirements had to carry across every digital asset.
The approach we chose
Each part of the platform was given the job it suits best, with design and backend teams working from shared Figma wireframes:
- React with Inertia.js. The interactive application screens, with Inertia.js connecting them to Laravel so that navigation behaves like a single-page app.
- Laravel and MySQL. Backend APIs for eligibility, calculations, loan approvals and workflow automation, with structured storage for applications, profiles and broker interactions.
- WordPress. Knowledge center articles, guides and SEO landing pages that marketing and content teams can update.
A customer's journey runs through four stages:
- Explore. Read guides and use the repayment calculator to see what a loan could look like.
- Quote. Enter some details, pass the eligibility check and receive a personalised rate.
- Apply. Complete the loan application digitally, on a phone or a computer.
- Manage. Keep track of the loan and its repayments online.
What we built
Our contribution was the frontend: UI and UX implementation for customer journeys and broker portals, working with the design and backend teams. Lending decisions and backend systems sit outside that scope, although the frontend had to integrate closely with them.
A rate quote flow
We architected the flow for rate quotes, where a customer enters their details and receives a personalised offer in minutes. NOW Finance states that getting a quote does not affect a customer's credit score, because it uses a soft credit enquiry.
Eligibility and repayment tools
Adaptive React components let customers check eligibility, calculate repayments and move on to the application, connected to the Laravel backend APIs through Inertia.js.
Landing pages and application flows
Landing pages and internal application flows were built from Figma wireframes into interactive components, along with user onboarding. Pages were built closely to the designs and with conversion in mind.
Broker portal journeys
The same implementation work extended to broker tools, with attention to keeping design consistent across web, mobile and broker experiences.
Responsive performance
React components were optimized and integrated with Inertia.js and Laravel so that the experience stays responsive across devices.
Getting a quote should feel simple, however many systems are working behind it.
The guardrails around a loan journey
Customers share personal and financial details in these flows, and the screens they see can shape a financial decision. These considerations were part of the frontend work rather than a late addition.
- Decisions stay on the backend. Eligibility, calculations and loan approvals run through backend APIs. The interface presents them and does not make them.
- A quote before a commitment. Customers can see a personalised quote before they apply.
- Privacy as a requirement. Real-time eligibility checks and quotes had to be delivered with user privacy and regulatory requirements in mind.
- Consistent presentation. Brand and financial services requirements were carried through digital assets so that customers see consistent information.
- A clear view of compliance. Compliance depends on the lender, its licences, its processes and how a system is used. We do not describe a frontend as compliant in itself.
What was reported
The platform is live, and customers can get quotes, check eligibility and apply online from a phone or computer. The effects below are what the project team reported; none of them is a measured result:
- Customer experience. A lower-friction journey and clear communication were reported to improve conversion and customer satisfaction. Neither figure is published here.
- Channels. The frontend serves both direct customers and brokers from a consistent design.
- Iteration. Integration between Laravel, React and the CMS supports content updates, analytics and faster feature changes.
What stays hard
Five challenges shaped this work, and any team building a digital lending journey should plan for them.
- Real-time quotes. Eligibility checks and loan quotes have to arrive quickly while still respecting user privacy and regulatory requirements.
- Speed and security. An application should feel fast and frictionless, but verification and security cannot be traded away to get there.
- Many systems, one screen. Calculations, user management and analytics each have their own backend needs, and the customer should see only one intuitive experience.
- Brand across platforms. Visuals and experience have to stay uniform across WordPress, React and marketing channels.
- Handoffs under deadline. Research, design, frontend and backend stakeholders all need smooth handoffs, especially when deadlines are tight.