
THE TAKEAWAYA product with twenty-four features does not have a feature problem, it has an order problem. The front end's job is to decide what a stranger reads first.
The public face of an AI-native inventory platform — a front end that has to make twenty-four features feel like one product.
Remarkable is an AI-native inventory platform — real-time SKU tracking, demand prediction, automated reordering, multi-warehouse sync. The kind of software a company buys once and then runs its whole operation on. Software like that has a specific problem, and it is not a technical one. It does roughly two dozen things, all of them genuinely useful, and every one of them sounds exactly as important as the others when written down. Pick paths, pallet receiving, customs handling, vendor lead times, audit trails, anomaly detection, carrier labels. A warehouse manager needs all of it. A stranger landing on the site for eleven seconds needs one of it. I designed and built the front end: the product's public face.
My Role: the design and the front-end build — layout, type, colour system, motion, responsive behaviour, and the order the whole thing is read in. Not the inventory engine itself; that is the company's software. What I was responsible for is the part a buyer meets first and judges the rest by. The brief from the client's side was clear about outcome rather than execution: it had to look like serious infrastructure, not a startup landing page, and it had to convert without shouting. Everything about how that got done was mine.
One claim above the fold, not twenty-four. The hero says "All your inventory on one platform" and then "Simple, fast, yet unstoppable" — a promise and a tone, nothing else. The twenty-four capabilities are real and they are all on the page, but they sit below, grouped, after the visitor has been given a reason to keep scrolling. Leading with a feature grid is how good software gets mistaken for a list.
A palette with one voice. White ground, black type, and a single electric blue carrying every interactive element — buttons, links, active states, the pulse on the live indicator. One accent used consistently is what makes an interface read as a system rather than a collection of screens. A second brand colour would have cost that immediately.
Motion that reports progress, not personality. Scroll-driven reveals, staggered so a section assembles rather than appearing, with the underline draw on the headline as the only flourish. On a tool people will use for eight hours a day, animation that performs is animation that will be hated by the second week.
The free tier said out loud. "Start now — it's free" sits beside "$0 to start, for every warehouse" rather than hiding in a pricing table. The biggest objection to operations software is the cost of finding out whether it works. Answering that in the hero removes it before it forms.
Built in React and Vite with Tailwind, motion through GSAP with ScrollTrigger and Observer, and laid out mobile-first — a warehouse floor is a phone environment long before it is a desk one.
The live product site
remarkable-dashboard.vercel.app
NEXT PROJECT ↘Mockingbird — A Calling Agent That Had to Pay for Itself