01 · Local marketSEO shaped for Australian search
Website delivery for a New Zealand organisation begins with ownership, customer journeys and operating constraints rather than a preferred technology. Discovery identifies who needs the site, which actions matter, who supplies and approves content, what systems must connect and who will maintain each area after release. A business serving several regions may need clear service boundaries and inquiry routing. Retail requirements can include delivery, returns and the accurate presentation of Afterpay or Laybuy where offered. Property journeys may need to explain the relationship between the owned site, Trade Me Property and realestate.co.nz rather than duplicating portal listings without a purpose. New Zealand English and -ise spelling apply to client-approved interface copy. Prices and financial references are shown in NZD when public content includes them. Requirements are converted into page maps, component behaviour, form rules, analytics events and acceptance criteria before implementation is treated as complete. Responsive interfaces are checked across relevant devices, with keyboard operation, labels, errors and content hierarchy reviewed as working behaviour. Manila morning falls in New Zealand early afternoon, so a same-day reply is structurally possible for every delivery ticket. Review environments and issue records make that window useful without overstating it as round-the-clock support. Release planning names account owners, backups, domain and hosting responsibilities, approval authority and the response to a critical problem. Documentation then gives the New Zealand team a practical basis for content updates, access control and future maintenance.
02 · ComplianceNew Zealand privacy and promotion requirements translated into web acceptance criteria
The Privacy Act 2020 directly changes web requirements when forms, analytics, accounts or integrations handle personal information. We document what is collected, why it is needed, where it goes, who can access it and which third parties are involved. Forms minimise unnecessary fields, permission levels follow ownership, and privacy notices are connected to the actual data flow. The Unsolicited Electronic Messages Act 2007 changes newsletter forms and automated follow-up by requiring appropriate consent, sender identification and a working unsubscribe route. The Commerce Commission and the Fair Trading Act affect prices, stock, comparisons, guarantees, reviews and performance claims. This creates acceptance criteria for visible conditions, consistent checkout information and content approval rather than relying on a footer disclaimer. The Advertising Standards Authority codes shape promotional landing pages, endorsements and sponsored material, so claim evidence and disclosure presentation are reviewed in the interface. Medsafe and the Medicines Act change health and therapeutic sites by requiring claim classification, approved content and controls around testimonials or product indications. The Financial Markets Authority changes financial pages, calculators and lead journeys by requiring balanced promotion, suitable qualification prominence and client approval for material statements. These regulators alter component design, form behaviour, publishing permissions, review states and launch checks. Accessibility is handled as practical product quality through semantic structure, keyboard use, readable contrast, clear labels and useful error feedback.
03 · ProofA website scope the New Zealand team can verify
This page does not attribute a website result to a New Zealand client. Proof is limited to the deliverables, decisions and checks visible during the client’s own project. Scope may include requirements workshops, information architecture, responsive components, CMS configuration, content implementation, form routing, analytics events, search foundations, performance work, accessibility review, integration checks, release preparation and documentation. Requirements become acceptance criteria so stakeholders can inspect whether an agreed behaviour is complete. A review environment supports comments before release, while issue records preserve decisions, defects, ownership and resolution status. Form destinations, automated messages, analytics events and key journeys can be tested against the approved specification. Release preparation identifies account owners, backups, domain and hosting responsibilities, approval authority and the response if an important journey fails. Handover records distinguish routine content editing from restricted technical access and explain where maintenance responsibility sits. These artefacts give the client concrete evidence of delivery quality without inventing traffic, conversion, revenue or testimonial proof. A later case study should only replace this scope description when the client authorises publication and the original condition, delivered work and observation method are clear.
04 · PricingSEO pricing in NZD
Comparable local agency rangeNZD $4,000 to NZD $12,000
BX published rangeNZD $2,500 to NZD $6,600
The NZD figures provide a monthly engagement frame rather than a fixed project quote. Website pricing follows requirements, page and component scope, CMS work, integrations, content readiness, accessibility checks, migration effort and release support. Hosting, paid software, licences, external production and continuing maintenance are identified separately where applicable.
