Skip to content
FintechWeb platform

One Park Financial

This is a funnel first and a marketing site second, so every decision was judged on whether it kept an applicant moving.

One Park Financial: the live site
Our role
Full-stack: the application funnel and the design system behind it
Timeline
Ongoing engagement
Team
Lead engineer, frontend engineer

~2 min

To prequalify

multi-step, mobile-first

<1 day

To funding

where underwriting allows

1

Design system

shared by marketing and the app

01

The problem

A funnel wearing a marketing site

The business is lending, and the only thing on the site that makes money is the prequalification flow. Everything else exists to get an owner into it.

That flow has to stay fast and credible on a phone, feed underwriting cleanly, and above all never lose an applicant halfway through. A business owner abandoning at step three of five is the single most expensive event on the site.

02

What we did

Work both sides of the form

The work ran across the Laravel API and the React front end: the multi-step form with its validation and state handling, and the data contracts behind it, so that what the form collects is what underwriting can actually use.

A Tailwind design system keeps the marketing pages and the application surface visually consistent. That matters more in lending than in most categories: a form that looks like it came from a different company than the page that sold it is exactly where people stop trusting a financial product.

  • Multi-step prequalification form with resilient state and validation
  • Data contracts designed against what underwriting consumes
  • Shared Tailwind design system across marketing and application
  • Mobile-first, because that is where the applicants are
03

The outcome

An application people finish

Owners prequalify in roughly two minutes on a phone, the submitted data lands in a shape underwriting can act on, and the marketing and application surfaces share one visual system.

What it is built on

Frontend

  • React
  • TypeScript
  • Tailwind CSS

Backend

  • Laravel
  • PHP
  • REST API
  • MySQL

What we learned

  • 01

    Design the form against what the downstream system consumes, not against what is easy to ask. A tidy form that produces unusable data has moved the problem, not solved it.

  • 02

    In a financial product, visual consistency between the pitch and the form is a conversion mechanism, not a brand nicety.

Next step

Tell us what you are trying to build.

Thirty minutes with the engineer who would lead the project. You will leave with an opinion on what to build, what to skip, and roughly what it costs, whether or not you hire us.

2 build slots open · Next start: early next month

What happens next

  1. 1You send a few lines about the product and the deadline
  2. 2We reply within one working day with times
  3. 3A 30-minute call, no deck, no sales script
  4. 4A written summary and a ballpark range within 48 hours