Web Development Company in Auckland

A scoped Auckland marketing site at our rates runs NZD $35,000 to $90,000 over six to ten weeks, covering discovery, design system, build, bilingual Te Reo Maori and English content scaffolding, CMS, and launch. A multi-section corporate or retail brand site with custom design, Shopify Plus or headless commerce, and CRM integration typically lands at NZD $90,000 to $250,000. A full SaaS web app or government citizen-facing platform with RealMe integration, complex CMS, and multi-region hosting ranges from NZD $250,000 to $900,000. USD pricing for SaaS exporters serving offshore markets starts roughly 40 percent lower at our offshore hub rates. Auckland sits above Wellington and Christchurch on cost because of local talent rates. Fixed-fee proposals only.

Yes. Te Reo Maori is an official language of Aotearoa New Zealand under the Maori Language Act 2016, and citizen-facing government services as well as iwi-partnered organisations increasingly expect parallel Te Reo and English experiences. We model bilingual content in Sanity, Contentful, or Storyblok with Te Taura Whiri i te Reo Maori macron handling, separate URL roots (te-reo and en), hreflang and lang attributes set correctly, and translation workflows that respect kaitiakitanga over translated content. For builds involving iwi-specific reo or imagery we scope mana whenua consultation into discovery. Codazz does not pretend to be the source of Te Reo content, but we build the platform so iwi and translation partners can publish without engineering.

Yes. RealMe is the NZ Government's verified identity service operated by the Department of Internal Affairs. For citizen-facing applications, council services, and regulated industry portals (financial services, health, education) we integrate RealMe login and verified identity assertions, scope the system against the Digital Identity Services Trust Framework Act 2023 expectations where relevant, and keep authentication and identity data inside NZ-resident infrastructure. Build patterns follow DIA technical guidance, the Government Service Standard, and the NZ Government Web Usability Standard. We coordinate with the agency Privacy Officer and Chief Digital Officer team before any code touches a RealMe assertion.

We default to WCAG 2.2 AA, aligned with the NZ Government Web Accessibility Standard 1.1 for public sector clients and the Human Rights Act 1993 prohibition on disability discrimination for private sector. Builds run axe-core, Pa11y, and manual screen reader testing (NVDA, JAWS, VoiceOver) into every PR. We deliver an accessibility conformance report, a VPAT-equivalent statement, and a remediation log. For Crown clients we align with the Office for Disability Issues guidance and Accessibility-friendly Information Standard where it applies. Builds destined for AU markets layer DDA Premises Standards alignment, and EU customer-facing surfaces ship under EN 301 549 and the European Accessibility Act 2025 from day one.

We target Lighthouse 95+ on mobile and Core Web Vitals in the green band for LCP (under 2.5s), INP (under 200ms), and CLS (under 0.1). Auckland mobile traffic over 4G and 5G on Spark, One NZ, and 2degrees networks routinely lands at 1.2 to 1.8 second LCP for our Next.js 15 builds hosted on Vercel or Cloudflare with images served through Sanity, Cloudinary, or Cloudflare Images. For NZ-resident builds on AWS Auckland Local Zone we route static assets through CloudFront with origin in Sydney ap-southeast-2 and dynamic inference at the Local Zone. Performance budgets ship in the design system, regress in CI, and live on a 30-day post-launch watch.

Yes. The NZ Government Web Usability Standard 1.3 and Web Accessibility Standard 1.1, mandated for central government public-facing websites and recommended for the wider state sector, set requirements on navigation, search, plain English, accessibility (WCAG 2.2 AA), and content design. Our public sector engagements ship a Standards conformance statement, design patterns aligned with the Government Service Design Principles, and a content style guide aligned with the Plain Language Act 2022 obligations. We coordinate with Government Communications Security Bureau guidance on hosting and the Government Chief Digital Officer team where required, and we deliver OIA-defensible content workflows out of the box.

The Privacy Act 2020 does not include a GDPR-style consent banner mandate, but the Office of the Privacy Commissioner's guidance on cookies and analytics, combined with cross-border restrictions under IPP 12, makes default-on GA4 risky for Crown and regulated clients. Our standard pattern offers a first-party analytics option (PostHog self-hosted, Matomo, Plausible) with explicit consent and EU-friendly defaults for clients who also serve EU and UK customers. We document IPP 12 cross-border flows in the privacy policy, deliver an OPC-aligned consent UX where third-party trackers are in scope, and avoid the dark-pattern banners that erode trust and invite a Compliance Notice.

Yes. Auckland SaaS exporters typically need NZD for local customers, AUD for trans-Tasman, USD for North America, GBP for the UK, and EUR for the rest of Europe. We integrate Stripe Tax for GST (NZ 15 percent), GST AU 10 percent, US sales tax via Avalara or Stripe Tax, UK and EU VAT, and route inference and storage to the regional AWS instance closest to the customer. Pricing pages render local currency from IP and account settings, tax-inclusive vs tax-exclusive display follows local convention (NZ and AU show inclusive, US shows exclusive), and the checkout integrates Afterpay, Laybuy, Klarna, and PayPal where the market expects them. Currency and tax logic ship in the design system as configuration, not custom code per market.