A website helps visitors decide
A website project fits unclear services, evidence or contact routes. Identify the visitors, information they need and action the page supports. Include content, mobile display, languages and forms in the scope.
A new website form is not automatically a CRM, quotation system or schedule. Specify those subsequent functions separately when needed so proposals describe equivalent deliveries.
An AI workflow supports an existing task
An AI workflow fits a repeatable task with useful source information and staff who review its output. Hypothetical example: summarise enquiries, prepare draft replies and save follow-up tasks in an existing system.
The MAAS Enquiry Assistant pilot covers one form or shared mailbox and up to two standard integrations. A different process, automatic sending or additional systems needs separate assessment. Continuation after the pilot requires a new agreement.
Custom software manages additional logic
Custom software may fit when users need roles, cases, statuses and documents that existing systems cannot support. Map the process and permissions first. Then discuss screens, migration, integrations and operations.
Check whether configuring your current software solves the problem first. A new system also needs handover, maintenance and data export. Additional features help only when someone can manage the whole process.
Make the proposal comparable and testable
Bring one concrete situation, current systems and expected volume. Ask what is included, what is excluded, which external costs may arise and how acceptance is assessed. Identify who provides access and approves content.
A website check measures technical website signals; an AI assessment helps organise a process question. Neither replaces a technically reviewed proposal. Choose a package once goals, scope, costs and responsibilities are clear.