Do you only work with SaaS companies?

No. I work with companies whose product is hard to explain: SaaS, AI, fintech, deep tech and B2B. SaaS is where that problem shows up most often.

How long does a SaaS website take?

About three weeks: one for the positioning sprint, then two for most builds. Larger sites with a CMS take a little longer. You get a fixed timeline with the quote.

Can you match our product's design system?

Yes, and I recommend it. When the marketing site and the app share type, spacing and components, signing up feels like one product instead of two.

Do you redesign existing sites without losing SEO?

Yes. Every redesign includes a URL inventory and a 301 redirect map, so pages that rank keep their traffic after launch.

How long does a typical project take?

About three weeks. The positioning sprint takes one week, then most builds go live two weeks later; larger sites with a CMS take a little longer. You get a fixed timeline with the quote, at the end of the sprint.

Who do you work with?

Companies whose product is hard to explain, usually in AI, SaaS, fintech, deep tech or B2B, from funded startups to established teams that want a premium site. If a buyer has to understand something before they sign, it is a fit. I work remotely with teams anywhere, in English and French.

AI can build a website now. Why does this cost what it costs?

Because the part AI does well is the part that was never the problem. It will give you pages. It will not decide what your company should claim, work out which of the eleven people on the buying committee is actually blocking the deal, or write the paragraph that makes your product land with someone who is not an engineer. That is the work here, and the build is what proves it. If all you need is pages, use a generator and keep the money.

Do you offer a free audit?

Yes. Every project starts with a 15-minute call and a free written audit of your current site. No charge, no obligation.

What stack do you build on?

Astro and Next.js, with TypeScript and Tailwind. A headless CMS when the team needs one. I optimize for Core Web Vitals on every project.

What happens after launch?

You get clean, documented code and analytics wired up. I stay reachable for fixes and follow-on work.

You are a new studio. Why should I trust you?

Because you can judge the work instead of a logo wall. Every project on this page was positioned, designed and built by me, and every claim on this site is checkable: open Krust, Orba or Exogen, run the page through PageSpeed, read my background. On top of that, the audit is free and the sprint is credited against the build, so the only thing you risk on a first conversation is 15 minutes.

What if I do not like the design?

You see the direction in week one, before the build, and you get revisions at that stage. Because copy and structure are agreed before anything is designed, there is rarely a surprise at the end. If the direction is wrong after the first round, you can stop and owe nothing further.

Who owns the code and the site?

You do, entirely, once the final invoice is paid. Clean, documented code, in your repository, on your hosting. No proprietary builder, no licence, nothing that stops another developer taking over.

What do you need from me?

About three hours in total: one call at the start, one round of feedback on copy and direction, one review before launch. Anything you already have (logo files, photography, product screenshots) helps, but I can work without it.

SaaS website design

SaaS website design.For products that are hard to explain.

Your product does something specific and technical. Your website should make that obvious to every person on the buying committee, not only the engineer. I handle positioning, copy, design and the build, as one person, at a fixed price.

Start a project See the work

Why SaaS websites stall

They list features instead of a reason to buy

A feature grid tells a visitor what the product has, not why their team should change how it works. Buyers leave before they understand what is different.

They talk to one reader

SaaS is bought by committees: the user who finds you, the lead who evaluates you, the finance person who signs. A site written for one of them loses the others.

Marketing cannot ship without a developer

When every new page needs a ticket, the site freezes the week after launch and slowly drifts away from the product.

What you get

Positioning: one sentence your team can repeat, and the primary buyer named
Every line of copy, written before anything is designed
A design system that matches your product UI, not a template
A fast Next.js or Astro build, with a CMS if your team publishes often
Technical SEO done at build time: structured data, sitemaps, hreflang, redirects
Analytics and conversion events wired up, clean code in your repository

How it works

Week 1
Positioning sprint
We map what you sell, who signs and what they need to read. You get the positioning and every line of copy. If we stop there, you keep both.
Weeks 2 to 3
Design and build
Design in the first days, then the build. You see the direction early and review once before launch, not in five rounds by email.
Launch
Live, measured, handed over
Redirects, sitemap and analytics in place on day one. Documented code and a CMS your team can use without me.

Products I positioned, designed and built

Every claim here is checkable. Open the live ones, use them, run them through PageSpeed.

Pricing

Trial week from €2,000

Every project starts with the one-week positioning sprint. If we continue, the build is quoted at a fixed price at the end of the sprint and the sprint is credited in full. No retainer.

Start a project

Questions

Do you only work with SaaS companies?: No. I work with companies whose product is hard to explain: SaaS, AI, fintech, deep tech and B2B. SaaS is where that problem shows up most often.
How long does a SaaS website take?: About three weeks: one for the positioning sprint, then two for most builds. Larger sites with a CMS take a little longer. You get a fixed timeline with the quote.
Can you match our product's design system?: Yes, and I recommend it. When the marketing site and the app share type, spacing and components, signing up feels like one product instead of two.
Do you redesign existing sites without losing SEO?: Yes. Every redesign includes a URL inventory and a 301 redirect map, so pages that rank keep their traffic after launch.

Tell me what your product does.I will tell you what your site should say.