Trust

A method you can see, and a model you can shape

“Prove, don't claim” applied to Testify's own scoring. The opposite of a proprietary number a buyer cannot interrogate.

Testify's methodology is transparent to the customer inside the platform and authorable: you can see how a score is produced, and you can shape the model. A gate engine with canonical gates and composite scoring, a capability-coverage matrix, and a Console for inspecting score derivation make the method inspectable.

Inspectable by design

The Cyber Maturity Engine is customer-visible inside the platform. A gate engine (canonical gates plus composite scoring), a capability-coverage matrix UI, and a Console for inspecting how scores are produced let a customer see the derivation rather than trust a number.

Authorable: the bridge beyond a fixed formula

An Overlay SDK and a working layer (REST plus MCP tools, with dry-run) let a business author its own methodology, metrics, and risk models in its own language: custom frameworks, gates, and verdicts, without forking or code changes. A custom-framework authoring wizard builds and scores a firm's own top-level framework. The platform is teachable to a customer's worldview.

Method transparency boundary: the methodology is transparent to paying customers inside the product and authorable. Testify does not open-source or publicly publish the scoring internals.

Failure patterns you can extend

Failure patterns are methodology content too. Testify ships a versioned pack (for example “Backups run nightly, restores never tested”), and a firm can add its own patterns or customize a shipped one in the working layer. Each pattern shows its origin (shipped, vendor or firm) and its pack version, and pack updates never overwrite a firm's edits. Patterns inform a case; they don't recommend, rank or decide.

Why this is the brand

You cannot sell "prove it, don't claim it" and run a black box. Transparency of method, to the people paying for and using the platform, is consistent with the brand and is itself part of the product.

Frequently asked questions

Is Testify's maturity score a black box?

No. The methodology is transparent to customers inside the platform (a gate engine, a capability-coverage matrix, and a Console let you inspect how a score is produced), and it is authorable via an Overlay SDK.

Can a customer change or extend the methodology?

Yes. An Overlay SDK and a working layer (REST plus MCP tools with dry-run) let a business define custom frameworks, gates, and verdicts and author its own methodology, metrics, and risk models, without forking or code changes.

Is the scoring method published publicly?

No. Method transparency is to paying customers inside the platform. Testify does not open-source or publicly publish the scoring internals.

See it on your portfolio

Testify is accepting early customers. Portfolio Directors and Operating Partners get priority access to a guided walkthrough.