Skip to content
people at office workspace

Why DIY? Reasons to Buy or Build

CIOs and other organizational decision-makers are looking past the so-called digital sprints of 2020 and planning on transformation technology efforts, according to industry analysts. But when it comes to transformational efforts, does it make sense to go it alone–that is, do it yourself?

Often, companies favor building software projects in-house, fearing that third-party solutions may not meet their specialized needs or be compatible with existing systems. The challenge is two fold: determining whether some of your IT staff has specialty skills, such as data mining or data visualization. And if you are lucky enough to have a large enough team to tackle a transformational technology, does it make sense to tie them up with one project?

When considering the age-old problem of whether to build or buy, you’ll get a different answer depending on the business landscape and project urgency. To determine whether to keep a software project in-house or search for a collaborative technology partner, it makes sense to look at the following four major factors: cost, control, connectivity, and maintenance. 


According to Gartner, global enterprise software spending is projected to climb 9% in 2021 to a total of around 4.2 trillion dollars. According to John-David Lovelock, research vice president at Gartner, “This means building technologies that don’t yet exist, and further differentiating their organization in an already crowded market”.  CEOs are much more willing to invest in technology that has a clear tie to business outcomes, and less so for everything else, according to Gartner.

The challenge is that IT projects tend to exceed both time and cost estimates. In short, IT teams often find themselves wishing they had found a reliable software or solutions partner.  While purchasing software from a third party can sometimes have a higher upfront cost, it’s also a known cost for a product that is ready to use immediately or by a set date. As one Forester report put it, technology implementations – even those “really easy” software-as-a-service based implementations – are no different than the DIY home improvement project gone totally awry with surprise time and cost requirements.


One of the biggest appeals of building in-house is that the software can be customized. On the other hand, that approach can leave a company entirely dependent on its coders and developers to deliver a perfect product. And companies are often left with unusable code bases created by developers who no longer work at the company, meaning they might need to hire new developers to rebuild code from scratch or maintain a legacy codebase. When you build, you have 100% control of the software’s function. This comes, however, with weaknesses, as it creates a burden on IT teams, and also leaves them without the benefit of collaboration with dedicated developers who are focused solely on the type of software they are deploying or coding.


Each company has its own unique ecosystem of applications that all need to be compatible with systems beyond the company. Building your own solutions should help ensure total compatibility, something that isn’t guaranteed with all third-party vendors. It’s important to assess if a third party has pre-built APIs or an open-source platform that allows for integrations, or a way to leverage your existing systems.


When you buy software, SaaS vendors handle all the maintenance behind the scenes and usually roll the costs onto a subscription fee. It’s important to understand that these external vendors have hundreds of hours of experience setting up and maintaining their software. If you choose to build, you will be responsible for all the maintenance of your new software: managing the launch, resolving any bugs, training people to use the software, setting up passwords, etc. All of this maintenance will require increased bandwidth, and possibly additional staff. 


The Lambent AI-powered platform provides facilities and security teams with an accurate, real-time understanding of how many, and how often people are utilizing different spaces. The software enables smarter decisions related to crowd density, space utilization, safety, maintenance, and guest experience while also providing easy access to valuable data trends for ROI related to space management.  If you’re unfamiliar with spatial utilization and the terms surrounding it, check out our blog on some key definitions. If you are considering installing a space utilization software. For more on how spatial representation software can bring density data to life, check out our blog on spatial representations.

Layering our Lambent software over existing infrastructure turns data into actionable intelligence. Our software monitors occupancy and provided predictive analytics for space planning. We’re helping transform corporate and higher education campuses into smart spaces.

To learn more about how Lambent helps facilities teams deliver on priorities like this, schedule time with one of our experts today.

Subscribe to the Newsletter

Keep Up To Date With Updates & Insights

*By clicking the "Subscribe" button, you are
agreeing to the Terms and Conditions.

Related Posts

Purdue University is not actually out of space, and you might not be either 

The number one topic at Tradeline's University Facilities Conference was Occupancy Analytics. Find out more.
Read More >
Students using technology on campus

Managing Campus Space in 2024: Insights from the Higher Education Round Table

Learn what the leading institutions are thinking about in terms of space planning technologies from our New England
Read More >
Corporate Office spaces with only one room used

How to identify opportunities for mothballing underutilized office space

Learn how to identify opportunities for mothballing underutilized office space.
Read More >