Why we turn buyers away
A product built to produce discomfort has to be willing to refuse the customer who wants to look better rather than be better. Here is the qualification we run before we sell anyone anything — and why the discomfort is the point.
Most companies treat a lost deal as a failure to be fixed. We built one where some of the deals we lose are the product working exactly as designed. That sounds like a line. It is not. It is the single most important decision we made, and everything else about Frank follows from it.
Frank exists to tell you the truth about your posture — whether the controls you claim are actually holding, whether the evidence still stands, whether the state you certified is the state you are in today. That truth is frequently uncomfortable. It has to be, because the comfortable version is the one already on sale everywhere, and the comfortable version is what keeps getting organisations breached with a valid certificate on the wall. A tool built to produce discomfort cannot also promise comfort to whoever is holding the budget. So we do not. And when it becomes clear that comfort is what a buyer actually wants, we say no.
We sell the finding, not the feeling
Be precise about what most GRC tooling sells, because the category has become very good at disguising it. It sells the feeling of being covered. A green dashboard, a readiness score, a progress bar that fills toward a certificate — these are instruments for converting effort into reassurance. They are bought by people who need to walk into a meeting and say the programme is healthy, and they are worth the money precisely because they will say that on demand.
Frank sells the opposite thing. It sells the finding — the exception nobody re-read, the control your own incidents contradict, the assumption that quietly stopped being true. The finding does not fill a progress bar. Some weeks it does the reverse. If your success is measured by how good the board deck looks on Thursday, we are the wrong purchase, and an honest sales process should surface that before the invoice, not after.
The buyer we cannot serve
There are two people who might sign our contract, and they want opposite things from it.
One of them bears the consequence when the posture turns out to be wrong — the person who has to sit in the room after the incident and answer for what was signed. That person wants to know the truth early, while it is still cheap to act on, even when the truth is unwelcome. We can serve them completely.
The other one owns the appearance of the posture and is measured on keeping it green. For that person a finding is not information, it is a problem — a thing that now exists in writing, with a date and an owner, that someone might ask about. What they need from a tool is that it not produce findings like ours, or that it let them be curated away before anyone accountable sees them. We cannot serve that, and more to the point we will not, because the instant we build the setting that makes discomfort optional we have rebuilt the thing we exist to replace.
A tool that lets you make the finding go away is not an assurance tool. It is a tool for manufacturing the confidence it was supposed to test.
Most of turning buyers away is telling these two people apart early, and declining the second one plainly rather than selling them a version of Frank that would betray the first.
The discomfort is the signal
Here is the part that sounds like arrogance and is not. When Frank makes you uncomfortable, that is not a defect we are working to sand off in the next release. It is the reading on the instrument. Discomfort is what accurate information about an overstated posture feels like from the inside. If we removed it, we would not have made your organisation safer — we would only have removed your ability to tell.
This is why we will not add the features that would make the discomfort optional. No override that credits a control your evidence does not support. No setting that ages a finding out of view before it is resolved. No mode that lets you present a posture you cannot currently stand behind. Each of those would sell well. Each of them is a request we have already refused, on principle, in the architecture — not at the point of sale where it is easy to cave.
What saying no looks like
In practice it is undramatic. It is a qualifying conversation that ends with us saying Frank is not for you, and meaning it. It is a demo where the honest thing to say is that we will show you contradictions you may not want to circulate, and watching whether that lands as relief or as threat. It is a refusal to promise a clean report by a date, because the report is clean when your evidence is, and not before.
We are aware of how this reads against a market that will tell any buyer what they want to hear. We have decided that the buyers we lose to that market are, on the whole, the ones we were always going to disappoint — and that a smaller set of the right customers, who wanted to be defensible rather than merely certified, is the only foundation an assurance product can honestly be built on. A vendor who will sell an uncomfortable truth to one buyer and let the next buyer quietly switch it off is not in the truth business at all. It is selling whatever the room wants, and has only priced the discomfort as an optional extra.
Who this is for
If a tool that occasionally makes your posture look worse than the dashboard does sounds like a threat, we are genuinely not the right choice, and we would rather you knew that now. If it sounds like the thing you have quietly wanted — a straight answer you can act on while it is still early, and stand behind when someone asks — then we should talk, and the fastest way to find out is to point Frank at your own scope and read what it says.
You can do that without us reassuring you first. Start with obligation visibility — it will not score you, certify you, or tell you that you are fine. It will tell you what your evidence actually does, which is the only thing we ever meant to sell.