The short answer: our price ranges up front
"What should we budget for our website?" That question opens almost every first call with a SaaS team. The honest answer is not a number but a range: the price hangs on five levers that you set yourself. Up front, the overview from our projects of the past few years.
| Stage | One-off | Per month (incl. maintenance) |
|---|---|---|
| Seed startup: 5β7 pages, one language | β¬8,000β15,000 | β¬20β300 |
| Growing SaaS: CMS, blog, landing pages | β¬18,000β35,000 | β¬250β700 |
| Enterprise presence: trust center, integrations, two languages | β¬40,000β80,000 | β¬600β1,500 |
Important context: these are net prices and figures from happycoding projects built on Next.js, Sanity, and Vercel. Not a market study, not averages from other agencies. A freelancer can come in below these ranges, a large agency well above. What a SaaS website has to deliver in terms of content, I have written up in the guide to the B2B SaaS website. This article is about the money.
The three stages are not a price list but an upgrade path: almost every project starts on the left and moves right as the company grows. What matters is paying for the stages in the right order instead of ordering everything at once. The following sections show why.
What drives the price: five levers
Before we calculate, the price drivers one by one. You can turn each of these levers deliberately β up as well as down. Knowing them lets you negotiate with any agency on equal footing.
Page count
A SaaS website needs surprisingly few pages at launch: home, product page, pricing page, about, contact, plus legal notice and privacy policy. Every additional page costs concept, copy, design, and implementation. Feature subpages, use-case pages, and comparison pages are growth instruments, not launch requirements. As a rule of thumb from our projects: every additional individually designed page costs β¬800β2,000, a page built from an existing CMS template only a fraction of that.
One page deserves special care: the pricing page. It is usually the last stop before a trial or demo request and decides your conversion. How to structure it is something I show in my article on SaaS pricing page examples.
Design ambition
The range runs from an adapted template to your own design system. A template-based design with your branding costs β¬2,500β5,000 in our projects. A distinct design language with illustrations, staged product screenshots, and animations lands at β¬8,000β20,000. Enterprise buyers expect the latter: they infer the maturity of the product from the website.
CMS or static pages
Without a CMS, only a developer can change content. That is fine at launch but gets expensive once marketing wants to publish weekly. A headless CMS like Sanity adds β¬3,000β8,000 of one-off implementation in our projects, but makes your team independent afterwards.
Integrations with your product
This is where the SaaS website differs from any brochure website. Typical items: a signup flow that hands over to the app, a CRM connection for demo requests, analytics with clean campaign attribution, a status page. In our experience, each integration costs β¬1,000β5,000, depending on the API quality on the other side. Plan them early: wiring them in later is more expensive.
Multiple languages
German plus English does not double the cost, but it raises it noticeably: by 30β50 percent in our project experience. The effort sits less in the technology than in the content: translation, maintenance processes, SEO in two markets. Start with one language if your sales still live in one market. Preparing the technical side early via i18n routing costs little and saves a lot later.
Three sample budgets from our projects
Now let's get specific: three typical setups, each with its assumptions laid open. Once again: all figures are net ranges from our own project experience as an agency, not market averages.
Example 1: seed startup before launch
Assumptions: six pages, one language, template-based design with your own branding, no CMS, analytics and a form tool connected. The budget breaks down like this:
- Concept and page structure: β¬1,000β2,000
- Design: β¬2,500β5,000
- Implementation with Next.js: β¬3,500β6,000
- Copy, SEO basics, launch: β¬1,000β2,000
Total: β¬8,000β15,000. Ongoing costs are almost nothing beyond domain and hosting. This stage carries you to your first paying customers, and that is exactly as long as it should carry you.
What pushes you to the upper end of this range is mostly indecision: every extra design feedback round costs money. A clear briefing and one person with decision authority on your side are the cheapest cost-saving measure I know.
Example 2: growing SaaS with CMS and blog
Assumptions: 12β20 pages, a distinct design language, Sanity as the CMS, a blog with categories, two to three landing page templates for marketing, a CRM connection.
- Concept, information architecture, wireframes: β¬2,500β5,000
- Design language and components: β¬5,000β10,000
- Implementation including Sanity schemas and templates: β¬8,000β15,000
- Content migration, SEO, integrations: β¬2,500β5,000
Total: β¬18,000β35,000. The biggest lever is the landing page template: marketing uses it to build campaign pages without a developer. Every developer hour saved this way pays back the CMS.
In this setup, the range is usually explained by the blog: if you carry over existing articles unchanged, a migration is enough. If the blog is to be restructured at the same time, say with categories, author profiles, and series, the project moves toward β¬35,000.
Example 3: enterprise presence with a trust center
Assumptions: more than 30 pages, German and English, a custom design system, a trust center with pages on security, compliance, and data protection, plus integration of CRM, signup, and status page.
- Strategy, messaging, information architecture: β¬5,000β10,000
- Design system with animations: β¬10,000β20,000
- Implementation, CMS, multiple languages: β¬18,000β35,000
- Trust center, integrations, quality assurance: β¬7,000β15,000
Total: β¬40,000β80,000. The trust center is not a cost driver born of vanity: in enterprise deals, procurement asks for security evidence and data processing agreements before the business side even tests the product. Having these pages ready measurably shortens the sales cycle.
The open end of this budget sits in the integrations: a cleanly documented CRM is connected in days, a legacy system that grew over the years can cost weeks. Clarify the API situation before you lock in the budget.
Hidden line items no proposal mentions
When comparing agency proposals, it pays to look at what is not in them. In our experience, five items show up in hardly any proposal and still hit you later:
- Copy: the most common project brake. Clarify before signing who writes β you, the agency, or a copywriter. Professional website copy costs β¬1,500β5,000 extra in our experience, depending on scope.
- Imagery: product screenshots need to be staged, cropped, and exported in several resolutions. Across 30 pages, that is a small project of its own.
- Legal: privacy policy, cookie consent, data processing agreements with the services you use. The technology is built in quickly; the legal review is billed separately.
- SEO migration: if the new website replaces an old one, every old URL needs a redirect. Forget this and you lose rankings you built over years.
- Your own time: briefings, feedback rounds, approvals. Plan on 2β4 hours per project week internally, or it will not be the agency slowing things down but your calendar.
None of these items argues against a cheap proposal. But a proposal that stays silent on all of them is not cheap, it is incomplete. Ask about every item before you sign: the answer tells you a lot about the collaboration ahead.
Recurring costs: hosting, licenses, maintenance
The one-off costs are only half the truth. Three items keep running. Two of them are pleasantly small, the third tends to go unmentioned.
Hosting on Vercel
Vercel comes in three plans: Hobby at $0, Pro at $20 per team member per month, Enterprise on request (as of September 22, 2026, per the Vercel pricing page). Important: under Vercel's fair use guidelines, the Hobby plan is restricted to non-commercial use. For a SaaS, that means you need Pro.
Pro includes 1 TB of data transfer per month; beyond that, $0.15 per GB applies. For a B2B website with five-figure visitor numbers, in practice it almost always stays at the base fee. Outliers come from unoptimized videos, rarely from traffic.
CMS license: Sanity
Sanity has three plans (as of September 22, 2026, per the Sanity pricing page): Free at $0 with 20 user seats, 10,000 documents, 100 GB of asset storage, and 100 GB of bandwidth per month. Growth at $15 per seat per month, adding private datasets and 25,000 documents, among other things. Enterprise with custom pricing.
My experience: the Free plan carries most SaaS websites for a surprisingly long time. The reason to switch is rarely the quotas but features like private datasets or scheduled publishing. For hosting plus CMS combined, plan on around β¬20 to β¬100 per month while your team is small.
Maintenance and further development
The most honest item is the least comfortable one: a website without maintenance goes stale. Screenshots show the old product version, prices no longer match, dependencies want updates. From our projects: 2β8 hours per month, depending on how often you publish. At hourly rates of β¬100β140, that is β¬200β1,120 per month; a maintenance retainer usually comes in cheaper.
Added up, the middle stage looks like this: around β¬20β40 for hosting and domain, $0β45 for Sanity with up to three editor seats, plus the maintenance effort. Realistically you land at β¬250β700 per month. The striking part: the software is the smallest item. In operations, you mostly pay people, not servers.
Where you can save β and where you'd better not
To close the budget planning, the question of all questions: where are you allowed to cut? After plenty of SaaS projects, my answer is clear, in both directions. Three items take the red pencil well:
- Page count: start with six strong pages and expand once you have traction. A CMS makes extensions cheap.
- Illustrations and photography: good product screenshots beat expensive custom illustrations, especially in the early phase.
- Special formats: interactive calculators, elaborate animations, and video productions can be retrofitted once the basics convert.
In three places, saving reliably backfires. On positioning and copy: the prettiest website with an interchangeable message does not convert. On the pricing page: that is where the buying decision happens. And on the technical foundation: load time and clean SEO stay with you for years, for better or worse.
A special case: you already have a website, and it no longer pulls its weight. Then a rebuild on a green field is rarely necessary: a structured relaunch usually gets you there for less.
SaaS website and company website: the difference in budget
You may be wondering why these figures sit above what you know from a classic company website. Three reasons: a SaaS website has to sell rather than represent, it is connected to your product, and it is updated far more often. A pricing page, signup integration, and landing page machine simply do not exist on a brochure website. Add the cadence: a SaaS website is a tool in weekly use, not a yearly business card.
The reverse also holds: not every software company needs the big stage right away. If you sell complex software exclusively through sales reps and trade fairs, your website works more like a company website in a good suit. Planned honestly, you skip the signup flow and landing page machine for now. You can always upgrade later.
If you are budgeting a classic company website instead, say for a consultancy or a mid-sized business without a software product, different ranges apply than the ones in this article.
Next steps
My advice for your budget: first define what the website has to deliver in twelve months. Trials, demo requests, visibility in a new market? Stage and budget follow almost automatically from that β and you do not pay for expansion you do not need yet.
As a website agency for B2B and SaaS companies we build exactly these websites: Next.js, Sanity, Vercel, with a clear cost structure instead of surprises. Want to know where your project lands within these ranges? Then book a free intro call: 30 minutes, and you will walk away with a solid ballpark figure.
