How We Build Websites for Clients

We show them what we can do — using their own site.

Instead of pitching a proposal, we rebuild an example of the client's site from their existing one — a working demonstration of what we can do and the problems we can solve for them. Paired with the reports, it turns an abstract pitch into something they can see and click. Everything in this deck exists to make that demonstration identical and repeatable on every project.

• Prototype-first. An example of their site is built, click-through complete, and on-brand before the first meeting — so they see it, not imagine it.
• Their brand, not ours. We pull the client's real logo, colors, fonts, and images — we never invent them.
• Same package, every time. 10 deliverables, one consistent standard, no matter who builds it.

What a prototype is — and what it isn't.

Definition: A prototype is a clickable simulation of the client's website, rebuilt from their existing site, that demonstrates what we can do and the specific problems we can solve — a sales tool created before they buy, to make the value visible instead of promised.

Two inputs. Then we run the whole prototype workflow.

We only ever need two things to kick off a build. Everything else is pulled from the live site or documented as an assumption.

The order we build in — every time.

Each stage feeds the next. We never skip ahead; brand comes before pixels, prototype before reports.

Pull the brand from the live site. Never invent it.

The client should recognize their own business the moment the prototype loads. That only happens if we use their real assets.

• Logo: download from the live site (SVG > PNG). Never recreate or redesign it.
• Colors: extract hex values from the site's CSS or logo. Map to primary, accent, dark, muted, background.
• Fonts: match the exact families and load from the same source. Fall back only if unidentifiable.
• Images: download every image locally to img/ — no hot-linking to external CDNs.

brand.html is the single source of truth.

We build it before any prototype page. Every color, font, and button used anywhere else must first be documented here.

Mirror every page — then make it better.

We crawl the live site, rebuild every page in its nav and footer, and improve UX and conversion on each one.

• One file per live page, with a comment at the top noting the source URL and the improvements made.
• Every CTA and flow is simulated to look like it works. No dead buttons — server actions open the prototype modal.
• A prototype banner marks each page as a preview and shows the performance report.
• A clever, industry-specific 404 is included on every project.

The package around the website.

These deliverables turn a nice site into a compelling case. Each is a polished, standalone page on the client's brand.

The rules that keep every build consistent.

Definition of done.

Before a project is "ready to present," we open every file, click every CTA, and verify each item:

• Logo loads correctly in nav, footer, and brand guide.
• Every color and font used is documented in brand.html.
• No {{TOKEN}} placeholders remain in any file.
• Mobile: no horizontal scroll, 44×44px tap targets, working hamburger.
• Every content image has descriptive alt text.
• Every CTA and flow completes — no dead links, no dead ends.

The complete package.

Every one of these is finished before the sale — the same 10 deliverables, built to the same standard, on every project.