i already know what i want to do

i recently wanted to upgrade one subscription while keeping another separate. i ended up asking an assistant how three linked accounts related to each other, which billing arrangement would change, and whether i would be made to combine them.

i knew the outcome i wanted. i did not know how to express it safely through the account setup in front of me.

first i asked whether the accounts could stay separate. then i asked whether upgrading one would require the unification flow. i was trying to understand the consequences before taking the action.

this is part of my frustration with software. a product has a model of accounts and subscriptions. i have a change i want to make. i would like the product to work out the implications and show them to me.

for this task, the useful view would have been a preview of the plan being upgraded, its resulting price, and the status of the plan i wanted to keep. if my constraint could not be honored, that needed to be visible before i committed.

an agent could help produce that preview. it would need access to the actual account state and the rules governing the change. a plausible explanation of how billing usually works would leave me with the same uncertainty.