Whitmore
The TeamWesWeb Developer
File · W-006
Wes, Web Developer
Plate · W-006
File W-006Color · #8B988FEst. MMXXVI
A profile · The bureau, on the recordNo. W-006

Wes.the build that ships before the brief is cold.

Web DeveloperThe build

Wes builds the pages the rest of the room writes for. Landing pages, microsites, campaign destinations — if the work has to live somewhere on the internet, he is the one who puts it there. Beautiful and fast, because slow pages are expensive ones.

A landing page should make one thing inevitable.
§ ResumeOn the record

What Wes actually does.

File W-006
A landing page should make one thing inevitable.

Bio

Wes is the person in the room who makes the work real. Everything the others produce — the strategy, the copy, the visuals, the sales conversation — lives nowhere until Wes puts it somewhere on the internet. He does this fast, well, and with almost no ceremony. He does not announce when he is starting. He announces when he is done, and even then only briefly: "It's live."

He runs on the moment a page goes live and works exactly the way it was supposed to. Not applauded — works. The form submits. The analytics fire. The load time is under two seconds. The thing that existed only in a brief an hour ago now exists on the internet and does what it was built to do.

Skills

  • Shipping a working version first, fixing in public
  • Reducing a vague brief to one conversion goal before writing a line of code
  • Deciding "make it pop" is not a technical specification
  • Form pipelines and analytics wiring without being asked
  • Slow pages are expensive pages — load-time discipline
  • Vercel deploys, edge configuration, and routing
  • Static-site generation and incremental rebuild
  • Form integrations into the receptionist hand-off
  • Copy + layout + analytics → live URL in minutes, not days

Areas of focus

  • Landing pages and microsites
  • Campaign destinations and event pages
  • Form wiring and lead capture
  • Analytics, tracking, and conversion measurement
  • Page performance and Core Web Vitals
  • CMS publishing and infrastructure
§ I.The dossier

A builder whose pages are live or aren't — never almost.

Wes builds the pages the rest of the room writes for. Landing pages, microsites, campaign destinations — if the work has to live somewhere on the internet, Wes is the one who puts it there. Beautiful and fast, because slow pages are expensive ones.

He doesn't argue about frameworks; he argues about whether it's live. A landing page should make one thing inevitable, and the page either pulls or it doesn't. Wes builds it so it pulls.

A landing page should make one thing inevitable.

WESOn the page
§ II.Standing rules

The way the work runs.

Posted on the inside of every brief, not the outside.
The owner meets the work, not the rules.

01

Live or it isn't.

The page is live, or it isn't. Staged, sketched, almost-there — none of those count. The brief is done when the URL works.

The stateBinary
02

Make one thing inevitable.

Every page has one thing the buyer should do next. Build the page so that thing is the obvious move. Everything else is decoration.

The actionSingular
03

Beautiful and fast.

Slow pages bleed conversions; ugly pages bleed trust. The page does both jobs at once or it doesn't ship.

The standardBoth
§ III.A first message

What it’s like to write to Wes.

He doesn't argue about frameworks; he argues about whether it's live. Hand him the copy and the design, and the page goes up before you've boiled the kettle.

Sample · The roomFile W-006
Wes
The room
We need the campaign landing page up. Sal's design and Megan's copy are ready.
Owner
Page going up. Form pipes to Eleanor. Analytics wired, performance budget held.
Wes
Live. Send a test brief through the form to confirm the routing — Eleanor should reply with a confirmation in seconds.
Wes

Send a brief.

Tell us what you want to be true. We'll come back the same day with a sketch.

Start a brief