A product-first website, built in a month

Wildeye makes the hardware that sits in a paddock and measures water. Its old website talked about the company and never really showed the product, so I rebuilt it around the product, on my own.

RoleSolo, end to endResearch · design · build · ship

Timeline1 monthConcept to a deployed domain

Scope15 pagesDesigned phone-first, plus live 3D

Median page486 KBDown from 3,097 KB

The site

Every page leads with the hardware, named and photographed, so a buyer sees what they would be buying before anything else.

The rebuilt Wildeye homepage on a laptop resting on dark stone: the logger large against a pale ground beside the headline Real-time monitoring, Trusted Globally, above four market cards — Homepage. The product first, at the size it deserves.

The Wildeye mobile homepage on an iPhone standing between two slabs of dark rock — The homepage on a phone.

The Wildeye mobile homepage on an iPhone lying on dark rock: the headline, a Talk to sales button and the logger — Where most visitors arrive.

The weather-station package schematic on an iPhone lying on dark rock — A package, drawn part by part.

A laptop on dark stone showing the Up and running in minutes carousel, starting with Connect your sensor — Setup, shown as steps instead of promised in a sentence.

The setup carousel on a laptop opening over dark rock, seen from a low angle — The same carousel, from below.

See the site at wildeye-static.vercel.app →

What I did

Talk to the people who did not buy, then make every product page answer the same four questions.

Before designing anything I interviewed 20 people across the business, from the CEO to installers, and rang the 6 resellers who had looked at Wildeye and signed with someone else. Every reason they gave came back to something the site never told them.

So every product page has to answer four questions: what is it, what does it measure, what does it cost and what’s in the box. A page didn’t ship until it answered all four.

Two columns on the rebuilt products page: Specifications, listing dimensions, enclosure, sensor inputs, cellular, power and compliance, and How it is sold, listing the hardware, the per-device subscription and what is not charged — **What it measures and what it costs, on the product page.** Including a line for what isn’t charged, which almost nobody in this market publishes.

It runs on the design system I built for the Wildeye product, trimmed for marketing, which is why a month was enough. The site and the app look like one company.

The logger, in 3D

Built from the factory’s own files, so a buyer can turn the product over without booking a sales call.

Everyone in this market sells a sensor, but no one lets you pick it up. The logger on the homepage is built from the factory’s SolidWorks files, so what you turn over is the real geometry, and it updates when the hardware does.

The Wildeye Enterprise field logger — a sealed grey IP68 housing with a raised button, a brass antenna bulkhead and two M12 sensor cables leaving the base — **Drag it.** Live 3D, not a video. It only loads when you scroll to it.

How it will be judged

It has not launched yet, so these are the targets rather than the results.

The site hasn’t launched yet, so there are no results to show. These are the targets I agreed with the CEO before design started. Pages already load far lighter: the median page is 486 KB, down from 3,097 KB.

Measure	Old site	Target
Organic sessions / month	2,400	4,000
Sessions that reach a product page	14%	40%
Qualified enquiries / month	9	25
New reseller applications / quarter	4	12

Built, launching at mywildeye.com. The research and analytics figures are my reconstruction of that work; the original notes and dashboards were lost.