This resonates a lot. We’ve seen that a single “static” setup rarely survives once teams move from early traction to real scale.
What’s interesting here is how you’re letting intent drive structure instead of forcing users into one workflow. On the infra side, we notice a similar pattern: early flexibility boosts speed, but once usage grows, observability and failure boundaries become the real bottleneck.
Curious how you’re thinking about edge cases where user intent shifts mid-session—do you reclassify continuously or lock the UI once a path is chosen?
Good point, currently if user intent classified as DIY and because it take more time to process the plan and the products, I added a button during process to cancel that will disregard the DIY path and simply return only the products. There is also follow up with context and can update the results and UI as well, but still finetuning these hard turns from DIY to shopping and vice versa.
This resonates a lot. We’ve seen that a single “static” setup rarely survives once teams move from early traction to real scale.
What’s interesting here is how you’re letting intent drive structure instead of forcing users into one workflow. On the infra side, we notice a similar pattern: early flexibility boosts speed, but once usage grows, observability and failure boundaries become the real bottleneck.
Curious how you’re thinking about edge cases where user intent shifts mid-session—do you reclassify continuously or lock the UI once a path is chosen?
Good point, currently if user intent classified as DIY and because it take more time to process the plan and the products, I added a button during process to cancel that will disregard the DIY path and simply return only the products. There is also follow up with context and can update the results and UI as well, but still finetuning these hard turns from DIY to shopping and vice versa.