The index
Heat pump buying guide, 58 pages
Regional pages, cost guides and a sizing calculator, all statically generated.
nz-mortgages.co.nzSix mortgage calculators
Repayments, borrowing power, break fees and offset comparisons, computed client-side with no data leaving the browser.
nz-visas.co.nzNZ immigration reference, 37 pages
Visa categories and planning tools, written to stay on the right side of the line between information and regulated advice.
nz-funerals.co.nzFuneral director directory
129 firms transcribed from the FDANZ member register, each page carrying the date the register was read.
rate-your-apprenticeship.co.nzApprenticeship reviews, 74 pages
The best-performing site in the group on real mobile click-through.
everything-mangawhai.co.nzLocal area guide
Every venue listed with a link to its own site and the date we read its hours.
nz-honey.co.nzNew Zealand honey varieties
Eleven single-source honeys explained by floral source, region and season.
spanish-lessons-near-me.co.nzTutor matching, with payments
Stripe checkout, city and lesson-type pages, and the only site in the group ranking on page one for its head term.
All live, all built here, all still maintained. These are my own ventures rather than commissions — which is why I can show you what happened after launch instead of what it looked like on day one.
How it gets built
Static by default
Pages are built once and served from a CDN. Nothing waits on a database to draw, so it is fast everywhere and it stays up on the day it gets attention.
Search handled while building
Canonicals, sitemaps, structured data per page type, headings that match how people actually search. Done during the build because retrofitting it costs more than doing it once.
No stack you did not ask for
Content lives in typed files, or a CMS you specifically wanted. Nothing to keep patched, and nothing that breaks because a plugin you never chose updated itself.
Payments done properly
Stripe checkout, subscriptions and refunds including the parts usually skipped: webhooks, idempotency, and a refund path that works when someone is angry.
Awkward questions, answered first
- How big is the studio?
- One person, and that is the whole answer. You deal with whoever writes the code. It is the main advantage and also the constraint — I take a small number of projects at a time and would rather say no than be the reason yours is late.
- Is the work below for clients?
- No. Every site listed is one I built and still run myself. Saying otherwise would be the one lie that matters on a page like this. It does mean the work is mine end to end, and that I have lived with every decision far longer than a client engagement lasts.
- What does it cost?
- It depends on scope, and a published tier would not describe your project. Send a brief with a rough budget and you will get a straight answer — including that it is not worth paying me for, where that is true.
- Will you work on a site that already exists?
- Often. Moving a site off Webflow, WordPress or Squarespace into Next.js is a good share of the work. Doing it without losing rankings is mostly careful redirect mapping and holding your nerve about URLs.
- What do you not do?
- Brand identity from nothing, ongoing social, paid ads, or anything needing a design team. If that is what you need you will hear it in the first reply rather than after an invoice.
Start a project
Tell me what you are trying to build and what is currently in the way. You will get a real reply from the person who would do the work, including an honest no if that is the right answer.