Research

Research and methodology

Where the numbers on this site come from, what each one supports, and what it does not. Last updated October 29, 2026.

Four kinds of numbers

Each number on the site carries one of these labels, so outside research, your own scenario and GoSentrix's own evidence are never mixed up.

Market research: Published research by other organizations. We name the source, date and population, and link to it. These numbers describe the market around GoSentrix, not GoSentrix itself.
Buyer research: Anonymized interviews from GoSentrix buyer research. They illustrate situations buyers describe. They are not customer testimonials and do not show how common a situation is.
Illustrative economics · not a result: Figures you calculate from your own inputs in the cost worksheet. They are scenarios, not savings GoSentrix has achieved.
GoSentrix evidence: Results from a controlled demonstration or a customer assessment. None are published yet.

Sources

Market research

Gartner forecasts that by 2027, 80% of organizations in regulated verticals that use application-security testing will incorporate some form of ASPM, compared with 29% when the report was published.

Source: Gartner, Innovation Insight: Application Security Posture Management (as quoted on cycode’s public report page)
Published: January 9, 2025
Population: Organizations in regulated verticals that use application-security testing
Qualification: A forecast for a defined population, not a measured adoption rate for all companies.
Supports: Application-security tooling is consolidating, and GoSentrix operates in that context.
Does not support: That Gartner predicts demand for GoSentrix or for closure review specifically.
Link: https://cycode.com/blog/cycode-named-in-the-gartner-innovation-insight-for-application-security-posture-management-2025-report/

Market research

Veracode reports that critical security debt affects 60% of organizations. Security debt of any severity affects 82%.

Source: Veracode, 2026 State of Software Security
Published: February 24, 2026
Population: Organizations in Veracode’s dataset (analysis of 1.6 million applications)
Qualification: Security debt means flaws left unresolved more than a year after discovery. Critical security debt is the subset severe enough to cause serious damage if exploited.
Supports: Application-security programs continue to carry persistent, unresolved risk.
Does not support: That these organizations have a closure-review problem, or that GoSentrix reduces security debt.
Link: https://www.veracode.com/blog/2026-state-of-software-security-report-risky-security-debt/

Buyer research

A bank customer challenged whether the explanation a software provider had supplied was sufficient.

Source: GoSentrix buyer interview INT-06
Population: One interview
Qualification: One anonymized interview from GoSentrix buyer research. Not a GoSentrix customer or testimonial.
Supports: An example of an outside reviewer asking for a documented basis for a security explanation.
Does not support: That this is typical of all bank relationships, or that the interviewee uses GoSentrix.

The Gartner figure is a forecast. We cite it as quoted on a public vendor page, not from the full report, and will update this entry if we quote the report directly.

How we use interviews

Quotes come from GoSentrix buyer research interviews.
They are anonymized, published with permission, and identified by an interview code such as INT-06.
They are labeled as research. They are never presented as customer testimonials, and interviewees are not GoSentrix customers unless we say so.
A single interview illustrates a situation. It does not show how often it occurs.

Cost worksheet

The homepage worksheet calculates a scenario from figures you enter. It starts with 20 closures a month and a $120 loaded hourly cost as editable examples. The subscription field starts empty, and nothing on the page is a price quote.

Output	How it is calculated
Closures per year	Closures per month × 12
Current annual investigation cost	Closures per year × current effort per case × hourly cost
Capacity released	Closures per year × net effort reduction per case (hours)
Value of capacity released	Capacity released × hourly cost
Cash spending avoided	The cash expense displaced per year that you enter
Recurring net benefit	Value of capacity released + cash avoided − annual subscription
First-year net benefit	Recurring net benefit − first-year implementation cost
Break-even net reduction	(Annual subscription − cash avoided) ÷ (closures per year × hourly cost)

Net effort reduction must include the time your team spends reviewing GoSentrix's output, resolving gaps and supplying evidence.
Capacity released is team time freed for other work. It is not cash saved unless you would actually stop spending it.
We have not measured an effort reduction for GoSentrix yet, so the worksheet has no default for it.

GoSentrix results

No controlled demonstration or customer result is published yet. When one is, we will state what GoSentrix produced, the scope and date, whether records were synthetic, internal or customer-provided, how much human assistance was involved, and what was measured. See what is still experimental.

Corrections and updates

Last updated October 29, 2026. If you find an error in a number or its source, email hello@gosentrix.com. We correct this page and note the date of the change.