Home
/Knowledge center /Insights /Why we publish our frameworks instead of keeping them behind a proposal
Why we publish our frameworks instead of keeping them behind a proposal
A short note on why a framework that only makes sense after you hire someone isn't actually a framework.
A methodology kept confidential until a client signs an engagement functions more as a sales device than a genuine framework — its value should be legible on its own terms, not contingent on secrecy.
Publishing the reasoning behind our recommendations doesn't reduce their value in an engagement; the value was never in the framework being secret, it was in applying it correctly to a specific organization's actual data.
Not sure this is the right fit yet?
Request an executive consultation and we'll tell you plainly what an honest diagnosis would find.
Request an executive consultation