u/founder_ops

What's your process for checking property hazards before making an offer?

I'm looking for some honest feedback from people that have experienced buying property in NZ.

When you're researching a property, do you actually check council maps for things like flood prone areas, overland flow paths, coastal inundation, land stability, zoning, heritage overlays, significant trees and other natural hazards?

If you do, what's your experience been like?

I've always found the council GIS sites pretty clunky, especially on mobile, and not particularly easy to understand unless you already know what you're looking at.

I'm wondering if there would be any value in a simple mobile-friendly tool where you enter an address (or use your current location while standing outside a property) and it gives you a plain English summary of the relevant council data, along with a simple evidence map and links back to the original council information.

Would something like that be genuinely useful before making an offer, or are the existing council tools good enough?

Thanks.

Edit: Just to clarify, I'm not talking about replacing a LIM report or providing legal advice. I was thinking more about the very start of the buying process, when you're standing outside an open home or scrolling listings and want a quick summary of publicly available council information before deciding whether to investigate further. Think of it as a simpler, mobile-friendly way to access council GIS data, with links back to the official sources if you want to dig deeper.

reddit.com
u/founder_ops — 6 days ago
▲ 1 r/webdev

[ShowOff Saturday] iQWEB - Client ready site diagnostics (performance, SEO, trust, AI visibility) for agencies.

I’ve been building iQWEB (https://iqweb.ai) over the last few months with feedback from developers and agencies.

What it is

Paste a URL, get a structured report covering:

  • Performance + Core Web Vitals
  • Mobile experience
  • Technical SEO
  • Security & trust
  • Structure & accessibility
  • AI visibility (category/recommendation style checks, not just “AI score” fluff)

The output is meant to be client facing, not a raw PSI dump. Overview uses plain English issues and a prioritised fix plan. Signals/Evidence stay technical if you want more detail.

Why I built it

Help save agencies time stitching together Lighthouse, spreadsheets, and slide decks. Clients don’t want LCP and CLS explained in a meeting. They want “what’s wrong, why it matters, what to fix first.”

Stuff that might matter to this sub

  • Platform aware scoring for Webflow, Shopify, Wix, Squarespace: doesn’t treat platform-controlled hosting/headers as your fault
  • White label reports (logo, colours, agency branding)
  • Baselines in the dashboard to compare scans over time
  • No AI narrative on reports (tried that route; it was vague/wrong). Copy is templated from measured findings instead
  • v2 report UI: Overview / Signals / Evidence tabs, PDF export, shareable report links

Free tier

You can run scans from the homepage without signing up. Free account gives 5 scans and baseline tracking.

Would appreciate any feedback on

  1. Does the Overview read clearly enough for non-technical clients?
  2. Is AI visibility useful or gimmicky in your workflow?
  3. Anything that still feels too “developer report” vs “client deliverable”?

I’m the dev behind it (iQLABS, NZ). Happy to answer questions about methodology, scoring, or what’s on the roadmap.

Thanks to everyone who’s already helped in the past.

https://iqweb.ai

Example report: https://iqweb.ai/report.html?report_id=WEB-20260615-96415

u/founder_ops — 16 days ago