fynoAI website — marketing site with Puck page builder, newsletter and CRM on Laravel 13

A marketing website for a SaaS product is no longer a brochure. It is an SEO landing page, a citation source for ChatGPT, Perplexity and Claude, a multilingual multi-domain site for AT/DE/global — and above all the one place where leads touch the product for the first time. That turns the website into the intake channel for the entire sales pipeline.

Our requirements for fynoAI:

• Editable without code — marketing assembles pages from blocks without touching Blade templates
• First-party leads — beta requests, contact forms and newsletter signups must not disappear into HubSpot or Mailchimp but land in a dedicated CRM in the admin
• Newsletter in the same system — double opt-in, campaign sending, feedback and bounce tracking; no Mailchimp lock-in
• AI citation ready — `llms.txt` and Schema.org JSON-LD, citation-friendly text structure
• Multi-domain + multi-locale — .at / .de / .com with automatic locale resolution, hreflang sitemap
• GDPR-compliant analytics — GA4 with Consent Mode v2, server-side Measurement Protocol, bot filtering on the server
• EU hosting end to end — web, database and mail in the EU, no US hyperscaler, no Schrems-II grey zone

Laravel 13 as the backend — deliberately not Next.js, WordPress or Webflow. Laravel ships with Filament v4 as the admin, Blade rendering for SSR, queues, mail stack and migrations — all in one place. One codebase, one framework, no second toolset to maintain.

Filament v4 + Filament Shield as admin. Editorial, pages, newsletter, CRM, redirects, glossary and site settings all live in the Filament panel. Filament Shield provides roles and granular abilities per resource (marketing can edit pages, sales sees only the CRM resources, dev sees everything). Spatie Permission under the hood.

Puck as a visual page builder. We embed `@puckeditor/core` (React, inside the Filament admin) as the drag-and-drop editor. Editors compose pages from blocks — hero, pillar, bento, FAQ, feature grid, module, CTA. The result is not shortcode chaos but structured block JSON, versioned in `page_versions` (with rollback). On request, Laravel renders it into 100 % server-generated Blade HTML with Alpine.js for small interactions.

Supabase as managed Postgres — nothing else. Production DB runs on Supabase (`eu-central-1`), the Laravel container connects directly through the connection pooler (session mode for migrations, transaction mode for web). Not in use: Supabase Auth, Storage, Realtime, Edge Functions or REST — Laravel owns auth, media lives in Spatie Media Library. The upside: managed Postgres with backups and pooler, without locking into a proprietary Supabase SDK.

Newsletter stack in-house. The tables `newsletter_subscribers`, `newsletter_campaigns`, `newsletter_feedback` and `email_logs` cover double opt-in, campaigns, recipient feedback and delivery logs. Delivery via Resend Laravel, templates as Blade mails. The outcome: the subscriber list is our asset, not Mailchimp's.

CRM in the admin. Beta requests, contact messages and lead flows roll into `beta_requests` → status pipeline (`crm_status_changes`) → appointments (`crm_appointments`) → notes (`crm_notes`). Assignment to users, Spatie Activity Log as the audit trail, magic login tokens for collaborators without password setup. Every lead is traceable, no shadow tables in Notion.

First-party analytics + GA4 Consent Mode v2. `page_visits` and `page_events` flow straight into our own Postgres, `jaybizzle/crawler-detect` filters bots server-side before anything is logged. In parallel GA4 runs with Consent Mode v2 and server-side Measurement Protocol via a dedicated subdomain endpoint. Cookie banner only for the categories that are really needed — default is privacy-first.

Multi-domain, multi-locale, AI citation. `mcamara/laravel-localization` at the URL layer, Spatie Translatable at the model layer (every content field translatable), Spatie Sitemap for hreflang maps, Spatie Schema-Org for JSON-LD (Organization, SoftwareApplication, FAQPage). On top of that, dedicated `llms.txt` and `llms-full.txt` per page for ChatGPT / Perplexity / Claude as citation sources.

Deployment on Fly.io in the EU. Dockerised Laravel container, Vite + Tailwind v4 in the build, queue workers for dispatch and webhooks, Resend for transactional mail, Spatie Media Library for asset management. Deploy-based rollback, no US hyperscaler, no third-party CDN risk around cookie tracking.