Ideas made
visible.

There is no useful single price for “a website” or “a web app” because the work can differ radically in scope. Cost is shaped by the number and complexity of journeys, custom functionality, content, integrations, CMS requirements, migration, languages, testing and the state of what already exists.

Once the problem and boundaries are clear enough, AMUI can turn that into a defined proposal rather than inventing a number from the first email.

Most projects take approximately 3–6 weeks. The exact timeline depends on the scope, complexity of the website and how quickly the necessary materials and feedback are available.

No. You can arrive with a detailed specification, a rough idea, an existing product that is causing trouble, or simply a business problem that needs a digital answer. The first job is to understand what actually needs to change.

Yes. When editable content is needed, we usually integrate Payload CMS (Content Management System) and structure it around your website. You only see the fields and controls you actually need, making day-to-day editing much simpler.

Ownership, licences, third-party components and any reusable AMUI intellectual property should be defined explicitly in the project agreement. The important part is that these boundaries are understood before delivery, not discovered while somebody is trying to move a production account six months later.

Handover can include access, editor training, documentation and an agreed defect-support period. Ongoing maintenance, product improvement or additional feature work can then be scoped separately where it creates value.