Oakmont CS

The brief

Oakmont Capital Solutions arranges vehicle, business and property finance for developers, business owners and investors. The specification opened with the distinction that shaped every decision after it: Oakmont is not a finance broker. It is a capital solutions business — the firm a developer calls before buying a site, not a comparison service. The site had to carry the weight of an established advisory firm rather than the urgency of a lead generator.

Structure

Three kinds of finance, three audiences who do not overlap much: someone financing a car has little in common with a developer funding a scheme. Each became its own route with its own hero, its own cards and its own FAQs, rather than three tabs on one page fighting for the same headline.

Copy, figures and per-route content live in a content directory, separate from the route files. A trust-bar figure appears in several places and is written once — change it there and it changes everywhere, which is what stops a site drifting out of agreement with itself after launch.

Build

Next.js with the App Router, React and TypeScript, every route prerendered to static HTML at build time. No CSS framework: one hand-written stylesheet, which for a site of this size ships less and stays easier to reason about than a utility layer plus the config to constrain it.

Photography is WebP, converted before it reaches the repository. The result is a homepage that arrives in roughly eleven kilobytes of compressed HTML, with a share card generated as part of the build rather than maintained by hand.

Regulation

Oakmont operates as an appointed representative of a principal firm, which means the regulatory wording on the site is not decoration — the firm reference number belongs to the principal, not to Oakmont, and the site has to say so accurately. Those details sit in the same content layer as everything else, so compliance changes do not need a developer.