It might seem to make sense to create an client object type, a nested table of client, a client_services object with an attribute of client nested table and then a table of client_services types.
The Object perfect for that application is a "client" object identified by client_name or account number.
That Client object has all of the attributes of one of your clients, a company name, an address, a list of accounts with all of the account attributes, a list of client_services, and so on.
The main debate seems to be in the smaller bits of information to be displayed.
While the developers and I agree that the larger items need to be objects, They are wondering if the smaller items (100 charachters or so) shouldn't be varchar. These smaller items will be hit far more often, which leads to the question, When exactly do you see the performance hit?
Would using the varchar on the smaller items give us any perfomance benefit at all? If so, would it be enough to justify using it over the clob?