1. Understand the goal
Describe your customers, services and current bottleneck. For a website, define the visitor's next action. For automation, map the steps, people and systems already involved. Identify missing information before preparing the proposal.
2. Agree the scope
Specify pages, languages, functions, content and connections. Agree price, recurring costs, responsibilities and timing. A configurator records preferences; the project is defined by the accepted proposal.
3. Prepare and build
Agree who supplies and checks text, images and business information. Preserve the chosen visual style and prepare layouts for mobile and desktop. Confirm changes outside the original scope before including them.
4. Check and hand over
Check the agreed route from input to its intended result, including relevant connections and exception handling. Demonstration behaviour does not prove a customer integration is active. At handover, clarify access, management and support.
5. Improve through actual use
Review real enquiries, content questions and process bottlenecks. Decide which changes belong in ongoing management and which need a separate proposal. Expand once the first complete route works as agreed.