Dear Mr. Bedell,
MSTR Technology needs to spend some more time on the user interface. Report Services is absolutely the right idea from a formatting perspective, but the powerful interactive analytic capabilities are still stuck back in the native MSTR Web objects.
I'm working with a Business Objects person a lot right now, and am getting dinged a lot because the BO (not Webintelligence) interface simply allows any element to be placed anywhere, while retaining the "on-report analysis" features such as filtering and sorting. It's difficult to tell end users that they can't have a layout that they can create in Excel, Crystal, or BO because MSTR won't support it, while still retain the ability to INTERACT with the data.
Once MSTR manages to marry the rich Report Servies formatting -- in something other than PDF! -- with the robust MSTR Web analytical feature set, then you'll have a killer app.
This enhancement has to be easier than the hill that BO has to climb in re-architecting their entire back-end to merge the BO/Crystal assets AND play catch up with the server-centric MSTR 7.x approach, which they have admitted is the direction in which they are moving.
If MSTR doesn't act fast, then you guys won't have the whole "enterprise class architecture" argument to stand on anymore. BO has always copied the best of your technology, and your beloved 7.x architecture is now on their radar -- just as it was with Cognos, resulting in the ReportNet architecture, which looks very much like the first release of MSTR 7.0 (i.e. not fully baked, but still tastes okay). If BO is successful, then BO/Crystal will offer the best user interface as well as the best enterprise architecture.
Best of luck to you and your team.
MSTR Fan