Skip to content
Subscribe →
DOC-001 / FILED 2026.04.23 REV 01
DOC-PRC-001 / Process Return to Index ↗
Client File · What Happens Next · Rev 01

No mystery. Just shipped work.

You bring the page, product, or messy web problem. I turn it into a sharper argument, design the surface, hand-code it, verify it, and ship the live thing.

01 — Working Rules III Rules
PRC-001 Restraint

Every section needs a job.

The page should explain, prove, sell, or route. If a section is only there because most websites have one, it leaves.

PRC-002 Conversion

The next step should be obvious.

A beautiful page that makes people hunt for the action is unfinished. The offer, proof, objections, and CTA get designed together.

PRC-003 Code

Ship the real thing.

Figma can help us think. It is not the finish line. The deliverable is working code, a live URL, and a repo your team can inspect.

02 — What Happens VI Records
  1. 01 BLD-001
    Audit

    Start with the page you have.

    I read the current site like a buyer: offer, audience, traffic source, conversion path, visual debt, technical debt, and trust gaps.

    • What does a first-time visitor understand in 15 seconds?
    • Where does the page ask too early, too late, or too quietly?
    • What is a real constraint, and what is just inherited clutter?
    Artifact Findings, priority list, first request
  2. 02 BLD-002
    Structure

    Make the argument clearer.

    Before styling anything, the page gets a sharper order: premise, proof, offer, details, objections, action.

    • Turn vague sections into decision-making sections.
    • Move proof next to the claims it supports.
    • Name what is not included so the right buyers self-select faster.
    Artifact Section map, copy pass, conversion path
  3. 03 BLD-003
    Design

    Design the surface.

    Type, spacing, hierarchy, screenshots, states, and responsive layout get handled before novelty gets invited into the room.

    • Use motion only when it makes the page easier to read.
    • Keep components reusable enough to make the next request faster.
    • Let the brand feel specific without making the system fragile.
    Artifact Design direction, component states, responsive checks
  4. 04 BLD-004
    Code

    Hand-code the page.

    The design turns into real code in the stack that fits the client: Astro, React, Next.js, Shopify Liquid, or plain HTML/CSS/JS.

    • Use semantic markup and accessible controls.
    • Keep styling tied to tokens instead of one-off decoration.
    • Avoid page builders, templates, and exported no-code output.
    Artifact Repo commit, preview URL, implementation notes
  5. 05 BLD-005
    Verify

    Test the surface like a buyer.

    Mobile, desktop, navigation, forms, analytics events, performance, SEO basics, and copy all get checked before launch.

    • Confirm text fits and controls do not shift layout.
    • Verify CTAs route to the right action.
    • Check the page under reduced-motion preferences.
    Artifact QA pass, build output, launch checklist
  6. 06 BLD-006
    Ship

    Deploy, measure, and file the next request.

    The work goes live, analytics are checked, and the next highest-leverage improvement becomes the next filing.

    • Deploy to Vercel or the client's host of choice.
    • Keep measurement cookieless unless the client already has a compliant stack.
    • Document what shipped and what should be improved next.
    Artifact Live URL, analytics check, next filing
03 — How Decisions Get Made VI Tests
LNS-001 Reduction

What can leave?

Cut anything that does not help a buyer understand, trust, decide, or act.

LNS-002 Story

What should people believe faster?

The page needs a point of view. Otherwise it turns into category wallpaper.

LNS-003 Experience

Where does the buyer hesitate?

The page, checkout, intake, and kickoff should feel like one path, not four disconnected tools.

LNS-004 Selling

Does the page ask clearly?

Make the hook, offer, proof, objections, and next action unmistakable.

LNS-005 Systems

What should repeat?

Good judgment should turn into a loop: ship, observe, tighten, and file the next request.

LNS-006 Image

What should it feel like at first glance?

Use pacing, screenshots, and visual proof to make the work memorable without drifting into decoration.

04 — What You Are Buying

You are not buying a ceremony. You are buying taste, speed, code, and judgment applied to the part of the business customers actually touch.

Best first step: pick the tier that matches the pace you need, or book a short call if the first request needs shaping.

See Plans → Book Call