Sites that make a businesslook as serious as it is.
One ladder, from a single page to a system with accounts and roles behind it. Find the step that matches what you need and you have the price — no call, no proposal, no discovery phase to sit through first.
What it costs
Three packages, and the first two have steps inside them — press to see the one that matches what you need. Every figure is where that kind of build STARTS: ask for exactly what is listed and that is what it costs, and it only moves if you want something between one step and the next. Security is designed into every one of them, at every price.
Site
A site that shows what you do. Nothing stored behind it — what a visitor sees, built properly, on whatever they open it with.
from€250
Single page
A single page, front end only. Everything a visitor needs to judge you and get in touch, and nothing else.
- One page, structured around the enquiry
- Fast on every screen it lands on
- Enquiry form with delivery and a record
- Metadata and structured data
- Certificates, hosting and email configured
from€400
Multi-page site
Five pages or more, front end only — a page per thing you actually sell, rather than one page trying to carry all of it.
- Everything in the single page
- A page per service, with its own scope and its own copy
- Navigation that survives you adding to it later
- Content, images and pages you edit yourself
- A second language, written rather than machine-passed
System
A site that also runs part of the business. Which step you are on is decided by how much of it the software has to model.
from€600
Managed content
Real data behind the pages: things stored, listed and edited, rather than written into the markup.
- Everything in the multi-page site
- A written data model before the build starts
- An admin your staff operate, not a database client
- Records that stay records, rather than pages pretending to be
- Migration with no downtime, monitoring and tested backups
from€800
Accounts and roles
Accounts and roles: more than one kind of user, each allowed to do different things.
- Everything in managed content
- Authentication, roles and permissions enforced on the server
- A hidden button is never treated as a permission
- Staged delivery, each stage usable before the next begins
- An audit trail of who changed what
from€1,000
Integrated systems
Integrations, background work and a data model carrying real operational weight.
- Everything in accounts and roles
- Integrations with the systems you already run
- Background jobs, scheduled work and failure handling
- Reporting built on the records rather than bolted beside them
- Architecture written down, so year two is not a rewrite
Enterprise
Past the ladder, where the scope decides the number rather than the step does.
from€1,500
A floor rather than a price: we put a figure on it against a written specification, after the analysis rather than before it.
- Everything in integrated systems
- Scope established in analysis before any figure is given
- A specification you own and could hand to somebody else
- Delivery planned against your operational calendar
All prices exclude VAT.
How paying for it works
Terms stated up front, on the page, rather than produced at signing.
40 / 30 / 30
40% to begin, 30% at the agreed midpoint, and 30% on delivery. You are never paying for work that has not happened yet, and we are never carrying the whole build on trust.
We are late, you pay 20% less
Every tier states a response window. If we miss it, 20% comes off — not as a goodwill gesture argued for afterwards, but as a term of the work. A promise with nothing behind it is not a promise.
Send us someone, keep 20%
If you bring us a client, 20% of what they pay for their build is yours. No cap, no qualifying period, and it applies whether or not you are a client yourself.
AI and automation
Added to whichever step you are on, from €350. It is not a rung on the ladder and it is not a kind of website — it is a capability you attach to one, which is why it is not sitting in that row pretending to be a plan.
A grounded assistant reads your own documents and records and answers out of them, refuses when it has no basis and hands over to a person. It is evaluated against real questions with known answers before it goes anywhere near a visitor, and the conversations stay reviewable so the material behind it can be corrected.
An assistant with nothing underneath it has no material to be grounded in, which is why this attaches to a build rather than being sold on its own.
True of every step
Fast on every screen it lands on
We do not design for the phone and enlarge it. We build the site once, properly, and hold it to the same standard on a phone on a bad connection as on the desk it was designed on.
Content you edit yourself
Text, images and pages change without a support ticket and without a bill. If you have to call us to fix a typo, we have built it wrong.
Enquiries that reach a person
A form that delivers, keeps a record, and survives a spam wave. This is the single most common thing we find broken on a site we inherit.
Security, built in
Access rules enforced on the server and never only in the interface, input validated at the boundary, secrets kept out of the codebase. At every price on the ladder, not as an upsell.
Findable for what you actually sell
Metadata, structured data and page structure written for the services in your invoices — not for a keyword list somebody bought.
Built to be kept
Architecture chosen so the thing is still maintainable in its third year, by us or by whoever comes after us.
How it runs
- [ 01 ]
Analysis
What you sell, who buys it, and what the current page is doing wrong. Ends in a written scope with the boundaries drawn, including what is deliberately out.
- [ 02 ]
Structure
Pages, hierarchy and the route from landing to enquiry — and, where there is a backend, the data model and the access rules. Agreed before anything is designed.
- [ 03 ]
Build
Assembled in stages you can look at, on a real address, not in screenshots. Something works early and more works each time.
- [ 04 ]
Launch
Moved across with no downtime, certificates valid, monitoring on, backups tested by restoring one. Then either you run it, or we do.
Questions
How long does it take?
Less time than most people expect — a single page or a small multi-page site is usually days rather than weeks once the copy and images exist. Anything with accounts, roles or integrations follows the scope that comes out of analysis, and we give you a date against a written specification rather than a guess in conversation.
Can I edit it myself afterwards?
Anything held in the backend is yours to change — pages, entries, images, prices, whatever the site stores. The front end is code: changing that means knowing Astro or HTML, so if you want it altered you either learn it or we do it for you. We would rather tell you that plainly than imply you can rewrite the whole site from a dashboard.
What if I already have a site?
The first job is establishing what is actually there: where the domain is, who has access, whether anything is backed up, and whether security was ever considered. Usually it was not. In most cases we would rather rebuild than inherit — you get a current image and a site whose security was designed in rather than patched on afterwards.
Do you do the writing?
We structure it and edit what you give us. We do not invent claims about your business, and a site written entirely by people who do not do your job reads exactly like one.
Do you build multilingual sites?
Yes, and from the data model outward rather than translated over the top — locale URLs, hreflang, and a language switch that lands on the same page rather than the home page.
Start with what is wrong with the current one.
No sales pressure and no generic proposal. Tell us what you are trying to build and you will get a straight technical read on it and a clear next step.