A form that respects both visitors and operators
The contact flow asks for only the information needed to start a useful conversation: name, email, optional company, and message. A clear response-time promise lowers uncertainty for visitors and helps the business set expectations.
Static-friendly by design
The frontend can submit to a Cloud Function when configured, but it also keeps a mailto fallback. That means a customer can launch a static site first and connect the richer inquiry pipeline later without rebuilding the page.
Privacy posture
The planned backend stores hashed email and IP values for analytics and rate limiting. Raw IP addresses are never stored, and email delivery is guarded by an environment feature flag.