How we price projects
We don’t sell packages. Every project is scoped on its own: we learn your goals and scope, then send a clear estimate with a timeline. Here is what drives cost and how the work runs.
Asking what a website costs is a bit like asking what a house costs. It depends on what you’re building, how many rooms it has and what is already on the plot. So instead of a price list, we talk first and then send an estimate for your project. You pay for what you actually need, not for a package designed around someone else.
What drives the cost
A few things matter on every project: how much bespoke design is needed, how many languages, how much content you prepare and how much we do, which systems we need to connect to, and the deadline. Below is what weighs most for each service.
Websites
- The number of page templates: ten similar service pages cost less than ten different layouts.
- Languages, and whether you need a content system so your team can edit the copy.
- Animation, interactive elements, booking or calculators.
- Moving content from an old site and setting up redirects so you keep your search rankings.
Online stores
- A custom Shopify theme or a store built from scratch.
- Number of products, variants, and importing them from your current system or warehouse.
- Payments, shipping options, multiple currencies or languages.
- Integrations with accounting, inventory or a CRM.
Web apps and platforms
- User roles and permissions: who sees and edits what.
- How complex the workflows are: ordering, approvals, pricing rules, reporting.
- Integrations with existing systems and data migration.
- Security and audit requirements.
SaaS and MVPs
- How many features the first version really needs. Usually fewer than it seems at the start.
- Sign-in, subscriptions and payments.
- An admin area, analytics and transactional email.
- Whether the product serves one organisation or many customers on one system.
AI automation
- How many steps the process has and how many systems take part.
- What data is used and how it is stored.
- Whether a person approves actions before they happen, and how errors are handled.
- How heavily the language model is used, which also shapes the running costs.
How we make the estimate
It starts with your enquiry. In the form you choose the project type, describe your goals and pick a budget range, and we reply within one business day. Then we have a short call about what you want to achieve, what already exists and when you need it.
After the call we send the scope in writing: exactly what we’ll build, what is out of scope, the phases, the cost and the delivery date. If we misunderstood something, you’ll see it straight away, before any work begins. Nothing is built until you approve it.
Larger projects: scope first
For a platform, a SaaS product or a complex integration, one call is rarely enough for an accurate estimate. In that case we spend more time before estimating: over a few calls we map the workflows, the user journey and the integrations together and prioritise features. This is free; the estimate follows once the scope of work is clear.
The outcome is a written scope, the key decisions and a firm estimate. They are yours to keep, even if you decide to work with someone else. Both sides take on far less risk than when a large project is estimated by eye.
Fixed scope or time and materials
Fixed scope, fixed price. Right when it’s clear what we’re building: a website, a store, a well-defined MVP or automation. You know the cost and the date up front. If you want to add something, we estimate the change separately and only start once you agree.
Time and materials. Right when a product grows step by step and priorities shift, for example improving a SaaS product after launch. We work in short cycles; at the end of each you see what was done and how long it took, and we plan the next one together.
We’ll recommend a model after the call. Often the first version is built on a fixed scope and later improvements run on time and materials.
What’s included in a project
- Design. Bespoke, made for your brand and content, with the mobile version designed too.
- Build. We adapt to any tech stack your project needs. Once the project is paid in full, the code and every account are yours.
- Quality checks. Testing on phones and browsers, speed, forms, and building with accessibility in mind.
- Launch. Domain and hosting setup, redirects, analytics and a sound technical SEO foundation.
- Handover. We show you how to manage the content and hand over all access and documentation.
Ongoing costs after launch
Beyond the one-off build, it’s worth planning for the costs that recur:
- Hosting. Often low or free for static sites; for platforms and SaaS it depends on load.
- Licences and services. A Shopify plan, apps, email delivery, payment fees or AI model usage.
- Domain. An annual registration fee.
- Care. Updates, backups, monitoring and small changes. You can handle these yourself or choose one of ourcare plans.
We list all of these separately in the estimate, so there are no surprises.
How to save without cutting corners
What moves the cost most isn’t an hourly rate but how much work has to be done, and redone. A few things genuinely bring an estimate down:
- Have the content ready. Copy, photos and product data delivered at the start save the most time. If you don’t have them yet, we’ll help you set out the structure so you know what to write.
- Start with what’s essential. A first version can go live with the core features, and the rest can follow once you see what customers actually need.
- Name one decision-maker. When feedback comes from one person, there is less rework and the timeline stays shorter.
- Use what already works. If your accounting, CRM or inventory system does the job, we connect to it rather than rebuild it.
When you compare proposals, look beyond the total. Check whether it covers design, testing, content migration and handing over access, and who will own the code once the project ends.
Budget ranges in the form
To make the first call useful from the start, the enquiry form asks you to pick a rough budget. It isn’t a price; it’s a guide that helps us suggest the right scope. The options are:
- €500–2k
- €2k–5k
- €5k–15k
- €15k–50k
- €50k+
- Not sure yet
If the budget is smaller than the scope you have in mind, we’ll say so plainly and suggest what to do first and what can wait.
How the work runs
- Discovery. A call about your goals, your audience and what already exists. We reply to enquiries within one business day.
- Scope and estimate. In writing: what we build, what’s out of scope, phases, cost and dates. We start only once you approve.
- Design. The key pages or screens first. We review them together and refine until they’re right.
- Build and test. We build in phases, show progress along the way and test speed, phones and forms.
- Launch and support. We go live, hand over access and, if you wish, keep looking after and improving the product.