From the previous questions, SharePoint can be seen to have real potential – in particular the ability to do “good enough” record keeping and gain adoption. However, we see and hear of too many feral implementations where inadequate or no IT infrastructure planning or information design has been done. If you can’t get technical governance and the money/support resources then we would caution against SharePoint use.

Open source is doing great things in the Web 2.0 and collaborative space - on small and in some cases massive scales. However, support can be problematic. Record keeping functionality needs to be thought through and designed as it does with SharePoint. In other words, it can be a legitimate path, but you need to do the hard yards as you do with SharePoint.

This sounds like "software as a service can do anything" thinking and hammer-nail advice. SharePoint for line of business applications can work but be very careful

This is our view. The ability to move from
Business need > Requirements > Specification > Build TO
Business Need > Requirements >Prototype>Iterate
cuts costs, timeframes and brings a business improvement focus to where it needs to be – close to users. Talk to us about how to get technical governance ; business case; change management; and information design using our iWorkplace methodology. With our compliance packs, you can get started quickly and at low cost.