Web design for insurance brokers in NZ starts with two practical questions: what can this brokerage help with, and what should a visitor do next? A useful website makes the advice scope and contact routes clear while giving the brokerage a manageable process for approving and maintaining its information.
This is an agency-authored website planning guide, not insurance advice or a compliance certification. No Brainer Creative is based in Te AtatΕ« Peninsula, Auckland. The brokerage’s responsible people should approve its regulatory statements and customer journeys before launch.
Start with the brokerage’s actual service model
Write a short brief identifying the legal trading entity, intended clients, insurance services, advice limitations and the people responsible for content approval. Do not describe a business as independent, whole-of-market or able to advise on every insurer unless that accurately reflects its arrangements and approved wording.
- New enquiries: help visitors identify whether their needs fit the services offered and request a conversation.
- Existing clients: provide a clear route for policy questions, renewals and changes.
- Claims enquiries: use the brokerageβs approved instructions, contacts and availability. Do not promise claim acceptance or emergency response that the business cannot provide.
Plan disclosure with the responsible reviewer
The FMA explains that a financial advice provider with a website must make certain information publicly available, with other disclosures required at relevant advice stages. Its guidance addresses clarity, prominence, readability and format. A web page does not replace the full advice process. See the FMA’s financial advice provider guidance.
Agree the approved disclosure and complaints content, how it will be reached, and who maintains it. Do not assume every PDF is prohibited or that an HTML page automatically meets the requirements. Check the proposed format and storage arrangements with the reviewer, then test the real implementation.
Keep registration and licensing language accurate. The FMA’s FSPR explanation makes clear that registration alone does not establish that a business is licensed or regulated by the FMA. Verify the brokerageβs specific status and relationships before publishing badges or claims.
Separate enquiries from quotes and cover
A simple initial enquiry can ask for a name, contact preference and broad reason for getting in touch. Decide what information is necessary at this stage before adding detailed personal, medical or financial questions. Agree how information is collected, accessed and retained, including any external form or CRM provider.
Use button and confirmation wording that describes the actual outcome: for example, “Request a conversation” when that is what happens. A submitted form is not a confirmed appointment, an insurer-issued quote or active cover. If a booking system is included, show its availability rules and test the confirmation process separately.
For a calculator, document who supplies the rates or assumptions, what the result represents and when it expires. Identify the owner of future changes and any insurer approval needed. An attractive calculator without a reliable maintenance process can create more work than a well-designed enquiry route.
Compare implementation scope rather than platform verdicts
| Project option | Potential fit | Evidence to request |
|---|---|---|
| Improve the existing website | The current system supports approved content and necessary customer journeys. | A list of actual limitations, proposed fixes and acceptance checks. |
| Rebuild on a managed CMS | Content ownership, support or the existing structure needs a substantial change. | Migration plan, editing demonstration, redirects, backup and support responsibilities. |
| Add a quoting or client integration | The brokerage has a defined process and an approved provider connection. | Supported capabilities, permissions, failure handling, data flow and ongoing maintenance. |
| Combine branding and web work | There is an agreed identity or messaging problem to resolve. | Approved deliverables and dependencies, with website and branding responsibilities explicit. |
WordPress, Wix, Squarespace and other systems should be assessed against the requirements of the specific build. Do not rebuild solely because an article labels one platform unsuitable. Compare editing access, document handling, forms, accessibility, integrations, ownership and ongoing costs. Our web design service describes the website work available from No Brainer.
Make search pages useful and geographically accurate
Create service pages where there is a distinct customer need and enough approved information to answer it. Explain who the service is for, its scope and how to start an enquiry without inventing premiums, policy features or eligibility. Keep links between relevant services, the team and contact details clear.
Describe real locations and service arrangements. A brokerage serving a region remotely should not imply a staffed office in every suburb. Separate location pages need useful local information, not a place-name substitution. Search rankings depend on factors beyond a website build; publication is not evidence of a top-three position.
A practical launch and handover checklist
- Record approval for service descriptions, regulatory wording, insurer names and any permitted logos.
- Test disclosure links and documents, including readable text, navigation and access without unexpected sign-in.
- Check phone and email links, keyboard navigation, form labels and error messages at desktop and phone widths.
- With an agreed controlled test, verify form receipt, routing, acknowledgement wording and any CRM handoff. Exclude test records from enquiry reporting.
- For migration, preserve useful URLs or map specific redirects; check page titles, canonicals and sitemap discovery.
- Provide named content owners, update instructions, support contacts and a process for failed enquiries or integrations.
Define success using suitable enquiries and a functioning customer journey. Keep search visibility, website clicks, submitted requests and confirmed business outcomes separate. Agree what will be measured before assuming a new design has improved conversion.
Discuss the website scope
Bring your current URL, service list, approved disclosure material and examples of the journeys you need. No Brainer can discuss website design and implementation scope with you; the brokerage retains responsibility for approval of its financial advice and regulatory content. Contact No Brainer about your website.
FAQ
What should an insurance broker website help visitors do?
Understand the services and advice scope, find approved disclosure and complaints information, and choose the right contact route for a new enquiry or existing policy. The right structure depends on the brokerage and its clients.
How much does an insurance broker website cost?
Request an itemised scope covering content, approval rounds, document management, enquiry handling, migration, integrations and ongoing support. A platform label or industry average does not establish the cost of your project.
Does an FSP number prove that a business is licensed?
No. FSPR registration and licensing are distinct. Confirm the exact legal entity, licence or authorised-body relationship and approved wording with the person responsible for the brokerage’s compliance.
Must every disclosure be an HTML page rather than a PDF?
Do not decide compliance from the file format alone. Agree the applicable information, prominence, readability, access and storage requirements with the responsible reviewer. Test the chosen pages and documents on phones and with assistive technology.
Can an insurance broker use Wix, Squarespace or WordPress?
Evaluate the actual implementation against approved content, document updates, accessibility, form handling, integrations, ownership and support. No platform automatically certifies compliance, and a rebuild should address a demonstrated limitation.
How long will a broker website project take?
Agree the schedule after reviewing page inventory, approved copy, document owners, migration and integration dependencies. Include time for brokerage approval and acceptance testing rather than relying on a universal delivery promise.
Does the website need an instant quote calculator?
Only include one where its purpose, data source, assumptions, limitations and maintenance are approved. An illustrative estimate, a request for a quote and an insurer-issued quote are different outcomes. Do not imply cover is active when a form is submitted.
When should website content be reviewed?
Assign owners and review triggers for service scope, insurer relationships, adviser details, disclosures, complaints routes and contact information. Test important journeys after changes. Redesign when evidence identifies a problem rather than on a fixed age rule.