01What does AMUI actually build?
AMUI designs and develops websites, web applications, digital products, content systems and selected internal business systems. A project can also include UI/UX, information architecture, visual identity work, migration, technical SEO foundations, QA and launch support when those belong to the outcome.
02Do we need a finished brief before contacting you?
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.
03Do you only work on completely new projects?
No. Existing websites and products can be redesigned, rebuilt, migrated, simplified or improved in focused stages. Keeping valuable parts of an existing system is often more sensible than replacing everything for ceremonial reasons.
04Do you work with clients outside Prague or the Czech Republic?
Yes. AMUI is based in Prague and works internationally. The practical collaboration model depends on the project, time zones and the people involved, not on whether everybody can occupy the same conference room at the same time.
05Who will we actually work with?
AMUI is structured to keep the people responsible for the work close to the client, the decisions and the outcome. Specialist capability can be added when the project genuinely requires it, without turning communication into a relay race.
01What technology do you use to build websites?
We mainly build with Next.js and React, which gives us the flexibility to create custom, fast and scalable websites without relying on pre-made templates.
02Will I be able to edit the website myself?
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.
03Where will my website be hosted?
We typically use Vercel or Cloudflare, depending on the needs of the project. We choose the infrastructure based on performance, functionality, expected traffic and the overall technical setup.
If you already have hosting you want to keep, we can also assess whether it’s suitable for the website and, where technically possible, deploy the project there instead.
04Can you connect the website to other systems?
Yes. We can integrate forms, analytics, CRMs, databases, newsletters, external services and custom APIs depending on what your business needs.
05Do you use WordPress or website builders?
No. Our websites are primarily custom-built using modern web technologies. This gives us greater control over design, performance, functionality and future development.
06Do I need to understand any of this technology?
Not at all. We take care of the technical side and explain the decisions that matter to you. You do not need to manage code or understand the underlying infrastructure to use your website.
07Can the website grow later?
Yes. We structure projects so additional pages, functionality, integrations or CMS features can be added as the business grows.
08Do we need to provide Figma files or finished designs?
No. AMUI does not require clients to arrive with Figma files or with the interface already designed. If useful design material exists, we can assess it. If not, design can be part of the work. The objective is a coherent product, not compliance with a particular design-tool ritual.
09Why do you use Next.js and Payload CMS?
They are useful when a project benefits from a modern React application framework and a flexible structured-content backend. Payload can give editors control of content while Next.js handles the public experience or application layer. They are tools AMUI can use well, not compulsory ingredients in every engagement.
10Does every website need a CMS?
No. A CMS is valuable when people need to create or update meaningful content regularly. If a site is small and rarely changes, adding a CMS can increase hosting, maintenance and implementation complexity without giving the client much in return.
11What is the difference between a website and a web application?
A website is often primarily about presenting information, publishing content and guiding visitors. A web application usually has users performing tasks, signing in, creating data, moving through workflows or interacting with application logic. Many real projects sit somewhere between the two.
12Do you have to replace our current technology?
No. Existing technology should be assessed before replacement is proposed. Sometimes the right answer is a rebuild; sometimes it is better architecture around what already works; sometimes the most responsible recommendation is to leave a functioning part alone.
13Do you build custom CRM systems?
Yes. We design and build custom CRM and internal business systems for companies whose processes are not well served by off-the-shelf tools.
A CRM can be tailored around the way your team actually works and may include customer and company records, contacts, leads, sales pipelines, tasks, notes, documents, user roles, dashboards, reporting, notifications and workflow automation.
Where appropriate, we can use technologies such as Payload CMS as the foundation for the system, giving us established functionality for authentication, permissions, structured data and administration while allowing us to customise the workflows and interface around your business.
We do not assume that a custom CRM is always the right solution. If an existing platform can solve the problem more efficiently, we can recommend integration or configuration instead of unnecessarily building software from scratch.
For larger systems, we usually begin with a focused first version and expand it in stages as the requirements become clearer.
01Can you redesign our website without replacing our brand?
Yes. A redesign can change hierarchy, typography, interaction, responsiveness, content structure and technology while preserving the identity people already recognise. Brand equity should not be discarded simply because a website needs to grow up.
02Can you migrate our existing content?
Yes, when migration is part of the agreed scope. The work can include mapping old content into the new structure, cleaning inconsistencies, moving media and preserving relationships between content types. Large migrations deserve their own planning rather than being treated as an afternoon copy-and-paste adventure.
03What happens to SEO when an existing site is rebuilt?
A rebuild should account for existing URLs, redirects, metadata, canonical behaviour, crawlability, sitemaps, internal linking and content that already has search value. That reduces avoidable migration damage. Nobody can honestly guarantee specific rankings, because search engines remain stubbornly outside the project contract.
04Can you integrate third-party systems and APIs?
Yes, where the required service exposes a usable integration path. The feasibility, security model, rate limits, data ownership and reliability of external systems need to be assessed because an integration is only as cooperative as the system on the other end.
01How much does a project cost?
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.
02How much does a landing page cost?
A custom landing page typically starts from CZK 35,000. Most projects of this type fall between approximately CZK 35,000 and CZK 60,000, depending on the content, design complexity and functionality required.
This can include UX and competitor research, conversion-focused structure and wireframing, custom interface design, Next.js development, responsive implementation and essential technical SEO.
A straightforward landing page can usually be completed in around 1–2 weeks, provided that content, feedback and approvals are available as agreed.
Every project is scoped individually before work begins, and we provide a fixed quotation based on the actual requirements.
03How much does a standard company website cost?
A custom company website typically starts from CZK 70,000. Most projects of this type fall between approximately CZK 70,000 and CZK 140,000, depending on the number of unique page types, content requirements, languages, functionality and design complexity.
As a general reference, this can cover a website of around 5–10 pages, including UX and competitor research, information architecture, custom interface design, Next.js development, technical SEO and structured data.
Projects of this size usually take approximately 3–4 weeks.
The starting price is an indication rather than a package price. We first understand the project and then prepare a defined scope and fixed quotation based on what is actually required.
04How much does a website with a CMS cost?
A custom website with a content management system typically starts from CZK 110,000. Depending on the content structure, integrations and functionality required, projects of this type commonly fall between approximately CZK 110,000 and CZK 200,000 or more.
This can include content architecture, search and website structure planning, custom interface design and development, and a CMS configured around the content your team actually needs to manage.
This type of solution is suitable for larger websites, regularly updated content, blogs, case studies, multilingual websites and projects with more complex content structures.
Development generally takes around 4–7 weeks, depending on scope and the availability of content, feedback and approvals.
Every CMS implementation is evaluated individually because content models, permissions, integrations, migration requirements and editorial workflows can differ substantially between projects.
05How much does a custom CRM system cost?
A custom CRM or internal business system typically starts from CZK 135,000. This starting point is suitable for a focused system with clearly defined workflows, such as managing companies, contacts, leads, opportunities, tasks, notes and users.
More advanced CRM projects involving custom dashboards, complex permissions, workflow automation, reporting, external integrations, customer portals or connections to existing business systems can range from approximately CZK 180,000 to CZK 400,000 or more.
Where appropriate, we can build CRM systems on technologies such as Payload CMS, which provides a strong foundation for structured data, authentication, permissions and administration. This allows us to concentrate development effort on the workflows and functionality specific to your business rather than rebuilding standard administrative features unnecessarily.
A focused first version can typically be delivered in around 6–10 weeks, while larger systems are usually developed in defined phases.
Before recommending a custom CRM, we first look at how your company currently works and what problem needs to be solved. In some cases, configuring or integrating an existing CRM may be more appropriate than building a new system.
Every CRM project is therefore scoped individually before we provide a fixed quotation.
06How much does a web application or custom app cost?
Custom web applications typically start from CZK 200,000. Projects with more complex workflows, user accounts, dashboards, integrations, administrative systems or custom business logic can range from approximately CZK 200,000 to CZK 600,000 or more.
Unlike a standard website, an application usually involves deeper product planning, UX design, technical architecture, data modelling, authentication, application logic, integrations, testing and deployment.
Depending on the project, we can help with the full process from defining the initial product and prioritising an MVP through interface design, development and launch.
A smaller MVP can typically take around 6–10 weeks, while larger applications may require several months and are often delivered in defined phases.
Because application projects can vary substantially in scope and technical complexity, we first discuss the product, users and business requirements before defining the recommended approach, scope and fixed quotation.
07Can you tell me the exact price before we start?
Yes. The prices above are starting points intended to give you an idea of the typical project scale. After an initial free 15-minute consultation, we define the required functionality, scope, content and timeline and provide a clear project quotation before any work begins.
08Can we start with a smaller sprint or defined phase?
Yes, when that produces a useful standalone outcome. Research, direction-setting, UX definition, technical investigation or a tightly bounded piece of delivery can sometimes be separated from a larger build. The important part is that the phase answers a real question rather than becoming paid ceremony.
09How long does a project take?
It depends on scope, decision speed, content readiness, integrations, review cycles and technical uncertainty. A focused website and a complex application should not be sold with the same calendar. AMUI defines a delivery plan once the work is understood well enough to make the timeline meaningful.
10What if we have a hard deadline?
Tell us early. A fixed date changes prioritisation, sequencing and sometimes scope. The sensible response is to decide what must be excellent by that date, what can safely follow later and which dependencies create real delivery risk.
11What happens if the scope changes during the project?
Some change is normal once real work reveals better information. Small refinements can often be absorbed inside the agreed process; material changes to functionality, content, integrations or direction should be made explicit so everyone understands the effect on cost and timing.
01Is the first consultation really free?
Yes. We start with a free 15-minute consultation to understand your project, goals and what you need from the website. We’ll look at your current situation and recommend the most sensible next step.
02How do you figure out what my website actually needs?
We begin with a discovery workshop where we discuss your audience, business goals, customer journey, content and the role the website should play. From this, we define the project scope, priorities and main conversion goals.
03Will you help me plan the structure of the website?
Yes. We research the market and relevant competitors, define the target audience and create the information architecture, navigation and wireframes. SEO and usability are considered from the beginning.
04What if I don’t have all the content ready?
That’s not a problem. We can work with your existing content, refine its structure and tone, or help you determine what content is needed. For larger copywriting projects, we can also recommend a specialist.
05Do I need to find a separate developer?
No. We handle both design and development, so the project can move from strategy and UX through visual design to a fully working website within one process.
06Will the website be optimised for Google?
Technical SEO is included in the build. This covers essentials such as metadata, structured data, sitemap, performance, responsiveness and other technical foundations. We also connect Google Search Console at launch.
07Can I update the website myself afterwards?
Yes, if your project requires regular content updates, we can build and configure a CMS so you can manage the relevant parts of the website without touching the code.
08What do I get before the website goes live?
You receive a test version to review before launch. We complete QA, fine-tune the final details together and only launch once everything has been approved.
09Do you disappear once the website is launched?
No. We check performance, Core Web Vitals, indexing and the initial post-launch behaviour of the website. Minor post-launch adjustments are included, and ongoing optimisation or SEO can be arranged separately.
10How soon can my website be live?
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.
01Who owns the code and the finished product?
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.
02Will our team be able to update the site themselves?
If content editing is part of the product need, yes: the CMS and editorial model can be designed around the people who actually publish. Routine content changes should not require somebody to edit source code for sport.
03What about hosting and deployment?
AMUI can plan and implement deployment as part of the project. The right hosting model depends on the application, database, CMS, traffic, compliance needs and client ownership requirements. Hosting and third-party infrastructure costs are separate from the fact that the software itself has been built.
04What happens after launch?
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.
05What does handover include?
That depends on the system, but a sensible handover can cover the accounts and access the client needs, CMS/editor guidance, deployment information, relevant documentation and the operational knowledge required to use what was delivered.
01How do you approach accessibility?
Accessibility should influence structure, semantics, contrast, keyboard interaction, focus behaviour, form design and responsive implementation rather than being stapled onto the project at the end. If a project has a specific compliance target, that target needs to be defined in scope and verified accordingly.
02Do you care about performance or mainly the visual design?
Performance is part of the product. Images, fonts, rendering strategy, third-party scripts, hosting and application behaviour all affect how the experience feels. Visual ambition is not an exemption from loading time.
03Is SEO included?
Technical SEO foundations can be part of delivery: semantic structure, metadata, canonical URLs, crawlability, sitemaps, redirects, structured content and indexing setup where appropriate. Broader search strategy, content programmes and ongoing performance improvement are a larger workstream than simply adding a title tag.
04How do you test the work before launch?
The verification approach depends on the product, but can include responsive and browser checks, interaction testing, forms and workflows, content states, permissions, production builds, deployment checks and technical validation relevant to the system. Complex products deserve stronger evidence than “it worked on my laptop.”
05Do you use AI in design or development?
AMUI can use AI-assisted tools as part of research, development and production workflows. The important question is not whether an AI tool touched the work; it is whether the output is reviewed, tested, secure, maintainable and appropriate for the project. Automation does not remove responsibility.