Wildeye · marketing site
A product-first website, shipped in a month
Role
Solo, end to end
Research · design · build · ship
Timeline
1 month
concept to live domain
Median page
486 KB
was 3,097 KB
Status
Built
launching at mywildeye.com
Only what it needs
One system, two surfaces
Marketing subsetWildeye design systemBrand
Neutral ramp
Type
The site runs on the design system I built for the product, trimmed to what a marketing page needs. Same tokens, same face, so the website and the app look like one company.
The idea
Show the product. Cut everything else.
The old site
stakeholder interviews
lost-deal calls with resellers
of site analytics reviewed
pages content-audited
A year of analytics
Google Analytics 4Google Search ConsoleHotjarMicrosoft Clarityof sessions arrived on a market or blog page, never the product page
median time on the Products page before bouncing
of traffic was mobile, the layout the site handled worst
search query was “wildeye logger price”, and no page answered it
Six resellers who didn’t sign
Lost-deal follow-up callsCouldn’t send a spec sheet to their own customer
Every product page ships a downloadable datasheet
No price to quote from, so the deal stalled at email
A price or a lead time, printed on the page
Couldn’t tell which sensors the logger actually reads
Compatibility listed per application, in plain names
Site unreadable on a phone in the field
Mobile-first, high contrast, light pages
Didn’t believe it was still an active product
Real product photography and current specs, not stock
Went with a competitor whose site “just explained it”
One labelled schematic beats three paragraphs
I rang the prospects who looked at Wildeye and went with someone else. Every reason came back to something the site never told them, so every reason became a rule.
What the content audit found
30 pagesOne rubric, every pagedatasheets a buyer could download
products named on the Products page
pages showed a price
contrast failures in field sunlight
The brief
Three people, three demands.
Make it product-focused.
Every selling page leads with named, photographed, specified hardware. The company story moves to the back.
Make it work where the buyer is standing.
A paddock, a pit, a pump shed. Two bars of signal, full sun, gloves on. That means light pages, plain language, high contrast, and nothing that keeps them waiting.
Make it obvious what you’re buying.
Four answers within one click of every product, and nothing ships until all four are there.
What a product entry owes the reader
The content modelFour required answersWhat is it?
A named product, photographed, front and centre.
The logger leads the homepage in 3D; the products page opens with the hardware, named.
What does it measure?
A spec table: range, accuracy, power, ingress rating.
Spec tables on the products page; sensors listed per application.
What does it cost?
A price or a lead time, printed on the page.
A pricing page of its own, one click from anywhere in the nav.
What’s in the box?
A labelled schematic of the whole installation.
Package schematics drawn into the page: solar panel, logger, sensors, every part on its own lead.
From SolidWorks to the browser
A buyer can turn the product over at 2am without booking a sales call. The model up the top isn’t a web asset, it’s the factory’s own STEP files, and getting that much CAD onto a page took a pipeline of its own.
of manufacturing CAD: the front shell and lid, straight from SolidWorks
triangles, tessellated from the CAD’s exact surfaces for the GPU
meshopt-compressed GLB, the whole model the page ships
in React Three Fiber: drag, inertia, idle turntable, and no cost at all off-screen
The CAD only carries the housing. Label, button, LEDs, brass antenna and cables are all drawn on top in code.
The results
Every page prerenders to plain HTML, because the buyer’s connection is two bars of rural signal. Here’s what that buys.
The scoreboard we launch against
Baseline from the analytics reviewTargets agreed with the CEOOrganic 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
Every target traces to something the research found: the product page nobody reached, the price nobody could quote, the resellers who walked.
The median page, before and after
Cold-load wire bytesAll 15 pages- Old site, median page30 WordPress pages3,097 KB
- New site, median page15 static pages486 KB
- New site, heaviest pagethe homepage, hero renders included1,348 KB
largest contentful paint on Slow 4G, on a mid-tier phone
public pages, every one prerendered static
the 3D model itself, fetched only when seen
What I keep
Minimal is a decision
Every section had to argue its way onto the page. The audience decided what stayed: a buyer in the field doesn’t scroll past brand copy to find a spec, so the spec goes first and the copy goes.
The strongest assets already existed
The factory’s CAD, the install schematics, the price list. The best content was already in the building, so the job was getting it on screen untranslated instead of writing prose about it.
Own the whole pipeline
Designing the site meant owning how its assets get made, from manufacturing CAD down to a 691 KB GLB, and reusing one set of schematics everywhere. The pipeline is as much the design as the pages are.
Where it stands
A site that described the company, rebuilt around the product.
Built · launching at mywildeye.com.