A web system project should begin with the work people need to complete, not only the pages someone wants to see. Describe the users, current process, repeated problems, important records, and decision the first release should support.
Clarify ownership early. The project needs someone who can confirm requirements, provide examples, review data, test the workflow, and approve the result. Without that role, small uncertainties can become expensive changes near launch.
For a Johor Bahru business, the local context may include branches, suppliers, staff roles, bilingual communication, delivery areas, or existing software. Record those facts and boundaries so the development team can plan a realistic first stage.
Before development or a major change, turn this idea into a clear operating agreement: define the people who use the process, the records that must remain trustworthy, the approval boundaries, and the result the business will review. A small pilot with real examples can reveal missing rules earlier than a large build and make later support, handover, and integration safer.