Scoped To Your Requirements. Priced Before We Start.
There is no package tier and no published rate card, because the two variables that decide cost — scope and technical complexity — are different on every project. We work through your requirements line by line on an initial call, then send an itemised proposal with the deliverables and the number attached. Nothing begins until you have seen both.
Itemised Estimates
Your requirements get broken down line by line during the initial call. The proposal lists what gets built and what it costs, with no line item held back for the final invoice.
Value-Based Pricing
You pay for the features, pages, and integrations your business actually needs. Work that would not be used does not appear on the quote.
Milestone Payments
Larger builds are split around checkpoints you can inspect. You see the work in a working state before the next payment is due.
Tell Us What You Need Built.
Give us the project details and a short description of the problem. You will hear back within 24 to 48 hours.
Thank you.
We will be in touch within 24–48 hours.
Zero vendor or platform lock-ins. Every file we write is handed over to you at completion — no licence attached, no monthly platform fee, and no dependency on us to make the next change.
Questions We Get Asked Before Signing.
If something is not answered here, ask it on the call. We would rather answer it now than have it become a problem after handover.
How do I update content after the site launches?
It depends on which of two setups we build. If your content is text and images on a small number of pages, we can wire it to a headless CMS such as Sanity or Contentful — you edit through a normal interface and never touch code. If the site is a fixed static bundle, the markup is simple enough that you or any developer can edit it directly in a text editor. Either way, we document which approach you have and how it works before handover.
Who legally owns the code when the project is finished?
You do, completely. Ownership transfers at final payment. We hand over every source file — markup, styles, scripts, images, and documentation — and there is no licence, attribution requirement, or restriction on what you do with it afterwards.
If you want a repository of record, we push the project to a GitHub or GitLab account you own from the first commit, so there is a complete history rather than a single zip file at the end.
What happens if I want to work with a different developer later?
They can. That is the point of the handover. The code is yours, written to be read, and documented to the level where someone else can pick it up without calling us. No proprietary framework, no hosted-only backend, no API keys we hold on your behalf. If you would like an introduction to another developer, we can provide one.
What support do I get after launch?
Thirty days of post-launch support is included, covering bug fixes and minor adjustments. After that, ongoing work is quoted as a retainer or a per-task basis — your choice.
Support runs through email and WhatsApp, and we answer infrastructure questions as well as code questions. If your hosting, domain, or DNS is arranged with our help, we will help you move it elsewhere at no charge.
How do you handle accessibility and security?
Every build is tested before launch against WCAG AA contrast requirements, keyboard navigation order, focus visibility, and screen reader labelling on interactive elements. We run a dependency audit to confirm there is no known vulnerability in what we ship.
For anything handling user accounts or payments, we would recommend the client’s own hosting and a managed service such as Stripe or Auth0, where the security burden sits with a vendor who maintains it continuously.
What is actually included in the handover?
All source files, a written document covering page structure and how to make common edits, deployment configuration files, and a walkthrough call recorded for your records. Hosting and domain are set up in your name, not ours.