The functionality of the solution set in Claromentis intranet framework are so large now that we often spend considerable time during projects, and especially at inception – in choosing from various options in order to meet a business need.
Since the Claromentis business framework also includes a complete intranet API, we also need to consider whether a bespoke application to meet the client need is the best solution, as opposed to the superficially ‘easier’ route of configuring an existing application to meet the requirement.
This is particularly the case with e-forms, which for many simpler business needs can indeed be configured to meet a requirement as initially expressed to us. This is basically because many small applications are based on collecting data, moving along a process and notifying participants of significant events that need their attention – exactly the space Process Manager occupies.
When we are making these decisions we are in general terms trying to balance 3 disparate needs :
- Project risk – configuring and localizing an application is a relatively simple and certainly time limited process that does not involve scope creep, whereas developing a bespoke intranet application takes time and resources.
- Budgets – applications need to be licensed, this might be commercially inappropriate for the number of users that need access.
- Flexibility as a solution for future requirements – we have learnt that there is always a phase 2, and after using the solution in phase 1 the client may well drastically change the application requirements – it is so much easier to evolve a bespoke application.

Technology selection factors
What we are finding is that we are emphasizing flexibility more and more as we continue to engage with intranet clients around the world. And because we can now give so many examples and speak with the confidence that comes from working in this space for 10 years now, we are noticing that clients are increasingly listening to us.
The result is that they do take slightly longer to get to phase 1, they take more risk, and generally may spend slightly more to get to the first release – but the platform for their success is built on the solid foundation of an intranet application that was built from the ground up to meet the need, and can grow without constraints to continue to serve the client well.
If, as is so often the case – phase 2 is considerably different to the initial requirements – the client in the end saves money as well as getting exactly what they need – since the changed specifications do not require us to start again.
In the fast moving web based intranet world where there are almost no technological limits, building for possible feedback and change requests is basically too important to ignore.
So in the longer term it seems that time and time again actually focusing on flexibility can minimize budget and project risk, rather than increase them. Another great lesson.
Intranet-Extranet, Products, Workflow Services
bespoke development, e-forms, intranet software