Elantis approaches all our projects by first evaluating whether your goals can be accomplished using configuration of a low-code or no-code platform. If configuration will not meet your needs, we then look at custom development. Why? Configuration of low-code/no-code platforms is cheaper and faster. We want to provide you with cost effective solutions that provide real ROI as quickly as possible.
In the past, we have discussed how configurable platforms, such as Nintex, can save you money on automation. Can this model also be used to save money on your intranet?
Your company is unique, and you want your intranet to be customized to your needs and culture. But we find that all companies want the same basic functionality from their intranet. For example:
These common features and functionality don’t need to be uniquely re-developed for each intranet. Why re-invent the wheel? Instead, an intranet-in-a-box solution provides these features with significantly lower design and implementation costs.
Around this framework, we can customize pages and branding as needed to make your intranet truly yours.
Today’s modern workforce is increasingly embracing flexible workstyles – working remotely or on a modified schedule and communicating on the go. Employees need their intranet available where ever they are, through any device.
Using custom development means adding in development time for each intranet platform: desktop, Android and Apple phone or tablet. More development time means – you guessed it – higher costs. These costs can grow exponentially if you decide to make modifications to your intranet in the future. On the other hand, an intranet-in-a-box solution with a responsive design provides a user-friendly experience, without the additional design costs.
Another area where costs creep in for custom development is ongoing maintenance. This is especially true if your organization needs to do a SharePoint upgrade or migration. Custom development can create complexities for a SharePoint upgrade. Even if your intranet is based on SharePoint Online so there are no future migrations anticipated, Microsoft updates can cause issues with custom development.
On the other hand, intranet-in-a-box solutions are typically simpler to maintain, even in the event of a migration or upgrade. An intranet-in-a-box solution is well tested to withstand SharePoint updates and provides the advantage of support from the manufacturer. Ultimately this will save you money in long term costs.
Perhaps you have concerns about the cost of software subscription intranet-in-a-box solution. Elantis creates intranets for our clients using Valo software, which has a perpetual licensing model. Valo’s “pay one, use always” model keeps your ongoing operating costs to a minimum.
What is more, Valo’s pricing model is modular, meaning you only pay for the components you need. For example, if multilingual capabilities are not relevant to your business, you don’t need to purchase the multilingual module.
Custom developed intranets average 92 full time work days, and more than two-thirds of custom developed intranets face cost overruns. In contrast, Elantis designs and implements Valo intranet for our clients in a matter of weeks, not months.
Elantis’ Valo implementations for Office 365 are completed as a fixed cost engagement, so there are no cost overruns. Our fixed cost model put the risk on us, rather than on you!
Amy is a results-focused marketing professional with over eight years’ experience working closely with sales teams to provide effective solutions to customers.
Edmonton, Alberta — Dec 3, 2019 — Elantis Solutions Inc. announced that it is the only company in the world with two Nintex virtual Technical Evangelists (vTEs) on staff. There are only three vTEs in Canada – and less than sixty in the world – making this a unique competitive advantage for Elantis.
What are the digital transformations trends shaping 2020? Let’s unpack a couple of these and understand where you can stay ahead of the technology curve.
Can I use one Microsoft Flow for multiple libraries? I could Save As, but then I’d have to make updates to each Flow individually. Is there a better way?