- Why is this so much cheaper than an agency?
- Because the cost structure is different, not the engineering. A traditional agency price carries account management, bench time, and a project team that rotates — you are paying for the org chart as well as the work. We price the work. The stack is also one we run in production for our own products, so the scaffolding every project needs — accounts, payments, deployment, testing — is not rebuilt from zero at your expense. What is not different: who writes the code, and how carefully.
- Can I edit the content myself afterwards?
- Yes, if you want to. Tell us on the first call and a CMS is part of the build — you get a login, and you can change text and images without touching code or paying us to. If you would rather not think about it, we can leave that out and handle changes on the partnership instead, or just send an invoice for the occasional edit. What we will not do is build something only we can update and then charge you for the privilege.
- Who handles hosting and the domain?
- You own both, in your own accounts, and we set them up. Hosting for a site of this kind is typically free to a few euros a month, and the domain is usually around ten to fifteen a year — you pay those directly to the provider rather than through us, at cost, with no markup and no reselling. If you already have hosting we will work with it where it is sensible and tell you plainly when it is not.
- What happens if you become unavailable?
- Continuity is designed in rather than promised. Source code, hosting, and the domain live in your accounts from day one, not ours — you can revoke our access this afternoon and carry on. Everything needed to run and deploy the project is configuration committed to your repository rather than knowledge in somebody's head: the build steps, the deploy lane, the tests and the monitoring are all reviewable, and runnable by any competent developer without us. Partnerships run month to month after the three-month minimum, either side can end with 30 days' notice, and ending one includes a written handover rather than a cliff. No vendor of any size can honestly guarantee availability, so the question worth asking all of them is what you are left holding if it stops. Here it is everything.
- Is the price really fixed?
- Yes, against a written scope agreed before work starts. If you change the scope mid-build we price the change and you decide — you will never receive an invoice you did not agree to in advance. Genuinely open-ended problems are quoted at an hourly rate up front, rather than as a fixed price that quietly becomes one.
- How does payment work?
- Retainers are invoiced monthly in advance, on the same date each month, against a three-month minimum and rolling monthly after that. Fixed-scope builds are typically 50% to start and 50% on delivery, with larger builds split across milestones instead. Either way the exact structure is written into the scope document before any work begins.
- I have never heard of you. What protects my deposit?
- A fair question to ask anyone, and the honest answer is structural rather than contractual. The first payment buys a written scope and a working build in week one — so if week one does not arrive, you have paid for one week of work and you stop. That is the actual reason the cadence is weekly rather than monthly: your exposure never exceeds one week at any point in the project, because there is never more than a week between you and the next thing you can click. Deposits are invoiced against the scope document rather than against a promise, and if you would rather start smaller, we will scope the smallest useful piece of the project and do that one first.
- What does the three-month minimum mean?
- It means the first three months are committed, because taking over somebody else's codebase and getting genuinely useful in it takes longer than four weeks — the first month is largely learning your systems, and cancelling at that point leaves you worse off than before you started. After month three it runs month to month and you can end it with 30 days' notice. No annual lock-in and no auto-escalating rate.
- What if a quiet month goes by and nothing breaks?
- That is the outcome you are paying for, and it is a fair question to ask before signing. A partnership buys ownership and availability, not a ticket quota: dependencies and frameworks still move underneath you, security patches still land, and monitoring still needs somebody reading it. If genuinely quiet months repeat, the honest answer is to move you to the ad-hoc hourly rate rather than keep billing a partnership you have outgrown — we would rather lose the line item than have you resent it.
- Do I need a project or a monthly partnership?
- A project if the thing does not exist yet and has a defined finish line — a site, an MVP, a platform. A partnership if it already exists and the work is recurring: updates, security patches, and the next set of features. A project usually becomes a partnership at launch, which is the point at which the recurring work actually begins. If you are unsure, say so when you get in touch — a straight 'you do not need us monthly' is a normal outcome.
- What if we are not happy with the result?
- You get a live build every week — a URL you can open and use — so the first chance to say 'this is not what we wanted' is week one rather than the end, when changing it is still cheap. That cadence exists specifically so a project cannot fail silently for two months. After launch, anything that shipped broken is fixed for two weeks at no cost.
- Do you work with AI-generated codebases?
- Yes, and it is work we actively want. Taking something built in Lovable, Bolt, v0, Replit or Cursor from 'the demo works' to software that real customers can depend on is scoped as a rescue rather than a rebuild, and it usually costs less than starting over. The work is normally the same three things: the data model, the parts that handle money or identity, and everything that only fails under load or on a bad connection.
- Who owns the code?
- You do, outright, at handover — source and infrastructure in your own accounts. No license, no hosting lock-in, no per-seat fee afterwards.
Prices, timelines, and payment structures on this page are informational, and are fixed per project in a written scope. They are an invitation to start a conversation, not a binding offer — see the terms.