Most conceptual Web design methods proposed so far focus on browsing (i.e. inquiry tasks) but it is not clear how to integrate them with transactional tasks which have a lasting effect. Moreover, tasks are commonly integrated into higher-order behavioural units: the processes. For instance, the process of a purchase includes "browsing the catalog", "adding to the trolley", ''filling up billing data" and other tasks that end up in the fulfillment of the order. We claim that these distinct task types (i.e. inquiry and transactional tasks) impose different demands and require distinct skills from the designer. On these grounds, we envisage a bottom-up approach to web application construction. First, inquiry and transactional task design is conducted by two separate teams each with expertise in one area. Second, processes are realised through inter-task dependencies. Declarative and separate description of tasks and dependencies accounts for maintenability of the whole solution. This paper presents how this approach has been realised in AtariX, a tool environment for the specification and support of web applications. Transactional tasks reside in the middle-tier implemented as Enterprise JavaBeans whereas both inquiry tasks and inter-tasks dependencies are regulated at the Web server.