​SharePoint can be used to build portals, intranets, extranets, except for Internet portals, which is only possible if SharePoint on-premise is deployed. Portals need to contain information for them to be useful. They need to contain relevant, updated information for users to use them repeatedly. That's where information architecture plays an important role in keeping the information fresh, and agile to react to the constant change in business.

Our approach to building portals is very different from our competitors. We focus on getting the information architecture right, then we build the functionalities required to support the information. This mindset allows functionality to follow the information, and information architecture changes with the business, be it due to business growth, or change in the business environment. 

Before we build the portal for our customers, we access the maturity of the customer and design the portal that is suitable for them. At one end is the basic portal, built to help build up the content with the basic information architecture, and designed to let users get used to the different concepts. At the other end is the search-driven portal, where information is retrieved using search, but the users are not aware of it. 

The portals evolved as the users grow in maturity, and the next version builts on top of the previous version, without the need to tear down. Just like how a child grows with knowledge to become an expert in his chosen field when he is an adult. And the journey doesn't end, as its life long learning journey. ​

​​