MinistryWatch Covers a Publicly Traded Commercial Entity, Raising Grave Questions About the Structural Integrity of MinistryWatch Itself

The Institute for Ministry Watch Accountability has completed a preliminary review of MinistryWatch’s recent coverage of Gloo, the Boulder, Colorado-based Christian technology company currently navigating $438 million in accumulated losses, a post-IPO stock decline of approximately 58%, and a going-concern flag from the SEC. The article is, by conventional journalistic standards, competent. It is thorough. It contains numbers. And yet the Institute cannot, in good conscience, proceed without raising what we believe to be the single most consequential question embedded in this moment: MinistryWatch — a ministry accountability organization whose foundational mandate is the watchful oversight of ministries — has now trained its considerable institutional gaze upon a publicly traded commercial technology company answerable to the Securities and Exchange Commission. We do not make this observation lightly. We make it with the full weight of our directorial authority and a deep and abiding concern for the load-bearing walls of the accountability ecosystem.

The Jurisdictional Precipice

MinistryWatch exists, as its name plainly states, to watch ministries. It watches them. That is the arrangement. The organization has built its credibility, its donor base, and its entire reason for being on the premise that ministries require watching and that MinistryWatch is the appropriate entity to do that watching. Gloo, however, is not simply a ministry. Gloo is a company with ticker symbols, quarterly earnings calls, institutional investors, SEC filings, and a stock price that one may observe in real time on a financial terminal. The SEC is already watching Gloo. FINRA is, presumably, watching Gloo. Individual retail investors — some of them quite agitated — are watching Gloo. The question the Institute must now formally pose is this: who is watching MinistryWatch while MinistryWatch watches something that is already being watched by entities specifically chartered and legally empowered to watch it? The answer, we are prepared to state for the record, is us. It has always been us. But the situation has grown measurably more complex.

The Scope Creep Scenario: A Formal Assessment

The Institute does not use the phrase “scope creep” casually. We use it the way a structural engineer uses the phrase “load-bearing wall” — with gravity, with precision, and with the implicit understanding that removing it without proper analysis could bring down the entire ceiling. If MinistryWatch covers Gloo today — a company with $41.5 million in Q1 revenue, 25 nonprofit contracts exceeding $1 million annually, and Pat Gelsinger of Intel serving as executive chair — what does MinistryWatch cover tomorrow? Salesforce, if it sells to enough churches? Amazon Web Services, if a sufficient number of pastors store their sermon notes in the cloud? The Institute is not predicting these outcomes. We are observing that no formal boundary has been articulated, and that the absence of a formal boundary is itself a condition requiring formal observation. We have observed it. We are continuing to observe it. We will report our ongoing observations in future bulletins.

What MinistryWatch Got Right, and Why That Is Not the Point

In fairness to MinistryWatch — and the Institute is nothing if not scrupulously fair — the article in question is substantive. It accurately reports Gloo’s financial distress. It contextualizes the stock decline. It presents leadership’s optimism alongside analyst skepticism with admirable evenhandedness. The Institute awards partial credit. However, the Institute must also note that producing accurate, thorough, balanced accountability journalism about an entity that may or may not fall within one’s organizational mandate is not the same as resolving the question of whether one should be producing it. MinistryWatch has answered the journalistic question — is Gloo’s situation newsworthy? — without first answering the foundational institutional question — is Gloo’s situation MinistryWatch-worthy? These are not the same question. The Institute has drafted a seventeen-page framework distinguishing them. It is available upon request.

Conclusion and Formal Recommendation

The Institute for Ministry Watch Accountability issues the following formal recommendation: MinistryWatch should be considered Concerned But Functional at this time. Its coverage of Gloo demonstrates continued journalistic capability while simultaneously introducing an unresolved tension at the level of institutional identity. We are not panicking. We wish to be clear that we are not panicking. We are, however, escalating this matter to our Internal Subcommittee on Watching Organizations That Watch Things That Are Also Being Watched, which convenes quarterly or whenever circumstances compel an emergency session. Circumstances, at this time, are compelling an emergency session. We will report our findings. Someone must.

The Institute for Ministry Watch Accountability remains committed to watching MinistryWatch watch Gloo, for as long as Gloo remains watchable, and for a reasonable period thereafter. — P. Vigilance-Howell, Director of Redundant Oversight