And when we do our relational reach through, we look for the highest level of aggregation we can find to do it with because therefore it reduces processing. By highest level of aggregation, I mean, let's say I have some data by zip code, some data by metro region, some data by state, some by country. When a user gives a query and they want to see something like the trendline by geography, if they limit their ge ographies to metro regions, we'll check if there is any stored by metro region. We won't restrict what you can do. If you don't already have it aggregated by metro region, we'll aggregate it on the fly for you.
People often forget that kind of thing.
Very often people come from the bottom up instead of the top down. And then I think you'll find something very quickly. You'll find that a lot of u sers need analysis, but don't necessarily themselves do a lot of analysis. What I mean by that is part of their application is doing a lot of calculations, the trends and projections, the what-ifs and simulations, and so on. They wouldn't be able to define those on their own, because they're not analysts.