Summary

Process

FAQs

• Do I own all the files?

  Yes. You'll get the Webflow project, Figma design files, Spline source files, and any documentation. Full ownership, no licensing weirdness, no vendor lock-in. The only thing you can't do is resell my work as your own template—but you weren't planning that anyway, right?

• Can you integrate with my existing tools?

  Most likely. Webflow plays nice with popular tools—email platforms (Mailchimp, ConvertKit), CRMs (HubSpot), analytics (GA4, Hotjar), payment systems (Stripe), and more. If it has an API or embed code, we can probably make it work. Some integrations need Zapier as the middleman.

• Will the site work on older devices?

  Yes, with smart degradation. Modern devices get the full 3D experience; older or lower-powered devices get optimized versions or static fallbacks. Nobody gets a broken experience—some just get the "performance mode" version, like playing on lower graphics settings.

• Do all pages need 3D elements?

  Absolutely not. Strategic 3D placement works best—hero sections, feature showcases, or key interaction points. Overusing 3D is like adding a cutscene to every menu screen: annoying and performance-killing. We'll plan where 3D adds value and where clean design does the job.

• How many pages are included?

  Depends on your package, but typically 1-6 pages (Home, About, Services, Blog/Shop, Contact, etc.). Each additional page or complex section is scoped separately. I won't surprise you with "page 3 of 47" halfway through like some bloated open-world game.

• What's included in CMS setup?

  Custom CMS collections for your dynamic content (blogs, portfolios, team members, etc.), organized fields, and initial content population. You'll be able to add/edit/delete items yourself afterward. I'll also add filtering, pagination, and dynamic pages so everything feels native, not bolted-on.