A website built for one business, by hand, with the price on the page before you ask for it.
What separates this from a template build
Three things you can check yourself, before signing anything.
- No theme and no page builder
- Nothing here starts from a purchased template. You can confirm it on any site built here: view source, and there is no theme name, no builder shortcode and no marketplace stylesheet in the bundle.
- A design system that exists only for your project
- Palette, type scale, spacing, motion and the layout families are derived from your business and from what your actual competitors already do - specifically so the result does not look like the others.
- Static output, measured before it ships
- Every page is prerendered and checked against Core Web Vitals - Google’s own measures of how fast a page loads and how steady it is while loading - on the real build, not on a development copy. A build that misses them is fixed rather than documented.
Which of the three am I
Landing, corporate or shop - stepped, not scattered.
The brief decides this more than the budget does. A landing site is one argument told properly; a corporate site is a structure people navigate; a shop is a transaction with everything that implies.
Landing site
EUR 2,000
per project
2 to 3 weeks
Included. One page built to the depth of a full site: bespoke design system, scroll-driven hero, copy structure, contact form, SEO metadata and JSON-LD, static build, deployment to the client’s hosting. Two revision rounds.
Not included. Copywriting, photography, a content management system, ongoing SEO work, and any page beyond the one.
Corporate site
EUR 2,600
per project
4 to 6 weeks
Included. Up to 8 pages, bespoke design system, shared component library, contact form, per-page SEO metadata and JSON-LD, static build, deployment. Two revision rounds.
Not included. Copywriting, photography, a content management system, ongoing SEO work, translation, and content entry beyond the eight pages.
Online shop
EUR 4,400
per project
6 to 9 weeks
Included. Storefront, catalogue structure, cart and checkout against a hosted commerce backend, payment and shipping configuration, order notifications, SEO and product structured data. Two revision rounds.
Not included. Product photography, product copy, catalogue data entry, the commerce backend subscription, payment provider fees, and fulfilment integration beyond one shipping method.
What the price covers, in both directions
Included, and explicitly not included.
Delivered
- Design system and every page in the agreed list
- Built to the depth the page needs rather than to a fixed section template, and reviewed at 375, 768, 1280 and 1920 pixels before it is called done.
- Technical SEO and structured data
- Per-page titles and descriptions, canonical URLs, JSON-LD, sitemap, robots policy and an llms.txt for AI crawlers.
- A working contact form
- Client-side validation, accessible errors, a real submission target and a confirmation the visitor can trust.
- Deployment and handover
- Deployed to your hosting, with the repository, the build, DNS control and every credential transferred.
Out of scope
- Copywriting
- Structure and headings come from the build; the words come from you or from a copywriter you commission. A site cannot be finished around missing text.
- Photography and video
- Real photographs of your premises, your team and your work have to be real. Nothing that functions as proof is ever generated here.
- Ongoing SEO and content marketing
- Technical SEO is built in. Ranking work over months is a retainer, and retainers are declined - that is a different trade.
- Content entry past the agreed page count
- Pages beyond the list are quoted at the per-page rate below rather than absorbed quietly into the timeline.
How it proceeds and what you prepare
Five steps, each with a handover in it.
The same five steps for every site. The whole sequence takes 2 to 3 weeks for a landing site, 4 to 6 for a corporate site and 6 to 9 for a shop.
Step 1
Discovery and fixed scope
Your brief becomes a written page list with what is built on each page, a timeline and a fixed price.
You supply
Business details, the site’s purpose, and who signs off.
Step 2
Design system
Palette, typography, spacing, motion and layout families, presented as two or three directions to choose between.
You supply
A decision on the direction within three working days.
Step 3
Build
Pages implemented in priority order on a URL you can open, with the highest-value page first.
You supply
Copy and images for each page as it comes up. This is where timelines slip, and it is the one step outside this studio’s control.
Step 4
Two consolidated rounds
Each round is worked through in full and returned. A third round is quoted before it starts.
You supply
One consolidated list per round, from the named decision-maker. Not a stream of messages.
Step 5
Deploy and transfer
Production deployment, loading speed verified on the live site, then repository, credentials and DNS transferred.
You supply
Hosting and domain access, if they are not already with you.
Why your quote might differ
What moves the number, and by how much.
A published price with hidden mechanics is still a hidden price. These are the decisions that change it, with the actual deltas.
| Decision | Effect on the price | Why |
|---|---|---|
| Each page beyond the agreed countA page inside an existing design system is fast. The number is flat because the system is already paid for. | + EUR 220 | |
| Second languageLanguage switching, the tags that tell search engines which language each page is in, a second set of page titles and descriptions, and every layout re-checked against longer text. | + 35% | |
| Adding a shop to a corporate siteCatalogue, cart and checkout, payment and shipping setup, order notifications. The corporate site plus this is exactly the Online shop row above - it is not added on top of the shop price. It assumes a hosted shop platform; a bespoke one is quoted separately. | + EUR 1,800 | |
| Scroll-driven video film, like the home page hereA generated video that plays as the visitor scrolls. The standard animated hero is already in every price; this is the film on top of it - storyboard, generation, compression so the page stays fast, and a still-image version for visitors who turn motion off. | + EUR 600 | |
| Content migration from an existing siteCharged per page of real content moved from your old site into the new one, not per URL. If you are replacing an existing site with ten or more pages, the redesign service is usually the better fit - it includes the first 10 pages. | + EUR 12 per page | |
| Rush timelineApplied when a date requires displacing other scheduled work. It is refused rather than quoted when the date is not achievable at any price. | + 25% |
After it is live
What you are handed, and what changing things costs.
- The repository, with its full history
- Not a zip of the final state. Any developer can read how the site was built and continue from there.
- Domain, DNS and hosting control
- In your accounts, in your name. Nothing stays registered to this studio, which is the usual way an agency makes leaving expensive.
- Updates without a CMS
- Text and image changes are a small edit and a rebuild. Send them and they are quoted by the hour, or your own developer does it - the source is ordinary and readable.
- Later changes
- Billed at EUR 65 per hour against a maximum number of hours agreed in advance. There is no retainer, and the 10-hour minimum that applies to UX/UI work does not apply to changes.
- No lock-in, stated plainly
- Nothing in the build requires coming back here. That is deliberate: a studio that has to trap clients to keep them is telling you something about the work.
Asked first, most often
Questions about a build.
Why static output rather than WordPress?
A static site has no database to breach, no plugin to update, no PHP version to chase, and nothing that can be slow under load because there is nothing running per request. The trade is that changing text means a rebuild rather than logging into an admin panel. For a site that changes a few times a year, that trade is heavily in your favour; for one that changes weekly, say so at the brief stage and a content layer goes into the scope.
What happens if I need a blog later?
The build is designed so that a content layer can be added without rebuilding the site around it: the routing, the design system and the deployment stay as they are, and the posts arrive as files or from a headless CMS. It is quoted when you want it, not paid for in advance on the chance that you might.
Can I host it myself?
Yes, and that is the normal case. The output is a directory of files. It runs on shared hosting, on a static host, on a CDN, or on a server you already own. No Node runtime is needed anywhere, and there is no proprietary platform in the chain that could start charging you later.
Who owns the code?
You do, in full, from the moment the final invoice is settled. That includes the design system, the components and the repository with its complete history. Nothing is licensed back to you and nothing is withheld to make leaving expensive.
What if I want to stop mid-project?
You can, at any point. The deposit covers the work done up to the design system and is not refundable once that exists, because it is the part that cannot be reused elsewhere. Everything produced to that point is handed over in the state it is in. The full terms are on the refund and cancellation page.