Skip to content

Brief → Build → Launch

A focused 72-hour pipeline. Minimal meetings, clear approvals, and hosting included—plus weekly content updates and a quarterly design refresh.

Three phases, one launch window.

Start conditions

Content Supplied — Build starts after you complete the discovery form, you upload copy/logo/images and complete the setup payment via secure Stripe checkout link.

See this flow →

Content Curated — We craft copy & visuals immediately after your discovery form completion and setup payment (Secure Stripe link sent after a discovery completion).

See this flow →

The 72-hour clock starts at payment confirmation per the chosen track.

What’s included — full breakdown

Build & design

  • Bespoke one-page site (no templates)
  • Responsive layout across mobile/tablet/desktop
  • Clear hierarchy, scannable sections, strong CTA placement
  • Micro-interactions that remain accessible and performant
  • Image pipeline (format, compression, dimension sanity)

Content

  • Content Supplied: we place, lightly edit for clarity, structure headings
  • Content Curated: conversion-focused copy for all sections
  • Alt text; semantic headings (H1–H3)
  • One consolidated pre-launch revision

Performance & accessibility

Core Web Vitals (targets & tactics)

Targets (mobile, 75th percentile of real users): LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.10.

  • LCP (hero image/content): optimized hero media (exact dimensions, loading="eager" + fetchpriority="high" for the single LCP element), responsive images (srcset/sizes), preload critical asset(s), defer everything non-critical.
  • INP (interactivity latency): ship minimal JS, defer/async non-critical scripts, avoid long tasks (>50ms), break work with requestIdleCallback/setTimeout, reduce layout thrash (style reads/writes batched), use CSS for animations when possible.
  • CLS (layout shift): always include width/height (or aspect-ratio) on images/video/iframes; avoid inserting late content above the fold; reserve space for dynamic UI; load fonts with font-display: swap to prevent FOIT; prefer CSS transforms to animate.
Accessibility (WCAG 2.1 AA practices)
  • Structure: semantic landmarks (header/main/nav/footer), single <h1> per page, logical heading order.
  • Keyboard: visible focus states, logical tab/focus order, skip-link, no keyboard traps.
  • Labels & names: explicit form labels, descriptive alt text for meaning-bearing images, ARIA only to enhance semantics (not replace).
  • Contrast & readability: body text ≥ 4.5:1, large text ≥ 3:1, sufficient line-height and spacing, reflow without loss on small screens.
  • Motion: honor prefers-reduced-motion; avoid parallax/heavy motion by default; provide non-motion alternatives.
  • Touch targets: aim for ~44×44px tappable areas; avoid hover-only interactions on mobile.
  • Errors & help: inline error messages tied to fields via aria-describedby, clear instructions/examples where needed.
Asset strategy (fast by default)
  • Lean images: pre-sized, responsive (srcset/sizes), compressed; lazy-load below-the-fold (loading="lazy", decoding="async").
  • Fonts: system stack where possible; webfonts with font-display: swap; subset/preload if needed; minimal families/weights.
  • CSS/JS: critical CSS inlined; non-critical deferred; tree-shaken/minified bundles; no unused libraries.
  • HTTP: HTTP/2 or HTTP/3, Brotli compression, long-lived immutable cache for static assets with fingerprinting; HTML kept small.
  • Third-party: audit embeds; async/defer; load only on pages that need them; graceful fallbacks if blocked.
Caching & headers
  • Caching: HTML short TTL; static assets far-future (cache-control: public, max-age=31536000, immutable) with hashed filenames.
  • Preload / preconnect: key fonts/hero image; preconnect DNS for required third-party origins to reduce TTFB on those calls.
  • Security: HTTPS redirect, HSTS (optional), sensible CSP where possible.
Monitoring & acceptance criteria
  • Launch checks: Lighthouse (mobile) and PageSpeed Insights for key templates; verify LCP element and layout stability; check focus order and contrast.
  • Post-launch: GSC Core Web Vitals report monitoring; surface regressions and propose fixes; periodic asset review as content grows.
  • Acceptance (mobile): LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.10 on primary templates; no critical a11y blockers (keyboard traps, missing labels on forms, insufficient contrast on primary text).
  • Core Web Vitals tuned: LCP/INP/CLS targets met on key pages
  • Keyboard nav & focus order; explicit labels; contrast verified
  • Lean assets, responsive images, caching & compression for fast loads

Integrations & setup

  • Hosting on SiteRevive infrastructure + SSL (Let’s Encrypt) + domain connection (client-owned)

    DNS ACCESS REQUIRED (non-negotiable): To keep the 72-hour launch window, you must provide DNS access at your registrar (e.g., Namecheap, GoDaddy, Cloudflare) via a temporary login or delegated user. If DNS access is not provided, I cannot take on the project.

    Ownership: You purchase and retain ownership of your domain. I perform all DNS configuration to connect it to SiteRevive hosting.

    What I configure in DNS
    • A/AAAA for apex (@) to my server IP(s) or ALIAS/ANAME if required
    • CNAME for www → your chosen canonical (www ↔ apex, we’ll pick one)
    • TXT for Google Search Console domain verification (google-site-verification=…)
    After DNS is live
    • Provision/auto-renew SSL (Let’s Encrypt)
    • Force HTTPS; set canonical host (www vs non-www); optional HSTS
    • Update sitemap.xml, robots.txt, and site metadata to the final domain

    Email/MX: I do not change MX records without your written approval. If you use domain email, MX remains untouched; I can advise on SPF/DKIM/DMARC if needed.

    Security: Access is limited to DNS settings needed for launch. Credentials/delegations are removed immediately after go-live. A change log can be provided on request.

    Go-live is gated on DNS completion. Until DNS resolves to my servers, I cannot issue SSL, finalize redirects, or submit your domain to Google for indexing.

  • Google Search Console (GSC) setup & management

    I configure and manage GSC so we can monitor indexing, coverage, and essential health signals. You retain ownership; I operate as a verified owner/manager.

    Property type & verification

    Required: Domain property (covers all protocols/subdomains).

    • Verification via DNS TXT at @: google-site-verification=XXXXXXXX (value provided by me)
    • No alternatives: URL-prefix/HTML/GA/GTM methods are not used in this workflow.
    What I manage in GSC
    • Submit /sitemap.xml and validate canonical host
    • Inspect/submit important URLs for indexing after changes
    • Monitor Index Coverage, Sitemaps, and Core Web Vitals (LCP/INP/CLS)
    • Handle 404/redirect hygiene for removed/renamed pages
    • Temporary removals when needed
    • Change-of-address assistance for rebrands/migrations
    • Access control: add/remove users with correct roles
  • GA4 analytics enabled with sensible defaults (linkable to GSC)
  • Contact form routed to your email (no mailboxes included)
  • sitemap.xml, robots.txt, Open Graph & social metadata

Review, launch & handoff

  • Private review URL (basic auth) for your first pass
  • One consolidated revision pre-launch
  • Change log

Post-launch care

  • Weekly content revision (one session per week: copy tweaks, promos, image swaps, hours, CTAs)
  • Quarterly design refresh (one focused session per quarter: visual tuning, spacing, seasonal tweaks)
  • Light maintenance: uptime watch, minor dependency hygiene
  • Backlog suggestions for future enhancements

Ownership & access

  • Your domain stays yours (we provide DNS records or handle with delegated access)
  • Licensed/royalty-free assets documented
  • Export options for page content & assets, upon request.

Support

  • Hands-on during the sprint; target response 2–4 hours
  • After launch: standard business-hours response
Start in 60 seconds FAQ

Notes

  • Single one-page site. Contact form routes to your email (no mailboxes included).
  • Third-party embeds may affect performance/accessibility; alternatives provided where helpful.
  • The 72-hour window starts at payment confirmation per your selected track.

FAQs

What if my content isn’t ready by H6?

We can use tasteful placeholders to protect momentum; the build starts once payment is confirmed per your selected track.

Can you create my copy and images?

Yes—choose the Content Curated track. We start right after payment and craft conversion-focused copy and visuals.

What’s included after launch?

Weekly content updates and a quarterly design refresh are built into hosted plans.

Have a deadline coming up?

Tell me the date—I'll lock your 72-hour window.

Get a plan

Deliverables