Client marketing website · June to August 2026
Sprint Coach
Designed and built the first website for a Wellington sprint coaching business, from creative direction through to production launch.
sprintcoach.co.nz
Case snapshot
- Problem
- Nathan coached a growing group of Wellington athletes with no website at all. Enquiries arrived by word of mouth, and nothing explained the service, established his credibility, or could be found in local search.
- My role
- Sole designer and developer. I ran the project end to end: design direction, content, build, SEO, launch, and client handover.
- What I changed
- Set the design direction and shaped the copy with the client, keeping every claim traceable to something verifiable.
- Built the site as prerendered static pages with a single serverless function for enquiry email.
- Split staging from production so the client approves the exact commit that ships.
- Result
- The site is live at sprintcoach.co.nz with a working enquiry form, local SEO structured data, and a documented launch checklist handed to the client. Nothing reaches production until the client has approved the exact build that ships.
Context, decisions, and evidence
A coaching business with no website at all
Nathan had built a growing group of Wellington athletes entirely through word of mouth. There was nothing a prospective athlete or parent could read before getting in touch, no explanation of what a session actually involves, and nothing for local search to find.
Credibility had to come from what is true
For a solo coach the person is the product, so the site leads with Nathan rather than burying him on an About page. Every claim traces back to something verifiable and the copy carries no invented figures. Where a number would have been persuasive but unfounded, the site says nothing instead.
Static pages, one moving part
The site is built with TanStack Start and React, and every public page is prerendered to static HTML at build time. The only server-side code is a single serverless function that takes an enquiry and sends notification and confirmation email over authenticated SMTP. All copy lives in one content module, so the text can move to a CMS later without touching the components.
The client approves the exact commit that ships
Staging and production are deliberately separate projects. Staging follows the main branch automatically and serves noindex headers, so review builds never compete with the real site in search. Production has no Git integration at all and is deployed by hand, only once Nathan has approved that same commit. A build audit checks routes, links, metadata, and discovery files before anything is deployed.
Handover was part of the work
The site is live at sprintcoach.co.nz with local SEO structured data and a documented launch checklist covering DNS, mailboxes, and the Google Business Profile. Nathan controls the domain and the mail, so the parts he needs to own are written down rather than left in my head.
Enquiry flow
The one moving part on a static site
Live site
See the finished project in use.