How much does a 3D animated website cost?

Projects start from $1,500 for a focused interactive landing page, $2,800 for a SaaS or startup website, and $4,000+ for a full multi-page animated experience.

How long does it take to build a custom animated website?

A landing page typically takes 2 to 3 weeks. A full multi-page website runs 4 to 6 weeks depending on scope and feedback cycles.

Do you work with clients outside Europe?

Yes — fully remote, worldwide. Most current and past clients are in the US and UK. Time-zone overlap is handled via async communication plus scheduled video calls.

What technologies do you use to build websites?

Next.js for the framework, Three.js and WebGL for 3D scenes, GSAP for scroll and micro-animations, and Cloudflare Pages for static deployment. No WordPress, no Webflow, no templates.

Can you redesign or rebuild my existing website?

Absolutely. Redesigns are a significant part of the work. If your current site looks dated, loads slowly, or fails to convert, a focused rebuild usually pays for itself quickly.

LOG 06 · STYLING

Tailwind CSS v4

Tailwind v4 for fast, consistent layout work — paired with hand-written CSS for the parts (3D stacking, custom shader overlays, keyframe animation) that need pixel-level control a utility class can’t express.

Utilities for structure, CSS for craft

Tailwind handles the parts of a layout that are genuinely repetitive — spacing scales, flex/grid structure, responsive breakpoints — fast, and without inventing a new class name for every div. But the parts of a site that make it feel custom rather than templated (a specific oklch color ramp, a z-index choreography between a WebGL canvas and a CSS3D layer, a hand-tuned keyframe animation) are still hand-written CSS, because that's where a utility class stops being faster than just writing the three lines of CSS directly.

Tailwind v4's CSS-first configuration — real `@theme` custom properties instead of a JS config object — makes that split easier to maintain: the same design tokens (color, spacing) are addressable from both the utility classes and the hand-written CSS sitting right next to them.