QBCC Home Warranty Insurance Calculator
A Next.js calculator for estimating Queensland QBCC home warranty insurance premiums and QLeave levy amounts. It also captures calculator-intent leads and shows contextual next-step offers based on the user's project type and value band.
Local Development
npm install
npm run dev
Open http://localhost:3000.
Environment Variables
NEXT_PUBLIC_GTM_ID=GTM-XXXXXXX
NEXT_PUBLIC_POSTHOG_KEY=phc_your_project_key
NEXT_PUBLIC_POSTHOG_HOST=https://us.i.posthog.com
RESEND_API_KEY=re_your_key_here
[email protected]
LEAD_EMAIL_FROM=QBCC Calculator <[email protected]>
[email protected]
DATABASE_URL=postgres://USER:PASSWORD@HOST/DB?sslmode=require
LEADS_WEBHOOK_URL=https://example.com/qbcc-leads
LEADS_WEBHOOK_SECRET=change-me
LEADS_STORAGE_MODE=local
LEADS_DATA_DIR=/tmp/qbcc-calculator-local-data
Production lead persistence requires DATABASE_URL (or POSTGRES_URL), Resend email delivery (RESEND_API_KEY + LEAD_NOTIFICATION_EMAIL), or LEADS_WEBHOOK_URL. Run npm run db:migrate after setting the database URL. Local JSON storage is useful for development, but it is disabled on Vercel even when LEADS_STORAGE_MODE=local because the Vercel filesystem is not durable. LEADS_DATA_DIR is honored only for non-Vercel local storage, allowing smoke tests to use isolated temporary storage without redirecting production persistence.
Lead Capture Loop
The calculator enriches each quote with:
- Work type, insurable value, units, QBCC premium, QLeave levy, and total estimate.
- Value band, project segment, QLeave applicability, and the recommended offer shown.
- A server-generated opaque lead reference and explicit
pending_review state shared by the API receipt and lead records.
- Non-PII PostHog submission properties for the opaque reference, review state, and quote segmentation; email, name, phone, and browser distinct ID are not used for lead identification in PostHog.
Current contextual offers are intentionally native to the calculator:
- Eligible new-build segments show a Trade Solar offer.
- Renovation pipeline projects show a Leva Relay offer only after the visitor selects builder / trade business.
- Smaller or multi-unit projects bias toward emailing a quote pack for follow-up.
Verification
npm run nuroc:preflight
npx tsc --noEmit
npm run build
npm run nuroc:lead-api-smoke
npm run lint
The lead API smoke boots the built app on loopback, removes Resend and webhook variables from the child process, uses an example.com address with temporary local storage, verifies invalid-request rejection and the opaque-reference/review-state round trip, then deletes the temporary data. For browser verification, start the app locally, calculate a new-build and renovation quote, confirm the contextual offer changes, and submit only a controlled test lead in development mode.
Deployment
The app is deployed on Vercel:
main: productionstaging: staging or preview validation
Before calling a production deploy complete, verify the canonical production URL loads the expected calculator and that lead capture posts to the configured webhook.
September 2026 release
lib/quote.ts is shared by the calculator, estimate URLs, lead API and WebMCP tools. It validates bounds, rounds the QLeave cost to cents before the $150,000 excluding-GST threshold, and attaches a rate version. Premium tables retain their existing interpolation behavior; confirm final amounts with QBCC.
Email receipts distinguish provider acceptance (sent) from a persisted request without confirmed customer email (saved). Webhook and email persistence run independently with bounded timeouts. Clients reuse an idempotency key for retries; upstream requests carry it through. The process-local receipt cache and abuse limiter are bounded, but are not a distributed database or durable retry queue. A durable receiver should deduplicate leadReference and own any delivery retry workflow. Resend acceptance does not prove inbox delivery.
For analytics, configure either NEXT_PUBLIC_GTM_ID or direct NEXT_PUBLIC_GA_MEASUREMENT_ID. GTM takes precedence. Configure GA4 Enhanced Measurement consistently to avoid a second history-based pageview. PostHog records one first result, distinct estimate revisions, explicit user actions and visible offer impressions; person profiles, autocapture and session replay are disabled. Dashboard/property access is needed to verify ingestion.
WebMCP uses document.modelContext with a compatibility fallback to navigator.modelContext. Supported browsers expose calculate_estimate and get_rate_methodology; unsupported browsers retain the ordinary form. Tools do not email, lodge, purchase insurance or capture contact details. Native registration and execution were validated in the Codex in-app browser.
Run npm test, npm run build, npm run nuroc:lead-api-smoke, and npm run verify:canonical. The production build enforces lint, regression tests and type checking. The GitHub workflow is configured for Node 22; it was manually disabled in repository settings at release time. Next.js 16 uses the webpack build path for compatibility with the existing project.
