For business website projects · AI in practice
A website built around the next enquiry
Follow an illustrative service-business journey from a visitor's question to a received request, and see where design, AI-assisted delivery and scope fit.
A potential customer arrives with a job in mind. They need to know whether the business provides the right service and how to explain what they need. A useful website gives that person enough information and a clear route to the business.
Consider an illustrative local service company preparing its first website or replacing an outdated one. A possible first release explains services and the area covered, shows relevant work and provides an agreed enquiry route. Use the example to identify a useful scope for your business.
Figure 1 as text
The visitor checks the service and area, sees relevant work, explains the requirement through the agreed route, and the intended person receives the request. Verify the route before accepting the release.
Follow one visitor from service to contact
On a phone, the visitor opens a service description, checks where the company works and reads an example relevant to their need. The next action lets them describe the job. A quotation request might identify the work, location and preferred date, giving the business information it can use in a response.
The route could be a form, an email link or an existing booking service. Agree which fits the work and who receives and responds to requests. If a form is chosen, the fields and confirmation message should help the visitor understand what happens next.
Before accepting the release, follow that journey on a phone and with a keyboard. Send a test request through the agreed route and verify that it reaches the intended recipient. A recorded button click and a received enquiry are different observations. The business also needs someone responsible for responding.
Give the business its own design
The service descriptions, evidence and contact action should shape the information hierarchy. Choose images and writing that represent the actual business. If replacing a site, agree which existing content and addresses must be retained or redirected.
A coherent visual direction and readable mobile layout help visitors follow that information. Image preparation, loading behaviour and accessibility checks belong in the project scope alongside the visual work. Content and image approval need named owners so the build can progress around real material.
Use AI within a reviewed build
At Devmojos, people guide business priorities, experience and architecture. AI coding agents can implement defined tasks, with automated and regression tests and independent review supporting human acceptance. People remain responsible for release.
Where suitable foundations or components can be reused, agree their fit and limits for the project. AI-assisted implementation and clearly bounded tasks are ways to pursue efficient delivery. The company's story, visual direction and content still need specific work. Content readiness, feedback and integrations shape the schedule and quote.
The Tribeca Festival Lisboa (SIC) project provides actual delivery evidence. Its launched website and content platform connects editorial work with the programme and tickets. Filipe led architecture and AI delivery; AI coding agents produced implementation code under his direction. Architecture, decisions, review and release remained human.
Connect what the project needs
For the illustrative service company, a link to an existing booking service may be sufficient. Sending enquiries to a CRM requires assessment of access, compatibility and responsibility. Custom booking, ecommerce and complex applications need their own agreed scope.
Search foundations should support the same clear information: meaningful service descriptions, useful page titles and agreed indexable pages. An appropriate consent-aware measurement setup can help the business examine visits and enquiry activity after launch.
Keep the proposal's cost categories visible. Distinguish initial delivery, hosting, third-party licences, optional care, and any advertising work and media spend. Handover should explain routine editing, access and who maintains the site. This gives the business a clearer basis for choosing and operating its website.
Figure 2 as text
Distinguish the initial build from hosting and licences. Define optional care separately, and give advertising work and media spend their own budget.
Bring the website's purpose to the conversation
Share the current site if there is one, the services to explain and what visitors should do. Identify who can supply content and who will handle enquiries. Devmojos can then discuss fit and a useful scope, with content dependencies and connected systems visible from the start.