How about "not yet" as an answer? Solutions always start with generating value against some relatively narrow use case. As they grow, they tackle new use cases but inevitably need to start thinking about efficiency. They also tend to move "upward" in the stack. Where are the constraints that this blocking more adoption? What are the new user groups that are using the solution but struggling? What components of this new solution are already aging out.
How about "not yet" as an answer? Solutions always start with generating value against some relatively narrow use case. As they grow, they tackle new use cases but inevitably need to start thinking about efficiency. They also tend to move "upward" in the stack. Where are the constraints that this blocking more adoption? What are the new user groups that are using the solution but struggling? What components of this new solution are already aging out.