By KOH NOMAD · AI & digital business
Choose the visitor's main action
A website may primarily explain a service and help a visitor make an enquiry. A web app usually adds continuing interactions such as accounts, saved records, bookings or collaboration. Start with the action the customer needs, not a preferred technology.
Write one end-to-end journey: arrival, information needed, action, confirmation and follow-up. If a simple page and a genuine contact method satisfy it, a complex account system may add unnecessary work.
Write a project brief that can be tested
Define the audience, problem, essential pages, required content and the first successful outcome. Add constraints: accessibility, mobile use, supported languages, budget and who maintains the site.
Separate the first release from later ideas. For example, an initial service site might need an offer page, proof of work and an enquiry path. A customer portal can follow when repeated customer needs justify it.
Plan the operational boundaries
If accounts are required, define who can read and change each type of record. If payment is involved, use a single clear payment flow and verify server-side confirmation before granting paid access.
Keep a prototype separate from operational claims. A button that shows success without saving or transmitting a request is not a functioning enquiry system. Specify what each confirmation proves and what happens if the operation fails.
Use AI for drafts, then verify the result
AI can assist with a sitemap, wording, test cases or a prototype. Someone still needs to check factual claims, links, access permissions, calculations and actual submission behaviour.
Prepare a review checklist before generation. Test with realistic content and a narrow-screen device. Check keyboard navigation, meaningful labels, error messages and whether the main task works without hidden manual intervention.
Build discovery and maintenance into the brief
For public pages, plan clear titles, useful descriptions, readable headings, internal links and a sitemap. Keep important explanatory text available to visitors and search engines.
Document who owns the domain, repository, hosting, data exports and deployment access. Include updates, backup recovery, content corrections and ongoing service charges in the operating plan. Delivery is the start of maintenance, not the end.
Your quick checklist
- One customer action and complete journey.
- A brief with launch scope and later ideas.
- Real confirmations and access boundaries.
- Mobile, keyboard and failure-path checks.
- Domain, code, data and maintenance ownership.
Not sure where to start? Find your next business step.
Find a place for your next workday
Explore public city guides, then confirm the current conditions with the venue.
