TrustSource Business Case

Based on the experience of several years, we collected data to determine the average savings value a TrustSource Setup may provide. Please find below an overview of the three main categories where we currently are able to calculate benefits.

Operational Savings:
TrustSource is a hosted service. This frees you from efforts to run updates, backups and other expenses such as CPU-power or server capacity.
Legal & documentation work:
TrustSource comes with a legal engine retrieving obligations from known licenses as well as the ability to prepare legal documentation in an automated manor. This saves on legal experts as well as on developer time.
Component Update verification & followup
In general, no code should enter your services without having been verified. TrustSource takes a lot of this work by evaluating the new versions and collecting the information required for the legal documentation as well as simple security checks, e.g. known vulnerabilities, and alerts users on known / matching issues.

Besides these aspects there are even more benefits. The transparency is of such a high value. With TrustSource the answer to the question: “Which projects are impacted by log4j v2.15.0?” is just one click away. Or the search for the next component version, that is not vulnerable anymore can be retrieved directly through the bump hint. All these sort of savings do not yet have enough data to build reliable calculations.

Below you will find a dynamic calculation. Change the variables to explore your business case.

TrustSource ROI Calculator

Generating and managing SBOMs at scale is not a might, it is good software development practise. However, since economic subjects require justification for investments, find below a list of savings potentials TrustSource will bring to your organisation. Feel free to play around with all assumptions. To get a more sophisticated calculation, reach out to the TrustSource team.

Annual savings (EUR)

=#8 + #11 + #17

Savings on Component handling & followupEstimate the savings potential based on effort estimates for component meta data handling

#1 - Avg. # releases per year

124

#2 - Number of projects*

select the number of project that typically run in parallel

#3 - Avg. number of components per project*

enter the number of transitive dependencies you have in average

#4 - Average change frequency*

change frequency (%) on dependencies as from our experience, adjust to your case

#5 - Average amount of time (min) saved per component*

adjust the avg. time required to review and check new components

#6 - Monthly effort saved by TrustSource (hrs)

= ( #2 * #3 * #4 * #5) / 60

#7 - Internal costs (EUR/hr) for a developer*

adjust the internal rate per hour for your developers

#8 - Annual savings on component followup (EUR)

= 12 * #6 * #7

Savings on operating expensesSummary of expenses saved by not operating the tooling inhouse

#9 - Avg. number of days to setup and maintain all tooling required for SCA, SBOM creation etc.*

#10 - Daily rate for an operator (EUR/day)*

adjust to the internal daily rate of your operators

#11 - Annual savings on tooling operations (EUR)

= #9 * #10 * 12

Savings in legal document handlingSums the efforts required to provide release documentation and assessment

#12 - Effort required by developers to review and assemble documentation (days/release)*

select the effort you assume will be required per project and release to assemble documentation for legal assessment.

#13 - Daily rate for a developer (EUR/day)*

= #7 * 8, feel free to overwrite

#14 - Time required by lawyer to review release documentation (hrs)*

select amount of hours required by a lawyer to review the documentation per release

#15 - Avg. hourly rate of your lawyer (EUR/h)*

You may adjust the value between 100 and 500 EUR/h

#16 - Costs per release & project saved (EUR)*

= #14 * #15 + #12 * #13

#17 - Annual savings across all releases and projects (EUR)

= #16 * #1 * #2

TrustSource Business Case

TrustSource ROI Calculator

Keywords