Custom websites.
Designed, not generated.

You get a fixed price after the intro call, based on scope. A marketing site in Astro with Sanity costs less than an app with login and integrations with your systems. The biggest cost drivers are the number of page types, languages and integrations, and how much animation the site needs.

A web app or client portal costs more than a marketing site, because it also handles login, roles, data and connections to other systems. I price it by concrete features: how many roles, which screens, which integrations. It often pays to start with a prototype built in days and validate the scope before building the full app. You get a fixed price after the intro call and brief.

A typical custom website launches in 2–3 weeks. Apps with login, roles and integrations take longer, depending on scope. Code starts only after you approve the Figma design, so the timeline also depends on how quickly we agree on it. You get an exact schedule with the proposal.

For a smaller site, Sanity's free plan is often enough, and it covers up to 20 users. The paid Growth plan costs $15 per user per month and suits larger teams. Hosting on Vercel requires the Pro plan for commercial sites, from $20 a month. The accounts are in your name, and you pay only for what you actually use.

I invoice as a Czech sole trader and I'm not VAT-registered, so the price in the proposal is final. The payment schedule, meaning how much is due upfront and how much at launch, is part of the proposal and agreed in advance. Ongoing work after launch is billed hourly or as a monthly retainer.

Scope changes are normal, and I plan for them. I describe and price any new feature or page first and start only once you approve it, so the cost never catches you off guard. Small tweaks within the approved design are handled as we go. If changes pile up, we move them to a post-launch phase so the launch date holds.

Because a site in Astro or Next.js doesn't rely on plugins that need constant updates, and its pages are prebuilt and served from a global CDN. You get a faster site, a smaller attack surface, and content you can reuse beyond the website through Sanity. WordPress has its place, and I help companies move off it. I go custom where themes and plugins start holding you back.

Choose Webflow if you need a marketing site that you'll edit yourself after launch, page layouts included. Custom development makes sense when your content lives in more than one place, when you need custom logic, login or an app, or when the platform starts limiting you. As a Webflow Premium Partner I do both, so I'll tell you when the cheaper option is enough.

You do. I hand over the code in a Git repository, the content lives in your own Sanity project, and hosting and the domain run on your accounts. You're not locked in to me: if you ever want to, any developer who knows Astro or Next.js can take the site over.

The site runs on Vercel and is served from a global CDN, while Sanity hosts the content in its own cloud. Most pages are static, so there's no server-side database or plugins to attack. Sanity handles logins to the editor, with roles that control who can change what, and HTTPS comes standard.

A static site on a CDN scales on its own, with no intervention. Pages are served from the nearest edge location, so a traffic spike from a campaign or press coverage won't slow it down. Dynamic parts and apps run on Vercel as serverless functions that scale with load, and content comes from Sanity through its API CDN.

Yes. I build on mainstream technologies (Astro, Next.js, TypeScript and Sanity) that any modern front-end team knows. The content schema is code and lives in Git with the rest of the site, so the full change history is there. At handover, I walk your team through the project structure and deployment.

A headless CMS manages only content and leaves the look to the front end, so the same content can power your website, an app and AI tools. I choose Sanity because it stores content as structured data, and its editing environment, Sanity Studio, can be shaped around your team. It also offers editing right in the site preview, scheduled releases and real-time collaboration.

Yes. I build Sanity Studio for the people who will use it, not for developers. Fields are named after your content, anything you don't need is hidden, and validation flags mistakes before they reach the site. With visual editing, you click a text on the page and edit it right there. After launch, I'll show you how to manage the site.

Yes. Sanity can translate whole documents or individual fields, depending on whether language versions differ in structure or only in text. Each version gets its own URL, metadata and hreflang on the site, so search engines don't treat it as duplicate content. AI can draft the translations right inside Sanity, and your team just reviews them.

Yes. Every change starts as a draft that you see in a live preview of the site, and it goes public only when you publish it. You can bundle several changes into one release, review it and schedule it for a set time. Clicking any text or image in the preview takes you straight to the field where it's edited.

Sanity's free plan covers up to 20 users, the paid Growth plan up to 50, and larger teams move to Enterprise. Editing happens in real time: you see who's in a document, and changes merge live. I can set up the Studio so sales, marketing and translators each see mainly their own content.

You upload an image to Sanity once, and the site generates the right size and a modern format for every device. You mark the focal point in the editor, so the photo crops correctly on mobile and desktop. AI can suggest alt text for you to approve. For video, I recommend a dedicated video host so the site stays fast.

Web apps, yes: I build client portals, dashboards, configurators and internal tools in Next.js with Sanity. I also design app UI/UX in Figma, mobile included, and the app's content can come from the same Sanity as your website. Bigger projects that need a full team, I build with Grevo, the studio I co-founded.

I build agents and automations that take routine work off your team and work with your own content and data. Typical examples: translations and alt text in Sanity, sorting website inquiries, drafting proposals from your CRM, or an internal assistant that answers from your documentation. The agent prepares a draft, and a person approves it before anything goes out.

Yes. If the system has an API, I connect your site or app to it directly in code. A website inquiry can create a contact in your CRM, an order can flow into your ERP, and an invoice into your accounting software. For simpler flows, Make or Zapier automations are quicker to set up and easier to change.

Yes, when it's designed properly: the AI gets access only to the data it needs for the task, and it publishes or changes nothing without a person's approval. I use APIs from major providers that don't train their models on API data by default. Sensitive data can be left out of AI entirely or anonymized before it's sent.

AI features are billed by usage: the more text an agent processes and the more capable the model, the more it costs. Routine tasks like translation or sorting run fine on cheaper models, while complex reasoning is worth a more expensive one. I'll estimate your monthly cost from the prototype, using the real volume of your data.

Yes. The key is that every old URL gets a 301 redirect to its new address and none ends up as a 404. I keep page titles, descriptions and article URLs where possible, and monitor Search Console after launch. A short dip after a migration is normal; lasting losses mostly come from missing redirects.

By making it easy for AI to understand and cite: every key page opens with a direct answer, the content is in clean HTML, and your details are consistent everywhere. I add structured data and llms.txt, and let AI crawlers in through robots.txt. Then we build topic clusters of articles that show your expertise. It doesn't replace classic SEO; it extends it.

Structured data (JSON-LD) describes in machine-readable form who you are, what you offer and what a page is about, while llms.txt gives language models a clear map of your most important content. I treat both as cheap insurance, not magic: Google doesn't require structured data for AI search and doesn't use llms.txt. Microsoft, however, says schema helps Bing and Copilot understand content.

I aim for a Lighthouse score of 95–100 on mobile and all three Core Web Vitals in the green. Static output, JavaScript only where it's needed, modern image formats and self-hosted fonts get it there. I measure speed before launch and keep an eye on it as the site grows.

Yes. I set up tracking around what you need to know: where visitors come from, what they read and how many send an inquiry. Depending on your needs, that's Google Analytics 4 or cookieless analytics, plus Search Console. Conversions such as form submissions or email clicks are tracked as separate events, and the cookie banner is set up to meet the rules.

Google usually indexes new and updated pages within a few days, but ranking changes tend to show over weeks to months. I can speed up indexing by submitting the sitemap and key URLs in Search Console. AI search engines pick up changes as often as their crawlers revisit the site, which is why robots.txt has to let them in.

After the first call, I put together the scope, a plan and a fixed price, and once you agree, we start with a design in Figma. Code starts only after you approve the design. Then I build the site, test speed and accessibility, launch it and show you how to manage it. You deal with me directly the whole time, not with an account manager.

Yes. You design, I build: development from your designs in Astro, Next.js or Webflow, white-label under your brand if you prefer. I turn the design into code precisely and hand it over in a state anyone can pick up. I work with studios long term and on repeat projects, across websites, animation and CMS.

I stay on hand. I check that the site runs, gets indexed and returns no errors, and I fine-tune whatever real traffic reveals. You already know how to manage the site, so everyday content is in your hands. New sections, features and campaigns get added as you need them, with no agency queue.

Yes, in two ways: at an hourly rate, where you pay only for work actually done, or as a monthly retainer with reserved capacity. Maintenance covers dependency updates, speed and security checks and small fixes; development covers new pages, features and integrations. We'll pick what fits based on how often your site changes.

Yes, I'll sign an NDA before you share the details of your project. Send me your own version, or I'll provide a simple mutual one. My access to your systems and data stays limited to what the project actually needs, and anything I no longer need is removed after handover.

Directly with me, no middlemen: the person who designs and builds your site is the one answering you. Day-to-day questions go by email or a shared channel, bigger decisions on a short call. You see the design in progress in Figma and the site on a staging URL, so you always know where things stand.