Where the numbers come from.
Benchmarks, regulatory mechanics, and frameworks cited on this site are listed here with their sources. Targets and estimates that are Preside's own are labeled as such. This page gives each source link and how Preside applies it. Other pages cite specific anchors here instead of repeating the disclosure inline.
If you find a claim on this site that does not trace back to one of these anchors, email engage@PresideInc.com. We update this page when the underlying sources update.
Scope
What this page is not.
A list of frameworks Preside cites is not a list of frameworks Preside has built or owns. Preside applies these standards; the standards themselves are maintained by the regulators, standards bodies, and researchers credited under each entry. Source links point to the original publisher of each source.
Terms
Two terms defined here.
-
Defensible
A conclusion that can be traced to identified evidence, stated assumptions, and a documented method. It does not mean a regulator, auditor, insurer, buyer, or court will agree.
-
Independent
Performed by people who did not build or run the controls reviewed. It does not mean auditor independence, certification, or regulatory approval. Preside is not paid by the providers it recommends. Preside may later be engaged to manage remediation of what a review finds.
Experience anchors
How we describe what we have run.
Preside is an operator-led firm. The experience claims on this site reference engagements across the founders' careers prior to and including Preside, in roles spanning embedded Microsoft Enterprise Strategy Consulting, large-enterprise IT leadership, post-close integration, and corporate restructures across financial services, life sciences, healthcare, retail, and technology. Specific client names are not used.
-
"100+ organizations" reference (career aggregate)
The "100+ organizations" framing refers to the cumulative count of organizations across the founders' careers in advisory, embedded consulting, post-close integration, and operator roles. It is not a count of Preside engagements alone. Specific organizations are not named because most engagements operated under confidentiality.
Relevant to: buyers evaluating operator depth.
-
No portfolio-company callouts (policy)
Preside does not name PE portfolio companies on this site. The experience described here is career experience of the founders. PE engagement is typically subject to GP confidentiality and downstream LP reporting constraints. The site uses generic deal-stage language (entry, hold, exit) rather than named situations.
Relevant to: GPs, operating partners, and diligence teams expecting discretion.
Initiative outcome anchors
The benchmarks, targets, and estimates we cite.
Each figure below is labeled as a benchmark, a design target, or a Preside estimate. Third-party figures name their source.
-
15 to 25 percent savings target for in-scope IT spend (Preside design target)
Our design target is to identify savings of 15 to 25 percent of in-scope technology spend (vendor, licensing, and managed-service spend) during the Initiative. Capturing them depends on renewal dates and can take up to twelve months. This is a target the work is built around. It is not a market benchmark, a guarantee, or a typical result. The figure for your company is sized from your contracts, utilization, and renewal calendar. The Cost Optimization and Vendor Rationalization Initiatives use this target.
No published benchmark states this range. The nearest published figure we found is BCG's statement that improving IT cost management "can reduce technology spending anywhere from 15% to 40%, depending on the situation" (BCG, Feb 2024, based on client experience; BCG sells cost consulting).
-
SaaS portfolio size (benchmark)
Zylo's 2026 SaaS Management Index reports 305 applications on average and 240 median across its sample. Productiv's 2025 statistics post states that the average SaaS portfolio decreased to 342 apps, down from 374 the previous year. The two figures differ because the sources use different samples and definitions. These figures describe portfolio size. They are not savings figures.
Sources: Zylo 2026 SaaS Management Index; Productiv, "The top 9 SaaS statistics that IT leaders need to know in 2025" (archived May 15, 2026).
-
About 30 percent of digital transformations meet target value (BCG, 2020)
Cited on the Change Readiness Initiative page. Boston Consulting Group's 2020 research reported that about 30 percent of digital transformations met or exceeded their target value and resulted in sustainable change. BCG sells transformation consulting.
Source: BCG: Flipping the Odds of Digital Transformation Success.
-
88 percent of AI POCs never reach production; 95 percent of GenAI pilots produce no measurable ROI (benchmark)
Two separate measurements. IDC and Lenovo report that 88 percent of AI proofs of concept never reach production. MIT NANDA's 2025 research found 95 percent of generative AI pilots in their sample produced no measurable ROI. Both are cited on the AI Technical Readiness Initiative page.
Sources: IDC + Lenovo AI research, MIT NANDA.
-
83 percent of organizations plan agentic AI; 29 percent feel ready (benchmark)
Cited on the AI Security and Compliance Initiative page. Cisco's 2026 State of AI Security report is the source. Preside's view is that the gap is in controls such as identity, scoped permissions, action logging, and a kill switch. The Cisco figures measure readiness, not which controls are missing.
Source: Cisco State of AI Security 2026.
Financial framework anchors
Where the Tech P&L and IT spend benchmarks come from.
-
TBM Council Taxonomy v4 (widely used IT-finance taxonomy)
The Technology P&L sample on /for-cfo/ is loosely based on the TBM Taxonomy v4. The tower names in the sample are adapted: End User Computing, Infrastructure & Cloud, Business Applications, Data & Platform, Security, Compliance & DR, IT Management & Delivery, Telecom & Connectivity, and Strategic Initiatives. TBM is a widely used taxonomy for aligning IT spend to business outcomes.
Source: TBM Council Taxonomy.
-
Avasant IT Spending and Staffing Benchmarks (annual)
Avasant publishes IT spending ranges by industry. A live engagement compares a company's total IT spend as a percent of revenue with a published benchmark of this kind. The sample P&L on /for-cfo/ does not use an Avasant figure. Gartner publishes a comparable benchmark.
-
Gartner IT Key Metrics Data 2025 (annual)
The companion benchmark to Avasant. Cited on /for-ceo/ for the run-cost-trajectory dimension on the quarterly view. Gartner IT Key Metrics Data is a paid Gartner publication. The CEO sample cites document 5973171 (Professional Services); document 5970339 covers Midsize Enterprises.
Source: Gartner Document 5970339.
-
Vertice SaaS Benchmarks 2025 (annual)
Not used in the sample P&L. No Vertice figure appears there, and the vendor concentration statement in the sample is an illustrative assumption. Listed here as a reference for SaaS spend benchmarking.
Risk methodology anchors
How dollar-denominated risk is calculated.
Preside expresses technology risk in financial terms on every board-facing deliverable. The methodology and the underlying frameworks are public.
-
Annualized Loss Expectancy (Hubbard & Seiersen)
ALE = Single Loss Expectancy (SLE) multiplied by Annualized Rate of Occurrence (ARO). SLE is grounded in asset value and exposure factor. ARO is grounded in industry incident data and the organization's own history. The worked examples on /ale/ use point estimates for clarity. Where data permits, Preside expresses each input as a range. Doug Hubbard and Richard Seiersen's How to Measure Anything in Cybersecurity Risk describes calibrated estimates and range-based risk quantification, which Preside draws on in the Security Posture, Board Governance, and AI Security Initiatives.
Source: How to Measure Anything in Cybersecurity Risk (Wiley, 2nd edition).
-
NIST Cybersecurity Framework 2.0 (February 2024)
NIST CSF 2.0 is a voluntary framework widely used by US organizations. Organized around six functions: Govern, Identify, Protect, Detect, Respond, Recover. The 2.0 release added Govern as a top-level function, which puts governance and oversight at the center of the framework. Used as the structural backbone for the Security Posture Initiative.
Source: NIST Cybersecurity Framework.
-
NIST SP 800-131A Revision 2 (March 2019)
"Transitioning the Use of Cryptographic Algorithms and Key Lengths." Used as a reference for cryptographic algorithm and key-length transitions across Preside's briefings, compliance analyses, and any cryptographic control discussion.
Source: NIST SP 800-131A Revision 2.
-
NIST SP 800-53 Revision 5 (September 2020, updates through 2025)
"Security and Privacy Controls for Information Systems and Organizations." Used for FedRAMP-adjacent assessments and for the SC-13 (Cryptographic Protection) finding language in Preside's compliance briefings.
Source: NIST SP 800-53 Rev 5.
-
NIST SP 800-171 Revision 3 (May 2024)
"Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations." CMMC Level 2 requirements are based on NIST SP 800-171. The revision that CMMC assesses against can differ from the latest published revision, so a requirement number cited in a Preside brief names its revision.
Source: NIST SP 800-171 Rev 3.
AI methodology anchors
Frameworks behind the AI Readiness and AI Security Initiatives.
-
NIST AI Risk Management Framework (AI 100-1, 2023, with GenAI profile 2024)
The structural backbone for the AI Readiness and AI Security Initiatives. Four functions: Govern, Map, Measure, Manage. Readiness scoring maps to Govern; data and use-case assessment maps to Map; control posture maps to Measure; operational posture maps to Manage.
Source: NIST AI Risk Management Framework.
-
OWASP Top 10 for LLM Applications (2025 edition)
Used as the prompt-injection-surface taxonomy for the AI Security and Compliance Initiative. LLM01:2025 (Prompt Injection), LLM02 (Sensitive Information Disclosure), and LLM06 (Excessive Agency) are among the risks most relevant to agentic deployments.
Source: OWASP LLM Top 10.
-
EU AI Act (Regulation (EU) 2024/1689)
Articles 9 to 15 cover high-risk system obligations. Article 50 covers transparency. Cited on the AI Security and Compliance Initiative and the AI Governance briefings.
Source: EU AI Act, Official Journal.
Regulatory anchors
The compliance mechanics every board, CFO, and CCO page cites.
-
SEC Item 106 of Regulation S-K and Item 1.05 of Form 8-K (Final rule 33-11216, 2023; disclosure phased in from December 2023)
Item 106 requires the annual 10-K to describe the board's oversight of cybersecurity risk and the management process for assessing and managing material risks. Item 1.05 requires disclosure of material cybersecurity incidents within four business days of the materiality determination. The clock starts at the materiality determination, not at incident detection. Cited on /for-board/, the Board Technology Governance Initiative, and every CISO page.
Source: SEC Final Rule 33-11216.
-
Delaware Caremark doctrine (Sorenson 2021, Bingle 2022)
Directors of Delaware corporations have a fiduciary duty of good-faith oversight of mission-critical risks. The Delaware Court of Chancery dismissed the SolarWinds derivative suit in Construction Industry Laborers Pension Fund v. Bingle (Sept. 6, 2022) and the Marriott derivative suit in Firemen's Retirement System of St. Louis v. Sorenson (Oct. 5, 2021). The linked analysis discusses how claims tied to misleading statements about cybersecurity may be treated differently. This is a summary, not legal advice. Cited on /for-board/ and the Board Technology Governance Initiative FAQ.
Source: Harvard Law CorpGov Forum analysis.
-
HIPAA Security Rule (45 CFR Part 164, with NPRM December 2024)
Cited on the Compliance Readiness Initiative and the healthcare briefings. The existing rule treats encryption as an addressable specification under 45 CFR § 164.312(a)(2)(iv) and § 164.312(e)(2)(ii). The HHS December 2024 NPRM proposed to move encryption from addressable to required for ePHI at rest and in transit, and to add a compliance-audit standard at least every 12 months. It is a proposed rule. Check the HHS link below for its current status.
Sources: 45 CFR § 164.312; HHS HIPAA Security Rule NPRM.
-
PCI DSS 4.0 (mandatory March 31, 2025)
Cited on the Compliance Readiness Initiative. As of March 31, 2025, the 51 future-dated requirements that were optional best practices in 4.0 are mandatory. Requirement 4.2.1 mandates strong cryptography for cardholder data transmission. Requirement 8.3 covers authentication. Requirement 12.3.3 requires a documented cipher inventory and remediation plan.
Source: PCI DSS v4.0 Document Library.
-
NYDFS 23 NYCRR Part 500 (Second Amendment, phased through November 2025)
Cited on /for-board/ for the CISO attestation language. The board or senior governing body must have sufficient cybersecurity understanding to exercise oversight, require management to maintain the program, and review the annual CISO program report.
Source: NYDFS cybersecurity guidance.
-
CMMC (Cybersecurity Maturity Model Certification)
Cited on the Compliance Readiness Initiative for defense-contractor briefings. CMMC Level 2 and Level 3 requirements map directly to NIST SP 800-171 and NIST SP 800-172. CMMC certification is a contract requirement for many DoD contractors.
Source: DoD CIO CMMC program.
-
FFIEC IT Examination Handbook (Architecture, Infrastructure, and Operations booklet)
Cited on /for-board/ for OCC, Fed, and FDIC-supervised institutions. The board approves IT strategy aligned to risk appetite, receives regular Architecture, Infrastructure, and Operations governance reports, and is educated to review performance.
Source: FFIEC IT Handbook.
How to use this page
If you came here from a footnote.
Other pages on this site link to specific anchors above via in-page IDs (for example, /methodology/#risk-ale for the ALE methodology). Each anchor names the source, the version or date, and how Preside applies it. Click through to the source. If the source has updated and we have not, email engage@PresideInc.com and we will fix this page.
Want to see the method applied to a specific output?
The Initiative pages apply this method to a specific output.
Each Preside Initiative applies the frameworks above to a concrete deliverable in two to six weeks. Fixed scope, fixed price.
Not sure which Initiative fits? Take the four-question Find Your Path tool for a personalized recommendation.